Project plan

A project stalls almost always for the same reason: nobody is sure what is in motion, what is waiting, and what was already signed off. When that state lives in one person's head or a mail thread, every update is an interruption. A board puts it in sight and answers that question without anyone having to ask.

This template organizes the project into four stages and adds a step many teams skip: review before calling something done. That filter keeps a half finished deliverable from slipping through as complete and having to redo it later, when it costs twice as much.

How the board flows

Each task is born in the first column and moves left to right as it progresses. The key rule is that nothing jumps straight to done: it passes through review first, so quality gets checked before closing.

To do

The project backlog, what is defined but not yet started:

• Define the scope and what is out of it
• List the tasks needed
• Assign owners to each block
• Estimate realistic timelines

In progress

What the team has in hand right now, ideally little at a time:

• Work on the first deliverable
• Coordinate with the team on the overlaps

In review

The quality filter before closing, where things get checked and feedback collected:

• Check the quality of the deliverable
• Collect feedback from whoever will use it

Done

What is finished and approved, plus what is worth leaving learned:

• Close the deliverable and announce it
• Document the learnings for next time

How it works in Foco

On import, Foco creates the "Project" job with these columns as a Kanban board. You drag each task from one stage to the next as it advances; on desktop with drag and drop, on mobile by switching columns through tabs.

In Panorama you see this project's tasks alongside those from your other jobs at once, each in its own color, and you can assign each block to its owner with a date and reminder so deadlines do not slip.