“Free Project Management Template for Figma (Download + Guide)”

Which Figma surface should the template live on?

project management template for Figma is a key topic in modern project management and teamwork. Three surfaces are available and they are built for different jobs. Choosing wrongly is the most common reason a beautiful template is abandoned by week three.

The practical split is FigJam for anything the team does together in a meeting, and Figma Design for anything the team reads between meetings. A kickoff workshop belongs in FigJam. A roadmap that the whole company checks on Monday belongs on a Figma Design canvas with clean typography and a locked layout.

How do you set up the template file?

Set it up once in roughly forty minutes, in six steps, and keep it as a master file separate from live project files. The steps below assume you know your way around the Figma toolbar but have never built a reusable board.

Step 1: Create the file and name the pages

Create a new Figma Design file and name the pages in the left panel: Cover, Brief, Timeline, Board, Log. Pages are cheap and they keep the canvas readable. A single page holding every section forces constant zooming, and zooming is how people lose the thread of a board.

On the Cover page, put the project name, the owner, the start and end dates, and one line stating what done means. That single line prevents more arguments than any Gantt chart.

Step 2: Build the four working sections

On the Timeline page, draw a horizontal line at the top and place week markers every 240 pixels, which gives a comfortable 40-pixel gutter between labels. On the Board page, create four columns as sections, each 480 pixels wide and 1,200 tall. On the Brief page, create a two-column text layout for goals and non-goals. On the Log page, create a table for decisions with four columns: date, decision, owner, and what it changes.

Keep all four on a consistent 8-pixel grid. Misaligned sections are the reason a board looks improvised even when the content is good.

Step 3: Turn the status chip into a component with variants

Draw one rounded rectangle, 96 by 32 pixels, with a text layer inside. Select both layers, press Ctrl+Alt+K on Windows or Cmd+Option+K on macOS to create a component. Then add two more variants and name them by property: Status = Not started, Status = In progress, Status = Blocked.

Change the fill colours for the variants, then use the component in every card. When a task moves, you change one property instead of picking a new colour from the palette, which is the difference between a board that stays accurate and one that drifts.

Step 4: Apply auto layout to the task card

Group the card contents: title, owner, due date, status chip. Then apply auto layout with 12 pixels of padding, 8 pixels between items, and vertical direction. Set the card width to fixed and the height to hug contents.

Now a two-line title pushes the card taller and everything below it moves down. Without auto layout, the same edit produces overlapping text, and someone spends ten minutes nudging rectangles instead of working.

Step 5: Build the FigJam ceremony boards

Duplicate the file into FigJam for the meeting layer, or create a separate FigJam file and link to it from the Cover page. Add a section per ceremony: kickoff, sprint planning, standup notes, retrospective. FigJam gives you a timer for timeboxing, voting for prioritisation, and tables for structured lists, all of which are built-in features rather than plugins.

The retrospective board is the fastest win. Three columns, a five-minute silent write, then dot voting on the top two actions. The output is a decision, not a feeling.

Step 6: Share it with the right permissions

Use the Share button and set the file to anyone with the link can view, then invite the working team as editors. Designers will open the file for reasons unrelated to the project, and a view-only link means they cannot accidentally move a frame during a design review.

For the status board, consider locking the layout layers and letting the team edit only text and component properties. It is not true permissions, but it prevents the slow decay that starts with one dragged card.

What does a filled status board look like?

A useful board shows four columns and no more. Each card carries a title, an owner, a due date, and a status chip. Here is a filled example for a five-week onboarding redesign, taken from the middle of week three.

Twenty-four cards, six per column on average. If the In progress column passes eight cards for two consecutive weeks, the team is starting work faster than it is finishing it, and the board is telling you something a burndown chart would take a meeting to explain.

The In review column is the one most templates omit, and it is usually where projects actually stall. Work that is finished but unapproved is not done, and collapsing it into Done hides the queue that legal, brand, or analytics owns.

How do you run a two-week sprint inside the template?

Run the ceremony in FigJam, move the outcome to the Figma board, and keep the numbers visible. The template only earns its keep if the plan and the reality meet in the same file at least once a week.

