Business Risk Cue
A gap in the startup packet that increases financial, legal, or operational exposure if mobilization proceeds anyway.
Project 13
Build, verify, and formally approve one complete job startup packet for a signed, approved residential project — confirming legal authorization, payment conditions, licenses, insurance, permits, selections, procurement, subcontractors, schedule, site readiness, customer expectations, and financial setup — before any mobilization to the jobsite is authorized.
These cues appear at the point of work. They identify legal, payment, licensing, permit, safety, and documentation conditions that must be resolved before a project is authorized to mobilize.
A gap in the startup packet that increases financial, legal, or operational exposure if mobilization proceeds anyway.
A condition that must stop mobilization until it is corrected or confirmed by an authorized party.
Practical controls that keep the startup packet accurate as conditions change before the first workday.
Permit, inspection, and license-status requirements vary by project and jurisdiction. Verify current status before mobilization.
A point where counsel, the CPA, the insurance broker, or the licensing authority must confirm a condition before mobilization.
A confirmation, date, or decision that must be written into the startup packet and retained in the project file.
This project produces one written, approved Job Startup Packet for a single signed and accepted residential project. The finished work product is a controlled packet that verifies the contract and required notices, deposit or payment conditions, license and insurance status, permits and approvals, final scope and selections, procurement and subcontractor readiness, staffing and equipment, site logistics, customer communication setup, billing setup, and a signed mobilization authorization.
You will confirm the correct legal entity and parties on the agreement, verify payment and financing conditions have been lawfully satisfied, confirm license, insurance, bond, and permit-holder status remain active, confirm the final scope and pending selections, confirm procurement and subcontractor readiness, confirm staffing and site logistics, conduct an internal startup meeting and, where appropriate, a customer preconstruction meeting, and obtain formal mobilization approval from an authorized manager.
This project sits directly downstream of the accepted proposal (Chapter 8), the contract-ready scope of work (Chapter 9), and the change-order and allowance system (Chapter 10), and it depends on active licensing (Chapter 3), insurance and bonding (Chapter 4), and banking and accounting (Chapter 5) already being in place. No project may mobilize on the strength of this chapter's packet alone if any of those upstream systems are incomplete.
This project converts an accepted contract into an authorized field mobilization. It draws on the accepted proposal and pricing worksheet (Chapters 7–8), the contract-ready scope of work (Chapter 9), the change-order and allowance system (Chapter 10), the customer intake and site-visit file (Chapter 11), and the sales pipeline handoff (Chapter 12). It also depends on active licensing (Chapter 3), current insurance and bonds (Chapter 4), and functioning banking and accounting controls (Chapter 5), and it references the Book 24 estimate, Book 25 permit and compliance file, and Book 26 project-management plan rather than creating disconnected duplicate systems.
The completed startup packet becomes the reference document for Chapter 14's customer-communication process during construction, and it is the first entry in the project record that Chapter 18's job-cost review and Chapter 19's closeout will later reconcile against.
This project covers:
This project does not authorize the learner to:
Any condition that cannot be verified through the approved contract, licenses, insurance file, permits, or company records must be resolved before mobilization is authorized.
Establish these references before assembling the packet, and do not change their meaning mid-document.
| Term | Definition |
|---|---|
| Job Startup Packet | The single controlling document produced by this chapter that verifies legal, payment, licensing, permit, scope, procurement, staffing, and site conditions before mobilization |
| Mobilization | The point at which company personnel, subcontractors, materials, or equipment are first dispatched to the jobsite to begin the contracted work |
| Startup date | The confirmed calendar date on which mobilization is authorized to occur, distinct from any earlier target or estimated date |
| Critical condition | A legal, payment, permit, insurance, design, safety, or procurement item that must be resolved before mobilization is authorized |
| Pending selection | A customer or material decision required by the scope of work that has not yet been finalized, priced, or approved |
| Long-lead item | A material, product, or fabricated component whose order-to-delivery time affects the schedule and must be committed before mobilization |
| Startup meeting | The internal meeting among sales, estimating, operations, accounting, safety, and field leadership that reviews the completed packet before approval |
| Mobilization approval | The signed, dated authorization from a designated manager confirming the packet is complete and the project may begin |
Before the packet is assembled, record the following directly on the Job Startup Packet template:
Project name/number: ______ Customer(s): ______ Property address: ______
Contract execution date: ____________ Target startup date: ____________ Packet owner/manager: ____________
Every approved project passes through the same four checkpoints before mobilization: is the project legally authorized to proceed, is the company currently licensed, insured, and permitted to perform it, is the scope and procurement chain actually ready, and has the customer and jobsite been prepared to receive the crew. Confirming these checkpoints in writing, before dispatch, keeps the job-start decision auditable and keeps field personnel from absorbing risk that belongs to sales, accounting, or licensing.
A condition is only marked complete on the packet after it is confirmed against a primary source — the signed contract, the deposit receipt, the active license record, the current certificate of insurance, the issued permit, or the subcontractor's own current document. A condition is never marked complete on the basis of a verbal assurance, a screenshot without verification, or an assumption that a prior project's status still applies.
When a condition on the startup packet is marked confirmed, record what was checked, the source document, the date checked, and who checked it. Do not simply check a box. The source record protects the business if a license lapses, a policy is cancelled, or a deposit is later disputed.
Do not schedule or authorize mobilization while any critical legal, payment, permit, insurance, design, safety, or procurement condition remains unresolved on the packet. A packet that is mostly complete is not an authorized packet.
Maintain a single controlled copy of the Job Startup Packet in the project file established under Chapter 2 records. Do not allow separate, informal startup notes to circulate among sales, estimating, and field personnel. Every later reference in Chapters 14, 18, and 19 points to this single approved copy.
Deposit, financing, escrow, and cancellation or commencement conditions must be confirmed using the counsel-approved procedure established when the contract templates were reviewed in Chapters 8 and 9. Do not rely on an informal payment confirmation to satisfy a statutory waiting period or right of cancellation.
PC-073 – PC-078
Project Startup / Compliance Verification
Quantity: one approved Job Startup Packet per contracted project, including a completed contact and authority directory, a current document index, a first-day job-start checklist, and a signed, dated mobilization approval.
| Document | Quantity | Format | Content Required | Preparation / Purpose |
|---|---|---|---|---|
| Job Startup Packet | 1 | Bound or digital file, multi-section | Legal, payment, license, insurance, permit, scope, selection, procurement, staffing, and site sections | The single controlling record verified before mobilization |
| Project Contact and Authority Directory | 1 | One-page directory | Customer, decision authority, field leadership, accounting, and emergency contacts | Used by field and office staff throughout construction |
| Current Document Index and Field-Issue Set | 1 | Index plus issued documents | Current plans, specifications, selections, permits, and change orders | Prevents field use of superseded documents |
| Site-Start Checklist | 1 | Checklist | First-day sequence for access, protection, utilities, and safety setup | Used by the field lead on mobilization day |
| Check | Standard |
|---|---|
| Legal and payment verification | Correct entity and parties confirmed on the agreement; signature, delivery, notice, and payment conditions confirmed against the counsel-approved procedure, not a screenshot or verbal assurance |
| Authority verification | License, registration, insurance, bond, and permit-holder status confirmed active as of the packet date and sourced from the Chapter 3 and Chapter 4 records |
| Scope and selections | Final scope, allowances, and approved changes are reconciled with Chapter 9 and Chapter 10 records; every pending selection has a named responsible party and decision date |
| Procurement and subcontractors | Long-lead items are on order with confirmed delivery dates; subcontractor agreements, licenses, insurance, and startup documents are on file |
| Site and customer readiness | Access, protection, occupied-home rules, and communication channel are confirmed and recorded before the startup date |
| Approval | The startup meeting has occurred, all critical conditions are resolved, and a designated manager has signed and dated the mobilization approval |
Inspect the completed startup packet using the same checks regardless of project size or trade.
Complete the Job Startup Approval Worksheet in the Inspection Checklist section below before mobilization is scheduled.
Probable cause: scheduling relied on a customer's verbal statement or a payment screenshot rather than a verified bank or escrow record.
Confirmation: compare the scheduled startup date against the Chapter 5 bank or escrow confirmation date for this project.
Correction: pause mobilization, verify the payment through the accounting system, and reschedule only after confirmation is on file.
Reinspection: repeat the payment-verification check on the corrected packet before rescheduling.
Probable cause: the permit status field on the packet was marked complete from an application date rather than an issuance date.
Confirmation: check the permit authority's current record against the Book 25 permit file for this project.
Correction: stop the permitted portion of the work, correct the packet to reflect actual issuance status, and hold mobilization for that scope until the permit is issued.
Reinspection: repeat the authority-verification check before rescheduling the permitted work.
Probable cause: the pending-selections list did not assign a responsible party and decision date, or the deadline passed without escalation.
Confirmation: compare the current selection status against the decision date recorded in Section F.
Correction: escalate the outstanding selection to the customer through the Chapter 14 communication process and adjust the schedule; do not substitute an unapproved product.
Reinspection: repeat the selections check before confirming the next mobilization date.
Probable cause: the subcontractor's certificate expired between qualification under Chapter 16 and this project's startup date, and the packet was not re-checked before mobilization.
Confirmation: compare the certificate expiration date against the packet's approval date.
Correction: remove the subcontractor from the site until a current certificate is obtained and verified.
Reinspection: repeat the subcontractor-readiness check before allowing site access.
Probable cause: the current document index was not updated after a Chapter 10 approved change, or superseded documents were not removed from the field set.
Confirmation: compare the field-issued documents against the current document index and the Chapter 10 approved-change log.
Correction: reissue the current document set, collect and destroy or clearly mark superseded copies, and confirm the field team acknowledges the update.
Reinspection: repeat the scope and selections check on the corrected document set.
Probable cause: scheduling pressure led a manager to sign the mobilization approval before sales, estimating, operations, accounting, safety, and field leadership reviewed the packet together.
Confirmation: check the packet for a recorded startup meeting date and attendee list.
Correction: suspend mobilization, convene the startup meeting, resolve any items it surfaces, and obtain a new, dated mobilization approval.
Reinspection: repeat the approval check before mobilization proceeds.
This project ends with the approved packet filed for reuse throughout construction, not left as informal notes.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PC-073 | Confirms the correct entity, parties, signature, delivery, and notice conditions on the agreement before startup activity begins | |||
| PC-074 | Confirms deposit or payment terms are satisfied against a verified accounting or escrow record before mobilization is scheduled | |||
| PC-075 | Collects and confirms all required customer and material selections, with a responsible party and date for every pending item | |||
| PC-076 | Confirms schedule, procurement, and subcontractor readiness against the startup date using current source documents | |||
| PC-077 | Organizes permits, licenses, insurance, and required project documents into one controlled, current packet | |||
| PC-078 | Produces a job-start checklist and obtains a signed, dated mobilization approval only after every critical condition is resolved |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Item | Standard | Complete (Y/N) | Notes / Correction |
|---|---|---|---|
| Legal entity and signed agreement | Verified per Section E | ||
| Cancellation/commencement conditions | Confirmed through counsel-approved procedure | ||
| Deposit or payment condition | Verified against bank or escrow record | ||
| License, insurance, bond, permit status | Confirmed active from current Chapter 3/4 records | ||
| Final scope and approved changes | Reconciled with Chapter 9 and Chapter 10 records | ||
| Pending selections | Each has a responsible party and decision date | ||
| Long-lead items and subcontractors | Confirmed delivery dates and current qualification documents | ||
| Site logistics and occupied-home rules | Documented and issued to the field team | ||
| Contact directory and document index | Assembled and current | ||
| Startup meeting | Conducted with all required functions represented | ||
| Mobilization approval | Signed, dated, and issued by an authorized manager |
Job Startup Packet declared complete: ______ (Pass/Fail) Date: ____________ Authorizing manager: ____________
Confirmed mobilization date: ____________ Packet owner: ____________
With all four documents completed, review the finished packet against the Acceptance Standards table and confirm the agreement, notices, and payment conditions are verified against primary sources; license, insurance, bond, and permit status are confirmed active; final scope, allowances, and changes are reconciled with Chapters 9 and 10; every pending selection and long-lead item has a responsible party and date; subcontractor documents are current; site logistics and occupied-home rules are documented and issued; and the startup meeting occurred before the authorized manager signed the mobilization approval. Complete the Job Startup Approval Worksheet and correct any failed item before mobilization is scheduled. If an item fails, identify whether the gap is in legal verification, payment verification, authority verification, scope and procurement, or site and customer readiness before revising the packet.
You have completed the thirteenth project in the professional-contractor sequence: creating a job startup packet for an approved project. This project required you to confirm the signed agreement (PC-073), confirm deposit or payment terms (PC-074), collect and confirm selections (PC-075), confirm schedule and readiness (PC-076), organize permits and documents (PC-077), and prepare a job-start checklist and obtain mobilization approval (PC-078).
You now have one approved, dated Job Startup Packet, a project contact and authority directory, a current document index, and a site-start checklist. That approved packet carries directly into the next project: managing customer expectations during construction, using the same contacts, schedule, and communication channel confirmed here to report progress, disruption, decisions, and changes throughout the build.
Store your approved Job Startup Packet and its supporting documents in the project's controlled record location. You will reference this exact packet throughout construction, job costing, and closeout.