Document Header
Project name, contract number, version or draft date, and a unique identifier for traceability across document controls and the project filing system.
A properly prepared CM BOH Draft reduces ambiguity, preserves an audit trail of project decisions, and helps align contract expectations. It supports compliance with procurement rules and minimizes downstream disputes by documenting authority, dates, and rationale in a standardized format.
Use the draft as a controlled document for internal approvals, and move to a finalized change order or directive only after required sign-offs and any necessary notarization or countersignature steps.
The Contract Manager typically has day-to-day authority to prepare the draft, coordinate attachments, and obtain internal approvals. They must ensure the draft references the controlling contract, includes justification for changes, and lists impacted schedule and cost items in clear line-item format.
An executive or authorized officer provides final sign-off where contract thresholds require higher-level approval. That signer confirms authority to bind the company and accepts the legal and financial consequences described in the draft.
Project name, contract number, version or draft date, and a unique identifier for traceability across document controls and the project filing system.
Full legal names of owner, CM, contractors, and any third parties plus role definitions and the individual responsible for execution and notices.
Clear description of the proposed change or BOH action, including the technical rationale, scope additions or deletions, and reference to original contract clauses.
Explicit effect on the project timeline: affected milestones, new durations, and any required resequencing or acceleration measures.
Line-item cost estimate or allowance, source of funds, contingency implications, and whether cost approval is pending or included.
Required approval chain, signature blocks with printed names and titles, and any witness/notary requirements or conditional e-sign steps.
| Field | Configuration |
|---|---|
| Signer Order | Sequential routing with locking after each signature |
| Authentication | Email + SMS code for external parties |
| Attachments | Required supporting files must be uploaded before signing |
| Retention Flag | Auto-archive on final approval |
Ensure the selected platform provides audit trails, role-based access, and export options to meet compliance and recordkeeping needs.
Typically within 2–5 business days after request
Allow 3–7 business days for stakeholder review
Varies; expedited routing can reduce to 24–48 hours
Add 1–3 business days depending on availability
Archive immediately after the final signature and distribution
Document prepared and version stamped for circulation.
Procurement, legal, and technical teams provide comments.
Authorized signers execute the document; record retained.
Store final signed version and archive prior drafts.
The operations team used a standard draft to consolidate contract changes and approvals
Field managers completed BOH drafts on mobile devices during site visits
| 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 free 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 | No cap | No cap | No cap |