A parking-lot question needs a return path

A meeting parking lot works only when every item leaves with a precise question, a next owner, a return place and a return time.

Without those four parts, “let's park that” is a polite way to make a relevant concern disappear. The meeting stays on time, but the uncertainty survives outside the record.

Park a question, not a topic

Broad labels are hard to return to:

• pricing;
• onboarding;
• legal concerns;
• launch timing.

Nobody can tell from “pricing” whether the room deferred a missing fact, a decision, a disagreement or a piece of work. Rewrite the interruption as the question that stopped progress:

Can the annual plan include a 30-day cancellation window without changing the approved revenue forecast?

That wording preserves the boundary. It prevents the follow-up from expanding into “review pricing” and tells the next owner what answer would close the item.

If the room cannot state the question, take one minute to discover it. A vague parked topic is usually evidence that participants are worried about different things.

Decide whether the item needs an answer, a decision or work

Different parked items need different return paths.

An answer closes a factual gap: Which contract clause controls cancellation? What did the customer already accept? Who has access to the source data?

A decision needs a person with authority to choose among valid options: Will the launch move, narrow or proceed with the known risk?

An action creates a result: Update the forecast with the cancellation assumption and attach the revised model.

Do not turn all three into “Mira to follow up.” Name the actual result:

Answer needed: Confirm whether the signed order form permits a 30-day cancellation window.

Owner: Priya.

Evidence: The controlling clause and a plain-language interpretation.

If the answer then creates a decision, record that as the next step rather than pretending one task can silently contain both.

Give the next move to one person

“Product and Finance to discuss” names a group, not an owner. Each person can reasonably wait for someone else to begin.

Choose one person who will make the question move. That person may need evidence from colleagues or authority from a decision owner, but they remain responsible for returning the item to the agreed place.

The owner should confirm three things before the meeting moves on:

1. the question is accurate;
2. they can obtain the required input;
3. the return time is credible.

If the proposed owner was not present, the assignment remains a request until they accept it. Use the same care you would when assigning an action item to someone who missed the meeting.

Ownership does not mean answering alone. It means nobody has to guess who will restart the thread.

Name where the answer will return

“Take it offline” describes where the current conversation stops. It says nothing about where the result becomes visible.

Choose a return place that matches the item:

• add a written answer to the source meeting record;
• update a connected action item with evidence;
• send a decision request to the named decision owner;
• place the question on a specific future agenda;
• attach the finished analysis and notify the people waiting on it.

The answer should return to the record even when two people resolve it in a hallway or chat. Otherwise everyone else still sees an open question, and the reasoning becomes private knowledge.

In Scripta, teams can keep notes, decisions, action items, files and comments with the source meeting. That makes the meeting record a practical return place. Scripta will not decide which parked question matters or chase its owner for you; the team still has to make the return path explicit.

This is different from moving unfinished agenda work into another meeting. When the group genuinely needs more live time, record the return point so the next conversation starts from the unresolved question rather than replaying the whole discussion.

Set a return time based on who is waiting

A parked question needs a date even when it is not a conventional task. The date tells people when they can rely on an answer or when they should choose a safe alternative.

Work backwards from the dependent event:

The launch brief goes to customers on Friday. The cancellation question returns to the meeting record by Wednesday at noon. If it remains unanswered, the brief excludes the cancellation promise.

This is stronger than “circle back next week.” It protects the downstream work and gives silence a consequence.

Do not automatically use the next recurring meeting as the deadline. The next meeting may move or be cancelled, while the dependent work continues. The guidance on not using the next meeting as a deadline applies here too.

Review the parking lot before people leave

Reserve the last two minutes to read each item back. For every question, ask:

• Is the question written narrowly enough to answer?
• Does it need a fact, a decision or a deliverable?
• Who accepted the next move?
• Where will the result be recorded?
• By when, and what happens if it is late?

Some items should be deleted. The group may realise the question no longer matters, is outside the meeting's scope or duplicates work already underway. Deleting it deliberately is better than assigning ceremonial follow-up nobody needs.

Other items may belong in the current meeting after all. If deferring the question makes the planned decision unsafe, change the agenda rather than preserving the schedule at the expense of the outcome.

Use this five-line parking record

Write this while the context is still in the room:

Question: [the precise uncertainty].

Next result: [answer, decision or deliverable].

Owner: [the person who accepted the next move].

Returns to: [meeting record, decision owner or named agenda].

By / if late: [time and fallback or escalation].

Then read it back with the owner.

The parking lot is not a storage place. It is a routing tool. Use it to protect the current agenda without losing the question that still deserves an answer.