Take a team of three designers with six productive hours a day each, over ten working days. Gross capacity is 3 × 6 × 10 = 180 hours. Subtract 4 hours of ceremonies per person, which is 12 hours, and 8 hours of unplanned support, leaving 160 hours of delivery capacity.

Now size the work. Twelve stories at an average of 12 hours each is 144 hours, which fits with 16 hours of buffer, about 10 percent. Thirteen stories at the same average is 156 hours, leaving 4 hours of buffer, which is not a buffer at all; it is an optimism. The board should show twelve cards in the sprint section, and the thirteenth should sit in a visibly separate Next column so nobody mistakes it for a commitment.

The ceremonies themselves take real time, so price them before you plan:

That is 195 minutes per person per sprint, roughly 3.25 hours, which is why the capacity sum above subtracts four hours rather than pretending ceremonies are free.

How many Figma files does the template need?

Count carefully on the free plan, because the Starter limit is three files per product, not three files in total. On Starter you can co-edit up to three Figma Design files and three FigJam files, with unlimited personal drafts, and version history is limited to 30 days.

So the workable arrangement is: one Figma Design file as the master template kept in Drafts, one Figma Design file as the live project board, and one more for the next project when it starts. FigJam gets its own three-file allowance for the ceremony boards, which in practice means one FigJam file with several sections rather than one file per ceremony.

If the team runs more than two projects at once, the free plan stops fitting, and the Professional tier at 16 dollars per full seat per month becomes the honest comparison rather than a nice-to-have. Add the dev seats at 12 dollars only if developers actually open the files; on many teams they do not.

What does Figma do badly for project management?

Figma cannot remind anyone about anything. There are no due-date notifications, no recurring tasks, no escalation when a card sits in review for nine days, and no way to grant one contractor access to a single card. Comments exist, but a comment is a conversation, not a workflow state.

Three more limits matter in practice. Version history on the free plan runs 30 days, so a board changed in September is not auditable in November. There is no reporting layer, which means the percentage complete in a steering deck is calculated by hand or guessed. And the file is only as current as the last person who opened it, because nothing pushes an update to anyone.

Used honestly, Figma is a shared visual surface with excellent craft. Used as a system of record, it becomes a very pretty place for tasks to go quiet.

Should a design team manage projects in Figma at all?

Yes, for the visual layer, and no for the record. The split that works is: tasks and deadlines in a tracker, decisions and design context in Figma, and one link between them so nobody has to guess which file is current.

The honest trade-off is maintenance. A Figma board is updated by hand, and hand-updated boards decay. Budget ten minutes at the end of each standup to move cards, or accept that the board will be a week stale and stop using it for decisions.

Where does a dedicated platform fit?

When the board is accurate but the work still slips, the missing piece is usually not design. It is ownership, dependencies, and a reminder that arrives without anyone opening a file.

That is the layer Doitify covers. Tasks and sub-tasks carry owners and due dates, dependencies can be modelled, and the same work appears as a board, a calendar, or a Gantt chart. Design context can stay in Figma, with a link from the task, so the canvas keeps the craft and the tracker keeps the commitments. Doitify is our product, so read that as a description of scope rather than an independent review; for a two-person studio, a Figma board and a shared calendar may genuinely be enough.

What mistakes make Figma project templates fail?

Most failures are structural rather than aesthetic, and they show up within two sprints.

• One file for everything. Planning, presenting, and tracking in a single canvas produces a file nobody can navigate at any zoom level.
• No components. Hand-drawn status chips drift in colour and size until the board looks like a collage.
• Cards without owners. A card with no name on it is a topic, not a task.
• The In review column missing. Approvals are work, and hiding them makes the plan look faster than it is.
• No update ritual. A board is only current if a named person updates it at a named time.

Conclusion

A project management template for Figma works when it is treated as the visual layer of a project and not as its memory. Build four sections, one component with three variants, and cards on auto layout, and you have a board a designer will actually open.

Then decide, in writing, what lives where. If the answer is that tasks live in Figma and nothing else exists, the file will be accurate for two weeks and decorative after that. Pair it with something that remembers deadlines, and the canvas can stay what it is best at: the place where the work becomes visible.

If this post on project management template for Figma was helpful, you might also enjoy Roadmap vs Gantt Chart: Which Should You Use? and Project Management Software for SaaS Companies: 2026 Guide.