Cannot access the customer's property? A no-access visit workflow

The short answer

If the team reaches the right property during the agreed window but cannot enter, record the attempted occurrence and the work left undone. Check the location and access instructions safely, contact the authorized access person, and choose whether to wait or release the technician under your own dispatch policy. Give the follow-up a named owner and due time. Confirm access and a new appointment with the customer before returning; an unanswered call or moved calendar entry is not confirmation.

A failed access attempt is an event, not proof that the customer caused it, that the service was performed, or that a fee is owed. This workflow begins before the work starts. A callback after completed service and an unfinished visit awaiting a part need different records.

Five decisions at the gate

1. Verify the visit context. Compare the job's site and scheduled arrival window with the actual location and clock, including the time zone. Read the approved access instructions without displaying codes or private details in a public log. If the location may be wrong, pause and ask dispatch to resolve it.
2. Try the authorized contacts. Call or message the designated person for access, then dispatch or the office if your process calls for it. Record the timestamp, channel and result of each attempt, including no answer. The person paying for or approving a job may be different from the person who can open the property.
3. Choose wait or release. Dispatch decides based on its policy, commitments and live workload. This guide sets no universal wait length. If conditions are unsafe, do not force entry or improvise; use your existing emergency response process where applicable.
4. Preserve the occurrence. Record arrival, departure, verified site, attempts, reason as unknown or confirmed, release decision and unperformed scope before changing the future schedule. Keep an identifiable link from this attempt to the next appointment. A photo is optional only if genuinely relevant and allowed; never collect locks, alarm codes, keys, people or unnecessary customer data as proof.
5. Rebook only after the access plan is ready. Name the follow-up owner and due time, confirm who will provide access and how, offer actual availability, then record an agreed slot and send a checked confirmation. If there is no agreement, the new slot remains pending.

Jobber's visit documentation treats a visit as a calendar occurrence within a job and describes completion when the work is finished. Completion can feed invoicing and reports, so do not mark unperformed service complete merely to clear a queue. Its rescheduling prompt can be skipped, applies to an individual visit rather than every recurring occurrence, and is unavailable for assessment and bulk moves; the old reminders are canceled when a visit is rescheduled. A changed schedule therefore does not prove a customer received or accepted a message. This is a general operating protocol, not a claim that Jobber offers a native "No access" status.

Copy the occurrence record

Use a job note, a controlled spreadsheet or paper. Keep the original attempt separate from the later booking decision. Real names, phone numbers and site instructions belong only in your authorized system; the example below is entirely fictional.

This is a working record, not an immutable audit trail. Jobber's notes guide says notes display their author and time, show an edited indicator after changes, and are internal by default; visit notes appear as job notes. Notes can also be edited or deleted. Keep the event and subsequent correction distinguishable, and check who can see or share attachments. An internal note is not automatically a customer notification.

A fictional attempt with no assigned blame

On 25 September, VISIT-1 is scheduled for 10:00 to 12:00 in Europe/Paris. The technician arrives at the correct site at 10:35 and finds a closed gate. The authorized access contact does not answer at 10:38; the office answers at 10:43 and releases the technician at 10:50 under its own policy. Those times illustrate a record, not recommended waiting intervals. The reason for the closed gate remains unknown. The technician records no performed work, and the office owns a follow-up to establish who can provide access. A second visit has not been accepted, so it has no confirmed time.

Only after the access person and customer agree on a practicable plan does the office offer a real slot, link the new visit to VISIT-1 and verify the notification was sent to the right person. Any question about billing for an attempted visit is reviewed separately against the actual agreement and business policy. The operational record alone creates no automatic charge, fault finding or customer acknowledgment.

Three neutral messages to adapt

Replace brackets with verified details and send manually. These are original drafts, not real customer quotations or delivery outcomes.

While on site

Hello [name], our team is at [agreed site] for the visit scheduled in [window], but we cannot access the work area. Could the person responsible for access contact [office or technician channel]? We will update you when dispatch decides the next step.

After departure

Hello [name], we were unable to access [site] during today's scheduled visit and have now left. The work has not been performed. Please tell [follow-up owner] who can arrange access and when we may discuss a new time. We will follow up by [date and time] if we have not heard back.

After a new slot is agreed

Hello [name], we have agreed to return on [date and window] to [site]. [Access person or agreed method] will provide access. Please confirm if anything in that plan changes before the visit. We will keep the earlier attempted visit in the job record.

Keep the next action visible

The follow-up is complete only when someone owns the access question, the customer has received a clear update, and any new time is accepted and recorded. Preserve the failed occurrence even after the schedule changes. If a solo operator needs only this small workflow, a paper card or spreadsheet is enough; no software purchase follows from one locked gate. See the solo operator path for broader admin decisions and the estimate checklist if a later visit needs a separately agreed scope. Neither changes the facts of this attempt.