Punch Lists · NOC Signatures
Capture the punch list at substantial completion, get the customer to e-sign it, and finish the job knowing exactly what closes it out. No more end-of-project scope creep — every signed punch list carries a legally binding electronic signature with SHA-256 hashes, signer IP capture, and an append-only audit trail.
Documents e-signed through NOC Signatures are enforceable under the federal E-SIGN Act and state UETA. Every signed punch list carries the signer's drawn signature, printed name, title, timestamp, and IP address for non-repudiation, plus SHA-256 hashes of the original and signed PDFs for tamper-evidence. Free for all signed-in NOC Signatures users while in beta.
A punch list (sometimes 'snag list') is the itemized list of small fixes, touch-ups, and incomplete details remaining at substantial completion. Once they're done, the contract is complete. Locking the list in writing — and getting it signed — protects against the customer adding 'one more thing' indefinitely.
Walk the project with the customer at substantial completion. List every defect, deficiency, or unfinished detail they identify, plus anything you already know needs touch-up. Send it for e-signature that same day so the list is closed.
Once a signed punch list exists, anything added later is a change order — not a punch list item. Issue a Change Order for the new scope. That's exactly the workflow this app is designed around.
Yes, under E-SIGN and state UETA. The customer's IP, user-agent, and timestamp are captured at signing, and the document carries SHA-256 hashes for tamper-evidence — the same audit trail as the Notice of Commencement.
This page is general information about punch lists and electronic signatures — not legal advice. Consult a licensed construction attorney for questions about your specific project or state.