Keep each vehicle distinct
Give every vehicle its own visit and job reference, including staggered arrivals from a fleet customer.
For wrap shops
Every panel considered. Every visit organized.
From wash and disassembly to install and reassembly, a wrap moves through several hands. GuestLot gives the team one place to keep the vehicle’s condition, location context, and handoffs.
One visit per vehicle, a job reference that survives a staggered fleet drop-off, and a record the reassembly shift can read.
A clearer visit, from the start
- 1
Open a visit per vehicle
Six cars from one fleet customer are six visits, six condition records and six job references — not one line item.
- 2
Record before disassembly
Existing marks under the trim you are about to remove are the ones nobody can re-photograph later.
- 3
Carry context to reassembly
Notes added during install stay on the same visit, so the shift that puts the car back together reads what the shift that took it apart saw.
- 4
Hand back per vehicle
Retain each visit and choose, car by car, whether the fleet contact receives a private report.
The work behind the visit
A week of careful work deserves continuity.
Document prep and reassembly
Record existing marks and relevant condition notes as the work progresses. The next shift can find the same information.
Prepare useful fleet paperwork
Review the record at collection and choose whether to share an owner report with the appropriate customer contact.
Choosing software
Is this a vinyl wrap installation management platform?
Not in the sense most people mean by that phrase. GuestLot does not manage the install — no quoting by square foot, no material tracking, no bay scheduling, no design proofs. What it manages is the customer vehicle while it sits with you: one visit per car with its own condition record and job reference, staff key handoffs, available authorized Tesla readings with observation times, and a private report per vehicle. For a shop wrapping a six-car fleet across a week, that is the part a general shop system usually handles worst.
What GuestLot does not do for you
GuestLot records the vehicle’s stay. It does not run the rest of the shop, and these stay with the systems you already use:
- Square-foot quoting, material usage and scheduling — your shop management platform.
- Design proofs and print files — your design and print workflow.
- Fleet billing and purchase orders — your accounting system.
If a visit record is not the gap you have, the honest answer is that GuestLot is not the tool to buy.
Respect the vehicle. Support the team.
Settings are a choice. Records are a habit.
A physical key card and a Tesla app authorization are separate controls. Log card handoffs, return the card at collection, and review any shop keys or app permissions separately. A closed GuestLot visit does not remotely erase them.
Read the relevant guidance: Tesla Model Y keys.
Your shop can change these. They are review thresholds and agreed settings, not remote controls: GuestLot does not set Guest Mode, Valet Mode, or driving permissions on the car, and a boundary only detects an eligible arrival — it does not grant or restrict driving access.
Fleet wrap work records fine without a Tesla connection
Per-vehicle condition records, job references, disassembly notes, key card handoffs and collection details are all shop-entered. Without owner authorization, Tesla location and vehicle readings are unavailable, and those fields read “not recorded” rather than filling in a guess.
The record is yours to share
Keep the shop record for later questions, and preview a private owner report before enabling its link. Documentation can support an insurance review; it does not determine coverage or a claim outcome.
Questions
Built around wrap shops
Does a six-car fleet create six visits?
Yes. Each vehicle has its own condition record and visit history. GuestLot’s subscription remains $179 per location per month, with no per-vehicle charge.
Who authorizes a fleet vehicle?
Use the person or business account authorized to grant access for that Tesla. A driver dropping it off may not control the account; confirm this before connection.
Can we prove which of our installers had a given fleet car’s key card?
You can prove what your team recorded. The handoff log holds the staff entries your people made. A Tesla NFC key card produces no usage audit trail of its own and cannot be remotely wiped, so the card log is your record — the card itself is not a tracker.
When we finish a fleet job, is the customer’s access closed out?
GuestLot closes each visit and discards its stored Tesla connection tokens. That is a local closeout, not a verified key removal: paired phone keys, shop keys and Tesla app permissions must be reviewed on each vehicle and in the owner’s Tesla account separately.
Keep reading
Six cars in. Six records out.
Keep every vehicle in a fleet job distinct, from the marks under the trim to the report the fleet contact receives.