Subcontractor Job Handoff: Verify Acceptance and the Booked Visit

The short answer

Treat receipt, acceptance, booking, reported completion and your own review as separate states. Send one limited work packet, ask the selected contractor to accept that scope, and record the visit they can actually book. Acceptance of a ServiceM8 Network request does not establish a scheduled appointment. Do not promise the customer a window until the booking and communication responsibilities are checked.

This original coordination protocol starts after your business has independently selected a qualified contractor. It does not establish worker classification, licensing, insurance, customer authorization, tax treatment or technical safety. Resolve those matters separately before assigning work. No request, booking or service was tested for this guide.

Define the part you are handing over

Identify whether this is a Quote Request or a Work Order. A Quote Request asks for a quotation; accepting that request does not authorize performing the underlying work. Keep the quotation response separate from a later authorized work assignment.

Give the packet its own reference and version while keeping it linked to the originating job. Describe included work and exclusions in plain language. Review each file actually sent, rather than granting access to a full customer history because it is easier. Keep access codes, credentials and unrelated personal details out of the public worksheet and use your approved private process for necessary operational information.

ServiceM8's subcontracting guidance warns that a copied original description can be too broad for a partial handoff. It also says to agree customer communication and the contractor's invoice recipient. The sending business cannot create the Network Request's scheduled booking; the contractor does that after conversion. A requested window therefore needs a separate booking check.

The sending guide describes editable outgoing job and contact defaults without changing the original job card, a unique request reference that becomes the recipient's purchase-order reference, and task, photo, document and form requirements. Sent changes to In Progress after acceptance and conversion. Those statuses do not independently establish an appointment, service quality or customer agreement.

Keep acceptance and booking distinct

ServiceM8 Network's introduction says the sender needs an account and the Network add-on, while a recipient can use a browser without an account. Multiple requests can relate to one original job. Verify the intended business email and configured channel before sending; a separate account does not prove the packet contains only appropriate information.

The completion guide distinguishes recipient paths. In Online Dashboard, acceptance involves conversion and a decline is communicated by emailing the requester. A browser recipient without an account can use Accept Job to notify the sender, then mark requirements before Completed. Do not apply the Dashboard conversion requirement universally to that browser path.

One person should own the customer update and another contact may own physical access. Record both roles when different. If acceptance arrives but the requested morning is unavailable, keep booking unresolved and ask for a real available window. Do not silently treat the original request as a customer promise.

Copy the one-job handoff ledger

This blank record is an editorial aid, not a native automated workflow, immutable audit trail or legal contract. Keep it in an authorized workspace. A paper sheet or spreadsheet can work if the references and owners stay clear.

The invoice recipient field is a routing check, not a decision about rates, tax or payment entitlement. Agree it through your existing business process. Likewise, evidence received records what arrived; do not fill missing photographs or measurements with assumptions just to close the row.

Three fictional handoffs

These are untested examples. The outcome fields are deliberately blank, and the packet contents are proposed rather than observed.

Three unsent message drafts

Adapt these placeholders to the agreed scope and approved channel. They are original drafts, not customer correspondence or product-generated notifications.

Request

Please review [reference/version] for [included scope]. We request [window/time zone]. Confirm acceptance separately from the window you can book. [Owner] handles customer communication. This packet excludes [excluded work]. Send questions or additional-work requests through [channel] before proceeding.

Accepted, with booking still pending

We have recorded your acceptance of [reference/version]. The visit is not yet confirmed. Please send the actual booking window and coordinator by [real deadline], so [owner] can check the customer update.

Return for review

The listed work for [reference/version] is reported complete. Evidence received: [specific files]. Open items: [items]. [Owner] will review the return. This report does not close the originating job or authorize payment.

If an external crew uses a user seat instead

A user seat is a different access route, not a native Jobber acceptance workflow. Jobber's permissions documentation separates own-schedule, client, pricing and notes access, with plan and administrator limits. View all notes can expose notes beyond other accessed areas. An authorized administrator must check the actual access scope; no permission audit was performed here.

Keep the same business ledger even if tools differ. After the return, match the files to the packet version, preserve reported exceptions and decide the originating job's next action through your own review. Neither a contractor's checkbox nor an accepted request settles unrelated remaining work.

The ServiceM8 review covers broader product fit. Use the scope-change workflow if additional work is requested. An agreed visit that later runs late belongs in the arrival-window update workflow; a crew that arrives but cannot enter belongs in the no-access visit record. Those events should not be folded into acceptance or marked as completed service.