The Intent Ledger
← All articles

Meeting Parking Lot: How to Run One That Gets Followed Up

Meeting Parking Lot: How to Run One That Gets Followed Up

A meeting parking lot is a visible list where you put questions, ideas and tangents that matter but don’t belong in the current discussion, so the meeting stays on its agenda and the contributor still feels heard. It only works if every parked item is revisited. A parking lot that nobody reads afterward is just a polite way of ignoring people.

This guide covers what a parking lot is, how to run one step by step, what a good template looks like, the ways it fails, and how design and project teams can turn parked items into lasting project records.

Theintentledger
Keep Parked Topics in Project Memory
The Intent Ledger turns project conversations, meeting notes, and client comments into source-backed records of decisions, actions, and unresolved questions.
Explore The Intent Ledger

TL;DR

  • A parking lot captures off-topic or out-of-scope items during a meeting so the agenda stays on track, without dismissing the person who raised them.
  • Introduce it at the start, keep it visible, and let the contributor write their own item.
  • Review every item before the meeting ends and give each one an owner and a next step, or an explicit decision to drop it.
  • The biggest risk is the “graveyard”: items parked and never revisited, which teaches people to stop speaking up.
  • For project work, parked items should flow into a searchable record, not vanish with the meeting notes.

Table of Contents

What a meeting parking lot is

The idea is simple. During a meeting or workshop, someone raises a point that is real but not for now. Instead of debating it or shutting it down, the facilitator writes it on a flipchart, whiteboard or shared document headed “Parking Lot” and moves on. Nielsen Norman Group describes the parking lot as a technique for workshops and lengthy meetings that captures unrelated questions and out-of-scope conversations, so the discussion stays focused and momentum holds.

You will hear the same thing called parking lot notes or parking lot items. They all mean the same list: the things set aside on purpose. Some teams also call it a “bike rack,” an “issue bin” or a “later list.” The name matters less than the commitment behind it.

It helps to be clear about what a parking lot is not:

  • It is not a place to hide disagreement. If a topic is central to the decision on the table, it belongs in the discussion.
  • It is not a to-do list. Items become tasks only after someone decides they should.
  • It is not a personal notepad. A parking lot is a shared artifact the whole group can see.

The Meeting Toolchest write-up on parking lot principles frames it the same way: a simple sheet of paper headed “Parking Lot” that keeps meetings on track while attendees stay engaged.

When a parking lot earns its place

Not every meeting needs one. A ten-minute check-in with three people and a tight agenda probably doesn’t. A parking lot pays off when:

  • The meeting has a fixed decision to reach and a fixed amount of time.
  • The group is mixed: clients and designers, or several disciplines, where each person brings their own priorities.
  • The topic invites tangents, such as a design critique, a kickoff, a retrospective or a stakeholder review.
  • A few strong voices tend to pull the conversation sideways.

It is less useful when a team uses it to avoid hard conversations, or when the real fix is a better agenda. If half your meeting ends up in the lot, the agenda was wrong, or the wrong people were in the room.

How to run a parking lot, step by step

The practitioner guidance Workshop Weaver gives boils down to four moves. Here they are with some practical detail added.

1. Introduce it at the start

Tell the group in one or two sentences how it works. For example: “If something comes up that’s important but not for today’s decision, we’ll put it on this list, and we’ll go through the list before we finish.” The promise to review it is the part people need to hear. Without it, “parked” sounds like “rejected.”

2. Make it visible

Use a flipchart in the room or a shared digital board or document that everyone can see on screen. Visibility does two jobs: it shows the contributor their item was recorded, and it reminds the group the list exists. If the list lives in the facilitator’s private notes, trust erodes quickly.

3. Capture items as they arise

Write the item down in the contributor’s own words, or better, hand them the marker. Workshop Weaver notes that when the contributor writes the item themselves, the act validates their input and signals clearly that the topic is now parked. In a remote meeting, ask them to type it into the shared document.

Acknowledge the point briefly before you move on: “Good question, let’s park it so we can finish the review.” Don’t answer it halfway. A half-answer invites a follow-up and the tangent takes over anyway.

4. Review before you close

Set aside time at the end. Workshop Weaver’s guidance suggests that this review often takes 15 to 30 minutes in longer sessions, though in a regular 45-minute project meeting you will likely need only a few minutes. The principle holds at any scale: go through every item and decide what happens to it.

For each parked item, choose one of four outcomes:

  1. Answer it now, if the time is there and the answer is short.
  2. Assign it: a named owner and a date for a follow-up.
  3. Schedule it: add it to a specific future agenda.
  4. Decline it: say plainly that the group will not pursue it, and why.

