Saving a return summary · Chai with Jai

At the start of the workshop ([8:31]-[8:58]), Nicole Merced shared her goal: building a practical playbook with clear, concrete takeaways. To capture reliable takeaways from your own work, record what you checked, what you decided, and what remains open.

In this course, your browser saves your summary locally on your machine. This practice environment lets you pause your work, inspect your notes, and resume without losing your place.

Return summary format

Here is an example of a completed return summary. It records the chosen source, names rejected drafts, and lists pending questions:

json

{
  "task_name": "reference_page_review",
  "source_used": "source-x.txt",
  "status": "ready_for_review",
  "check_result": {
    "passed": ["source_x_matched", "approval_confirmed"],
    "rejected": ["source-y.txt"],
    "discrepancy_note": "Quiz experiment source-y was rejected per approval note."
  },
  "next_step": "Draft definition and example layout based on Tuesday draft.",
  "unresolved_questions": ["Confirm whether dark green heading styling is needed later."]
}

Unresolved work

Never hide incomplete checks in a return summary. If you find a mismatch or lack an approval, list it under unresolved_questions. Writing down an open question keeps your team aware of what still needs review before work moves forward.

Try it

Review these practice notes for a returning-practitioner checklist. Each date marks the version date of the draft:

text

record-17.txt (version date: Tuesday, 27 October 2026):
Audience: returning practitioners. Keep the known workflow visible. Compare the performed steps with the checklist and identify the first missing step; do not replace the workflow with an introductory explanation.

record-24.txt (version date: Thursday, 29 October 2026):
Audience: first-time learners. Explain every term before asking them to choose a first task. Replace the returning-practitioner checklist with a beginner introduction.

release-note.txt (version date: Friday, 30 October 2026):
For the returning-practitioner checklist, retain record-17. Record-24 is a proposal for a separate beginner introduction and is not approved for this checklist.

speaker-note.txt (version date: Friday, 30 October 2026):
The speaker grew up near the coast and enjoys hiking.

Try it

You need to write a return summary for the returning-practitioner checklist. Which source file do you accept, which do you reject, and what question remains open?

Check your answer

Accepted source: record-17.txt, because the release note approves it for the returning-practitioner checklist. Rejected source: record-24.txt, because it targets beginners instead and was not approved for this checklist. Ignored file: speaker-note.txt, because personal background has no bearing on the checklist. Unresolved question: confirm whether to write a separate beginner guide later using record-24.

Next steps

Open Your saved work in the sidebar to review your current notes. Make sure your card lists your chosen source, your check results, and any open questions. When you want to start a new exercise or review another draft, use Start a task or Check a draft in the sidebar.

Source References

Nicole Merced Workshop (0DvOP8moyME) [8:31]-[8:58] — Nicole Merced states her learning goal: building a practical playbook and walk-away takeaways.