Project Kickoff Checklist: Charter, RACI, First 2 Weeks
A project is ready to kick off when four documents exist and have been read by the people who will use them: an approved charter, a draft stakeholder register, a RACI matrix with one accountable owner per deliverable, and a scope statement that says what is out as well as what is in. The kickoff meeting itself then takes about 90 minutes plus 30 minutes of preparation (Atlassian’s Team Playbook sizes it at 30 minutes of prep, 90 minutes of run time and 3 to 14 people), and the work that decides whether the meeting mattered happens in the ten working days after it.
The checklist below puts those pieces in order, with the source for each. For the agenda itself, with timeboxes and owners, use the kickoff template in the meeting agenda guide; this page covers what has to be true before the meeting and what has to happen after it.
The checklist at a glance
| When | Item | Done when | Source of the practice |
|---|---|---|---|
| Before | Charter approved | Sponsor (and executive sponsor, if separate) have signed; trade-off ranking is in it | California PMF, Initiating phase |
| Before | Stakeholder register drafted | Names, positions, influence and preferred involvement level recorded | California PMF, Conduct Stakeholder Analysis |
| Before | RACI matrix drafted | Every deliverable has exactly one A and at least one R; every stakeholder appears | California PMF; NMSU RACI guide |
| Before | Agenda and pre-read sent | Charter or brief is in attendees’ hands before the meeting | California PMF (approved charter shared with the team) |
| During | Purpose, scope and objectives, roles, processes, schedule and first milestones | Decisions and owners captured live | California PMF kickoff review list |
| After, day 1 | Notes with decisions, owners and dates sent | Absent stakeholders can read them cold | Synthesis |
| After, days 2-10 | Register, RACI, risk list and first plan baselined | See the two-week table below | Synthesis |
What the evidence says about launch meetings
An often-cited empirical study of project launches is Ericksen and Dyer’s “Right from the Start,” published in Administrative Science Quarterly in 2004 (DOI 10.2307/4131442). It compared three high-performing and three low-performing project teams drawn from five major corporations. The high performers mobilised relatively quickly, used comprehensive rather than limited mobilisation strategies, and held participatory rather than programmed launch meetings. Those habits produced more time for the work, team members with the right competencies and enough time to contribute, and complete rather than partial performance strategies. The low performers lacked one or more of those resources and, per the abstract, never recovered from the accumulating confusion and inactivity.
Six teams is a small sample, so the study shows a pattern rather than a law. Its two labels still suggest a practical test for any kickoff: whether the team shapes the plan in the room or only receives it. Atlassian’s play reaches a participatory design from practice. Of its 85 minutes of in-meeting steps, 60 go to refining the project’s vision, mission and “mission tests”, first in three small groups and then together, before the group votes to accept the result.
Before the kickoff: the charter
The California Department of Technology’s Project Management Framework (CA-PMF) states the purpose plainly. The charter “formally authorizes a project,” describes the business need and anticipated results, and “provides the project with the authority to expend organizational resources.” Its stated purpose is to demonstrate organisational support for both the project and the project manager. The framework says the charter should ideally be led by the project manager, reviewed by key stakeholders and approved by the project sponsor and the executive sponsor, and that its approval signals that the other initiating activities can begin. The approved charter is then shared with the project team and other stakeholders. California says the framework supports practices that conform to industry standards as defined by the Project Management Institute (PMI), adapted to state government, and it refers readers to PMI’s PMBOK Guide for deeper treatment.
The charter is deliberately short on detail. Georgia Technology Authority’s Enterprise Portfolio Management Office publishes a charter template whose eleven sections show what the charter normally holds:
| # | Section | What goes in it |
|---|---|---|
| 1 | Executive summary | The problem the project was created to correct, at a high level; optional for smaller projects |
| 2 | Purpose and justification | Business case and business objectives |
| 3 | Project description | SMART objectives and success criteria, high-level requirements, constraints, assumptions, preliminary scope statement |
| 4 | Project organization | Roles and responsibilities; internal and external stakeholders |
| 5 | Risks | High-level risks known at the start |
| 6 | Deliverables | Everything the customer, sponsor or stakeholders require; adding one needs sponsor approval |
| 7 | Summary milestone schedule | Major checkpoints, not a task plan |
| 8 | Summary budget | General cost components and their planned costs |
| 9 | Project approval requirements | What counts as successful completion, accepted by whoever signs off the closeout; optional for smaller projects |
| 10 | Project manager | Who, and with what authority |
| 11 | Approvals | Signatures that authorise and fund the project and give the manager authority over its resources |
Two details in these sources are worth building into your own charter. First, the Georgia template says objectives should be Specific, Measurable, Attainable, Realistic and Time-bound, because vague objectives “make it difficult to measure progress and success.” Second, CA-PMF asks the manager to discuss trade-offs among scope, cost and schedule with the sponsors, to put an initial priority ranking of those constraints in the charter, and to learn which of them the sponsors see as flexible. When a mandate fixes the date, say so there. That ranking later settles arguments in minutes that would otherwise take a meeting.
Small projects do not need the full document. California publishes a mini charter for the smaller low-complexity projects, pilots and proofs of concept, and Oregon’s Department of Administrative Services offers small and large charter templates. The rule that scales down is the approval record: someone with budget authority has written down that this work is authorised, for this purpose, under this project manager. A fuller treatment of the work that follows the charter, breaking scope into deliverables, is in the work breakdown structure guide.
Stakeholder register and RACI: who is on the project
The stakeholder register
CA-PMF defines stakeholder analysis as identifying the individuals or groups likely to affect or be affected by the project, and sorting them by their impact on the project and the project’s impact on them. The preliminary register it produces may hold identification details (name, position, contact), assessment information (how the stakeholder may influence the project or be affected), and a classification of preferred involvement, such as a need for early engagement. The framework calls the register an input to planning governance and communication, and says the first version is developed further in the planning phase.
Each row is short enough to write before the kickoff, as the first rows for the help-center example later on this page show:
| Stakeholder | Position | Affected by / can influence | Involvement wanted | Owner of relationship |
|---|---|---|---|---|
| Support lead | Head of customer support | Approves article list; owns ticket data | Early and continuous | Project manager |
| Security reviewer | IT security | Can block platform access | Consulted at design | Technical lead |
| Legal | Counsel | Reviews policy wording | Informed, consulted on terms | Project manager |
CA-PMF adds a further step: identify key stakeholders’ project priorities and how much flexibility each has on time, cost, scope and quality, so the sponsor and manager understand which trade-offs are possible as conflicting priorities surface.
The RACI matrix
CA-PMF describes the RACI matrix as documenting stakeholders’ participation in completing tasks and deliverables, listing the major deliverables, all identified stakeholders, and the level of responsibility each holds for each deliverable. New Mexico State University’s IT PMO RACI quick guide defines the four letters this way: Responsible completes the work, Accountable is ultimately answerable for the result and decision, Consulted provides input before action, and Informed is kept updated but neither approves nor performs the work.
Its rules are short. Each task should usually have one Accountable role, a task may have several Responsible roles where execution is shared, and Consulted roles should be limited to people whose input is truly needed. The common mistakes it lists are more than one Accountable person on a task, confusing Responsible with Accountable, too many Consulted roles, a matrix that is too detailed, and failing to review and update it. CA-PMF adds that every task needs at least one R, and that the R and A can be the same person. Here is a compact matrix for the help-center example used later on this page:
| Deliverable | Sponsor | Project manager | Support lead | Editor | Admin |
|---|---|---|---|---|---|
| Article list (first 12) | I | R | A | C | I |
| Sample article | I | C | A | R | I |
| Platform access | I | C | I | I | A/R |
| Product accuracy check | I | I | A/R | C | I |
| Publishing approval | A | R | C | I | I |
Reading a column down shows load: if one person is R on most rows, the plan has a bottleneck. Reading a row across shows decisions: exactly one A and at least one R. CA-PMF suggests that on a small team the manager may go over the updated matrix at the kickoff that opens planning, which is a reason to draft it before the meeting and use the meeting to correct it rather than build it.
During the kickoff
Hold the meeting after the charter or statement of work is final; Atlassian places the kickoff after the statement of work or project poster has been finalised and everyone is ready to start. CA-PMF describes two kickoffs. The first opens planning: the project manager and sponsor meet the project team, the sponsor reviews the charter and communicates the project’s purpose, priority and vision, and the manager reviews the planning work ahead and each person’s role in it. The second opens execution, and in describing it the framework says every project, regardless of size, should have a kickoff, that large multi-phase projects may hold a series as new staff and contractors join, and that the sponsor should attend “to convey how the project supports the organization’s strategic direction.” Its list of what that meeting reviews is a good minimum agenda for either one:
- the project scope and objectives
- team members and their roles and responsibilities
- an overview of the project management processes in place
- the project schedule
- upcoming assignments and milestones
Atlassian lists the roles to identify before the meeting: the sponsor (the most senior stakeholder with most to gain or lose), the project leader who sets the vision, a facilitator who keeps the meeting flowing and focused, the core team and the stakeholders; one person may hold several of these. Its play opens with mutual agreements to keep the conversation productive (“Good enough: Let’s aim for progress, not perfection”) and suggests a “Roman vote” for gauging consensus: thumbs up means accepted, thumbs sideways means “I’ll go along”, thumbs down means a concern. The thumbs-sideways count is the one to read, since it marks agreement that has not yet been earned.
Timeboxes for each segment, with an owner for each, are in the meeting agenda templates. Three items deserve a decision rather than a discussion at this meeting: the definition of done for the first deliverable, the person who decides if scope changes, and the first actions, each with an owner and a date.
After the kickoff: the first two weeks
CA-PMF closes its initiating phase with a checklist whose completion “helps ensure that project staff, the organization, and external Stakeholders understand what is being undertaken and what to expect as the project takes shape.” The table below is a synthesis of the activities these sources describe, arranged as ten working days. The sequence is this page’s suggestion, built from those sources.
| Day | Action | Output | Owner |
|---|---|---|---|
| 1 | Send notes: decisions, actions, owners, dates, plus the charter and pre-read | Notes in one shared folder | Project manager |
| 1 | Create the project space and communication channels | Board, chat channel, mailing list | Project manager |
| 2 | Chase unresolved kickoff questions; give each an owner and a date | Open-items list | Project manager |
| 3 | Correct the stakeholder register and RACI from what the meeting revealed | Register and RACI v2 | Project manager |
| 3-4 | Hold a short risk session; record top risks with owner and response | Risk register (see the risk register guide) | Project manager, technical lead |
| 5 | Break scope into deliverables and work packages | Draft work breakdown structure | Team |
| 6-7 | Estimate; mark dependencies and external waits | Draft schedule with milestones | Team |
| 8 | Agree the reporting rhythm and escalation path (communication guide) | Written communication plan | Project manager |
| 9 | Review plan with sponsor; confirm trade-off ranking still holds | Sponsor sign-off on baseline | Sponsor |
| 10 | Start the first working cycle; confirm everyone has tool access | First sprint or phase begins | Team |
The day-3 update matches a CA-PMF planning step: the RACI matrix drafted during initiating is revisited “now that additional Stakeholders have been identified and more project planning activities conducted.” The framework also recommends validating the matrix with all parties and seeking signed agreement, then seeking re-approval whenever it changes. Atlassian’s follow-up list points to a “workback plan” or task backlog and a DACI decision framework to settle who will drive the project and who will be accountable, consulted and informed.
Worked example: a help-center launch
A support team is launching a help center. The brief names a first batch of 12 articles, the audience, the platform and the person who accepts the finished content. Translation and live chat are out of scope until funded. One sample article is attached so that “ready to publish” has a visible meaning. This is a hypothetical project used to show the artifacts; the names and numbers are illustrative.
The charter ranks the constraints: scope fixed at 12 articles, date flexible by up to two weeks, quality not negotiable. The stakeholder register and the RACI above come from the pre-meeting work. In the meeting, the group settles three things: who verifies product accuracy (the support lead does the check and answers for it, with the editor consulted), who edits language, and who can publish (only the project manager, as the sponsor’s delegate). It records the dependency that matters, access to the support platform, with an owner and a date. If access is late, the team drafts in a shared document, but publishing still waits for it.
The meeting ends with three dated actions: the support lead approves the article list, the editor prepares the sample, and the administrator confirms access. The manager sends notes and brief together on day 1, so someone who missed the meeting can follow the plan.
Mistakes that undo a kickoff
- No approved charter. Without a sign-off from someone holding budget authority, the manager has no standing when priorities collide. CA-PMF treats approval as the signal that the remaining initiating activities can begin.
- Two accountable people on one deliverable. Both assume the other is watching.
- Using the register as a mailing list. Without an assessment of influence and wanted involvement, it cannot guide communication.
- Presenting instead of deciding. The study above found that the high performers’ launch meetings were participatory, not programmed.
- Notes sent late or without owners. Decisions that are not written down, with a name and a date beside each action, did not happen.
Sources
- Ericksen, J. and Dyer, L. (2004), “Right from the Start: Exploring the Effects of Early Team Events on Subsequent Project Team Development and Performance,” Administrative Science Quarterly 49(3), 438-471
- California Department of Technology, Project Management Framework (CA-PMF)
- California Department of Technology, CA-PMF templates (charter, mini charter, stakeholder register, RACI)
- Georgia Technology Authority EPMO, Project Charter Template
- State of Oregon DAS, Project management templates
- New Mexico State University IT PMO, RACI Matrix Quick Guide
- Atlassian Team Playbook: Project Kickoff