Most contractor PMs treat the kickoff meeting as an administrative obligation. Send the slides, cover the contract basics, introduce the team, shake hands, done.
That's a mistake. The kickoff is one of the most valuable hours in the entire contract performance cycle, and most of the value comes from what you learn, not what you present.
The contract kickoff meeting sets the tone for everything that follows: how the government communicates with you, what they expect in terms of reporting and visibility, how conflict will be handled when it arises, and, critically, whether the contracting officer and program office are actually aligned on what they bought.
The kickoff is when you find out how much the government actually knows about what they bought. I've been in kickoffs where the COR and the CO had truly different interpretations of the same PWS paragraph. I've been in kickoffs where a key government POC didn't know they were getting a deliverable they were responsible for accepting. The kickoff is where those gaps surface, and it's infinitely better to surface them in a meeting than in a dispute six months into performance.
Why the First 90 Days Are the Most Dangerous
The first 90 days of a new contract are when most execution problems are seeded. Here's why:
The government doesn't fully know what they bought. The people who wrote the PWS are often different from the people who will manage the contract. The program office and the contracting office may have different priorities. The COR, who often drafts your CPARS evaluation, may be brand new to the program.
Your team is still coming up to speed. Even experienced teams have a learning curve on a new contract. Systems access, badge and facility clearances, GFE transfer, introductions. All of this takes time and creates risk in the early period.
First deliverables set expectations. How you perform on the first deliverable (on time, well-formatted, complete) tells the government everything they need to know about how you'll perform for the rest of the contract. A late or deficient first deliverable is very hard to recover from psychologically, even if the contract itself doesn't penalize you directly.
Problems that aren't addressed early become entrenched. If your first status report is too detailed and the government doesn't want that level of detail, but nobody says anything, you'll keep producing the wrong product for years. The kickoff is your chance to calibrate before bad habits form.
Who Should Be in the Room
The kickoff should include both sides of the relationship with decision-making authority. Here's a standard attendee list:
| Government Side | Contractor Side |
|---|---|
| Contracting Officer (CO): the legal authority on the contract | Program Manager: your authority to commit resources and make decisions |
| Contracting Officer's Representative (COR): day-to-day oversight | Deputy PM or Technical Lead: whoever manages execution |
| Program Manager (USG side): the mission owner | Contracts Manager: to ensure compliance obligations are understood |
| Technical POCs for each major work area | Key personnel as defined in the contract |
| Security officer (if classified work) | Sub PMs (for significant subcontractors) |
If a significant subcontractor is doing a major portion of the work, their PM should be at the kickoff too. The government needs to know who they are, and the sub needs to hear the government's priorities firsthand, not filtered through you.
What to Cover: The Non-Negotiable Agenda Items
1. Contract Baseline and Scope Confirmation
Walk through the PWS together. Not every paragraph, but the major work areas, key obligations, and anything that was clarified during Q&A. Ask explicitly: "Is there anything in how we've described the scope that doesn't match your understanding?" This is your chance to surface misalignment before it becomes a dispute.
2. Reporting Requirements and Cadence
Go through every reporting requirement in the contract: CDRLs, status reports, financial reports, milestone reviews. For each one, confirm: format, frequency, due dates, and who on the government side receives and reviews it. Don't just describe what the contract says. Ask what format works for the COR. A COR who gets a 40-page monthly status report and only needs three pages is a relationship management problem waiting to happen.
3. Government Points of Contact and Communication Protocols
Get clarity on exactly who you talk to for what. Who is your day-to-day COR contact? Who is the alternate COR? Who handles invoicing questions? Who do you call if there's an emergency? What's the government's preferred communication channel: email, teams, phone? Are there any communication restrictions (classification requirements, for example)?
This sounds like logistics. It isn't. Misrouted communication is a CPARS issue. If you've been emailing the wrong government POC for three months and deliverables aren't being tracked properly, that's a management deficiency, and it'll show up in your rating.
4. COR Relationship and Oversight Expectations
The COR is often the person who drafts your CPARS evaluation, in the role CPARS guidance calls the Assessing Official Representative. Take time at the kickoff to understand how they like to work. How often do they want to hear from you? What does "proactive communication" mean to them? What are their pet peeves? What are their top program priorities?
This isn't about flattering the COR. It's about understanding what they're measured on and how you can help them achieve it. A COR who feels informed, supported, and respected is a fundamentally different evaluator than one who feels out of the loop.
5. Key Milestones and the Program Baseline
Walk through the Integrated Master Schedule (IMS) or at minimum a summary milestone schedule. Confirm government-side dependencies: when you need GFE, when you need approvals, when review periods are scheduled. If any milestone is already at risk (transition from incumbent, access issues, system dependencies), surface it now. Better to flag a risk on Day 1 than explain a miss on Day 60.
6. GFE/GFI Transfer and Status
If the government is providing equipment, data, or access, confirm the status at kickoff. Document what has been transferred, what is still pending, and what the delivery commitment is. If GFE isn't provided on time and it affects your schedule, you need a documented record that you raised the issue immediately, not after the fact.
7. Invoicing and Payment Process
Your finance team needs this, but you should know it too. Who approves invoices on the government side? What's the submission process? What's the standard payment timeline? Are there any invoice format requirements? Invoicing problems are contract administration problems, and they affect your cash flow and your relationship with the CO's office.
What Most Contractor PMs Get Wrong
Treating it as a presentation, not a conversation
If your kickoff is 80% contractor slides and 20% government reaction, you've missed the point. The kickoff should be at least 50% back-and-forth. Ask questions. Surface ambiguities. Confirm assumptions. Let the government talk.
Skipping the hard topics
Most PMs avoid discussing what happens when things go wrong at a kickoff because it feels pessimistic. That's backwards. Discuss the communication protocol for issues before they arise. Ask: "If we encounter a scope question, what's your preferred process for addressing it?" "If we need to discuss a potential modification, who do we contact first?" Getting that framework established before problems arise is professionalism, not pessimism.
Not documenting the outcomes
The kickoff should produce a written summary, even a simple one. Attendees, topics covered, decisions made, action items with owners and due dates. This document becomes part of your contract file and provides a reference when "we discussed this at kickoff" becomes relevant later. If you had a verbal agreement about something at kickoff and there's no written record, it didn't happen contractually. The FAR's postaward orientation rules have long said the same thing (FAR Subpart 42.5, mostly cut in the FAR overhaul): the chair writes a report, and any change to the contract that comes out of the meeting happens only through a formal modification.
Not following up
Every open item from the kickoff needs to be tracked to closure. If the government committed to providing GFE by Day 30 and Day 25 arrives with no sign of it, you need to be on record asking about it, not discovering the slip at Day 45 when your schedule is already affected.
Get the Acqlerate Acquisition Starter Kit (Free)
Key terms, COR role breakdown, contract execution checklist, and the most common contractor PM mistakes, all in plain English.
How to Leave the Kickoff With Shared Understanding of Success
Before the kickoff ends, ask this question explicitly: "At the end of this contract period, what does success look like to you?"
It sounds obvious, but the answers are often surprising. A government PM might say "I need this system operational before the next fiscal year." A COR might say "I need clean, on-time deliverables because I'm getting evaluated on them." The CO might say "I need your invoices to come in correctly every time because my office is understaffed."
All of these are valid. All of them are different. All of them tell you something important about how to prioritize your resources and communication over the next 12, 24, or 36 months.
Shared understanding of success is not the same as signing the contract. The contract describes the minimum obligations. Shared understanding of success describes the relationship you're actually trying to build: one where the government trusts you, communicates with you directly, and writes you an Exceptional CPARS rating because you made their job easier every single day.
That starts on Day 1. It starts in the kickoff meeting.