# Job Handover (/docs/form-guides/building/national/national-job-handover)



A job handover records what was completed, which practical handover steps were done, and what remains outstanding. Fill it after the walkthrough, before the final job file is closed. The tradie signs the record. Customer name, date, and signature are optional.

This is a Tradie Forms designed customer record, not a government form or compliance certificate. Keep any required certificates, commissioning records, warranties, contract notices, and invoices as separate documents.

<RelatedForm slug="national-service-report">
  Recording a maintenance or service visit with findings and recommendations rather than a completed job handover? Use
</RelatedForm>

<Callout type="warn" className="docs-callout-warn my-4">
  This handover does not replace a compliance certificate, commissioning record, practical completion notice, or contract document the job still requires.
</Callout>

<span id="before-you-start" />

## Before you start [#before-you-start]

Have the final scope and loose ends in front of you before the walkthrough.

<GatherList>
  <Gather title="The completed scope">
    The quote, work order, approved variations, and a plain description of what was actually completed.
  </Gather>

  <Gather title="Customer and site details">
    The person receiving the handover and the address where the work was done.
  </Gather>

  <Gather title="Handover documents">
    Manuals, warranties, compliance certificates, commissioning records, and care instructions being provided separately.
  </Gather>

  <Gather title="Outstanding items">
    Each unfinished or third-party item, who owns it, and a realistic target date.
  </Gather>

  <Gather title="Who can accept the work">
    The homeowner, customer, agent, builder, or site representative available for the walkthrough.
  </Gather>
</GatherList>

<span id="business" />

## Business [#business]

Your business details and the job reference the customer will recognise.

<Fields>
  <Field name="Business Logo (Shown top right on the downloaded handover)" type="Photo" requirement="optional">
    Upload your business logo if you want it on the finished PDF.
  </Field>

  <Field name="Business Name" type="Text" requirement="required">
    Your trading name as it appears on the quote or invoice.
  </Field>

  <Field name="Contact Name" type="Text" requirement="optional">
    The person the customer should contact about the handover or outstanding work.
  </Field>

  <Field name="Phone" type="Tel" requirement="optional">
    The contact number for follow-up.
  </Field>

  <Field name="Licence Number" type="Text" requirement="optional">
    A licence, registration, or competency number when it belongs on the customer record.
  </Field>

  <Field name="Email" type="Email" requirement="optional">
    The address the customer should use for handover questions.
  </Field>

  <Field name="Job Reference" type="Text" requirement="optional">
    The work order, purchase order, or internal job number used on the quote and invoice.
  </Field>
</Fields>

<SavedDetail name="Business" reuse="next job handover" />

<span id="customer" />

## Customer [#customer]

Who receives the handover and where the work was completed.

<Fields>
  <Field name="Customer Name" type="Text" requirement="required">
    The homeowner, client, agent, builder, or site representative the PDF is for.
  </Field>

  <Field name="Phone" type="Tel" requirement="optional">
    A contact number for the handover and outstanding items.
  </Field>

  <Field name="Email" type="Email" requirement="optional">
    The address the final PDF, warranties, or follow-up can be sent to.
  </Field>

  <Field name="Street address" type="Address" requirement="optional">
    Search the Australian address where the work was completed. Confirm it against the work order before moving on.
  </Field>

  <Field name="State" type="Address" requirement="optional">
    Filled by address search. Confirm it when entering the address by hand.
  </Field>

  <Field name="Postcode" type="Address" requirement="optional">
    Filled by address search. Check it against the job record when typing manually.
  </Field>
</Fields>

<span id="job" />

## Job [#job]

Describe the completed work in plain language and set the completion date.

<Fields>
  <Field name="Description of Works" type="Textarea" requirement="required">
    Summarise what was completed, including the main rooms, systems, or stages. Keep pricing and invoice amounts out of this field.

    <WorkedExample good="Completed bathroom renovation plumbing, including new shower, vanity, toilet, floor waste, and hot and cold water connections." bad="Bathroom done" />
  </Field>

  <Field name="Date Started" type="Date" requirement="optional">
    The first day of the job or defined stage when it helps explain the handover period.
  </Field>

  <Field name="Date Completed" type="Date" requirement="required">
    The day the described work reached handover. Future dates are blocked.
  </Field>
</Fields>

<span id="completionChecklist" />

## Completion Checklist [#completion-checklist]

Answer every item **Yes** or **N/A**. Use N/A only when the item genuinely does not apply to this job. Add an item note when the answer needs context.

