How do I stop work getting lost during a job handover?

Create one controlled handover record from the accepted quote, customer messages and job schedule, then require a named person to approve missing or conflicting details before the crew starts. Automate the gathering and routing. Keep scope, price, safety and customer decisions human.

That is the short answer. The useful version is a job-start workflow that gives the delivery team one current record, makes gaps visible and stops exceptions from quietly becoming site problems.

Why work disappears between sale and delivery

A handover often looks complete from each person's point of view. The estimator has an accepted quote. The office has a customer email. The supervisor has a calendar entry. The crew has an address. No one owns the complete, current version of the job.

The missing work appears when someone asks a simple question: which access note is current, who approved the extra item, what must be ready before arrival, or whether the customer changed the date. The team searches messages, calls the office or asks the owner. A paid crew can be ready while the business reconstructs decisions it has already made.

This is not primarily a communication problem. It is a workflow ownership problem. The handover has sources, but no controlled record, readiness rule or exception owner.

Define one controlled handover record

Start with the information needed to begin the job safely and commercially. For a building, renovation or field service business, that could include:

• accepted quote and approved scope
• customer and site contact details
• access, parking and arrival instructions
• job date, crew and expected duration
• required materials, equipment and dependencies
• relevant plans, photos and site notes
• approved variations or exclusions
• known safety, licence or compliance requirements

Do not make staff copy all of this into another long form. Define which existing source is authoritative for each field. The accepted quote should remain the source for approved commercial scope. Business.gov.au recommends that a quote clearly describes the work, costs and conditions and that accepted quotes are retained as records. The handover should carry that approved information forward, not recreate it from memory.

Give every field an owner and a last-updated time. If two sources disagree, show the conflict rather than silently choosing one.

Set a ready-to-start gate

A useful handover has a visible state: draft, needs review, ready to schedule, or ready to start. Define the minimum information for each state.

The gate should be strict about genuine blockers and light about everything else. A missing site address, unapproved scope change or unresolved safety question should stop the normal path. An optional internal note should not. The business decides those rules before automation is switched on.

Assign a named person to approve readiness. That might be the project manager, service coordinator or supervisor. The system can show evidence and surface gaps, but it should not declare an ambiguous job safe or commercially approved.

Automate gathering and routing

Once the record and gate are clear, automate the repeated movement around them. A practical workflow can:

1. start when a quote becomes accepted
2. gather approved details from the quoting, customer and scheduling systems
3. create the handover record with source links
4. flag missing, conflicting or out-of-date fields
5. assign each exception to its named owner
6. notify the supervisor when the record passes the human gate
7. retain a simple trail of what changed, when and by whom

The point is not a new dashboard. The point is that the right person receives a complete handover or a specific question, without the owner chasing every normal job.

Build the exception path first

Real jobs change. A customer sends a late message. A supplier slips. The crew finds something the quote could not show. Automation is useful only if the unusual path is clear.

When information is missing, the record should stay in needs review and identify the owner. When two sources conflict, the workflow should present both with their dates and links. When a change arrives after approval, it should reopen the relevant gate and alert the responsible person. It should never overwrite approved scope or imply customer agreement.

This is the same discipline needed when the scope changes and the price may need review. The system can prepare context. The responsible person makes the commercial and customer decision.

What remains under human judgement

Keep these decisions with accountable people:

• whether a scope change is accepted and how it is priced
• whether a job is safe, compliant and genuinely ready
• how to handle an unusual customer request or relationship issue
• whether a schedule change is commercially and operationally sensible
• whether personal information is necessary and who may access it

For businesses covered by the Privacy Act, the Office of the Australian Information Commissioner says reasonable steps must protect personal information from misuse, loss and unauthorised access. Even where the Act does not apply, the operational principle is sound: include only what the crew needs, restrict access and remove records under a defined retention rule.

Test the workflow on recent jobs

Take three completed handovers: one normal, one with missing information and one with a late change. Run each through the proposed record and gate. Ask the estimator, coordinator and supervisor whether the sources are clear, whether blockers are useful and whether the exception reaches the right person.

Measure practical outcomes, not vanity activity. Did the crew receive the right information? Were unresolved decisions visible before arrival? Did the owner avoid a routine chase without losing control of an important decision?

If the answer is yes, expand carefully. If not, fix the record, rules or ownership before connecting more systems. A narrow workflow that survives real exceptions is a better first automation than a large system that only handles the ideal path.

Bring one handover, not a software wishlist

Bring one recent job handover to a $0 on-site automation review. Run Lighter can visit a suitable Sydney service business, follow the accepted job into delivery and identify the first useful improvement.

You can also see how clear status updates reduce avoidable follow-up when the same source-owned approach continues after work begins. Book an on-site automation review when you want to map the real workflow before choosing technology.