Initiation 4 - Resources, the Project Charter & Tools

Google Project Management Certificate · Course 2: Project Initiation - Starting a Successful Project

---

Having set the goals, scope, and stakeholders, the last piece of initiation is the practical one: what the project runs on. This module is about three linked things - the resources a project needs, the documentation that pins the plan down (above all the project charter), and the tools that keep the work organised.

Note

Where this sits: resources, charter, and tools are still initiation work - they’re decided before planning begins, so the team starts with funding, people, and a shared source of truth already in place.

---

Project resources

Note

Project resources - everything (and everyone) a project depends on to get done. Three buckets: budget, people, and materials.

The three are interdependent: the team can’t work without materials, and you can’t buy materials without a budget. Miss one and the others stall.

Resource	What it covers	Watch out for
Budget	The money the project needs - team cost, outside services/vendors, purchased materials, marketing	Hidden costs: taxes, fees, overtime; keep it aligned to scope
People	Everyone doing the work - you, internal teammates, and external specialists with skills you lack in-house	Get real commitment on the hours each task takes; avoid understaffing
Materials	Tangible items (lumber, hard drives, computers) and intangible ones (software licences, cloud storage, training)	Account for everything up front so nothing surprises the budget

Why plan resources early (during initiation). Figuring out resources before the work starts is what lets everyone actually do their job. Leave it late and you risk two classic failures:

Understaffing → progress stalls, timeline slipsUnderbudgeting → can’t buy materials, hire vendors, or cover overtime

Tip

How to find your resources: interview stakeholders and likely team members about what they think they’ll need. They often name materials you hadn’t budgeted for, or point you to a person whose expertise makes them an asset.

---

Documentation - and why it matters

A big part of the job is guiding decisions - and there are far too many (goals, deliverables, people, costs) for one person to hold in their head. Documentation makes those decisions visible to everyone, not just the project manager.

Documentation gives you	Why it helps
Transparency	Everyone can see goals, scope, deliverables, stakeholders, and resources
A reference point	People who join mid-project can catch up without re-asking
Discovery	Writing it down surfaces tasks, timelines, or costs you hadn’t considered
A historical record	Reviewed at close, so lessons carry into future projects

---

Proposal vs charter

Two early documents are easy to confuse. They answer different questions at different moments.

	Project proposal	Project charter
Purpose	Persuade stakeholders the project should begin	Define the project and its key details
When	Very start of initiation	End of initiation (before planning)
Usually written by	A senior organisational leader	The project manager
Lifespan	Used only at the early stage	A living document referenced all the way through

Proposalpersuade: should we do this?

→

Charterdefine: here’s exactly what & why

→

Planningapproved - build the plan

The proposal kicks off initiation; the charter closes it and, once approved, grants the authority to move into planning.

---

The project charter

Note

Project charter - a formal document that clearly defines the project and outlines the details needed to reach its goals. Think of it as the project’s compass: you steer by it for the whole life cycle.

What the charter does for you:

• Shows the benefits outweigh the costs (it carries the cost-benefit analysis - value created, money saved, time required).
• Gets everyone to agree on the value and the details before planning starts.
• Once the sponsor and stakeholders approve it, you have the authority to proceed.
• Is living - you review and refine it as the project evolves.

What goes in a charter

Charters vary by organisation, project, and audience (a marketing exec cares about brand impact; a CTO cares about engineering cost). Most pull from this menu:

Section	Section
Introduction / summary	Success criteria
Goals / objectives	Key deliverables / requirements
Business case (benefits & costs)	Budget
Project team	Schedule / milestones
Scope (in and out)	Constraints, assumptions, risks
Stakeholders	OKRs · Approvals

Tip

Match detail to the project: a short, simple charter suits small, low-complexity projects; for complex ones, keep the charter lean and push extra analysis into an appendix. Build it with your team and stakeholders so it captures their real concerns, and let the business case (the reason for doing the project) steer what you include.

A worked mini-charter

A condensed example, using the running “Plant Pals” office-plant service (goal: grow revenue 5%):

Field	Example entry
Summary	Offer high-volume customers small, low-maintenance office plants
Goal (SMART)	Increase revenue 5% by launching an office-plant service for top clients by year end
Deliverables	Ship 1,000 plants to 100 customers; launch an orders/support website
Business case	Top-requested service; improves customer satisfaction and retention
Benefits vs costs	Benefits: satisfaction + revenue. Costs: sourcing, website, marketing - est. $250,000
In scope / out of scope	In: deliver small plants to last year’s top clients. Out: plant care after delivery
Success criteria	+5% revenue by year end; 95% customer-satisfaction rate three months after launch

Caution

Benefits should always outweigh cost - that comparison is the charter’s whole argument. Real projects use a far more detailed cost-benefit analysis than a teaching example.

Drafting a charter with a gen-AI tool

A gen-AI assistant (e.g. Gemini) can produce a first draft fast and save time - but the output is a starting point, not a finished charter.