<Fields>
  <Field name="Completion Checklist" type="ChecklistItems" requirement="optional">
    The six checks cover quoted work, cleaning, the walkthrough, operation or demonstration, manuals or certificates, and the follow-up or warranty process. Unfinished work belongs in **Outstanding Items**, not under an inaccurate Yes.
  </Field>
</Fields>

<span id="outstanding" />

## Outstanding Items [#outstanding-items]

Leave this empty for a clean handover. Otherwise add one row per loose end. Long lists continue onto extra pages in the PDF.

<Fields>
  <Field name="Outstanding Items" type="TableRows" requirement="optional">
    **Item** says what remains. **Who Resolves** is Us, Customer, or Third party. **By When** is a clear target such as `Fri 14 Aug`. Every row needs the item and owner before it counts.
  </Field>
</Fields>

<span id="acceptance" />

## Acceptance [#acceptance]

The tradie signs the handover. Customer acceptance is optional, so the PDF can still be completed when the customer will sign later.

<Fields>
  <Field name="Tradie Name" type="Text" requirement="required">
    The person signing for the business after checking the scope, checklist, and outstanding items.
  </Field>

  <Field name="Date" type="Date" requirement="required">
    The tradie sign-off date. Check it aligns with the completion date.
  </Field>

  <Field name="Tradie Signature" type="Signature" requirement="required">
    Draw, upload, or use your saved signature after the handover record is final.
  </Field>

  <Field name="Customer Name" type="Text" requirement="optional">
    The person accepting the work. Leave blank if they will sign later.
  </Field>

  <Field name="Customer Date" type="Date" requirement="optional">
    The day the customer accepted the handover.
  </Field>

  <Field name="Customer Signature" type="Signature" requirement="optional">
    Capture on the phone when the customer is ready, or leave blank and send the PDF for signing later.
  </Field>
</Fields>

## Common mistakes [#common-mistakes]

<Mistakes>
  <Mistake title="Copying the quote instead of describing completed work.">
    A quote can include options or work removed by variation. Write what was actually completed and keep the quote and variations beside the handover.
  </Mistake>

  <Mistake title="Marking every checklist item Yes automatically.">
    Walk through the site and documents. Use N/A when an item does not apply, and put unfinished work in the outstanding list.
  </Mistake>

  <Mistake title="Writing one vague outstanding item.">
    `Finish bits` has no owner or target. Name the item, who resolves it, and when it is expected.
  </Mistake>

  <Mistake title="Using customer acceptance as a compliance certificate.">
    A signature does not replace testing, certification, commissioning, or regulator paperwork required for the work.
  </Mistake>

  <Mistake title="Adding invoice amounts to the handover.">
    Keep money in the quote, contract, variations, and invoice. This PDF records the work and acceptance.
  </Mistake>
</Mistakes>

<span id="before-download" />

## Before download [#before-download]

<Checklist>
  <Check>
    Business, customer, site, and job reference match the final job file
  </Check>

  <Check>
    Description of Works matches the completed scope and approved variations
  </Check>

  <Check>
    Every completion check is answered Yes or N/A
  </Check>

  <Check>
    Outstanding items have a clear owner and target date where known
  </Check>

  <Check>
    Required certificates, manuals, and warranties are prepared separately
  </Check>

  <Check>
    Tradie name, date, and signature are complete
  </Check>

  <Check>
    Customer details and signature are included only when the customer is ready to accept
  </Check>
</Checklist>

<span id="after-download" />

## After download [#after-download]

Give the customer a copy and keep one with the quote, variations, compliance or commissioning records, warranties, photos, and invoice.

* **Name the file by customer and date.** `Job Handover - Jordan Lee - 2026-08-02.pdf` is easy to find later.
* **Track every loose end.** Carry outstanding items into the booking or job system so the handover list does not become a dead end.
* **Send the missing documents.** Provide manuals, warranties, and certificates named during the walkthrough.
* **Keep customer acceptance optional.** If they sign later, retain the final signed copy with the original handover trail.

## Related guides [#related-guides]

<Cards className="docs-cards docs-cards-cols-2 my-6">
  <Card title="Service Report" href="/docs/form-guides/building/national/national-service-report">
    Record a maintenance or service visit, findings, recommendations, parts, and optional customer sign-off.
  </Card>

  <Card title="PDF downloads" href="/docs/features/pdf-export">
    Preview, download, regenerate, and send finished PDFs.
  </Card>
</Cards>