Winning the contract is the part you celebrate. The work starts the next morning, with a signed agreement, a start date the client has already told their GM about, and a property you have walked through twice at most.
Valet site onboarding is everything between those two points. Done well, the first shift looks like your five hundredth. Done badly, week one is runners guessing where to park, keys in a pile, and a client wondering whether they picked the right operator.
This is for valet service providers who run valet at other people's properties. Hotels, restaurants, hospitals, malls, event venues. The client is watching your first week and forming an opinion that lasts the whole contract.
Can you launch a new valet client location in 48 hours?
Yes, but only when the physical and staffing work is already done or genuinely small. The software side of standing up a new site takes under an hour at a desk. Everything else sets the real timeline, and no platform compresses it.
What takes minutes or hours: creating the location record, mapping parking and pickup zones, defining the key board layout, setting rates and payment methods, inviting staff, and configuring what valets must capture at check-in.
What takes days and cannot be shortened by software: the site walk, hiring or transferring runners, client-side access such as garage credentials, badges, gate remotes and radio channels, insurance certificates naming the property, and the client's own internal approvals on rates and signage.
So the answer is conditional. A single surface lot with one drop-off, a crew you already employ and have badged, and rates the client has signed off on? A 48-hour valet onboarding is realistic, and operators do it regularly. A hospital with three garages, a night shift, and a security office that issues badges on Tuesdays is not. Telling the client otherwise, then missing the date, costs more than quoting a week and hitting it.
What has to be true before the first car arrives
Five things: you have walked the property, your zones match what a runner can actually see, the key board exists physically and in the software, rates and payment methods are set, and your staff can sign in on a device that has synced.
Miss one and the first shift becomes improvisation.
Walk the property with the person who will run it
The site walk is the highest-value hour of the onboarding, and it should include the manager who will work the site, not just whoever negotiated the contract.
What to collect while you are there:
- Real capacity per area, counted, not the number in the RFP
- Where a full-size SUV will not fit, and where the ceiling gets low
- Walking time from the stand to the farthest space, timed once at normal pace
- Every entrance and exit a guest might use, including the one the client forgot to mention
- Where the key board can be mounted, and who else has access to that room
- Cell signal at the stand and on every garage level
- Peak patterns: check-out waves, restaurant seatings, surgery schedules, event load-in
That last one tells you how to staff. The rest goes straight into the system.
Map zones the way runners will actually park
A zone should match a boundary a runner can see without thinking. Level 2, North Lot, Rear Alley. If you have to explain a zone during training, it is drawn wrong.
Each parking zone carries a name, a capacity, a status, a color, and the walking distance and time you measured on the walk. You then switch on whatever describes it: covered, staff attended, security cameras, EV charging, gated access, permit required, or stacked parking with a depth if cars park one behind another. There is no fixed catalog of zone kinds, so you describe the space you have.
Pickup zones are separate, because the curb is a different constraint from the lot. Each has a name, a number of curb spaces, a maximum wait, and directions text valets and guests can both read.
Decide the key board before you decide anything else about keys
Keys are the biggest failure point at a new site, and the fix is boring: one physical board, one slot per key, a code on every slot, and the same codes in the software.
You can lay a board out as a grid with rows and columns, so slots read A1 through E10, as a numbered run from 1 upward, or as free form, where the valet types the label as they hang the key. Grid works when the board is mounted and permanent. Free form works when you inherited a pegboard and are not rebuilding it in week one.
Whatever you choose, label the physical board to match before the first shift. A slot code that exists only on a screen is a key nobody can find.
Set rates and payment methods before the first ticket
Rates are per location, and getting them wrong on day one creates a refund conversation with the client, not just the guest.
Set up the structure the contract specifies: hourly, daily, overnight, flat, event, or tiered brackets, with a daily cap and validity dates if the client runs seasonal pricing. Then set what the site accepts: cash, card, or charge to the front desk. Card payments run through your connected Stripe account and produce a digital receipt, which matters when the client's finance team asks how transactions reconcile.
Decide one more thing here: whether a ticket can be completed before payment is taken. A hotel charging to the room and a restaurant collecting at the curb want opposite answers.
Create staff accounts, assign them, and sync the devices
Staff access is location scoped, so a runner sees the site they are assigned to and nothing else. Roles are admin, manager, and valet, and every client's data stays isolated from every other client's.
The device check is the step operators skip. The app works offline, so a dead spot in the garage does not stop check-ins and everything uploads once signal returns. But a device that has never signed in has nothing to work from. Have every phone sign in and finish a first sync on site the day before, not five minutes before the first car.
How do you configure a new location in the admin dashboard?
Through one wizard, in five steps, with nothing written until you press Create. Basics, parking zones, pickup zones, key areas, payments. If you abandon it halfway, you have not created a half-configured location.
The basics step holds identity, address, timezone, and contact details, plus your liability policy text and whether guests must accept it before their vehicle is released. Per-client policy wording lives here, usually at the request of the client's legal team.
After Create, the location's own page is where the site gets tuned:
- Check-in capture: which fields are required, optional, or hidden. Plate, make and model, color, photos, guest name, guest phone, rate. A hospital may require photos on every vehicle. A busy restaurant curb may not want a name slowing the handoff.
- Capture tools: AI vehicle recognition at check-in, which reads plate, make, model and color from a photo, plus the damage log and photo capture.
- Customer experience: whether guests can request their vehicle from the portal, cancel a request, pay online, and rate the experience.
- Features and notifications: the optional modules and the events that trigger messages.
- Staff and pricing: assignment and rates for this site specifically.
Per-location configuration is what lets your hospital contract and your steakhouse contract run differently on the same account. If you add sites regularly, the patterns in multi-location valet management matter more than any single setup.