Quick answer
Use a meeting parking lot for relevant issues that should not consume the current agenda. Capture the item in the participant's language, test whether it affects today's outcome, and assign an owner, resolution path, and follow-up date. Review the list before closing. A parking lot without ownership is not follow-through. It is a visible place where concerns go to disappear.
What belongs in a parking lot
A parking-lot item is relevant enough to preserve but not necessary to complete the current meeting outcome.
Examples include:
- A related policy question owned by another function
- A useful improvement idea that does not affect today's decision
- A dependency that needs separate evidence
- A broader operating issue revealed by a narrow discussion
- A question that can be answered after the meeting
An item does not belong in the parking lot when it materially affects the current decision, exposes a safety or legal issue, challenges the accuracy of the evidence, or shows that the group lacks authority to proceed.
The four-step parking-lot method
1. Capture the issue
Write enough that the item will make sense tomorrow. Ask the participant to confirm the wording.
Weak: Communication.
Stronger: Confirm who notifies customer support when the release date changes.
2. Test relevance to today's outcome
Ask:
- Does this change the decision or output we need today?
- Does it introduce a risk we must address before proceeding?
- Can the group responsibly continue without resolving it?
If the item changes the current decision, keep it in the conversation. Do not park inconvenient evidence.
3. Name the owner and resolution path
Record who will move the item and where it belongs:
- Answer by email
- Add to a named future agenda
- Send to a specific decision owner
- Move to a risk register or action tracker
- Decline because it is out of scope and no action will be taken
Declining clearly is more respectful than pretending every item will receive attention.
4. Close the loop
Review the list before the meeting ends. Confirm the owner, action, and date. Send the status with the meeting record and report back when the item is resolved.
Language you can use
When the point is relevant but not needed now:
That issue matters, and I do not think we need to resolve it to make today's decision. I am capturing it as confirm the support-notification owner. Who can take it, and when should the group expect an answer?
When the point may belong in the current discussion:
Before we park this, does it change the risk or viability of the option we are evaluating?
When no action will be taken:
I want to be clear that we are recording this as context, but no owner is taking an action from today's meeting. If that is not acceptable, we need to identify the appropriate decision forum now.
A completed example
Item raised: The finance team may need a different approval threshold next quarter.
Current meeting outcome: Choose the approval path for the launch happening this month.
Parking-lot record:
- Issue: Confirm whether the approval threshold changes in Q4
- Relevance today: Does not change the current launch threshold
- Owner: Finance operations lead
- Resolution path: Confirm in the Q4 policy review
- Follow-up: Add answer to the operating log by October 3
The record shows why the group continued and what happens next.
Review the parking lot before the close
Reserve two to five minutes. Sort each item into one of four states:
- Answered now
- Assigned with an owner and date
- Scheduled in a named forum
- Closed with no action and a stated reason
Do not leave items in a fifth state called someone should probably look at this.
When the parking lot reveals a bigger problem
If the list keeps growing, the agenda may be addressing the wrong question. Pause and ask whether the group's actual concern differs from the planned outcome.
A large parking lot can also reveal:
- Missing stakeholders
- Repeated decision-right confusion
- An unaddressed operating issue
- A sponsor who has defined the scope too narrowly
- A pattern of meetings that collect issues without resolving them
The facilitator should surface the pattern rather than becoming its record keeper.
Common mistakes
- Recording a vague label that no one understands later
- Parking a risk that affects the current decision
- Assigning an owner who did not accept the action
- Saying we will come back to that without a forum or date
- Hiding dissent to preserve the agenda
- Reviewing the parking lot after participants have left
- Carrying the same unresolved items from meeting to meeting
Frequently asked questions
Should the parking lot be visible during the meeting?
Usually yes. Visibility lets participants verify what was captured and reduces the need to repeat the issue. Protect sensitive information and do not display personal details unnecessarily.
Who owns the parking lot?
The facilitator can maintain it during the session, but each action needs an accepted owner. The facilitator should not become the default owner of every unresolved issue.
What if an executive wants to park material dissent?
State the relationship to the decision and ask that the risk be recorded in the decision rationale. If the environment does not allow responsible challenge, involve the appropriate sponsor or independent support.
How many parking-lot items are too many?
There is no universal number. Repeated growth is a signal to reassess the outcome, scope, participants, or decision process.
Can I use a parking lot in a remote meeting?
Yes. Keep it in the shared artifact where participants can see the wording, owner, and status. Review it aloud before closing.
Give unresolved work a real destination
How to Facilitate a Productive Meeting or Workshop shows how the parking lot fits within the broader session design.
The free Ambiguity-to-Alignment Field Guide helps teams turn unresolved issues into a visible decision, named authority, ownership, next action, and review point.