Chai With JaiGPU Study Hall
Menu

How work moves from step to step

Follow a task from an initial goal to a checked, saved result without guessing.

Workflow Practice: Inspect the six steps from Task through Return.
/ Step 01: Task

Follow your work

See how your work moves across the six steps. Choose a step to inspect what you do, what you save, and how background checks can run.

Detail layer:
Pathway key:
01 Task 02 Source 03 Work 04 Result 05 Check 06 Return
Step 01 · Task Not started

In this session, I am making...

Name your reader, the one piece to make, and how you will know it is useful.

Needs from Your initial goal:

A clear statement of what you intend to make and who it is for.

Hands off to Source:

Gather only the files, notes, or examples this task genuinely needs.

WHAT YOU DO

Write what you want to make and how you will check that it helps your reader.

WHAT YOU SAVE

Name the reader, the decision or action this work supports, and how you will check it.

Self-check: Does your task name the finished piece, who it helps, and how you will check it? If not yet met: Name what the reader needs to do and what the result must show to help them do it. Add a length or count limit only when the task requires one.
Your saved task note Edit your work →

You have not entered a draft for this step yet.

Start this step in your work
Version comparison

No version history recorded yet. Use Save a version in Your work to compare changes.

In the workshop recording (0DvOP8moyME at [7:39]-[8:17]), Nicole Merced joined as an audience co-learner so viewers could learn by watching real problem solving. You can watch how she chooses a task, picks her source materials, asks a clear question, and tests it on her own work.

To keep your own work on track, this course uses a six-step model: Task, Source, Work, Result, Check, and Return. This model is our course guide for human review, not a method from Nicole:

  1. Task: Name what you want to make and set a clear stopping boundary.
  2. Source: Gather only the approved notes or reference text you need.
  3. Work: Ask the tool to draft or change the text.
  4. Result: Treat the generated output as an unchecked rough draft.
  5. Check: Compare the rough draft against your approved source to spot mistakes or extra text.
  6. Return: Save a short note of what you kept, what you cut, and what still needs an answer.

Never assume a draft is correct just because a tool finished without an error message. A completed run is only a rough attempt. Your work is reliable only after you inspect the draft directly against your source notes.

Worked example

Below is a written practice example. The dates show the order of choices, not delivery deadlines:

text
worked/source-x.txt (Tuesday, 20 October 2026):
Use the Tuesday draft for a reference page. Put each term beside its meaning and one short example, so a returning learner can look it up.

worked/source-y.txt (Thursday, 22 October 2026):
Experiment: replace the reference page with a quiz. Ask learners to recall each definition before showing it.

worked/approval.txt (Friday, 23 October 2026):
Keep source-x, the Tuesday reference-page instruction, for this release. The source-y quiz experiment has not been approved.

worked/color-note.txt (Friday, 23 October 2026):
Try dark green headings on a cream background.

To check a draft for this task, compare it against approval.txt. If the draft turns the page into a quiz from source-y.txt, reject that quiz section because approval.txt withheld approval. Set aside the styling note about color because it does not belong in this task. Use only source-x.txt.

Try it

Read these written practice notes:

text
guided/note-a.txt (Tuesday, 20 October 2026):
Updated Tuesday; teach a definition, then ask learners to recall it.

guided/note-b.txt (Thursday, 22 October 2026):
Updated Thursday; after trying recall, we approved a compare-two-actions practice.

guided/note-c.txt (Friday, 23 October 2026):
How to choose a website font: compare letter shapes and spacing at the sizes you will use.

guided/approval.txt (Friday, 23 October 2026):
Use Thursday's revision for the companion.
Practice question

Which note should you use for the companion, which should you reject, and which note is irrelevant?

Check your answer

Use note-b.txt because approval.txt picks Thursday's revision. Reject note-a.txt because Thursday's decision replaced Tuesday's proposal. Ignore note-c.txt because font selection has nothing to do with this task. The dates help you follow the sequence of choices.

Next steps

You can practice checking tasks in your browser under Your saved work in the sidebar, which saves your progress in your browser. When you want to practice setting clear task boundaries, open Start a task. When you are ready to compare drafts against sources, open Check a draft.

Source References