Back to all articlesMobile team operations

Transfer an Unfinished Field Job Between Mobile Workers

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A replacement worker can know the job name and still not know where to begin. Materials may be split between a vehicle and the site. A completed step may not have been checked. The customer may have agreed to a change that never reached the job record.

Transfer an unfinished field job by recording its current physical state, the exact stopping point, untouched work, outstanding dependencies, and the receiving worker's own confirmation. Do not treat sending the record as proof that the next worker can continue. Keep the transfer open until the receiver has compared the record with the site and identified any gaps.

The checklist below is designed for continuity on the same task. It does not replace technical work instructions, site procedures, or specialist safety guidance.

1. Transfer the state of the work, not just its status

A status such as “in progress” is useful for a schedule but weak as a handoff. It does not distinguish work that is complete from work that was started, put aside, or never touched. A completion percentage has the same problem: it compresses several different conditions into one number.

A useful handoff answers five questions:

  • What is physically present? Identify the work area, materials, loose items, packaging, and relevant site conditions.
  • What has been done? Name completed steps and record whether their required checks were performed.
  • What remains unchanged? Explicitly identify untouched work so the receiver does not infer progress.
  • What prevents continuation? Name missing materials, decisions, access, or information, with a person responsible for resolving each dependency.
  • What has the receiver confirmed? Separate reading the record from checking the actual site.

The goal is not a long departure report. It is a reliable boundary between what the next worker can establish independently and what still needs direct clarification.

2. Capture the stopping point before the outgoing worker leaves

The outgoing worker should write the handoff while the physical state is still available to inspect. Reconstructing it later from memory creates avoidable ambiguity, particularly when components look similar or materials have been moved.

Start with the job reference and precise work area. Then describe the last completed step and the step interrupted. Use concrete nouns and locations rather than “that part,” “over there,” or “nearly finished.” Distinguish completed and checked, completed but unchecked, partially complete, and not started.

Record the time the state was observed. If the site changes afterward, add a dated update rather than silently replacing the earlier account. This matters when another worker, the customer, or a delivery changes what the receiver will find.

Photos can support the record where workplace and customer rules permit them. Each useful image needs a written purpose: what it shows and which checklist item it supports. A close-up without a location can be harder to interpret than a short description. Do not let an image stand in for a missing explanation of whether the work is complete.

If the outgoing worker cannot verify something, record it as unknown. An explicit uncertainty is actionable; an empty field invites an assumption.

3. Filled hypothetical worker-to-worker handoff checklist

Fictional worked example: The following names, job reference, times, quantities, and circumstances are hypothetical. A mobile worker is transferring an unfinished storage-label installation at a customer site. The checklist records continuity information, not installation instructions.

Job identity and transfer record

  • Job: HYP-214 — replace shelf-location labels in the customer’s stockroom.
  • Exact work area: Rear stockroom, shelving bays A through D. Office cupboards are outside this job.
  • Outgoing worker: Mara.
  • Receiving worker: Eli.
  • State recorded: Tuesday, 13:40, immediately before Mara leaves.
  • Reason for transfer: Mara’s scheduled visit ends before the remaining materials arrive.
  • Current transfer state: Awaiting receiving worker’s on-site confirmation; not yet accepted for continuation.

Completed steps and checks

  • Completed and checked: Old labels removed and replacement labels applied in bays A and B. Mara compared the installed labels against the current job list.
  • Completed but unchecked: Replacement labels applied to the upper row of bay C. Comparison against the job list has not been performed.
  • Partially complete: Lower row of bay C has old labels removed but no replacement labels applied.
  • Last completed action: Applied the final upper-row label in bay C.
  • Stopping point: Before checking bay C or starting its lower-row replacements.

Untouched work and scope boundaries

  • Not started: Bay D remains in its original condition.
  • Not started: Final whole-job comparison and customer walkthrough.
  • Scope question: Customer asked whether the office cupboards could also be relabelled. No decision or authorisation is recorded. Do not treat the request as added scope.

Physical site condition and item locations

  • Work area at departure: Stock remains on the shelves. Loose backing paper has been collected. A label pack and the job list are together on the designated stockroom worktable.
  • Materials on site: One sealed replacement pack for bay D, marked HYP-214, is on that worktable.
  • Outstanding materials: Bay C lower-row replacement pack is not on site. The delivery coordinator reported dispatch, but receipt has not been confirmed.
  • Removed items: Old labels from bays A, B, and the lower row of C are in the marked waste bag beside the worktable, pending the site’s normal disposal process.
  • Access condition: Stockroom access was available when Mara left. Customer contact must confirm access for Eli’s arrival.
  • Supporting record: Permitted overview photo attached to the job record, captioned “Departure state: bays A–D and designated worktable.” It does not establish that individual labels are correct.

Outstanding dependencies and ownership

  • Missing pack: Delivery coordinator to confirm the location of the bay C pack and report an updated arrival expectation. No delivery time is confirmed.
  • Access: Job coordinator to confirm that the customer contact can admit Eli.
  • Scope request: Job coordinator to resolve the office-cupboard request separately. Existing stockroom work remains the recorded scope.
  • Clarification route: Eli to contact Mara about discrepancies in the departure record; contact the job coordinator if Mara is unavailable or the issue changes scope.

