Project Kickoff for General Contracting

Decide what you want to accomplish with the internal meeting, such as aligning on scope, clarifying roles, reviewing risks, and confirming first-90-day priorities. Write these objectives down so you can design the agenda around them. Keep the list focused to fit within the time you have.

Create an agenda that lists topics in logical order: project overview, scope and risk review, budget and schedule summary, roles, communication protocols, and immediate next steps. Assign time blocks to each section to prevent overruns. Note who will lead each agenda item.

Collect the contract, control budget summary, baseline schedule, risk register, permitting matrix, and organizational chart. Create short one- or two-page summaries for budget and schedule to avoid bogging down in detail. Save these in a dedicated “Internal Kickoff” folder for easy sharing.

If your team prefers visuals, build a simple slide deck using the agenda and key summaries. Include high-level drawings or site plans that help everyone visualize the project. Keep slides concise so discussion, not reading, drives the meeting.

Send the agenda and any pre-read materials to the internal team at least a day in advance. Highlight any items they should review beforehand, such as risk lists or schedule milestones. This gives people time to come prepared with questions and input.

Start on time and briefly restate the purpose of the meeting and what you want to accomplish. Confirm the time window and ask if anyone has hard stops. Set expectations that you will focus on decisions and clarity, not deep technical design discussions.

Give a concise overview of the project: client, location, type, size, and major features. Summarize scope and walk through the top risks from the risk register. Ask team members if they see additional risks that should be captured before work starts.

Review the high-level control budget and baseline schedule, focusing on big cost drivers and critical milestones. Highlight tight areas where there is little float or contingency. Make sure field and office staff have a shared understanding of what “on time and on budget” looks like.

Review the role matrix, confirming who owns RFIs, submittals, schedule updates, cost reporting, OAC meetings, and client communication. Outline basic protocols for document control and decision-making. Answer questions to remove ambiguity about who does what.

As you go, note open items, decisions needed, and follow-up tasks with owners and due dates. Before closing, recap these action items and confirm everyone understands their commitments. Explain next steps toward the external kickoff and early preconstruction tasks.

After the meeting, review your notes and any notes from others to pull out specific actions. Look for items that start with “we need to,” “someone should,” or “let’s check.” Turn vague comments into concrete statements like “Confirm…” or “Prepare…”.

Enter each action item into a simple log or task tool with columns for description, owner, due date, and status. Assign each item to a specific person, not just a role. Set realistic deadlines, especially for items that affect external kickoff readiness.

If an item’s owner or desired outcome is unclear, quickly check in with the project manager, superintendent, or other key attendees. Confirm expectations and update the log accordingly. Avoid leaving any item in the log without a clear owner.

Share the log with all internal kickoff attendees and explain where it will be maintained (PM system, shared file, or task tracker). Highlight critical items that must be completed before the external kickoff meeting. Encourage people to update status as they work items.

At early check-in meetings or huddles, briefly review the action log and update statuses. Close items that are complete and add new actions as they arise. Keep the log active until all kickoff-related actions are resolved.

Decide what you need from the external meeting: agreement on communication protocols, confirmation of scope and alternates, schedule expectations, and early submittal priorities. Write these objectives down so the agenda stays focused on alignment, not deep technical problem-solving.

Create an agenda that includes introductions, project overview, contract scope highlights, schedule milestones, RFI and submittal process, meeting cadence, site logistics overview, and next steps. Add specific items for any known hot spots such as phasing or tenant coordination.

Gather documents to present or reference, including a summary schedule, site logistics concept, RFI/submittal workflows, org charts for both GC and design team, and any owner reporting templates. Prepare simplified visuals such as a one-page milestone chart or site plan.

Send the draft agenda to the owner’s representative and lead architect/engineer ahead of time. Ask if they want to add topics or adjust order. Incorporate reasonable suggestions while preserving the core objectives of the kickoff.

Send the final agenda and any key pre-read documents to all attendees a few days before the meeting. Include meeting logistics such as time, location, and virtual links if hybrid. Encourage attendees to review materials and come prepared with questions.

Begin by welcoming participants, introducing the core GC team, and asking the owner and design team to introduce their roles. State the purpose of the meeting: to align on expectations, process, and early priorities, not to redesign the project.

Present a concise overview of the project, including scope, phasing, site constraints, and any special operational or tenant considerations. Highlight known constraints such as limited access, noise windows, or occupancy dates. Confirm that everyone shares the same understanding.

Share major schedule milestones and discuss expectations around decision timelines, response times, and OAC meeting cadence. Agree on standard meeting frequency and preferred days/times. Note any periods (holidays, tenant moves) that will require special planning.

Explain how RFIs and submittals will be submitted, reviewed, and tracked, including target response times and escalation paths. Show how drawings and specs will be updated and how bulletins or addenda will be distributed. Confirm that this aligns with contract requirements and design team capabilities.

