Project Kickoff & the Project Execution Plan

Welcome

Hello, and welcome. This is Super Structures General Contractors — a national general contractor headquartered in Powhatan, Virginia — here to help you and your clients build something that lasts. We're glad you're with us, and we look forward to connecting with you.

Alright, Project Kickoff & the Project Execution Plan. Don't let the plain title fool you. Here's the part that actually matters on the job: The first thirty days decide the job — understand the contract and the estimate, set up the budget and the systems, and write down how the project will be run. Learn it well and you spend the rest of the job executing instead of recovering.

Between award and the first day of real work, the PM sets up the project. It is the least visible month of the job and the most important. Jobs that go badly — missed notice deadlines, buyout losses, a schedule nobody believes — can usually be traced to something skipped here, when there was time to do it right.

Read the contract — all of it

Before anything else, read the owner contract and its general conditions: the scope and exclusions, the schedule and any liquidated damages, payment terms and retainage, the change-order and notice procedures, insurance and any bonds required, dispute resolution, and the specifications' Division 01 (general requirements), which is where submittal procedures, temporary facilities, closeout requirements, and meeting rules usually live. On a standard form such as the AIA A201 general conditions, the change, claim, and payment articles are the ones the team will live by. Make a one-page contract summary of the dates, deadlines, dollar thresholds, and procedures the team must follow — who can approve a change, how many days to give notice, when the pay app is due — and post it where the team works.

The estimate handoff

Sit with the estimator, in person, with the estimate open. Get the estimate detail by cost code, the bid assumptions, the clarifications and exclusions that went with the proposal, the proposed subs and suppliers with their quotes, the allowances and alternates, and anything the estimator was worried about. Ask the questions directly: where is the margin, which numbers are tight, which sub quotes were incomplete, and what did we assume about the schedule and site conditions? Then convert the estimate into the project budget by cost code — the baseline the job will be measured against for the next year.

Set up the systems

• Schedule of values for billing, built on the same cost-code structure as the budget so the pay app and the cost report can be reconciled.
• Baseline schedule — built with the super and the key subs, with the critical path identified, submitted per the contract.
• Logs — submittal, RFI, change order, and the procurement log for long-lead items, each with turnaround dates.
• Project management software loaded with the drawings, specs, addenda, and distribution lists, so the whole team works from one current set.
• Permits, insurance certificates, and notices required before mobilization.
• Cost accounting — job set up, cost codes loaded, and the approval workflow for sub invoices agreed with accounting.

The project execution plan (PEP)

A short written plan — a few pages, not a binder: project goals, team and roles, budget and margin targets, schedule milestones, the buyout plan and procurement priorities, the quality and safety approach, the communication plan (meeting cadence, reporting, who talks to the owner), and the known risks and how they'll be handled. Review it with the team and the company's leadership, then use it: the PEP is the document a new APM reads in week one and the reference when someone asks why the job is run the way it is.

The two kickoff meetings

The internal kickoff — PM, super, APM, estimator, safety — covers the job from the company's view: where the margin is, what the estimator assumed, which subs are strong and weak, what could hurt the job, and who owns what. The external kickoff with the owner and design team sets expectations: the schedule, submittal and RFI turnaround times, the pay-application process and dates, the meeting cadence, and who on the owner's side has authority to approve changes and at what dollar level. Get all of it in the minutes.

Going Deeper (Intermediate)

Build the budget and the schedule of values on the same structure. When the SOV lumps codes the budget separates, or vice versa, every monthly reconciliation becomes a translation exercise and errors hide in the gaps. Front-loading the SOV is tempting and most architects spot it; a fair SOV with mobilization and general conditions properly placed gets paid without argument.

The baseline schedule deserves real time at kickoff. Get the key subs' input on durations, confirm long-lead deliveries against the sequence, and make sure the schedule the contract requires is the schedule the super will actually run. A baseline nobody believes is worthless as a record when delay claims come.

Advanced / Pro-Level

Pros do a contract risk review at kickoff: pay-if-paid versus pay-when-paid, no-damage-for-delay clauses, consequential damages waivers, the notice periods for changes and claims (often 7 to 21 days), indemnity, warranty length, and who owns the schedule float. They flag every clause that needs flow-down to subcontracts so the GC isn't caught between the owner's terms and the sub's — if the owner contract waives delay damages, the subcontract had better say the same.

They also build the procurement plan from day one. Lead times for switchgear, elevators, structural steel, curtain wall, and mechanical equipment drive the submittal priorities and sometimes the whole schedule; a submittal sitting in the architect's queue for three weeks can cost the project months. Long-lead items are tracked weekly on a log with the required-on-site date, the lead time, and the latest date the submittal must be approved.

Practice Challenge

The estimator's clarifications say "winter conditions and temporary heat not included," but the owner's schedule has the slab pouring in January. What does the PM do at kickoff? (Answer: raise it before work starts — review whether the bid clarification made it into the contract, discuss with the owner and architect how temporary heat and winter protection will be handled and paid, and either get a change order or a schedule adjustment in writing; discovering this in January is a loss.)

In Practice

A PM who summarizes the contract on one page and posts it in the trailer has a team that knows the notice deadline, bills on the right date, and buys the switchgear before it matters. A PM who never read Division 01 misses the 10-day notice, loses the claim, and discovers in month eight that the SOV and the budget don't line up.

Common Mistakes to Avoid

• Starting work before reading the full contract and general conditions
• Losing the estimator's assumptions in the handoff
• Building the budget and the schedule of values on different structures
• Treating the baseline schedule as a submittal instead of a plan
• No written execution plan — everyone assumes a different plan

Takeaway: The first thirty days decide the job — understand the contract and the estimate, set up the budget and the systems, and write down how the project will be run.

Educational content — not legal, accounting, or contractual advice. Follow your contract's specific procedures and deadlines and consult your attorney and CPA as needed.