Receiving worker’s confirmation

  • Record read: Eli, Tuesday, 14:10. Read receipt only; site not yet checked.
  • On-site comparison: Eli, Tuesday, 14:35. Bays A and B, the upper row of C, and untouched bay D match the described state. Bay C upper-row checks remain outstanding.
  • Materials comparison: Bay D pack is present. Bay C pack is still absent. The printed job list is not on the worktable.
  • Gap raised: Eli asked Mara where the job list was placed. Mara confirmed it had been handed to the customer contact after the departure photo.
  • Gap resolution: Eli recovered the list from the customer contact and checked that it matched the current job record.
  • Acceptance: Accepted for continuation on the verified scope. Bay C lower-row work remains blocked by the missing pack. No acceptance of additional cupboard work.
  • Next recorded action: Complete the outstanding comparison for bay C’s upper row before treating that section as checked. Coordinator retains ownership of the missing-pack follow-up.

4. Make receiving confirmation a separate step

The receiving worker should not simply repeat the outgoing worker’s statements. Their task is to compare the description with what is present, then record agreement, discrepancies, and limits.

Use distinct transfer states such as prepared, read, site checked, and accepted for continuation. These are recommended operating labels, not claims about a particular application. They prevent a message receipt from becoming an accidental declaration that the job is ready.

Acceptance can be limited. In the fictional checklist, Eli can accept the verified scope while keeping one section blocked by missing materials. That is more informative than either accepting the entire job without qualification or marking everything blocked.

However, limited acceptance only works when the unresolved dependency does not undermine the work being continued. If a missing decision could change completed or planned work, clarify it first. The receiver should not guess that two portions are independent.

Keep the outgoing worker’s account intact and add the receiver’s observation alongside it. If the accounts disagree, that disagreement is useful evidence of a gap, not something to erase for a tidier record.

5. Resolve gaps without turning guesses into instructions

When something does not match, pause the affected part of the task and ask a question tied to the discrepancy. “Where is the current job list?” is easier to resolve than “Can you explain the job?” Include the item, the recorded claim, and what the receiver actually found.

Common failure cases need different responses:

  • Outgoing worker unavailable: Refer the specific gap to the job coordinator. Keep the affected work unresolved until an authorised person or reliable record establishes the state.
  • Material marked delivered but absent: Record “not located at site,” not “available.” Assign someone to establish where it is.
  • Customer gives a different account: Record the difference and seek clarification. Do not silently replace the job scope with the latest verbal request.
  • Photo conflicts with the site: Check the photo’s time and location. Record the current observation and investigate the intervening change.
  • Work looks finished but checks are missing: Keep it classified as unchecked until the applicable checks are completed.

If there is no worker overlap, arrange a reachable clarification contact and record any limits on availability. A voice conversation may resolve ambiguity faster than messages, but its outcome still belongs in the shared handoff record. Otherwise, the next transfer inherits the same missing information.

6. Keep the checklist usable on a mobile screen

Put the stopping point, unresolved dependencies, and receiver confirmation near the top of the mobile view or summary. A worker should not have to read a long activity history to discover that the materials are missing.

Keep one authoritative handoff record with the job. Messages can alert the receiver or discuss a question, but copy the resolved outcome back into that record. Otherwise, continuity depends on finding the right conversation and knowing which statement supersedes which.

Use short, visibly labelled fields. Allow “unknown,” “not started,” and “not applicable” where appropriate rather than forcing a confident answer. Require a useful explanation for an unresolved item, not a filler response just to complete a form.

There is a trade-off between detail and completion effort. Use brief entries for clear, completed work and more detail at uncertain boundaries: partial progress, unverified checks, moved materials, and changed requests. Avoid requesting the same information in both a narrative box and several structured fields.

If connectivity is unreliable, establish how the receiver will recognise the latest available record. An offline note is not a shared update until it reaches the agreed record. Do not assume that saving locally means the other worker can see it.

7. Test the handoff by measuring clarification, not form completion

For the next suitable transfer, use the five core categories from this checklist and require the receiving worker to record an on-site comparison before continuing. Assign a coordinator to close unresolved dependencies rather than leaving ownership with “the team.”

Review the transfer afterward using observable measures:

  • Which checklist fields needed clarification after arrival?
  • How long passed between the receiver’s site check and resolution of each blocking gap?
  • Did any work have to be repeated because the recorded state was wrong or incomplete?
  • Was each outstanding dependency attached to a named owner?
  • Did the receiver distinguish reading the record from confirming the site?

Use the findings to change the field that failed. If workers repeatedly cannot locate materials, strengthen the location entry. If completed work is repeatedly mistaken for checked work, separate those states more clearly. Adding more mandatory prose is not necessarily the answer.

The immediate next action is simple: take an upcoming worker transfer, fill the departure checklist, and ask the receiver to mark each item as matched, different, or not yet verified. The remaining differences become the clarification list—not hidden assumptions carried into the unfinished job.

Field operationsWorker handoffsMobile teamsJob continuity

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications