You arrive at a client’s building on time, only to find a locked side gate, a receptionist who has not been told you are coming, and the person who can authorize the work in a meeting. The calendar said “site visit,” but it did not say how to get from the curb to useful work.
This is a small operational failure with outsized costs. Mobile service providers, consultants, installers, photographers, trainers, cleaners, repair businesses, and account managers can lose hours to a visit that was technically scheduled but not practically arranged. The fix is an arrival brief: a compact record completed before each on-site appointment that answers the questions a calendar invitation usually misses.
It is not a lengthy client questionnaire or a new layer of bureaucracy. It is a repeatable check that turns “See you Tuesday at 10” into a workable arrival plan.
What an arrival brief does
An arrival brief is a single, scannable set of instructions for one visit. It records the conditions needed to begin work promptly: where to go, whom to contact, what has been approved, and what to do if the plan breaks down.
Keep it separate from a proposal, work order, or project notes. Those documents may explain the scope beautifully while leaving out the operational details that matter at 9:58 a.m. in an unfamiliar parking lot.
For a routine visit, the brief can be only a few lines. For a complex location, it may need a little more detail. The point is not completeness for its own sake; it is removing the specific uncertainty that would make the visit fail or start badly.
A booked time is not the same thing as usable access. Treat the first ten minutes of an on-site appointment as something to design, not something to hope will work out.
Use five fields that answer the practical questions
Build the brief in whatever system you already open before leaving: a job record, calendar note, shared document, or simple template. Put the important fields near the top, not buried among internal notes.
1. Purpose and finish line
Name the purpose in terms of an observable result. “Meet client” is vague. “Photograph the finished kitchen, including wide shots and detail images” gives the person traveling there a clear target.
Add what must be available for that result to happen. This might be a decision-maker, a cleared work area, an item to inspect, access to a utility room, or a staff group assembled for training. If a necessary condition is missing, it can be checked before the trip rather than discovered after it.
2. Arrival point and route
A street address is often insufficient. Record the entrance to use, suite or floor, reception instructions, loading access, and any useful landmark. If the location is large, distinguish between the customer’s mailing address and the place where work begins.
For businesses carrying equipment, the route matters as much as the destination. Note whether supplies can come through a main entrance, whether stairs are involved, and where a vehicle can reasonably pause for unloading. Do not assume a client knows what your setup requires; many will not think to mention it.
3. Day-of contact and escalation contact
List the person who will actually answer a call or message near the appointment time. A contract signer or project lead may be the right relationship contact but the wrong person to call from the lobby.
When useful, include a second contact who can grant access or make a decision if the first person is unavailable. Label their roles. A name without a role forces your team to guess whom to call first.
4. Access, environment, and constraints
Capture conditions that affect whether your work can begin: visitor check-in, keys or codes held by the client, a required escort, a quiet period, restricted rooms, pets, fragile surfaces, available power, or a need to work around customers.
Phrase this as operational information, not an intimidating demand list. “Please have the storage room unlocked by 9:45” is more useful and easier to act on than “Client responsible for access.”
Do not collect more personal or sensitive information than your team truly needs. A brief should help someone arrive and work, not become a miscellaneous repository of client details.
5. The fallback plan
This is the field that prevents an awkward, expensive stalemate. Decide in advance what happens if access is not available, the right person is absent, or the needed item is not on site.
A fallback can be simple: wait ten minutes, call the day-of contact, then switch to an off-site task and reschedule the physical work. The appropriate sequence depends on your business and the appointment, but writing it down keeps an employee from improvising a promise or waiting indefinitely.
Confirm the uncertain parts, not every obvious fact
An arrival brief works best when it is built around uncertainty. Reconfirming an address that has not changed may add little. Confirming whether the building manager will admit a subcontractor may save the entire appointment.
Use a short pre-visit message when the job has meaningful access requirements. It should make it easy for the client to correct something, rather than asking a broad question that receives a vague “Looks good.”
For example:
“For Thursday’s 10 a.m. equipment check, Jordan will arrive at the service entrance off the rear lot and call Mia at arrival. Please confirm the utility room will be unlocked and that there is an escort available for the restricted area. If access is delayed, Jordan will complete the exterior check first and we will arrange a return time for the interior work.”
This message does three things: it exposes assumptions, gives the client a chance to prepare, and makes the alternate plan visible before there is any pressure.
Choose a trigger that makes the habit reliable
The most common mistake is making the arrival brief a good intention. If it is completed only when someone remembers, it will disappear during busy weeks—the exact weeks when preventable misses hurt most.
Attach it to a repeatable moment in your workflow:
- When an appointment moves from tentative to confirmed, create the basic brief.
- One business day before the visit, check any details likely to change.
- Before departure, the person traveling reviews the brief and confirms they have the right materials.
Not every field needs to be retyped each time. Reuse stable location instructions, then make the appointment-specific elements conspicuous: today’s contact, purpose, access condition, and fallback. Reused information should be reviewed, however. An old door code or former contact can create false confidence.
Make the brief usable by someone other than its creator
If only the owner can interpret a note such as “usual setup, ask Sam,” the system does not protect the business. Write as if a capable teammate who has never visited the site will be responsible for the appointment.
That means replacing shorthand with clear directions and separating confirmed information from assumptions. A lightweight format can look like this:
- Job: Annual photo update; capture reception and three completed rooms.
- Arrive: 9:45 a.m. at the west entrance; check in at reception.
- Day-of contact: Mia, office manager; will meet photographer at reception.
- Needed to start: Rooms cleared by 10 a.m.; lights on; staff member available to move signs.
- Bring: Interior lighting kit and step stool.
- If delayed: Call Mia; photograph exterior first; do not enter treatment rooms without escort.
The exact wording is not important. What matters is that the record enables sound action without a scavenger hunt through texts, emails, and memory.
Match the detail to the cost of failure
A two-minute delivery to a familiar office may require only an address and receiving contact. A half-day installation at a secure facility deserves a fuller brief. Avoid imposing the most elaborate version on every appointment; people stop maintaining systems that feel disproportionate.
Consider three practical factors:
- Travel cost: Long drives, booked vehicles, or multiple staff members raise the cost of a failed arrival.
- Access complexity: Multi-tenant buildings, controlled areas, loading requirements, and unfamiliar sites need more specificity.
- Irreplaceable time: A photographer working with a limited-weather shoot or a trainer booked around a whole team has less ability to improvise later.
High-stakes visits may also benefit from a brief internal check: Is the scope still the scope? Is the necessary client representative aware of the appointment? Is there a known reason the work cannot begin? This is not a substitute for a client agreement; it is a last opportunity to catch an operational gap.
Common ways the system goes wrong
Putting everything in the calendar title
Calendar titles become unreadable, and important instructions get truncated or overlooked. Keep the calendar useful for time and location at a glance, then link or attach the brief where your team already works.
Confusing a contact with an authorization
Someone may be friendly, available, and unable to approve extra work, admit you to a room, or decide a scope question. Record what the day-of contact can actually do. This reduces pressure on employees to negotiate decisions on the spot.
Using vague fallbacks
“Figure it out” is not a contingency plan. A useful fallback names a next action, a time boundary, and a limit. For instance, “After one call and ten minutes, leave the equipment in the vehicle and complete the remote checklist” is actionable.
Failing to update after a near-miss
When an appointment begins badly, do not merely blame a client or employee. Ask which missing line in the brief would have made the problem visible earlier. Add that prompt to the template if the issue is likely to recur. A repeated surprise is usually a process field waiting to be named.
A realistic example: turning a wasted trip into a controlled exception
Imagine a small IT support firm scheduled to replace a device at a client’s second office. The original calendar entry has only the street address and a manager’s email. The technician arrives to learn that the device is in a locked server closet, the manager works at the main office, and building security requires a registered visitor.
With an arrival brief, the appointment would have identified the service entrance, the on-site office coordinator, the visitor registration requirement, and the person authorized to unlock the closet. If any of those were unconfirmed the day before, the firm could have moved the appointment before dispatching the technician.
Even if the client failed to prepare, the fallback would guide the response: document the blocked access, contact the designated person, use the time for approved non-site work if available, and reschedule the physical replacement. The business has not eliminated every disruption, but it has replaced confusion with a consistent response.
Start with the next appointment that involves travel
Do not redesign your whole booking system this week. Open the next on-site appointment and add five lines: purpose, arrival point, day-of contact, condition needed to start, and fallback. If you cannot fill one in, that is useful information to resolve now.
After the visit, spend two minutes asking whether the brief contained what the person arriving actually needed. Keep the fields that prevented friction, remove fields nobody used, and let the template earn its place in your operations.