Business
Meeting parking lot: how to defer a topic without losing it
Stefan Weiss
A meeting parking lot is a visible list of questions or ideas that deserve attention but do not need to be resolved in the current discussion. Use it to preserve a contribution, return to the meeting's purpose and agree what happens to the topic next. A parked item is neither a decision nor a promise to do the work.
The technique is useful when a relevant side issue could consume the time reserved for another outcome. It fails when “let's park that” means “stop raising it”. The practical difference is whether someone can see the question, understand why it was deferred and find its eventual disposition.
This guide explains what belongs in the list, how to introduce it, and how to close the loop without turning every idea into another meeting.
What a meeting parking lot is for
A parking lot provides a temporary place for discussion that falls outside the immediate agenda. It can be a section in shared notes, a whiteboard or a few sticky notes. The medium matters less than whether participants can see and correct the captured topic. Nielsen Norman Group describes both physical and digital versions and warns that an unmanaged list can become a place where contributions disappear. Read its facilitation guidance.
For example, a team discussing the order of a website migration might raise a useful question about next quarter's customer training. The question deserves a record, but answering it may require different people and evidence. Deferring it can protect the migration discussion without dismissing the training need.
The technique is less useful when the meeting has no clear purpose. If nobody can explain the outcome being pursued, there is no fair basis for deciding that another topic is off track. Start by clarifying the meeting agenda, then use the parking lot to handle exceptions.
Decide whether to discuss, park or redirect
Before writing something down for later, ask: could the answer change the decision we are making now?
If yes, it is probably part of the current discussion. A concern about whether a proposed service can handle an essential workload is not a distraction from selecting that service. It may be a reason to investigate, narrow the decision or stop until the missing evidence exists.
Use these three routes:
Discuss now: the issue affects the current decision, exposes a critical misunderstanding or needs immediate attention through the appropriate process.
Park for review: the issue is useful, but its answer will not change today's intended outcome and the group can agree when to reconsider it.
Redirect: the issue belongs with another person or process. Capture the destination and who will make the handover; do not imply that the receiving team has accepted it.
Consider a supplier review. A question about whether the supplier meets a mandatory requirement belongs in the current decision. A proposal to redesign the team's purchasing form could be parked. A report of a security incident should go through the established incident process, not sit on a general ideas list.
These are facilitation judgements, not a ranking of whose contribution matters. Explain the reason and invite correction: “Does this need an answer before we can choose today?” is more useful than “That's out of scope.”
Set up the parking lot before the conversation starts
Choose one visible place, name the person capturing items, and reserve a short closing review. In a remote meeting, put the list in the same shared document as the agenda. For a hybrid session, make sure people joining remotely can read it too; a whiteboard behind the facilitator is not a shared record.
Introduce it in plain language:
“If we find a useful question that doesn't affect today's outcome, we'll capture it here. Before we finish, we'll decide whether it needs follow-up, a different owner or no further work. Please flag anything we have parked that actually blocks today's decision.”
Do not promise that every item will be solved by the end. The closing review is for deciding the next route, which may include explicitly declining an idea. Nor should adding a name automatically make that person responsible for delivery. Distinguish the person who raised the question from anyone who later accepts follow-up.
Capture the question, not just a label
“Reporting” is a weak parking-lot entry. A week later, it could mean a missing export, a dashboard redesign or a question about who receives the monthly report.
“Do regional managers need the same monthly report as team leads?” preserves a question that someone can answer. Add enough context to explain why it arose, without transcribing the whole conversation.
A compact entry needs:
Question or idea: a sentence someone outside the meeting can understand.
Reason for deferral: why it does not need resolving now.
Source or context: the meeting, agenda item or relevant passage.
Review point: when or under what condition the group will decide what to do.
Disposition: pending review, routed, accepted as an action, or closed with a reason.
Add an owner and deadline only when someone has actually agreed to the corresponding action. “Owner not agreed” is more accurate than assigning the person who mentioned the topic.
Read the entry back before moving on. A quick “Have I captured your question correctly?” prevents the facilitator from unintentionally replacing a concern with an easier, less important one.
A worked example: from interruption to a clear outcome
Imagine a fictional operations team deciding the scope of a two-week onboarding trial. During the discussion, someone asks whether the guidance should also be translated for a later regional rollout.
The facilitator checks whether translation affects the trial. The group confirms that this trial uses the existing English-language audience and that any wider rollout remains a separate decision. Translation can therefore be parked without quietly removing a requirement from today's plan.
The captured entry reads:
Question: Which languages would a wider regional rollout need?
Why deferred: Today's decision concerns the existing English-language trial only.
Context: Onboarding trial scope discussion.
Review point: Review with the trial findings before proposing a wider rollout.
Status: Pending review; no translation work authorised.
At the closing review, the group agrees that an operations lead will gather the audience requirements before the rollout discussion. That creates a specific action. It does not authorise translation, choose languages or approve expansion.
The parking-lot entry can now link to that agreed action. The action belongs in the team's normal work tracker, while the original question retains its context. This separation prevents a useful idea from silently becoming a commitment. For the execution side, see how to track action items from meetings.
Review the list before people leave
For each item, ask what changed during the meeting and which route now makes sense. Some questions will have been answered later in the discussion. Others need a short clarification, a specific investigation or a different forum. Lucid Meetings similarly recommends reviewing parked items at the end and deciding whether they still need attention. See its parking-lot definition.
Choose an explicit outcome:
Answered: add the answer and where it came from.
Action agreed: record the accepted owner, expected result and agreed timing in the work tracker.
Routed: name the destination and the person responsible for asking it to take the question.
Deferred again: give a real review date or trigger, such as completion of a particular investigation.
Closed: explain why no further work is warranted.
“Discuss later” without a date, trigger or route leaves the item in the same uncertain state. If the group runs out of time even for review, record who will arrange that review and when. Do not mark the topics resolved because the meeting ended.
Recover context from a recording without inventing agreement
If the meeting was appropriately recorded, the source can help reconstruct what was parked and whether anyone accepted follow-up. In Weeve, use Chat with the relevant recording to draft a list of deferred questions, then inspect the cited source passages before copying it into the shared notes.
A useful request is:
“Find topics explicitly deferred in this recording. For each, separate the question, stated reason for deferral and any agreed follow-up. Cite the supporting passage. If an owner or timing was not agreed, say so. Do not treat every unanswered question as a parked item.”
Genuine Weeve interface with synthetic demo content. This example cites a summary; check the transcript or audio when confirming spoken agreement.
Treat the result as a draft. A phrase such as “maybe Sam could look at it” is a suggestion, not Sam accepting an action. If the passage remains ambiguous, ask the participants rather than promoting it to a commitment.
Weeve can help retrieve and organise source material; you still decide what belongs in the parking lot and copy agreed work into the appropriate tracker. It does not make another team accept a handover. When using an optional external AI provider, review which source text will be sent and follow your organisation's requirements. Read more about Weeve before choosing the workflow.
Fix the common failure patterns
The list keeps growing. Review old entries at the next relevant meeting. Close obsolete questions with a reason and move accepted work to the normal tracker. A larger list is not evidence of better follow-through.
People feel silenced. Recheck the deferral test. Ask the contributor to explain the connection to today's outcome, and keep the captured wording visible. If the topic changes the decision, bring it back into the discussion.
Everything becomes another meeting. Match the route to the question. A factual answer may need one message or a document update. Reserve a meeting for work that actually needs joint discussion or a decision.
Nobody knows what happened afterwards. Include dispositions in the follow-up notes and link the destination. “Routed to the support lead for assessment” is different from “support will deliver this”.
For your next meeting, start with one visible list and one closing review. The success check is simple: every parked question should have an understandable next route or a recorded reason for closure. That is what makes deferral useful rather than forgetful.
