Scribblit

Field notes · Editorial demonstration

Write meeting notes people can use

Blue alpine peaks beneath a bright sky

Give the conversation a purpose

Start the note with the decision the meeting is meant to support. A purpose such as “choose the first page to publish” gives the record a focus. A title like “Tuesday sync” tells a future reader much less.

Record the decision and its context

Write what was chosen and one sentence about why. Include an alternative only when it helps explain the choice. Avoid attributing agreement to someone who was not present or turning a suggestion into a commitment.

Keep uncertainty visible

Put unresolved questions in their own section. If the team needs an image license or a budget decision before moving ahead, make that dependency visible. A neat note that hides uncertainty is less useful than a rough note that tells the truth.

Make follow-up easy

For each agreed action, record what will happen, who accepted it, and when the group will revisit it. If no owner or date was agreed, write “unassigned” or “to confirm.” Send the record through the team’s usual channel and invite corrections.

Use the meeting template as a starting point. On a small project, the whole record may fit on one screen: purpose, two decisions, one question, and three actions. The goal is to preserve enough context for the next person to continue without recreating the meeting.