Approval operations · Small contractors
One request. One current decision. One released version.
Run customer approvals through the same lightweight gates every time, so scope, price, authority, signatures, field instructions, changes, invoices, and evidence stay connected without a full CRM.
The operating principle
Status should describe the next action, not a vague feeling.
“Sent,” “customer thinking,” and “probably approved” are not enough to run the field. Use a small controlled status set: intake, drafting, internal review, awaiting customer, needs revision, approved-not-released, released, completed, declined, superseded, and archived.
Every approval should have one owner, one project ID, one document type, one current revision, one customer decision, and one next action. Configure the gates for the contract, trade, jurisdiction, project amount, notices, cancellation rights, and existing business process.
Eight approval gates
Move from request to retained record without losing authority.
- 01
Capture the request
Record customer, property, requester, authority, need, location, urgency, photos, source conversation, desired outcome, and deadline. Assign a project and request ID.
- 02
Choose the document and pricing mode
Select estimate, contract, work authorization, change order, selection, access, emergency, unit, T&M, or NTE record. Apply the required underlying terms, notices, and signatures.
- 03
Draft the complete decision
State baseline, scope, additions/deletions, materials, price, payment, schedule, assumptions, exclusions, stop point, attachments, and what approval authorizes.
- 04
Run internal review
Check identity, authority, arithmetic, tax/markup basis, availability, lead time, crew capacity, permits, safety, attachments, current revision, and legal/project requirements.
- 05
Send one identifiable version
Give the authorized customer a clear subject, document ID/revision, short decision summary, complete record, attachments, genuine deadline, contact path, and retainable copy.
- 06
Resolve the customer decision
Track viewed or delivered only as evidence, not approval. Answer questions, record revision requests, supersede old drafts, verify signer, capture required signatures, and deliver the completed copy.
- 07
Release the exact work
Confirm every release condition, then update the field assignment, schedule, purchasing, budget, billing, and crew attachments. Approved-not-released and released are separate states.
- 08
Control changes, close, and archive
Route deviations through new approval, reconcile actuals, collect completion evidence, issue the invoice from approved authority, deliver closeout, and retain a searchable record chain.
Status board
Use states that force a next action.
Intake
Owner: estimator/office. Next: verify requester, site, need, authority, and missing facts.
Drafting
Owner: document creator. Next: complete scope, pricing, time, exclusions, and attachments.
Internal review
Owner: contractor/manager. Next: approve arithmetic, capacity, compliance, and release conditions.
Awaiting customer
Owner: named follow-up person. Next: answer questions or send the scheduled factual reminder.
Needs revision
Owner: document creator. Next: issue a new revision and mark the prior one superseded.
Approved, not released
Owner: operations. Next: satisfy payment, cancellation, permit, selection, procurement, or scheduling gates.
Released
Owner: crew lead. Next: perform only current approved scope and document deviations.
Completed / declined / superseded / archived
Owner: office. Next: invoice or close, deliver copies, retain evidence, and prevent accidental reuse.
One-page SOP
Small-contractor approval standard
Fill this once for the business, then apply it consistently by project type.
Run customer approvals with JobSign →- Scope and purpose
- [Jobs/trades/amounts covered; customer decisions controlled; exceptions and emergency escalation]
- Roles
- [Intake owner, estimator, reviewer, sender, follow-up owner, release authority, crew lead, billing, records custodian]
- Project and document IDs
- [Naming rule for customer/project, estimate, authorization, change, selection, work order, ticket, invoice]
- Document selector
- [Which request uses which form; required underlying agreement; pricing modes; local/state variants]
- Minimum drafting fields
- [Identity, baseline, scope, price/payment, time, assumptions/exclusions, attachments, authority, signatures, copy]
- Internal review gate
- [Arithmetic, rates, tax, availability, schedule, permits, safety, notices, authority, current revision, approval by]
- Send standard
- [Approved channel, subject format, document/revision, summary, attachments, deadline, contact, delivery record]
- Reminder cadence
- [First reminder ___; second ___; final status notice ___; escalation owner; no silence-as-approval]
- Revision control
- [Customer question vs. requested change; increment revision; preserve prior; superseded watermark/status; resend all attachments]
- Signature and completed-copy rule
- [Who signs, authority check, intent, timestamp, countersignature, consent where applicable, customer delivery]
- Release checklist
- [Approval complete, cancellation/notice, payment, permit, selection, access, procurement, schedule, crew current copy]
- Field change rule
- [Stop boundary, protect site, capture evidence, notify owner, price/limit, customer change approval, revised release]
- Completion and invoice link
- [Closeout evidence, actuals, customer communication, approved IDs on invoice, credits, payment milestone, remaining work]
- Retention and access
- [Project folder structure, file naming, signed PDFs, originals, delivery proof, backups, retention period, privacy/access]
Adapt this SOP to every applicable contract, licensing rule, notice, cancellation right, signature requirement, insurer process, trade standard, and jurisdiction. A workflow does not replace legal compliance.
Responsibility checklist
Every approval needs one accountable owner at each gate.
Owns proposal accuracy
Scope, quantities, products, pricing, assumptions, exclusions, lead time, options, and customer-facing clarity.
Owns release readiness
Arithmetic, commercial terms, availability, capacity, safety planning, permits, notices, signatures, and current version.
Owns the open decision
Delivery, questions, respectful reminders, revision requests, signer identity, and final decision status.
Owns field release
Only the executed current scope reaches schedule, crew, purchase order, work order, subcontractor, and site.
Owns the authorization boundary
Reviews source approval, performs current scope, captures evidence, stops at deviations, and reports status.
Owns billing and retention
Invoice ties to approvals and actuals; completed copies, attachments, delivery, closeout, and records stay retrievable.
Reminder system
Follow up without turning urgency into pressure.
Confirm delivery and invite questions
Identify the document/revision and the decision needed. Do not imply that opening the message equals agreement.
Restate genuine consequences
Explain real pricing validity, material lead time, schedule availability, safe-stop, or expiration without inventing scarcity.
Close the pending loop
State that work remains unapproved, the proposal expires or moves to inactive status as defined, and how to restart.
Escalate disputes or emergencies
Follow the contract and qualified guidance; do not automate threats, legal remedies, or emergency assumptions.
15-minute weekly audit
Clear the board before it becomes memory.
- 01
List every open approval by status and age
No document should be “somewhere with the customer.” Name its owner, revision, sent date, and next action.
- 02
Resolve version conflicts
Mark old drafts superseded, verify attachments, and ensure the customer and field have the same current record.
- 03
Check approved-not-released jobs
Identify the exact remaining gate: cancellation period, payment, selection, permit, parts, schedule, access, or internal review.
- 04
Check released work for undocumented change
Review crew notes, photos, T&M tickets, quantities, discoveries, and customer requests before billing or concealment.
- 05
Close completed and declined records
Deliver copies, issue invoice or credit, preserve closeout, assign follow-up, and archive under the retention rule.
Failure modes
Small teams need fewer states and firmer gates.
Three PDFs called “final”
Use stable IDs, revision numbers, one current status, and explicit supersession.
Approval from the easiest contact
Verify the contracting party and delegated decision authority before release.
Repeated “just checking in” messages
Use a defined cadence, exact decision, genuine deadline, and final inactive status.
Signature arrives; crew starts immediately
Separate approval from release and check permits, notices, cancellation, payment, access, materials, and schedule.
Field request lives only in chat
Capture the delta, cost, time, evidence, authority, and revised field release before expanded work.
Billing reconstructs the job afterward
Invoice from approved IDs, daily actuals, changes, credits, completion, and payment terms already in the record.
Research basis
The workflow joins contract completeness, delivery, change control, and retention.
California CSLB guidance illustrates customer-facing completeness: covered contracts and changes require detailed scope, price/payment, dates, notices, signatures, and completed copies. Oregon CCB identifies required contract terms, written-change practices, and proof-of-delivery retention for certain residential notices. These rules are jurisdiction-specific, but they show why an approval process needs compliance gates before field release.
Federal E-SIGN law supplies electronic-record principles: legal effect is not denied solely because a record is electronic, while required retained records must accurately reflect the information and remain accessible and reproducible. Caltrans project-record systems illustrate operational linking among authorized change IDs, daily extra-work records, bills, quantities, and payment to reduce duplicate or unsupported billing. Public-project procedures are illustrative, not small-contractor law.
- California CSLB: Contracting for Success ↗
- Oregon CCB: contracts, notices, and delivery proof ↗
- Oregon CCB: required-notice delivery chart ↗
- 15 U.S.C. § 7001: electronic records and retention ↗
- Caltrans: linked project, change, daily, and payment records ↗
Configure the workflow to the actual agreement, trade, project value, customer type, insurer or manager process, license, permits, notices, cancellation rights, privacy, signatures, and retention duties. Get qualified local advice for the business’s standard documents and SOP.
Customer approval workflow questions
What is a contractor approval workflow?
It is a repeatable process connecting request, document choice, drafting, review, customer decision, signatures, field release, changes, invoice, and retention.
Do I need a full CRM?
No. Stable IDs, clear statuses, one owner, one current revision, reminders, signed PDFs, and organized folders can support a disciplined small-team process.
When should work be released?
Only after every required agreement, notice, signature, cancellation, payment, permit, selection, access, and internal gate is satisfied.
How should reminders work?
Identify the record and decision, state genuine deadlines, invite questions, use a fixed cadence, and never treat silence as universal approval.
One focused approval system
From the way you describe the job to a signed field-ready record.
JobSign helps small contractors draft the approval, attach evidence, collect the customer decision, and share the completed PDF without adopting a full CRM.
Explore contractor approvals →