“Free Gantt Chart Template for Miro (Download + Guide)”

What are the building blocks of a Gantt chart in Miro?

Gantt chart template for Miro is a key topic in modern project management and teamwork. Four object types, and using more than four is how boards become unreadable. Miro’s frame tool (`F`) is the structural element: frames are the only objects that export cleanly as pages, appear in presentation mode, and can be nested. Everything inside a lane lives in that lane’s frame, so the lane can be duplicated or moved as a unit.

Two structural rules earn their keep. Never put a bar outside a frame — floating shapes do not export and vanish from presentation mode. Never group a bar with its label if the label sits in the task column, because moving the bar then drags the label out of alignment.

A useful addition for workshops is a “parking lot” frame to the right of the chart, outside the timeline, where sticky notes about scope, risk, and disagreement go. It keeps the discussion captured without corrupting the schedule geometry.

How do you set the time axis so the scale is honest?

Pick a unit and a pixel budget, then never change them mid-board. For a quarter-scale plan, one week equals 120 px. That gives 17.1 px per working day, which is enough for a bar edge to be visibly on the right day, and it keeps a 26-week plan at 3,120 px wide.

Build the axis as its own frame, above the lanes, with these three rows.

Then add vertical guide lines every four weeks, or a thin 1 px rectangle per month boundary. Guides are board-level and do not export; shapes do. If the board will be exported for a steering pack, use shapes.

Worked example. A plan starts Monday 5 January 2026 and runs 26 weeks to 5 July. The axis width is 26 × 120 = 3,120 px. Add a 320 px task column on the left, and the whole chart is 3,440 px wide, with the timeline starting at x = 320. A task starting in week 9 sits at 320 + (8 × 120) = 1,280 px, because week 1 begins at offset zero.

That offset arithmetic is the single most common error in hand-drawn Gantts. Week 9 is not 9 × 120; it is eight full weeks of elapsed time. Get it wrong once and every bar is one week to the right of reality, which is exactly the kind of error a workshop will not catch.

How do you draw the bars at the right width?

Width is duration divided by seven, times 120. Height is fixed, fill is status, and the label goes in the task column rather than on the bar.

Worked example. A nine-working-day task starting Monday of week 4. Nine working days spans two calendar weeks less one day: 9 ÷ 7 × 120 = 154 px. Its left edge is at 320 + (3 × 120) = 680 px, and its right edge at 834 px. Draw the rounded rectangle at x = 680, width = 154.

Three more, to show the range:

Fill colours should encode status, not workstream, because status is what the reader acts on and workstream is already visible from the lane. Three colours are enough: grey for not started, blue for in progress, green for done. Add a fourth, red, only for late, and use it sparingly enough that red still means something.

For percent complete, do not draw a second bar. Add a text line inside the bar reading `62%`, or overlay a lighter shade only if the bar is wide enough to make the split legible. On a 51 px bar, a progress overlay is noise.

How do you connect dependencies without creating spaghetti?

Use elbow connectors, anchored edge to edge, and show only the dependencies that gate something.

In Miro, select the connector tool, hover over the source bar until the blue anchor dots appear, then drag to the target bar and drop on the left-middle anchor. Set the line type to elbow in the connector toolbar. The result is a right-angle path that reads as a schedule, unlike a diagonal line that reads as a relationship diagram.

Three rules keep the chart legible.

1. Only gate-to-gate links. If task B can start before task A finishes, do not connect them. Overlap is normal; drawing it as a dependency makes the critical path false.
2. One arrow per pair. Two arrows between the same bars usually means a finish-to-start link and a separate information flow, and the second belongs in a sticky note.
3. Colour the critical path. Set the connectors along the longest chain to a 3 px red line. Everything else stays 1 px grey. That single change turns a wall of arrows into a schedule with a spine.

Worked example of why the critical path matters. Two parallel chains: design (10 days) → build (15 days) → test (5 days) is 30 days. Content (8 days) → review (4 days) is 12 days, starting the same day. The project is 30 days, not 42, and the content chain has 18 days of float. If the reviewer is on holiday in week 3, the content chain absorbs it without moving the date. If the design lead is on holiday, everything moves. The board should make that difference visible in one glance, and only the critical-path colouring does.

How do you handle milestones, the today line, and scope changes?

Milestones are diamonds, 32 px, rotated 45°, sitting on the boundary between two weeks rather than in the middle of one. A milestone in mid-week implies a level of precision the plan does not have. Label it outside the geometry with a short text object, and include the date.

The today line is a vertical line shape spanning the full height of every lane frame, locked, coloured red, 2 px. Move it every Monday during the review; that is a thirty-second edit that keeps the board honest. Do not use Miro’s timer or a sticky note for this — a note drifts, a locked line does not.

Scope changes need a discipline, not a tool. When something new arrives mid-workshop, put it in the parking lot frame as a sticky, not on the timeline. At the end of the session, add accepted items to the bottom lane with an explicit owner and date, then re-check the bars that moved. Boards that grow during discussion without a parking lot end up with tasks drawn over other tasks, and nobody can tell what was agreed.

Version discipline matters more than people expect. Duplicate the whole chart into a new frame named `Plan v3 — 12 Nov` before a big edit, and lock the old one. Miro’s version history exists, but frame-level snapshots are easier to present from.

How do you run a live planning workshop on the board?

The board is at its best in the first ninety minutes of a plan, before anything is certain. A sequence that works:

1. Ten minutes, silent brainstorm. Everyone adds tasks as sticky notes in their own column, no discussion. Silence prevents the loudest person from defining the plan.
2. Fifteen minutes, cluster and name. Group notes into workstreams, agree the lane names, delete duplicates. Name the owner of each lane out loud; ambiguity here costs weeks later.
3. Twenty minutes, sequence. Move notes into rough time positions on a stripped-back axis, arguing only about order, not dates.
4. Twenty minutes, size. Replace relative positions with durations in working days, and draw the first bars at the agreed scale. Push back on any estimate given as “about a month” — convert it.
5. Fifteen minutes, dependencies. Ask one question per lane: what must finish before this can start? Draw only those arrows.
6. Ten minutes, read the critical path. Colour the longest chain, name the finish date, and ask whether anyone present believes it.

The output is not a schedule anyone should trust to the day. It is a shared model, and it is usually better than the schedule one person would have written alone.

Which parts of Miro are genuinely useful here, and which are decoration?

Genuinely useful: frames for structure and export, shapes with fixed dimensions for geometry, elbow connectors, locking, alignment and distribute tools, presentation mode for walking a steering group through the plan lane by lane, and the parking lot for capturing dissent without corrupting the chart.

Decoration that costs more than it gives: elaborate colour legends nobody reads, icons inside bars, avatars on every task, and animated connectors. Also be careful with Miro’s own Gantt-adjacent templates and app integrations — they can seed a structure, but they will not maintain the pixel arithmetic for you, and mixing a template’s scale with your own is how a board ends up with two incompatible timelines.

Performance is a real constraint. A few hundred shapes is comfortable; a thousand is not, especially on a video call with ten participants. Keep a workshop board and an archive board, and export the archive to PDF rather than keeping a year of history live.

What are the limits of a Miro Gantt?

The structural limitation is that a Miro chart is a drawing of a schedule, not a schedule. Geometry has no memory: move a bar and the dependency arrow stretches, but the successor’s date does not move. That is fine for a two-month plan reviewed weekly by a small team. It is not fine for a programme with forty dependencies and three funders.

Three signals that it is time to move: the board is edited more than twice a week, more than one person is redrawing the same lane, or someone asks for a report the board cannot produce. Any of those means the maintenance cost has overtaken the visual benefit.

How does Doitify handle the plan after the workshop?

Doitify is our product, so read this as disclosure, not review. The workflow it fits is the one this article describes: run the messy, collaborative thinking on a board, then move the agreed structure into a tool where dates are computed rather than drawn. Tasks carry start, duration, dependency, owner, and effort as data; the Gantt chart, Kanban board, calendar, and workload view read from that data, so dragging a bar in the timeline moves the successor instead of leaving an arrow pointing at a stale date.

For teams that want to keep the workshop feeling, the useful pattern is to keep Miro for discovery and decision-making, and to treat the Gantt as a living artefact in the project tool. The chart stops being something you redraw and becomes something you read.

If your plan is a single quarter, six people, and a weekly review that takes ten minutes, the Miro version is genuinely enough. Build it to the dimensions above and it will serve better than a tool nobody opens.

Conclusion

A Miro Gantt chart is a thinking tool with a coordinate system, and that is a compliment. The frames, the fixed 120-pixel week, the 48-pixel bars, and the elbow connectors exist so that six people can argue about sequence in one room and leave with the same picture in their heads.

Build it once to those dimensions, run the workshop sequence, colour the critical path, and lock the today line. Then decide honestly: if the plan is small and the review is weekly, keep drawing it. If the board is being redrawn more often than it is read, move the schedule into a tool that calculates, and keep Miro for the conversation that produced it.

If this post on Gantt chart template for Miro was helpful, you might also enjoy Why Employees Don’t Use Project Management Software and How to Plan a Project From Start to Finish.