The fourth option is underused. An honest “no, and here’s the reason” respects the contributor far more than silence does.

A meeting parking lot template you can copy

A template doesn’t need to be elaborate. A table with six columns covers what most teams need. Paste it into your meeting notes, a shared doc or a board.

# Item (in the contributor’s words) Raised by Why it was parked Outcome Owner and date
1 Can we revisit the façade material once the budget is confirmed? Client rep Budget not final Scheduled: next design review PM, Nov 3
2 Does the egress route work with the new core position? Junior designer Needs code check Assigned Project architect, Nov 1
3 Switch to a different rendering workflow? Visualizer Out of scope for this meeting Declined for this project Studio lead, noted

Three habits make this template work:

  • Always fill in “Why it was parked.” Future you will not remember. “Out of scope,” “needs data” and “needs a decision-maker who isn’t here” are different situations.
  • Never leave “Outcome” blank at the end of the meeting. A blank cell is exactly how the graveyard starts.
  • Keep the contributor’s name. It tells you who to go back to, and it shows the group that parked items have owners.

If you want a wider structure for what to record from a meeting, our design documentation template shows how to capture decisions, not just tasks.

Why parking lots fail

The technique is old and common, and most of its failures are social, not mechanical.

The graveyard problem

Nielsen Norman Group warns that the parking lot can come across as dismissive when items are parked and then never revisited. Participants conclude their contributions are worthless, and they speak up less in future meetings. Effective use means every item has a clear path to resolution: a future meeting, an action item, or an explicit decision to decline.

The fix is procedural. Reserve the review time on the agenda itself, not as something that happens “if we have time.” If the meeting runs over, shorten another item, not the review.

Using it to dodge difficult topics

A facilitator under time pressure may park a topic because it is uncomfortable, not because it is off-topic. People notice. Ask yourself whether the item changes the decision on the table. If it does, it is not a tangent.

The private list

Workshop Weaver’s guidance for digital settings is that the parking lot works best as a group artifact, not a personal note-taking space. On a shared canvas, items can be clustered, tagged or upvoted by everyone. That turns a passive list into something the group uses to decide what to take up next.

Daily standups

Some agile teams push back on parking lots in standups, arguing that a recurring “extra items after the standup” slot invites more meeting. That is a fair critique for short, frequent meetings. If the same side conversations come up every day, consider whether they should simply happen right after the standup between the people involved, with no list at all.

A short facilitation script

Wording matters more than people expect. Some lines that work:

  • Opening: “We have a parking lot here. Anything important that doesn’t fit today goes on it, and we’ll review it before we leave.”
  • Parking an item: “That matters. Can you add it to the list so we don’t lose it? We’ll come back to it.”
  • Reviewing: “Item one: who should own this, and by when?”
  • Declining: “We’ve decided not to take this on for this phase. I’m noting that and the reason.”

None of this requires special training. It requires saying the words and then doing what you said.

Perspective: the parked item is a piece of project memory

We work with design and architecture teams, and one pattern shows up again and again. The meeting goes well, the parking lot gets filled in, and then it lives in a slide, a whiteboard photo or someone’s notebook. Three weeks later, a junior designer asks why a decision was made, and nobody can find the conversation where it was raised, let alone where it was parked.

That is the real cost of a parking lot with no afterlife. The parked items are often the earliest signals of risk: a client doubting the budget, a consultant flagging a clash, a team member unsure about the brief. They are exactly the things a project needs to remember. Nielsen Norman Group’s guidance points the same way: parking lots work best when they connect to broader project documentation, so parked items feed future action tracking instead of disappearing when the meeting ends.

Our view is that a parking lot item should carry three things: where it came from (the conversation), why it was set aside, and what became of it. If you can trace a decision back to the conversation that produced it, you can also trace an unresolved question forward until somebody answers it. That is the idea behind how we build ILM Records: structured, source-backed records of decisions, design intent, risks, actions, commitments and unresolved questions. A parked item is, in practice, an unresolved question or a risk that hasn’t been triaged yet.

We don’t think every team needs software for this. A disciplined table and a weekly habit will get you most of the way. But when a project runs for months and many conversations feed it, memory has to be built in, not hoped for.

, Rajas

Turning parked items into a record that lasts

Once you have a reliable review habit, the next step is making outcomes findable. A few practices help, whatever tools you use.

Separate the five kinds of parked item

Most parked items fall into one of these, and each deserves a different home:

