Project Kickoff Checklist: Three Copyable Agendas for Trade Subs

Run this checklist and you leave kickoff with a signed project charter, one accountable owner per workstream, agreed milestones, a RAID log, and a communication plan everyone can point to. The immediate next step is simple: send the meeting invite now, with the charter draft, agenda, and RACI attached as pre-reads.

TL;DR:

• A well-executed kickoff requires a clear RACI chart with a single accountable owner for each workstream to prevent decision delays.
• Drawing the scope in and out of scope live during the meeting reduces misunderstandings and scope creep disputes later.
• Visualizing only the key milestones and dependencies helps keep the schedule realistic and manages external risks effectively.
• Setting up a shared workspace and creating a RAID log during kickoff ensures decisions and risks are tracked and accessible throughout the project.
• Sending pre-reads 48 hours in advance with a specific question increases meeting preparation, while rapid follow-up preserves momentum.

Table of Contents

• The Project Kickoff Checklist: Before, During, and After
• Kickoff Meeting Agenda Templates: 30, 60, and 90 Minutes
• Build the RACI Before the Room Fills Up
• Draw the Scope Line Live, in the Room
• Make the Timeline and Dependencies Visible
• Set the Communication Plan and Single Source of Truth
• Build the RAID Log and Lock Down Success Criteria
• What to Send Before Kickoff, and When
• Turn Kickoff Decisions Into Tracked Work
• Ready-to-Copy Kickoff Templates
• How Kickoff Changes for Specialty Trade Subcontractors
• Stakeholder Identification and Involvement Strategy
• Tools and Technology Setup for Project Collaboration
• Setting Expectations and Ground Rules for Teamwork
• Addressing Change Management Considerations at Kickoff
• What Running Dozens of These Kickoffs Actually Teaches You
• Keep Kickoff Decisions From Getting Lost After the Meeting Ends
• Kickoff Resources Worth Bookmarking
• Sources
• FAQ

The Project Kickoff Checklist: Before, During, and After

A kickoff meeting fails for one of two reasons: nobody prepped the room, or nobody wrote anything down once the room was emptied. The fix is a three-phase checklist that treats the meeting itself as the middle step, not the whole event.

Before the meeting, get these ready:

1. Draft the project charter (purpose, scope, budget range, sponsor).
2. Build a stakeholder register — names, roles, decision authority.
3. Write the agenda with time boxes and assign a facilitator.
4. Draft a first-pass RACI so the meeting refines it instead of building it from scratch.
5. Confirm logistics: room or video link, recording plan, whiteboard or shared doc.
6. Send pre-reads at least 48 hours ahead, per the standard kickoff meeting template most PMs default to.

During the meeting, work through these checkpoints in order:

• State the purpose and business case in plain language.
• Confirm success criteria out loud, not just on a slide.
• Draw the scope line: what's in, what's explicitly out.
• Walk the RACI and get verbal confirmation from each owner.
• Present the milestone timeline and flag any dependency risks.
• Agree on the communication plan and where updates will live.
• Capture top risks and open decisions in a shared RAID log.
• Close with a recap of action items, owners, and dates.

After the meeting, three tasks make or break whether the kickoff actually changes anything:

• Distribute notes and the action tracker within 24 hours.
• Stand up the shared workspace (folder, board, or software built for the job) so decisions don't live in someone's inbox.
• Schedule the first status check, usually 5 to 7 days out, so momentum doesn't stall.

This sequence is what separates a project initiation checklist that produces real alignment from a meeting that just felt productive. The difference shows up two weeks later, when someone asks "who owns that?" and the answer is already written down.

Kickoff Meeting Agenda Templates: 30, 60, and 90 Minutes

Meeting length should match project complexity, not habit. Standard kickoffs for mid-sized projects run 60 to 90 minutes, scaled down to 45 minutes for small, well-acquainted teams and stretched to 120 minutes for complex, multi-stakeholder builds.

1. The 30-minute lean script (small internal teams)

• 0 to 5 min: Purpose and success criteria
• 5 to 15 min: Scope in/out and top 3 milestones
• 15 to 25 min: RACI confirmation and communication plan
• 25 to 30 min: Action items and next steps