Provide a high-level view of site access, laydown areas, temporary facilities, and safety expectations. Ask for any owner or tenant concerns about site operations. Close with a recap of agreements and outline next steps, including issuance of meeting minutes and any follow-up actions.

Gather the final contract, proposal, and any attachments that list allowances, alternates, and unit prices. Create a consolidated list showing descriptions, amounts, and status (accepted, rejected, or pending) for each item.

Go through the list with the project manager and estimator to confirm how each allowance or alternate was priced and any assumptions used. Identify items likely to be touched during design development or client changes. Note any areas where you anticipate confusion.

Schedule a brief focused discussion (can be part of kickoff) with the owner’s representative and, if needed, the design team. Walk through each allowance and alternate, confirming scope, finish levels, and how decisions will be made and tracked. Clarify how unit prices will be applied in field changes.

Summarize the confirmed allowances, alternates, and unit price rules in a short memo or meeting minutes. Include any clarifications that go beyond the contract language. Send this to the owner and design team for their records and store it in the contract admin folder.

Enter the allowances and alternates into your internal logs and cost tracking tools with the agreed descriptions. Ensure field, purchasing, and accounting know how to code costs related to each item. Use this information later when managing changes and reconciliations.

List the trades whose work or submittals drive early schedule activities, such as structural, site utilities, steel, concrete, major MEP, and envelope trades. Include any design-assist or delegated design subs who must coordinate closely with the design team.

Meet or call each key subcontractor to review their scope, inclusions, exclusions, and related schedule milestones. Confirm they understand required manpower levels and any phasing or off-hours constraints. Address obvious scope gaps or overlaps early.

Explain which submittals and shop drawings must be produced first based on long-lead items and structural or envelope sequencing. Agree on target submittal dates for these items and what information or approvals the sub needs from the GC or design team.

Review expectations for participation in coordination meetings, responses to RFIs, and use of collaboration tools (e.g., BIM coordination platforms). Confirm primary contacts on both sides for day-to-day coordination and escalation.

Summarize key points from each conversation in your coordination log and adjust the baseline schedule and submittal log if needed. Share any major commitments or risks from these discussions with the project manager and superintendent.

Study the site plan, surrounding streets, neighboring properties, and any existing buildings or operations. Note limitations on access, staging, parking, and crane or equipment placement. Confirm any owner or city-imposed restrictions on working hours and routes.

Create a simple plan view showing fencing, gates, material laydown, dumpsters, job trailers, temporary power, water, and sanitary facilities. Indicate pedestrian and vehicle routes, as well as loading and unloading zones. Use company templates if available.

List the steps required to mobilize: fencing, trailers, utilities, signage, temporary protections, and safety setups. Assign responsibilities to GC staff and subs, with target dates aligned with the baseline schedule and permit approvals.

Walk through the draft logistics plan with the superintendent and safety lead. Get their input on practical issues, safety concerns, and adjustments needed for different phases of the project. Revise the plan accordingly.

Present the initial logistics plan to the owner and key subs during or shortly after kickoff. Explain how it may evolve over time. Save the plan in the project documents and use it as the basis for updates as the project progresses.

After both internal and external kickoff meetings, review your notes and any minutes taken by others. Highlight items that represent risks, decisions, or constraints, not just general discussion. Focus on those that impact cost, schedule, safety, or quality.

Add any new risks identified during kickoff to the risk register, including their category, likelihood, impact, and proposed mitigations. Update existing entries if discussions clarified likelihood or impact. Save the revised register in the project folder.

Create or update a log that lists key decisions (e.g., preferred phasing, standard detail choices) and constraints (e.g., noise hours, access routes, no-work dates). For each, include the date, who decided, and where supporting documentation can be found.

Share the updated risk and decision logs with the project manager, superintendent, and, where appropriate, the owner’s representative. Confirm that the way items are recorded matches their understanding. Adjust any entries that were misunderstood.

Attach or link the updated logs and relevant meeting minutes in the PM system or shared drive under clear folders. Ensure all core team members know where to find this information. Refer back to these logs in later OAC and internal meetings.

Prepare minutes for internal and external kickoff meetings that summarize key points, decisions, and action items. Avoid verbatim transcripts; focus on what was agreed and what needs to happen next. Use consistent formatting and headings.

Include or reference the updated action log, risk register, decision/constraints log, and any confirmed allowances/alternates summaries. Link to schedules, logistics plans, and org charts rather than embedding large files if your system allows.

Distribute internal kickoff minutes and associated documents to all GC team members, including those who could not attend. Highlight deadlines and owners for action items. Confirm where documents are stored and how updates will be communicated.

Share external kickoff minutes and relevant attachments with the owner, architect/engineer, and others who attended. Keep the tone factual and professional. Invite recipients to correct any material inaccuracies within a set timeframe.

Store the final minutes and attachments in the appropriate folders or PM system records under “Kickoff” or “Meetings.” Mark them as the official record of kickoff. Refer back to these documents in later discussions if questions arise about what was agreed.