“Bilingual materials” goes on the whiteboard, and the meeting moves on. A week later, nobody remembers whether the question was translation cost, audience need, or approval to publish. Write the question being deferred, why it is outside today's discussion, and where the group intends to revisit it. A topic label needs enough context to survive the meeting.
Consider this original fictional planning meeting. Its current purpose is to agree the sequence of a workshop. The following topics are recorded for later discussion; no real meeting, assignment, publication decision, or follow-up has occurred.
Open the complete example · Download the full HTML source
P01 — Should a later workshop offer an evening session? It concerns a future offering, outside the current workshop's sequence. Proposed return: the next program-planning discussion. Actual meeting date and responsible person remain unconfirmed.
P02 — Would a bilingual summary help the intended audience? Audience need and available editorial support have not been checked. Proposed return: an editorial scoping discussion after those questions are investigated. No translation, budget, or publishing decision is supplied.
P03 — What should an alumni demonstration show? The suggestion needs a clearer purpose before the group can evaluate it. Next clarification: ask what the demonstration would help participants understand. No presenter has been invited.
The example preserves three questions. It does not show three agreed action items or three problems that have already occurred. Keep those distinctions when transferring a hurried whiteboard note into a document.
Give the facilitator a short capture format
Atlassian's meeting-notes article describes a parking lot for topics or ideas the team wants to revisit later. The record format here adds the question, current agenda boundary, and proposed return place so a later reader can understand the deferral.
During the meeting, capture enough to recognize the point without restarting the whole debate. Read the wording back if “bilingual materials” could mean several different decisions. Distinguish a suggestion from a request that the group has actually accepted.
Use this blank record:
Item ID and meeting/reference:
Exact question or idea to revisit:
Why it is outside the current agenda:
Context or source needed for the later discussion:
Proposed next conversation or clarification:
Actual responsible person and date, only if agreed:
Later decision or disposition and its record reference:
The last field stays empty until the later review occurs. A proposed future meeting does not mean the topic has already been scheduled.
Read the list before everyone leaves
Confirm the next step for each item without converting a proposal into an assignment. For P01, the group still needs to identify the program-planning discussion. For P02, it needs to determine who can investigate the audience and editorial questions. For P03, clarification comes before inviting a presenter.
If the group agrees an owner and date, record that agreement. If it does not, leave the gap visible and state the unresolved routing question in the recap. Avoid “handled” or “done” for a topic that was simply moved out of today's conversation.
Where an actual problem needs resolution now, use an appropriate operational record. The issue log follows observed problems through actions and closure evidence. A parking lot preserves deferred discussion; it should not conceal a current blocker.
Request a clean version of the meeting notes
Prepare a complete HTML meeting parking-lot reading copy.
Meeting purpose and current agenda boundary: [PASTE]
Deferred questions with IDs and original context: [PASTE]
Proposed next conversations or clarification requests: [PASTE]
Actually agreed owners/dates and source references: [PASTE OR NONE]
Later decisions already recorded: [PASTE OR NONE]
Keep deferred topics distinct from agreed actions and current issues.
Preserve questions, reasons for deferral and proposed return places.
Leave unconfirmed owners, dates and outcomes blank. Include a blank
record. No fake approval, assignment, scheduling or notification
controls. Use readable labeled records, inline styles and complete
HTML. Return the reading copy and unresolved routing questions.
Before distributing the recap, compare each entry with the actual notes and confirm the agreed return arrangements. Bring those questions back into the appropriate working agenda when the responsible group is ready to discuss them.