Cut introductions if the team already knows each other. Cut budget deep dives entirely, save that for a separate finance sync.

2. The 60-minute standard script (default for most projects)

• 0 to 5 min: Welcome and introductions
• 5 to 15 min: Project purpose and success criteria
• 15 to 25 min: Scope in/out
• 25 to 35 min: RACI walkthrough
• 35 to 45 min: Timeline and milestones
• 45 to 55 min: Communication plan and RAID review
• 55 to 60 min: Recap and next steps

3. The 90-minute client or complex script

• 0 to 10 min: Introductions and project overview
• 10 to 25 min: Scope in/out with live capture
• 25 to 40 min: RACI and escalation path
• 40 to 60 min: Timeline, milestones, and budget checkpoint
• 60 to 75 min: Risks, dependencies, and RAID
• 75 to 85 min: Extended Q&A
• 85 to 90 min: Action items and sign-off

The seven-question framework behind these blocks (why, who, when, how much, what could go wrong, how we'll talk, what success looks like) maps to a structured kickoff agenda that most experienced PMs already build toward, whether they name it that or not.

Pro Tip: Time-box the scope and plan blocks first when building your agenda. They're the two sections that reliably run long, and if you protect their time upfront, everything after them stays on schedule.

Build the RACI Before the Room Fills Up

A RACI chart assigns four roles to every task: Responsible (does the work), Accountable (owns the outcome), Consulted (gives input), Informed (needs updates). The rule that makes it work: every workstream gets exactly one Accountable owner. Split that "A" across two people and you've built a chart that looks organized but resolves nothing when a decision stalls.

• Map owners to major workstreams before the meeting, not during it.
• Bring a draft RACI to kickoff so the room is confirming, not inventing.
• Watch for vague labels like "the team" in the Accountable column. That's not an owner, that's an excuse waiting to happen.
• If two people think they're Accountable for the same line, resolve it before the meeting ends, not in a follow-up email three weeks later.

Pro Tip: When a workstream genuinely needs two decision makers, split it into two workstreams instead of splitting the accountability. It takes five extra minutes at kickoff and saves days of confusion later.

Getting the RACI right at kickoff is what turns a first project meeting checklist from a box-checking exercise into the document people actually reference when a dispute comes up in week six.

Draw the Scope Line Live, in the Room

Scope creep starts in the gap between what the team assumed and what the client meant. The fix: write the in-scope and out-of-scope lists on a shared screen, live, during kickoff, so nobody can later say they didn't hear it. Teams that capture this list in the room, rather than in a follow-up document, cut down disputes over scope creep significantly compared to teams that leave scope implicit.

1. Project two columns on screen: "In Scope" and "Out of Scope."
2. Ask the sponsor to confirm the top three deliverables first, that anchors the rest of the conversation.
3. Push every gray-area item into "Out of Scope" by default. It's easier to add scope later than to claw it back.
4. Read both lists aloud before moving to RACI. Silence is agreement; objections surface now, not in week four.

Once the boundary is set, define the change-request flow in one sentence: any scope addition needs a named requestor, a named approver, and a written note on schedule and budget impact before work starts. Put that sentence directly into the charter. A charter that says "scope changes require sponsor sign-off and a schedule/budget impact note" prevents more arguments than any amount of goodwill ever will.

Make the Timeline and Dependencies Visible

A kickoff slide should show the timeline in one glance, not force people to parse a twelve-row Gantt chart. Three to five major milestones, dates attached, is enough. If a stakeholder needs more detail than that, send the full schedule separately.

• List only the milestones that would change the project's outcome if missed.
• Call out dependencies that sit outside the team's control immediately: permit approvals, vendor lead times, inspection windows, third-party deliverables.
• Flag anything with a lead time longer than two weeks now, not when it becomes urgent.
• If a milestone date depends on a decision the sponsor hasn't made yet, say so out loud and get a decision date, not a vague "soon."

Any schedule change that moves a milestone by more than a few days needs sponsor sign-off before the team commits to it publicly. Agreeing on that rule at kickoff, rather than during the first schedule slip, keeps the milestone conversation calm instead of defensive later.

Set the Communication Plan and Single Source of Truth

Every project needs one place where the current status, the current scope, and the current schedule live, and it can't be "whatever email thread is most recent." Pick the workspace at kickoff, name it out loud, and put the link in the meeting notes.

• Name the single source of truth: a shared drive folder, a project management workspace, or a dedicated tracking tool.
• Set the cadence: who gets a status update, how often, and in what format (email recap, dashboard, standing call).
• Define escalation: what counts as urgent, who gets contacted first, and what response time is expected.
• Confirm who's copied on what. Not every stakeholder needs every update, and over-copying trains people to ignore the channel entirely.

Pro Tip: Write the escalation path down even if you think it'll never get used. The first time a foreman can't reach the PM at 6 a.m. over a site access problem is not the time to be improvising a chain of command.

Build the RAID Log and Lock Down Success Criteria

A kickoff that skips risk conversation is a kickoff that's guessing. Build a short RAID log (Risks, Assumptions, Issues, Decisions) at the meeting itself, not after, and assign an owner to every entry.

• Risks: name the top three, rate likelihood, assign an owner to monitor each one.
• Assumptions: write down what the team is assuming is true, especially about budget, access, or vendor timing.
• Issues: anything already blocking progress goes here on day one, don't wait for a status meeting to surface it.
• Decisions: log who decided what, and when, so nobody has to reconstruct the reasoning three months later.

Success criteria need the same specificity. Vague goals produce vague accountability. Review the RAID log on a set cadence, weekly for fast-moving projects, biweekly for longer ones, and require sponsor sign-off before accepting any risk that could move budget or schedule.

What to Send Before Kickoff, and When

The single biggest lever for a productive first project meeting checklist isn't what happens in the room. It's what people read before they walk in.

• Project charter draft (purpose, sponsor, budget range, high-level scope)
• Scope summary with a preliminary in/out list
• Draft timeline with major milestones
• Draft RACI for the room to confirm or correct

Send this package at least 48 hours ahead of the meeting, and attach one specific ask: "Come ready to answer whether the scope list on page two is missing anything." That single instruction turns pre-reads from ignored attachments into actual homework. Mark the charter and RACI as required reading; mark supplementary documents like vendor specs as optional, so nobody skips the essentials trying to get through everything.

Turn Kickoff Decisions Into Tracked Work

The meeting isn't the deliverable. What happens in the 24 hours after it is.

1. Write and distribute meeting notes within 24 hours, including a short executive summary at the top for anyone skimming.
2. List every action item with a named owner and a due date, no exceptions, no "the team will look into it."
3. Load those action items into a shared tracker immediately, not into someone's personal notebook.
4. Schedule the first status update before people leave the meeting, don't let it become a "we'll find a time" conversation.
5. Brief any stakeholder who missed kickoff within 48 hours, using the same notes, so they're not operating on secondhand summaries.

This is also where a lot of specialty trade projects lose the thread. RFIs get raised weeks into the job that trace back to a scope gap nobody flagged at kickoff. A tighter RFI workflow starts with cleaner scope and RAID capture up front, not with better forms later.

Ready-to-Copy Kickoff Templates

Here's a compact reference you can adapt straight into a calendar invite or meeting doc.

Keep the RACI sample to five or six workstream rows at kickoff. A 20-row RACI is a planning document for later, not something you'll walk through live without losing the room.

How Kickoff Changes for Specialty Trade Subcontractors

A masonry crew and a low-voltage crew don't run the same kickoff, even on similar-sized jobs. The difference is almost always lead time and site dependency.

• For trades with long procurement windows, glazing, specialty steel, custom millwork, add procurement milestones and a named supplier confirmation owner directly into the milestone list and RAID log, not as a footnote.
• Success criteria should be trade-specific and dated: "Foundation block course complete and inspected by March 20" beats "masonry on schedule."
• Site access, inspection windows, and material delivery timing are the risks that actually derail trade jobs, put them in the RAID log by name, not under a generic "schedule risk" line.
• For plumbing and MEP scopes, confirming as-built drawings and technical documents at kickoff avoids rework tied to outdated specs later in the job.
• Assign a specific owner, often the foreman, for on-site coordination items, and make sure that person's safety plan responsibilities get acknowledged at kickoff, not buried in a separate orientation.

Pro Tip: If your kickoff pre-reads don't mention a permit timeline or inspection window, you probably haven't finished the pre-reads. Trade jobs live or die on dates outside your control, name them early.

Stakeholder Identification and Involvement Strategy

The first real work of any kickoff happens before the invite goes out: deciding who actually needs to be in the room. Miss a decision maker and you'll redo half the meeting later. Invite too many and the conversation slows to a crawl.

Start by separating stakeholders into three tiers. Decision makers, the sponsor, the client's PM, the trade's principal, need to be present for the full meeting. Contributors, estimators, foremen, key subcontractor leads, need to be present for the sections that affect their work, even if that means a partial attendance plan for longer sessions. Informed parties, accounting, administrative staff, secondary vendors, don't need a seat at kickoff at all; they need the notes afterward.

Recommended attendance for productive kickoffs runs 5 to 10 people. Beyond that range, side conversations start, decisions slow down, and quieter stakeholders stop contributing entirely. If your stakeholder list runs longer, split the meeting: a decision-maker session for scope and budget, followed by a broader kickoff for the full team once the framework is locked.

Build the stakeholder register before the agenda, not after. For each name, note their role, their decision authority, and what they specifically need to walk away knowing. That list becomes the backbone of both your invite list and your RACI draft.

Tools and Technology Setup for Project Collaboration

A kickoff checklist only holds up if the tools underneath it actually get used. Before the meeting, decide where three things will live: the project charter, the action tracker, and day-to-day communication. Naming these choices at kickoff, out loud, prevents the slow drift back to scattered email threads and personal notebooks that swallows most project documentation within a few weeks.

For specialty trade subcontractors specifically, generic project software built for general contractors rarely fits the way a sub actually works, bid tracking, submittal management, daily field reports, and crew time all need to connect to the same job record. A platform built around sub workflows keeps that information in one place instead of spread across a spreadsheet, a group text, and a shared drive that nobody updates consistently.

At minimum, confirm four things before the meeting ends: where the RACI and action tracker live, how field updates get logged, who has edit access versus view-only access, and how photos or daily reports get attached to the job record. Skipping this step is how a well-run kickoff meeting still produces a project that runs on tribal knowledge three weeks later.

Setting Expectations and Ground Rules for Teamwork

Kickoff is the only time the entire team is in one room before deadlines start creating pressure. Use it to set a few ground rules explicitly, rather than assuming everyone shares the same unwritten standards.

State response-time expectations directly: if a question goes out over the project's communication channel, what's the expected turnaround? Twenty-four hours is a common default for non-urgent items, same-day for anything flagged urgent. Set a rule for how status updates get delivered, short written recap versus live call, and stick to it consistently so people know what to expect.

Address decision-making authority head-on. If the RACI says a foreman is Accountable for a site logistics decision, say clearly that the foreman doesn't need to escalate that decision upward for approval. Ambiguity here is what causes both stalled decisions and decisions made by the wrong person.

Finally, agree on how disagreements get handled. Not every disagreement needs to become an escalation. Give the team permission to work out minor scheduling conflicts directly with each other, and reserve the formal escalation path for issues that actually affect budget, scope, or schedule. A kickoff that sets this expectation clearly avoids both the extremes of over-escalation and silent frustration.

Addressing Change Management Considerations at Kickoff

Every project changes shape at some point, new information, a schedule shift, a client request that widens scope. The kickoff's job isn't to prevent change. It's to agree on how change gets handled before anyone's emotionally invested in a particular outcome.

Build the change-request process into the charter itself, using the same minimal structure covered earlier: a named requestor, a named approver, and a written note on schedule and budget impact. The specific wording matters less than having it written down and agreed to while everyone's still in problem-solving mode rather than defending a position.

Talk through how the team will handle a milestone slip, not if one happens, but when. Will the sponsor get notified immediately, or at the next scheduled status update? Who decides whether a slipped milestone requires a schedule renegotiation versus just tighter execution on the next phase? Agreeing on this process at kickoff means the first real schedule pressure gets handled by a process the team already accepted, not a negotiation invented under stress.

For trade subcontractors specifically, change management often means handling client-driven scope additions without absorbing the cost silently. The charter language from the scope section, sponsor sign-off plus a written impact note, is what protects the crew from doing free work because nobody wanted to be the one to raise a change order mid-job.

What Running Dozens of These Kickoffs Actually Teaches You

Three lessons hold up across almost every project, regardless of trade or size.

First, the RACI conversation is where kickoff either earns its time or wastes it. Everything else can run smoothly and still produce a confused project if the accountability chart is vague.

Second, the scope line drawn live in the room prevents more arguments than any contract clause written afterward. People remember what they said out loud far better than what they read in an email.

Third, follow-up speed matters more than meeting polish. A kickoff with a rough agenda but notes distributed the same day beats a beautifully run meeting that produces no written record for a week.

One masonry job stands out: a kickoff where the team flagged a supplier lead time issue in the RAID log, on day one, instead of discovering it three weeks in. That single line item saved a full week of schedule slip because the PM had already started a backup supplier conversation before it became urgent. My rule for every kickoff I run now: no meeting ends without a RAID log, a named Accountable owner on every line, and notes out the same day.

— Dave

Keep Kickoff Decisions From Getting Lost After the Meeting Ends

Some software platforms for specialty trade subcontractors help keep kickoff decisions, RACI ownership, and schedule dependencies attached to the job record instead of scattered across email and spreadsheets. The RACI you build at kickoff, the milestone list, the RAID log, all of it connects to bid tracking, daily field reports, and crew time in one workspace, helping to keep decisions made in the meeting visible.

If your last kickoff produced a great meeting and a forgotten action tracker, that's a workflow problem, not a discipline problem. Start a trial of Subascent and see how job setup, submittals, and crew tracking hold onto the decisions your team makes on day one, straight through to closeout.

Kickoff Resources Worth Bookmarking

• Project Kickoff Meeting Agenda Template and Checklist, ProjectManagement.com's breakdown of timed agenda structures.
• Project Kickoff Meeting Agenda: 7 Questions, 3 Templates, Scribbl's question-based framework and RACI guidance.
• Project Kickoff Meeting: Agenda, Checklist, and Template, Rework's pre-read timing and agenda table.
• Masonry Subcontractor Bid Invitation Checklist, for trades managing long procurement lead times.
• Construction Software Built for Subs, for setting up the collaboration tools kickoff decisions need to survive in.

Sources

• Projectmanagement
• Project kickoff meeting agenda: 7 questions, 3 templates · Scribbl
• Project Kickoff Meeting: Agenda, Checklist, and Template (Rework resources)

FAQ

What Should Be Included in a Project Kickoff?

A complete kickoff covers project purpose and success criteria, scope in and out, a confirmed RACI, milestone timeline, communication plan, and an initial RAID log, all captured live and distributed as notes within 24 hours.

What Are the 5 C's in Project Management?

Definitions vary across sources, and there's no single agreed-upon framework, so rather than force-fit an acronym, focus kickoff on the elements that consistently matter: clear scope, confirmed accountability, a communication plan, a captured RAID log, and a committed timeline.

How Long Should a Project Kickoff Meeting Be?

Standard kickoffs for mid-sized projects run 60 to 90 minutes; scale down to 30 to 45 minutes for small internal teams and up to 120 minutes for complex, multi-stakeholder projects.

What Is the Recommended Format for a Project Kickoff Meeting?

The most reliable format follows seven core questions: why the project exists, who owns what, when it ships, what it costs, what could go wrong, how the team will communicate, and what success looks like, each mapped to a time-boxed agenda block.

What Should Be Sent Before a Kickoff Meeting?

Send the project charter draft, scope summary, draft timeline, and draft RACI at least 48 hours before kickoff, along with one specific question you want attendees to come prepared to answer.

How Do You Track Action Items After Kickoff?

Distribute notes with named owners and due dates within 24 hours, load items into a shared tracker immediately, and schedule the first status update before the meeting ends, ideally using a workspace like Subascent that keeps kickoff decisions connected to the job record.

Recommended

• Subcontract Agreement Review Checklist for Trade Subs
• Submittals Workflow with General Contractors: A Sub's Guide
• How Bid Due Date Tracking Works for Trade Subs
• Subcontractor Prequalification Submission Guide for Trade Subs