Planning 5 - Communication and Documentation

Google Project Management Certificate · Course 3: Project Planning - Putting It All Together

---

The planning phase has produced a stack of artefacts so far: a schedule, a budget, a procurement approach and a risk management plan. This final module adds the thing that makes all of them usable by other people - communication, and the documentation that carries it.

The argument here is blunt: communication is arguably the single most important tool a project manager has. Whether a team succeeds or fails often comes down to whether every person understands what is happening and how their own tasks feed the project’s goals. That understanding does not appear on its own; a communication plan is how it gets planned rather than improvised. The module then turns to where all that information lives, because communication nobody can find later is not communication at all.

Note

Where this sits: last module of Course 3. Everything planned so far gets wrapped in a communication plan and a documentation system, so the plan can actually be handed to a team - and, if you leave, to the next project manager.

---

Why communication is central to the job

As project manager you are the person who makes sure everyone knows their role and their tasks, and you are also the person people come to for a quick answer. Without effective communication a project risks missing important opportunities, or failing outright.

A cautionary example

Stakeholders assigned a few design specialists to a project. In week one, one specialist skipped every project meeting. Asked about it, they explained they were well over capacity and could not commit to the deadlines being handed out.

Breakdown 1specialist ↔ their own manager: workload never discussed

Breakdown 2specialist ↔ project manager: absence never explained

Fast follow-upPM asked directly, another specialist assigned

Two communication failures, one week of work lost. Left unspoken, the same gap could have delayed the whole project or wrecked the delivery.

The lesson is the speed of the follow-up, not the fix itself. Silence is a signal; chase it early.

What communication actually is

Note

Communication - the flow of information. It covers everything that is shared, how it is shared, and with whom.

Good, effective communication is:

ClearHonestRelevantFrequent, but not too frequent

That last qualifier matters: information overload is real, and drowning people is its own failure mode. Effective communication is what lets the project run on time and to the expectations set out in the project plan.

Two habits to hold on to:

• Use the full range of channels - meetings, emails, phone calls, written documents, formal presentations - and make sure every one of them is accessible by everyone.
• Treat it as continuous and two-way. Communication is not a one-time event or a one-way route. It runs through the whole life cycle and flows from the team and stakeholders as much as from you. Clarify goals and client expectations, follow up on action items, and flag delays as they happen rather than after.

You are responsible for a consistent flow of communication and for setting the tone, so that everyone stays on the same page at every step.

---

Four tips for effective communication

1. Recognise and understand individual differences. You will always work with a diverse group. Make no assumptions about anyone’s background, identity or experience, stay mindful of your own biases, use professional and neutral language, and be genuinely curious about points of view unlike yours.

2. Brainstorm and craft the appropriate message. Start from the audience. Be explicit about why you are reaching out: are you conveying information, asking for input, clarifying an issue, or resolving a problem? Also tell people which channels they can use to reach you or the team. Some readers need full detail, others only an overview - either way, identify the purpose, state the request clearly and concisely, and stay on topic.

3. Deliver your message. Pick a method that suits the person: in person, video conference, phone, email or a meeting - and think hard about this when people sit in other regions and time zones. Two safety rules: keep sensitive or private information out, and write as though everyone at the company will end up reading it.

4. Obtain feedback and incorporate it. Delivery is not the end. Check the message actually landed, ask for feedback, encourage open communication, and answer questions quickly.

Drafting communications with a gen-AI tool

A gen-AI tool can save time writing communications, but only with a good prompt. The framework is TCREI:

Element	What it means
Task	What you want the tool to do, including the output format, a persona (what expertise to draw on) and who the audience is
Context	Detailed background that narrows the focus and produces tailored output
References	Examples or resources showing the style, tone and format you want
Evaluate	Check the result for accuracy, bias, relevance and consistency before sharing it - AI output is a starting point, never a final product
Iterate	Refine the prompt based on what came back; first attempts rarely land

---

The communication plan

Note

Communication plan - a document that organises and records the process, types and expectations of communication for a project.

