Sign Off Incomplete vs Return vs Partial Bill Decision Tree

Why this matters

A job is mostly done but not fully done. A part is on backorder, a customer decision is pending, an inspection has not happened, or one item could not be completed today. You face a closeout decision: call it complete and sign off, schedule a return to finish, or bill for what was finished and carry the rest. Pick wrong and you either misrepresent a job as complete (a warranty and liability trap), strand revenue you have already earned, or leave a customer feeling nickel-and-dimed. The right path depends on why the job is incomplete and whether what remains is functional, safe, and clearly defined.

The danger is the polite shortcut: a tech signs a near-complete job as "done" to avoid an awkward return conversation. That single decision can void the basis for warranty, hide an open item from the next tech, and create a dispute when the unfinished part surfaces. A clean process names the remaining work and routes the money honestly.

The situation

At the end of a visit, the work is partially complete. The tech and dispatcher decide how to close: mark complete, schedule a finish-return, or partial-bill and leave the balance open. The decision must reflect reality so that documentation, billing, and warranty all rest on accurate facts.

Quick checks

Before deciding, confirm three things:

• Is the system safe and functional in its current state? A job left non-functional or hazardous cannot be signed off and may not be safe to leave at all.
• Is the remaining work clearly defined and agreed? Vague "we'll finish later" is not a closeout; a named punch list is.
• Why is it incomplete? Backorder, customer decision pending, inspection gating, ran out of time, or discovered extra scope. The reason drives the branch.

Decision tree

Start: Is the system safe and functional as left?

• No, it is unsafe or non-functional. Do not sign off. Either complete enough to make it safe and functional, or if you cannot, treat it as a stop/return and ensure the site is left safe (utilities off as needed, area secured). Bill only for completed, deliverable work; schedule the return. Never sign a non-functional job as complete.

• Yes, safe and functional. Go to: Is the remaining work part of the original quoted scope?

  • No, the remainder is newly discovered additional scope the customer has not authorized. Sign off the original scope as complete (it is). Document the additional finding as a separate recommendation/quote. Bill the completed original scope in full. The new work becomes its own job once authorized; it does not hold the original job open.

  • Yes, the remainder is part of the original scope. Go to: Why is the original scope incomplete?

    • Backordered or unavailable part. Do not sign off as complete. Schedule a return for when the part lands. Decide billing: if the completed portion is a discrete, usable deliverable, a partial bill for that portion is fair, with the balance billed at completion. If the job is one integrated deliverable that is not usable until finished, hold billing to completion or bill a progress draw per your contract. Document the open item and the expected return.

    • Inspection or third-party gating (permit sign-off, another trade). Schedule the return tied to the gating event. The work you did is complete but cannot be certified done until the gate clears. Bill per your contract's progress terms; do not certify final completion until the inspection passes. Track the gate so the return is not forgotten.

    • Customer decision pending (they need to choose, approve, or be present). Leave functional, schedule the return, and put the ball in the customer's court in writing. Bill the completed portion if discrete. Note that the open item is waiting on the customer, so a later "why isn't it done" has a clear answer.

    • Ran out of time / scheduling overrun. Schedule the return. This is an operations issue, not a customer fault; absorb the return-trip cost as your own unless your terms say otherwise. Bill the completed portion only if it is a clean deliverable; otherwise complete on the return and bill whole.

Confirming the right close

Whatever branch you land on, verify before leaving:

• The customer understands and agrees to the closeout status (complete, return scheduled, or partial-billed).
• A return, if needed, has a date or a trigger, not just a promise.
• The billing matches the deliverable: you are not billing as "complete" something that has a known open item, and you are not eating revenue on work that is genuinely finished and usable.
• The open item is recorded on the job so the next tech and the next invoice both see it.

Remediation: making the close clean

• Write the punch list as specific named items, not "minor items remaining."
• For partial bills, state plainly what is billed now and what is billed at completion, and get acknowledgment.
• Tie any retainage or progress draw to your written contract terms; do not improvise payment timing.
• Schedule the return before you leave; an unscheduled "we'll call you" return is the one that slips.
• Update warranty start: warranty on an item generally starts when that item is genuinely complete, not when the partial close happened.

References

• Uniform Commercial Code Article 2, ss 2-307 (delivery in single vs several lots) and 2-601 to 2-608 (acceptance, rejection, and cure of non-conforming or incomplete performance).
• AIA Document G702/G703 (Application and Certificate for Payment / Continuation Sheet) as the standard model for progress billing and percent-complete certification.
• ConsensusDocs and AIA A201 General Conditions on substantial completion, punch lists, and final completion as distinct milestones.
• State home-improvement contractor statutes governing progress payments, final-payment triggers, and what may be billed before completion.