1. Feed it real detail. Prompt like “Act as a project manager and build a project charter from the information below; add placeholders for anything missing,” then paste your project description, business need, deliverables, stakeholders, and success criteria. The more you give, the more complete the draft.

2. Evaluate the output. Read closely, don’t skim - it may include things you didn’t intend, or bullets that need expanding into full sentences. The AI does the heavy lifting; you still do the heavy thinking.

3. Iterate. Refine the prompt: ask for less technical language, shorter/longer sections, a specific number of pages, or “what important information is missing?” Share an existing template or an example (the References idea) to steer format.

Tip

This maps onto a prompt framework: Evaluate the result and Iterate by adjusting wording, giving References/examples, and breaking instructions into shorter sentences.

---

Tools

Note

Tools - aids that make it easier to manage resources and organise work: track tasks, deliverables, and milestones, manage budgets, build charts, and keep everyone informed.

Effective communication and tracking are the bulk of a PM’s day, and tools power both. Crucially, information sharing goes both ways - teammates update you on progress without extra meetings, which raises visibility and transparency for the whole team, stakeholders included. (Picture the alternative: project details on a whiteboard everyone must walk over to read.)

Straightforward vs sophisticated

	Straightforward	Sophisticated
Examples	Docs, spreadsheets, email, chat	Scheduling / work-management software (e.g. Asana)
Best for	Small projects, few tasks/people	Big scope, many tasks, larger teams
Trade-off	Fast to adopt	Powerful, but the team needs time to learn it

Caution

Sometimes the choice isn’t yours - if the organisation has standardised on a tool, you work with what you’re given. Stay flexible.

Types of tool

Type	What it’s for	Examples
Scheduling / work management	Assign tasks, track progress, visualise team throughput	Asana, Monday.com, Basecamp, Trello, Jira, Smartsheet
Productivity	Create project artefacts - charters, agendas, plans, RACI charts, decks	Docs/Word, Sheets/Excel, Slides/PowerPoint
Collaboration	Quick check-ins and questions	Email, chat

Tip

Work-management software shines at spotting trouble: if a team closes 50 tasks one week and 3 the next, the tool makes the drop obvious so you know to check in. Most tools share the same core features (task tracking, assignment) - learn one deeply and you adapt to others quickly.

Spreadsheets are the versatile workhorse

Sheets/Excel do far more than lists. Handy features for PM:

Feature	Use
Sharing permissions	Edit / comment / view-only when you share
Freeze rows/columns	Keep header titles visible while scrolling
Conditional formatting	Auto-colour status: Not started (red), In progress (orange), Complete (green)
Dropdown lists (data validation)	Force consistent entries (“done” vs “complete”)
Sort & filter	Order by due date; show only your own tasks
Pivot tables / charts	Summarise data and present it to stakeholders
Functions	Auto-calc sums, averages, dates, % complete

Common templates worth reusing: a Project Timeline (whole life cycle), a Project Tracking sheet (budget, deliverables, costs), and a Gantt chart (tasks over time with dependencies).

Introducing a new tool to a team

People resist change, especially mid-project. Roll a new tool out deliberately:

1. Discuss it early and often - no one should feel blindsided; give the team time to prepare.

2. Ask key stakeholders for feedback - on features and priorities; incorporate it into next steps.

3. Involve them in demos - let them trial the tool; pull in key users to test before rollout, which also surfaces in-house experts for later training.

4. Ensure it’s fully functional and accessible before introducing it - a buggy tool kills adoption.

5. Set up training as needed - different people have different comfort levels; good first impressions raise adoption.

6. Plan a transition when replacing a tool - run both in parallel for a while, then sunset (retire) the old one; expect a temporary dip in productivity.

Tip

For interviews & your career: be ready to name tools you’ve used and how. No experience with a specific tool? Map a real-life example (planning a house move with a spreadsheet for budget and schedule). Building a personal tool tracker - a sheet listing each tool’s description, link, features, cost, and your experience level - is a good way to learn the landscape and show employers you understand the industry.

---

Revision summary

Must-know	One-line recall
Project resources	Budget + people + materials - interdependent; plan them early in initiation
Plan resources early	Prevents understaffing (slips timeline) and underbudgeting (can’t buy/hire)
Documentation	Creates transparency, a reference point, discovery of hidden work, and a historical record
Proposal vs charter	Proposal persuades (start); charter defines (end of initiation, living document)
Project charter	Formal doc defining the project; shows benefits > costs; approval = authority to proceed
Charter contents	Summary, goals, business case, scope, team, stakeholders, budget, success criteria, risks, approvals
Gen-AI charter	Great first draft; Evaluate & Iterate - AI does the lifting, you do the thinking
Tools	Aids to manage resources and organise work; power two-way tracking and communication
Straightforward vs sophisticated	Simple tools for small projects; work-management software for big scope
Tool types	Scheduling/work management, productivity, collaboration
Spreadsheets	Versatile: permissions, conditional formatting, dropdowns, sort/filter, pivots, functions
Introducing a new tool	Discuss early, get feedback, demo, ensure it works, train, transition then sunset the old one