Type Example Where it should go
Unresolved question “Who confirms the fire strategy?” Open questions list with an owner
Risk “Client may cut the landscape budget” Risk register
Future idea “Could we try a timber structure?” Ideas backlog, reviewed at phase gates
Action “Send the revised plan to the consultant” Task tracker
Decision needed “Choose between two entrance layouts” Decision log

Sorting at the review stage takes a minute per item and saves hours of searching later.

Record the rationale, not just the result

A project manager discussion on how to capture decisions describes a habit worth borrowing: document the decision, the rationale, the alternatives that were discussed and the context, including who was in the meeting. The same applies to parked items that get declined. “Declined, because it would add a month to the schedule” is a record someone will thank you for in six months.

Tag consistently

If your parked items carry the same fields every time (owner, type, source meeting, status), you can filter them. Our guide to tagging meeting notes lists six required fields for design teams, and most of them fit a parking lot row as well.

A parked item without its source is a bare assertion. Whether you link to a transcript, a recording timestamp or a dated note, keep a pointer back. When a client says “I never agreed to that,” the source is what settles it. We cover this in more depth in our piece on client meeting documentation.

Parking lots in design and architecture work

Design meetings are especially prone to tangents. A critique can drift from a plan diagram to material samples to a client’s unrelated worry about schedule. A parking lot is useful here because design conversations are layered: one comment touches structure, cost, aesthetics and regulation at once.

A few adaptations help:

  • In client meetings, park items visibly and send the list with the meeting summary. Clients who see their concerns written down are less likely to repeat them.
  • In crits and reviews, have the student or junior designer own the list for their own project. It builds the habit of tracking feedback and turning it into next steps.
  • In internal coordination meetings, assign each parked item to a discipline lead and review the list at the start of the next meeting.
  • For freelancers, a single running list per client works well. It doubles as a record of what was raised and what you agreed.

If your meeting notes are already a burden, see our guide on how to automate meeting notes for design teams and our look at traceable design meeting notes. For meetings where several stakeholders must converge, our piece on stakeholder alignment meetings explains the one-owner, one-decision-record approach.

A weekly routine that keeps the list honest

A parking lot is only as good as the follow-up habit around it. A routine that fits in ten minutes a week:

  1. After each meeting, clean up the list: confirm owners and dates, and sort items by type.
  2. Before the next meeting, read the open items from last time and put the due ones on the agenda.
  3. At the start of the next meeting, report back on what was resolved. Naming the outcomes aloud is how people learn the list is real.
  4. At each project phase gate, review the “future idea” items and decide which to adopt, defer or drop.

Workshop Weaver’s insight is worth keeping on a sticky note: the parking lot is a promise, not a dumping ground. Each time you keep the promise, the next meeting is a little more focused and a little more honest.

Where The Intent Ledger fits

If your parked items keep slipping away between meetings, a lightweight record can help. The Intent Ledger turns meeting notes, transcripts, critique feedback and client comments into ILM Records, each traceable back to the conversation it came from. Parked questions, risks and commitments get captured with their source instead of living in someone’s memory.

You can start with a one-time pack: Working Set at $12, Project Record at $29, Practice Memory at $59 or Studio Ledger at $119. If you’d rather keep creating records continuously, the monthly plans are Working Memory at $29 per month, Living Record at $79 per month and Shared Ledger at $149 per month. See the details on the pricing page, or read about the approach on our homepage.

FAQ

What does parking lot mean in meetings?

It means a visible list of topics set aside during a meeting because they are off-topic or out of scope for the current discussion. The items are acknowledged as valid and revisited later, usually at the end of the meeting or in a follow-up.

What should go in a parking lot?

Put in questions, ideas and concerns that matter but would derail the agenda: tangents, out-of-scope requests, issues needing data or a person who isn’t present. Don’t park anything that changes the decision on the table. That belongs in the discussion now.

How long should the end-of-meeting review take?

It depends on the meeting. Workshop Weaver’s guidance mentions 15 to 30 minutes for longer sessions, while a short project meeting may need only a few minutes. Whatever the length, schedule it on the agenda and review every item.

How do I stop the parking lot from becoming a graveyard?

Give every item an outcome before people leave: answer, assign, schedule or decline. Then report back on resolved items at the start of the next meeting. Nielsen Norman Group warns that unrevisited items make participants feel their contributions are worthless.

Do I need a special tool for a parking lot?

No. A flipchart, a shared document or a table in your meeting notes works. What matters is that the list is visible to everyone and that outcomes are recorded somewhere you can search later.

Sources