Start the Project
Before timelines, meetings, and spreadsheets, get clear on whether the project makes sense, what it includes, and what success actually looks like.
* all tools are free to download
Project Charter
A project charter is a short high-level document that defines the project before significant work begins. It usually sets out the purpose, objectives, sponsor, project manager, broad scope, key deliverables, high-level timeline, and early risks.
Use it near the beginning of a project, once the idea is serious enough to move forward but before the team disappears into detailed planning, delivery, or stakeholder confusion.
Projects often begin with energy but not much shared clarity. Different people think they agreed to the same thing, until it becomes obvious they did not. A project charter helps create an early reference point for what the project is, why it is being done, who owns it, and what success is supposed to look like.
Scope Definition
A scope definition template sets the boundaries of a project. It helps you clearly define what is included, what is excluded, the main deliverables, and any key assumptions or constraints shaping the work.
Use it once a project has been approved in principle, but before work starts expanding into areas nobody explicitly agreed to. It is especially useful when multiple stakeholders are involved or when expectations could easily drift.
A lot of project frustration is not really about poor delivery. It is about vague boundaries. When scope is unclear, teams end up doing extra work by accident, stakeholders assume things were included when they were not, and priorities become difficult to defend. A clear scope definition gives everyone a firmer shared reference point.
Feasibility Checklist
A feasibility checklist helps you assess whether a project is viable before you commit fully to it. It gives you a structured way to think through technical, financial, operational, legal, and time-related issues early, while there is still room to rethink the idea rather than defend it.
Use it at the very beginning of a project, especially when the idea is promising but still untested, underdefined, or likely to involve significant cost, change, or risk.
Most weak projects do not fail because nobody worked hard. They fail because nobody stopped early enough to ask whether the idea was realistic in the first place. A feasibility checklist helps you test the project before you invest too much time, money, or confidence in it.
SMART Goals Builder
A SMART Goals Builder helps turn a rough intention into a clear, actionable goal. It breaks the goal down into Specific, Measurable, Achievable, Relevant, and Time-bound parts, then helps you combine them into a stronger final statement.
Use it once the project direction is clear enough to define a concrete objective, but before the work starts moving without a clear target. It is useful at both project and task level, especially when goals still sound vague, broad, or overly ambitious.
A lot of goals sound good until someone asks what they actually mean in practice. A SMART goals builder helps move from loose intention to something more precise, realistic, and trackable. That makes it easier to prioritise work, assign responsibility, and judge whether progress is actually happening.
Risk Register
A risk register is a structured log used to identify, assess, and monitor potential risks throughout a project. It helps capture each risk clearly, assign an owner, assess its likelihood and impact, and record both mitigation and contingency actions.
Use it once a project moves beyond the idea stage and starts carrying real delivery, budget, timing, or stakeholder exposure. It should be set up early, then reviewed and updated throughout the project rather than treated as a one-off exercise.
Risks do not become easier to manage just because nobody writes them down. A risk register makes uncertainty visible before it turns into disruption. It helps teams think more clearly about what could go wrong, what can be done in advance, and who is responsible for paying attention.
Track and Deliver
Planning matters, but delivery is where projects usually get tested. These tools help you monitor progress, manage uncertainty, and make sure important things do not quietly disappear.
* all tools are free to download
Action Tracker
An action tracker is a simple working log used to capture tasks, assign ownership, set deadlines, and monitor status. It turns meeting decisions, requests, and next steps into something visible and trackable rather than leaving them scattered across notes, inboxes, or memory.
Use it as soon as a project starts generating actions that need follow-up. It is especially useful once meetings become regular, responsibilities are shared across people, or progress depends on small tasks being completed on time.
A lot of project slippage happens quietly. Something gets mentioned, someone says they will handle it, and then it disappears into the fog. An action tracker reduces that drift by making responsibilities, dates, and updates explicit. It helps teams follow through more consistently and makes accountability much easier to manage.
Organise Roles and People
This is the part of project work that deals with people rather than paperwork. Use these tools to clarify roles, map stakeholders, understand team capacity, and create better ways of working.
* all tools are free to download
Team Charter
A team charter is a shared working agreement that sets out how the team will communicate, make decisions, run meetings, manage conflict, and hold itself accountable.
Use it early in a project, especially when a team is newly formed, working under pressure, or likely to have overlapping roles and expectations.
Teams often struggle not because people are incapable, but because expectations stay unspoken. A team charter makes those expectations visible earlier and gives the group something practical to refer back to when communication, coordination, or behaviour starts to drift.
Team Skills Matrix
A team skills matrix maps who already has key skills, who would benefit from collaborating with that expertise, and who would like to develop it over time.
Use it before setting formal team agreements (before TEAM CHARTER), especially when roles, capability gaps, or support needs are still unclear.
Teams often have more overlap, hidden gaps, and unrealised development potential than they think. A skills matrix makes those patterns visible, helping teams allocate work more realistically, spot missing coverage, and identify where collaboration or learning would strengthen delivery.
Stakeholder Map
A stakeholder map helps you identify who matters to the project, assess their influence and interest, and plan how to engage them appropriately.
Use it early in a project and revisit it as relationships, priorities, or political dynamics change over time.
Projects do not exist in isolation. Different stakeholders have different levels of power, interest, and support, and ignoring that usually creates avoidable problems. A stakeholder map helps teams focus attention where it matters most and manage relationships more deliberately.
RACI Matrix
A RACI matrix is a responsibility mapping tool that clarifies who is Responsible, Accountable, Consulted, and Informed for each task or deliverable.
Use it when work is shared across multiple roles, especially if responsibilities are starting to overlap, drift, or remain unclear.
Projects often become inefficient when too many people assume someone else is handling something, or too many people think they own the same task. A RACI matrix creates clearer accountability, reduces confusion, and helps teams coordinate work with less friction.
More tools coming soon...
Have suggestions? Email us.