Size and complexity vary with the project, but it is always worth having one - especially where there are multiple stakeholders, several phases, or change management involved.

The questions it must answer

Question	What you record
What	The type of communication: status updates, issues, user feedback, daily check-ins, other project meetings
Who	The recipients: key stakeholders, the core project team, subgroups
When	Frequency (how often) plus key dates such as deadlines and major meetings
Why	The goal: progress update, risk identification, removing barriers, next steps, preparation, lessons learned
How	The delivery method: email, in-person or virtual meeting, shared document, formal presentation
Where	Where the communication resources are stored, plus any notes

Not everyone needs the same amount of information at the same time. Key stakeholders typically get less, less often - a monthly high-level summary email or a review meeting. The core team gets more detail more often, through daily email updates or quick virtual check-ins.

Why planning communication up front pays

Improves overall communication effectivenessKeeps people engaged & motivatedPulls stakeholders into effective conversationsGives continuity of operationsSupports change management

Continuity is the underrated one. A new project manager who opens the plan should immediately reach past meeting notes, documentation, and the current and upcoming communications - and carry on. The same access lets people fix problems, make decisions, or reuse the process on a later project after you have moved on. And since change management is the work of delivering the final project and getting it successfully adopted, a plan that says who hears what, when, is exactly what that needs.

---

Filling in the plan, column by column

Built as a spreadsheet, using the running Plant Pals project. Reach for the RACI chart and the stakeholder map first - they tell you what kind of communication suits each person, group or role.

Column	How to fill it
Type of communication	Newsletter, daily stand-up, weekly check-in, status report
Recipients	Who needs deep involvement, who has high interest, who only needs major milestones
Contact info + time zone	Useful for knowing when people are reachable. Contains sensitive data, so hide the column or link it privately
Frequency	Senior stakeholders weekly or monthly; core team daily; subgroups weekly
Key dates	Launches, presentations, deadlines. Recurring items can just say every Monday rather than listing dates
Delivery method	Email, in-person or virtual meeting, shared document, presented progress report
Goal	The why behind that specific communication
Sender / owner	Who is responsible for sending it
Resource location + notes	Where the underlying material lives, plus reminders and caveats

The worked Plant Pals plan

Type	Recipients	Frequency	Key date/time	Method	Goal	Owner
Newsletter	Key stakeholders (busy senior execs)	Monthly	First Monday of the month	Email	High-level status overview: milestones, progress to date	Project manager
Daily stand-up	Core project team	Daily	Noon	Meeting	Progress updates, blockers, next steps	Project manager
Weekly check-in	Marketing, procurement, product development subgroups	Weekly	Wednesdays at 2, 3 and 4 o’clock	Meeting	Coordinate each subgroup with the core team	Subgroup leads

Note

Daily stand-up - a short daily meeting where each member states what they finished and what is blocking them. It comes from Agile, and it keeps a team coordinated and fast-moving.

If time zones or other obligations make daily meetings impossible, keep the flow going another way: daily email status updates naming the action items in play, plus a project tracker for tasks and milestones so everyone can see the same picture.

Craft, so people actually read it

• Email length. Nobody wants a two-page email. Put a note at the top warning that some detail may not apply to every reader, lead with key points and action items in two or three sentences, then park the long version in a section at the bottom.
• Answer the so what. For senior stakeholders, keep asking why they should care. For the core team, ask what information helps them finish tasks on time and stay motivated. A director may have five minutes, so be concise and know exactly what you need from them.
• Match the channel to the group. Instant message and video chat may suit the core team while a subgroup responds far better to email and in-document comments.
• Share the sending. Communication should be a team effort, especially on complex projects. Let other team members own the communications that match their expertise - hence the sender/owner column.

Tip

People absorb information differently: some want charts and graphs, some prefer a presentation or meeting, some want to read and analyse alone before discussing. Present everything in only one or two ways and you engage some people and lose the rest. To optimise, send a short email or survey asking three questions - what is working in how we communicate with you, what is not working, and where can we improve.

---

Best practices for building the plan

Identify, identify, identify

Answer these before you start writing anything down.

