Parties
Full legal names and entity types for GC, subcontractor, owner, and any surety; include addresses and registration numbers where relevant.
A well-prepared GC Signed Document reduces payment disputes, clarifies responsibilities, and provides enforceable proof of approvals and change orders. When executed correctly—electronically or on paper—the record can be legally binding under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws.
Several project stakeholders create, review, or sign GC Signed Documents during a build; roles vary by project size and procurement model.
The signing party must have authority to bind the contracting entity; lack of authority is a common cause of later disputes.
A company officer or designated project manager typically signs on behalf of the GC. The signer should be listed in corporate records as having authority, and the document should record job title and capacity to avoid later challenges to authority.
An owner or owner representative signs acceptance and payment authorizations. Include company name, signer name, title, and contact details to link the signature to an authorized decision-maker.
Full legal names and entity types for GC, subcontractor, owner, and any surety; include addresses and registration numbers where relevant.
Concise, measurable description of work, referenced exhibits or plans, and a cross-reference to the controlling contract and purchase order numbers.
Contract price, milestone or progress-payment schedule, retainage rate, and invoicing instructions with payment timelines.
Method for pricing changes, approvals required, and impact on schedule; numbered change-order records reduce later disputes.
Exact waiver scope (conditional vs unconditional), payment reference, and dates; tie waivers to the specific invoice or payment.
Printed name, title, entity, signature, and date; specify signer capacity and add notary or witness lines if required by law or contract.
| Field | Configuration |
|---|---|
| Authentication | Email + SMS code or stronger KBA for high-value approvals |
| Notifications | Auto-reminders at 3, 7, and 14 days until signature |
| Bulk Send | Use for routine lien waivers or identical change orders |
| Integrations | Link to PM/ERP (Procore, NetSuite, Box) for archive |
Choose a platform that supports secure signatures, audit trails, and the file formats your team uses.
Ensure the platform provides tamper-evident storage, exportable audit trails, and compliance options (BAA, 21 CFR Part 11) where your project or client requires them.
Often net 30 days from invoice or certification date.
Commonly 7–14 calendar days for approval or rejection.
Tied to receipt and clearance of payment.
State-specific—often 90–180 days after last work.
Retain for at least statutory minimums (see Retention section).
Create the document, attach exhibits, and reference contract IDs.
Obtain project manager and legal sign-offs before sending.
Complete signatures; notarize or witness if required.
Send to stakeholders and store in secure repository.
A mid-size developer digitized change-order approvals to accelerate closeout.
A small contracting firm standardized lien-waiver forms and signature blocks.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |