Project retrospective template

Wrapping up a project without a structured retrospective means good insights get lost, and the same issues keep showing up on the next one. This free project retrospective template gives your team a repeatable way to capture what went well, what didn't, and why, then turn that into action items your team can actually follow through on, with built-in AI to help spot patterns along the way.

​

Try the template.

​

​

What is a project retrospective template?

A project retrospective template is a structured, repeatable framework for reviewing a completed project, whether at a single project milestone or at the very end of a project, and capturing what worked, what didn't, and why. It helps teams turn scattered notes and half-remembered meeting takeaways into a consistent process that produces real follow-through instead of just conversation. This free template helps teams accomplish that by pairing project details and sentiment tracking with structured feedback and owned action items, so lessons learned stay tied back to the original project plan instead of getting forgotten once the meeting ends.

​

​

Why use a project retrospective template?

A static PowerPoint deck, Excel spreadsheet, or shared doc can hold retrospective notes, but none of them connect those notes to due dates, owners, or patterns across other projects, and this template does. It's ideal for project managers, scrum masters, and team leads on agile teams who run an agile retrospective template style review every sprint, or a full project retrospective at the end of a longer initiative. Whether a team follows agile methodology or a more traditional project plan, the template supports team collaboration by keeping every retrospective in one connected place. The template is free and flexible enough to scale from one team's retrospectives to a full program across an organization.

​

​

Benefits of a project retrospective template

Running retrospectives without a shared structure means good insights and action items go nowhere. Here are some benefits, from sharper action planning to clearer visibility into team performance over time:

• Consistent feedback capture. Every retrospective follows the same structure for what went well, what didn't, and the root cause behind it, using the retrospective feedback data's category and theme fields so issues like scope creep or timeline slips get tagged consistently instead of buried in freeform notes.
• Clear ownership on follow-through. Action items include an owner, due date, and status, turning retrospective discussion into concrete action planning, and a built-in automation notifies the owner as soon as a new action item is created.
• Visibility into recurring themes. The recurring themes AI field surfaces patterns within a single project's feedback, supporting knowledge sharing across teams and helping everyone catch repeat issues before they become expected.
• At-a-glance sentiment tracking. The overall sentiment rating captures how the team felt about each project, and the theme and sentiment insights view brings that data together across every project so process improvements and trends are easy to see over time.

​

​

How to use a project retrospective template

The template is easy to use, with data and views already set up to capture and act on retrospective feedback. After clicking "Try the template," teams can start logging their first project retrospective right away. Here's how to get started in a few steps:

​

Log the project

Start by adding the project name, project lead, start and end dates, duration, and team members involved. This gives every retrospective a clear record of what was reviewed and who was part of it, and sets up the project record that feedback and action items will link back to.

​

Capture structured feedback

Add feedback entries for what went well and what didn't, tagging each one with a category and a theme like communication, scope, timeline, tooling, or process. Include a root cause explanation for anything that didn't go well, so the retrospective produces reasons, not just complaints.

​

Assign action items

Turn feedback into action items with an owner, due date, and status. As soon as an action item is created, the owner gets notified automatically, so follow-through starts immediately instead of waiting for someone to remember to assign it later.

​

Review sentiment and themes

Rate overall sentiment for the project, then check the theme and sentiment insights view to see how this project's feedback and sentiment compare to others. This closes the loop between one retrospective and the next, so teams can see whether changes actually reduced the issues that came up before.

​

​

Tips for using a project retrospective template

The template is easy to customize as a team's retrospective process changes. Here are some tips:

• Start with an icebreaker. Having the facilitator open with a quick icebreaker before diving into feedback helps team members feel comfortable, so the notes logged afterward in retrospective feedback data reflect what people actually think.
• Tag themes consistently. Using the same theme options across every retrospective, rather than free-typing new ones, makes the recurring themes AI field and the theme and sentiment insights view far more useful.
• Always fill in root cause, not just the symptom. A feedback entry that explains why something happened is more useful for prevention than one that only states what happened, and encouraging open communication around root causes makes that easier to capture.
• Trigger the AI fields before the retrospective meeting. Having the facilitator run the project summary and recurring themes fields ahead of time gives the team a starting point to react to, rather than starting the discussion cold.
• Check the insights view across projects, not just the current one. Sentiment and themes are most useful when compared over time, so make it a habit to look at trends, not just the latest retrospective.

​

​

Common retrospective formats to run

Teams use a range of formats to structure the actual retrospective conversation, and pairing one of these with the template's structured feedback capture can make discussions more focused.

​

Start, stop, continue

Teams identify what to start doing, what to stop doing, and what to keep doing. It's a quick way to generate concrete suggestions without getting stuck in open-ended discussion.

​

4Ls retrospective

Teams reflect on what they liked, learned, longed for, and lacked. This format works well when a team wants to cover both the practical and the emotional side of a project.

​

Sailboat retrospective

Teams use a sailboat as a visual guide, with wind representing what helped the team move forward, anchors representing what held the team back, and rocks representing risks ahead. It's a lighter way to get a team talking about both momentum and blockers.

​

Starfish retrospective

Teams sort feedback into five categories: start, stop, continue, do more of, and do less of. It's a more granular version of start, stop, continue for teams that want more nuance than three categories allow.

​

Hot air balloon retrospective

Teams describe sandbags and storms holding the project back, and hot air and fire pushing it forward. It's another visual format that can make it easier for teams to open up about pressure points.

​

Mad, sad, glad

Teams sort their feelings about the project into what made them mad, sad, or glad. This format centers team morale and emotional experience alongside the practical review.

​

​

What's included in the project retrospective template

A project retrospective template typically includes a way to log project details, capture structured feedback, and track follow-up action items. This template includes those features out of the box, and it can be customized further with natural language prompts through Omni, Airtable's built-in building expert. Here's what's included in this template:

• Projects data. Log project name, project lead, start and end dates, duration, team members, an overall sentiment rating, and a description, so every retrospective starts with clear project context.
• Retrospective feedback data. Capture feedback text, category, theme, and root cause explanation for each piece of feedback, linked back to its project.
• Action items data. Assign action items to owners with due dates and statuses, so follow-through is tracked in one place instead of scattered across notes.
• Notify action item owner automation. As soon as a new action item is created, the assigned owner gets notified, so nothing sits unassigned or unnoticed.
• Track action items view. See every outstanding action item grouped by owner or status, so it's easy to check what's due and who owns it.
• Theme and sentiment insights view. Pull together project sentiment, feedback themes, and action items into one analytical view to spot patterns across multiple projects.
• Field Agents. This template's Field Agents generate a project summary and surface recurring themes for each project, assess the sentiment of individual feedback entries, and suggest a priority for each action item, so teams get a head start on analysis without doing it by hand.
• No-code customization with Omni. Just describe what you need, and Omni builds it. Teams can ask Omni to add a field to track follow-up dates or set up an automation for upcoming due dates, without touching configuration menus.
• AI-powered reporting with Omni. Ask Omni questions like which projects have the lowest sentiment ratings, how many action items are overdue, or what the most common recurring themes are across retrospectives, and get an answer without building a report from scratch.

​

​

Try these Claude prompts for your project retrospective template

Airtable connects to Claude through the Airtable MCP integration, so teams can ask Claude to work with retrospective data directly. Here are some prompts to try:

• "Summarize the recurring themes across all of our project retrospectives from this quarter."
• "List every action item that's overdue and group them by owner."
• "Draft a root cause explanation for this feedback: our timeline slipped because approvals took longer than expected."

​

Streamline your project retrospectives with Airtable

When teams wrap up a project without a shared way to capture feedback, good insights and follow-up action items fall through the cracks. Airtable's project retrospective template brings it all into one place, with customizable views, flexible workflows, and built-in AI that surfaces recurring themes and sentiment trends automatically. Teams get a clear record of what worked and what didn't, and action items get assigned and tracked without extra manual work.

​

Try Airtable's project management templates and start your next retrospective with a system built to carry lessons forward.

​

​

Frequently asked questions

​

What's the difference between a sprint retrospective and a project retrospective?

A sprint retrospective reviews a single sprint and happens on a recurring cadence, while a project retrospective reviews an entire completed project from start to finish. Whether your team calls it a sprint retrospective template, a scrum retrospective template, or a project retrospective, this template supports either style of review, since each record in the projects data can represent a sprint or a full project depending on how a team sets it up.

​

How long should a project retrospective take?

Most teams run retrospectives in 60 to 90 minutes, depending on the size and complexity of the project. Logging structured feedback with a category, theme, and root cause ahead of the meeting can help keep the discussion focused within that window.

​

Who should attend a project retrospective?

The people directly involved in planning, execution, and delivery of the project should attend, since they're the ones who can speak to what actually happened. The team members field on each project record makes it easy to see who was involved and should be part of the conversation.

​

Is a project retrospective a one-time thing or recurring?

It depends on the team. Some run a single retrospective at the end of a project, while others run them at regular intervals throughout a longer project. Because this template tracks sentiment and themes across every project, it works well for either approach, and it gets more useful for spotting patterns the more retrospectives get logged.

​

What's the difference between a retrospective and a post-mortem?

A retrospective is often lighter and focused on a short list of near-term changes, while a post-mortem tends to be a more detailed, one-time review of an entire project, often after something went noticeably wrong. This template's root cause field and action items data support either use case, since both benefit from documented causes and tracked follow-up.