Identify	Questions to answer
Project stakeholders	Do you have a RACI chart or stakeholder map? Who is the audience? Who needs informing at which point of the life cycle?
Frequency and method	When and how often should you check in? Which methods do they prefer? How much detail does each one need?
Goals	What is this communication for? Do you need a response? Are you encouraging engagement, or just providing an update?
Barriers	Time zones, language barriers, stakeholders who need time to reply (an executive, say), privacy or internet access limits

Document and develop

Pick a tool or template, then work the details.

• Add a notes column. Project management is not one-size-fits-all. Do you need to copy someone on an email to a senior leader? Is a stakeholder out of office, and is there a backup plan? Notes hold the reminders.
• Use formatting to highlight key details. A launch announcement or an urgent decision that blocks progress deserves a different colour or size.
• Make sure the team can access the document. Sharing lets them review it, offer feedback, and catch anything crucial you missed.
• Test the plan. Send a test email to yourself or a colleague before a team-wide send; test visuals, audio and the technical setup before a virtual presentation.

Check in

Once the plan is live, ask the audience whether it works. Schedule routine check-ins, and double-check that key stakeholders have not changed over time. Look specifically for over-sharing, under-sharing, or missing stakeholders, using anonymous survey forms, polls or open feedback sessions inside team meetings, and one-on-one conversations with key stakeholders. The target is simple: the right information, to the right stakeholders, at the right time.

---

Documentation as a form of communication

Documentation is communication that other people can reference and contribute to later. On a project spanning quality assurance, testing, design, partner engineering and program management, every team owning its own deliverables, the only thing keeping them aligned was storing all plans and reports in one centralised place.

Documentation gives you	How it shows up
Speed	Everyone knows where to look, so communication is quicker and more streamlined
Findability	Clear labels and folders let teams in different countries find and share research, cutting duplicate work
Visibility	The project plan shows every task with an owner and a due date
Accountability	That owner is publicly on the hook for that task
A refresher	Team members and senior stakeholders come back to the plan for timelines and milestones
Continuity	If you fall ill, transfer, or take leave, the next PM picks up where you left off

Scattered personal notes help nobody. Store guides, manuals, meeting notes, plans and processes in one clearly labelled place, and grant access to the people in the relevant roles, so the project carries on whether or not you are there.

Note

Knowledge management - the best practice of documenting your plans and making them available so the project’s data can be accessed in the future by others.

Old plans answer questions nobody thought to record. An architect on a kitchen remodel can look back and see why the sink went where it did; an architect joining halfway through can find out why the plumbing was designed that way, and make better-informed decisions from there. It also sets the tone for future projects and future project managers - which is very welcome when the one jumping onto a strange project is you.

---

Sharing, permissions and need-to-know

Once documents are centralised, decide who may open what.

Core teamfull access: meeting notes, raw data

→

Informed stakeholdersstatus report summarising outcomes

→

Everyone elsefinal results only, no background

Someone outside the core team rarely needs the meeting notes; summarise the relevant part into a status report instead.

More is not better

A project manager working with the company’s VPs decides to send daily updates. Two things go wrong: VPs get enormous volumes of email and will simply not read them, so the effort is wasted; and burying people in unnecessary information makes it impossible to tell what is genuinely important.

Sensitive data

Financial data and user survey results are frequently highly sensitive and must never reach unauthorised viewers. Consider a high-profile launch of a brand new product, say an electric car. Most people do not need the thinking behind the project or the draft versions - only the final design. Share the entire project folder with everyone who only needs the end result and you risk leaking classified material, which can make project plans and company data public, ruin the launch, breach company policy, and damage your reputation as a trustworthy project manager.

Caution

PII (personally identifiable information) - anything that could reveal someone’s identity: screen name, password, phone number, email address, first or last name.

In the sample communication plan, one listed resource is the user feedback surveys - raw data from Plant Pals test users, therefore full of PII. Share that resource only with the project team members approved for that level of access; anyone else who opens the link is prompted to request permission. When the results need a wider audience, present them as a graph, chart or summary report with the PII stripped out, and share that instead.

