WindoorERP Documentation 19.0

Install it

Hand over and get it signed

Why this step

A signature on site closes the job and starts the warranty clock.

What this does

Closes the job formally: every opening complete, every snag cleared, the customer's signature captured, and the Handover Pack issued — the PDF that lists each opening with its completed actions, photos and warranty end date.

Before you start

  • Every opening in the package must be fully installed — the handover refuses at "All items must be fully installed before handover (…/… done)."
  • Every snag must be out of the open states — Resolved is enough; New or In Progress blocks with "Resolve the N open snag(s) before handover."
  • On a project with job-level Site QC, the job inspection must have passed.

Steps

  1. 01
    Open the work package and confirm the quantity chip reads done-equals-total and the open-snag count is zero.
  2. 02
    Walk the site with the customer and check the units together.
  3. 03
    Record anything found as a snag on its opening, with a photograph — then fix and resolve it before signing.
  4. 04
    Capture the signature: the crew's portal handover screen has a signature pad and requires the signer's typed name; the customer can equally sign from their own portal tracker.
  5. 05
    The handover stamps the date, notifies the customer by email, and back-fills any warranty date still missing.
  6. 06
    Issue the Handover Pack from the job — it is the completion evidence the retention payment waits on.

Where the signature lives

The signature, the signer's name and the handover date are stored on the work package itself, and the signature image prints in the pack. The office's Complete Handover button records a handover without a signature — legitimate for a formally-accepted commercial job, but the pack's signature block will be empty, so prefer the portal paths whenever someone is on site.

What handover does not do

The warranty clock does not wait for the signature: it starts per opening when the last required action was ticked — handover only back-fills stragglers. And there is no satisfaction rating at handover; ratings belong to After-Sales service sign-off. What the signature buys is the agreed acceptance date — the anchor for the defect-liability argument two years later.

Snags

Record them against the opening, not the project. A snag on one unit is a callback for that unit, and the service history for that opening is what answers a warranty claim later. The handover gate only counts open snags — resolving on site, with a fix photo, is what unblocks the signature the same day.

Example

A tower handover finds two sashes needing adjustment. Recorded per opening, fixed and marked resolved with photos, the handover signs the same afternoon — and the office closes the two snags after verifying, with the whole trail attached to the right units.

Common mistakes

  • Handing over verbally. Without the recorded signature there is no agreed acceptance date — only an argument.
  • Recording snags on the project, so nobody knows which unit to return to.
  • Using the backend button out of convenience while the customer is standing on site with a finger ready to sign.
  • Expecting the pack to appear before the handover — the button shows after; printing earlier goes through the form's Print menu.

Checkpoint

The handover carries the customer's signature and any snags are logged against the job.