oprill / original field notes

Give the task a shape the reviewer can check.

An original workbook for writing a useful instruction, choosing the right context and inspecting the result. Start with synthetic meeting notes and build a reviewable action summary.

1. Define the output before writing the prompt.

Start with the person who will use the result. For a meeting summary, that person needs commitments and unresolved questions, not a polished retelling of every sentence. Specify the fields that make the output useful: action, owner, due date if one was agreed and supporting note.

Practice source: A fictional product team discussed a help page. The designer agreed to draft an outline. The engineer will check whether the proposed search filter is feasible. Nobody committed to a launch date. The team will revisit the decision after those two checks.

2. Give the instruction a boundary.

Try this instruction with your preferred tool and the synthetic notes: “Using only these notes, produce an action summary. For each action, include the owner role and the exact supporting sentence. Write ‘not specified’ for dates that were not agreed. Put proposals and unresolved decisions in a separate section. Do not assign new work.”

The boundary matters because the missing date is part of the source, not an invitation to fill the gap. If the tool adds a deadline, the result fails this exercise even if its formatting is excellent.

3. Review the answer in two passes.

First compare every action with the notes. Check that the owner actually accepted the action and that no discussion point became a commitment. Then check whether the summary omitted something the reviewer needs to act.

In the second pass, inspect presentation. Are unresolved decisions easy to distinguish? Can the reader find the source sentence without searching the entire output? Edit the instruction only after identifying the specific failure.

4. Add a conflicting note.

Extend the exercise with a fictional follow-up: “The designer cannot prepare the outline this week; ownership will be reassigned at the next meeting.” Ask for an updated summary that distinguishes current commitments from earlier notes.

A useful output should show that the designer’s earlier commitment has changed and that the new owner is unknown. The reviewer should reject a summary that quietly retains the old owner or invents a replacement.

5. Carry the review method into real work.

Before using workplace content, follow your organization’s rules for approved tools and information sharing. Replace the synthetic material only after the relevant owner approves that use.

Keep the review checklist even as the task grows: authorized context, clear output, visible unknowns, traceable commitments and a human decision before external action. This workbook provides a method; it does not offer an AI service or guarantee an outcome.