Only share on a need-to-know basis. The job is to present the right information, at the right time, to the right people.

---

Organising your project files

By this point the course has produced a set of resources: the project plan, the budget, the RACI chart, the risk management plan and now the communication plan. The goal is that you, or anyone on the project, can reach any of them quickly.

1. Create a project folder on a shared file drive, labelled with the project name, and keep every project file inside it.

2. Add subfolders within the main folder for the natural groupings.

3. Create one centralised planning document that links everything together - a quick reference guide to all your frequently accessed files. Select each resource name in turn and link it, so the file opens straight from that document.

4. Group spreadsheets into one workbook with a tab per sheet, instead of opening many separate files. New tabs can be added any time.

5. Add an overview sheet, sometimes called a dashboard, holding a brief project description, instructions for using the sheet, communication expectations, and links to the non-spreadsheet files.

The technique transfers to almost any project management style or system; the shared drive brand does not matter.

---

Artifacts, and the plan as a living document

Note

Artifact - anything you physically put together that describes or showcases the work you are doing. It ranges from an executive brief or project overview down to something as tactical as a roles and responsibilities sheet.

Artifacts serve more audiences than you: stakeholders who sign off, teammates and volunteers, and outside vendors who need to see both where they fit in the larger picture and what they must tactically do. Kept well, they also give you a baseline - so when it is time to ask for more budget or take the work to the next level, you can show where you started and how far it came. In a job interview they are what turns a high-level story into evidence: they show the detail, what happened to the project, and your own contribution to it. You are the quarterback, and the quarterback holds the playbook.

Death by a thousand documents

The characteristic failure mode of a big program is document sprawl. The counter is one master document that centralises links to every sub-document: the charter, the budget, the agreed scope, approval matrices (the list of approvals you need). If everything links out from one place, you always know where to start looking.

Scattered docsmany files, no single entry point

One master trackerlinks out to charter, budget, scope, approvals

Revisit & revisedocumentation is living and breathing

There is no one-size-fits-all set of documents - one project needs a risk management plan, another does not. Starting from one place is what generalises.

You do not finish a project plan or a charter in a single pass. You return to it, revise it, and continue - it is a living document. The pay-off for detail is fewer iterations later, because more gets right the first time.

---

Revision summary

Tip

One-minute recap

• Communication = the flow of information: what is shared, how, and with whom. Effective means clear, honest, relevant and frequent but not overloading.
• It is continuous and two-way, across the whole life cycle; the PM owns the consistent flow and sets the tone.
• Four tips: understand individual differences, craft the message for the audience, deliver it by a suitable method, then obtain and act on feedback. TCREI guides gen-AI drafting.
• Communication plan = the process, types and expectations of project communication. It answers what, who, when, why, how, where stored.
• Fill it column by column: type, recipients, frequency, key dates, method, goal, sender/owner, notes. Use the RACI chart and stakeholder map to decide who gets what.
• Stakeholders get high-level and infrequent (monthly newsletter); the core team gets detailed and frequent (daily stand-up); subgroups sit in between (weekly check-in).
• Best practices: identify stakeholders, frequency/method, goals and barriers; add notes, highlight key details, share the doc, test it; then check in routinely for over- and under-sharing.
• Documentation gives speed, findability, visibility, accountability and continuity - and is the practice of knowledge management.
• Permissions matter: share on a need-to-know basis, keep sensitive data and PII restricted, and publish stripped-down summaries for the wider audience.
• Organise in one project folder with subfolders, plus one centralised document or master tracker linking everything.
• Plans and charters are living documents - revisit and revise them.

Note

Course 3, closed. Planning turned the approved charter into a workable plan: a work breakdown structure that split the goal into tasks, a schedule with estimates, milestones and dependencies, then a budget and the procurement needed to fund and source it, then a risk management plan for what could go wrong. This module supplies the last layer - the communication plan and the documentation system that let other people read, run and inherit all of it. A plan nobody can find is a plan nobody can follow.

---

Next: Project Execution: Tracking & Status → - running the plan you just built.