Everyday AI · Module 6

Reconcile a complete task register

Suggested time: 30 minutes.

Guided snapshot G6

Snapshot date: 2 October 2030. The following meeting notes include agreed tasks and other entries. “Blank” means the field was empty. A dependency says what the work relies on; it does not supply a missing status.

• G6.01: Agreed task T01. Action: Draft welcome script. Owner: Mira. Due: 3 October 2030. Dependency: none recorded. Status: Complete.
• G6.02: Agreed task T02. Action: Prepare sign-in sheet. Owner: Jo. Due: 4 October 2030. Dependency: none recorded. Status: complete.
• G6.03: Agreed task T03. Action: Request room confirmation. Owner: Lee. Due: 4 October 2030. Dependency: none recorded. Status: Done.
• G6.04: Agreed task T04. Action: Review handout wording. Owner: Arun. Due: 5 October 2030. Dependency: handout draft received. Status: In progress.
• G6.05: Agreed task T05. Action: Check projector availability. Owner: Dev. Due: 6 October 2030. Dependency: venue reply. Status: Not started.
• G6.06: Agreed task T06. Action: Prepare room layout. Owner: Sam. Due: 7 October 2030. Dependency: venue confirmation pending. Status: Blocked.
• G6.07: Agreed task T07. Action: Draft volunteer brief. Owner: Nia. Due: 4 October 2030. Dependency: none recorded. Status: Complete.
• G6.08: Required task T08. Action: Check access information. Owner: blank. Due: 6 October 2030. Dependency: venue reply. Status: blank.
• G6.09: Agreed task T09. Action: Review invitation wording. Owner: Jo. Due: 6 October 2030. Dependency: invitation draft received. Status: working.
• G6.10: Agreed task T10. Action: Prepare feedback form. Owner: Lee. Due: 8 October 2030. Dependency: none recorded. Status: not started.
• G6.11: Agreed task T11. Action: Create signage text. Owner: Dev. Due: 5 October 2030. Dependency: none recorded. Status: done.
• G6.12: Agreed task T12. Action: Check supply list. Owner: Mira. Due: blank. Dependency: none recorded. Status: in-progress.
• G6.13: The note taker copied G6.04 again. Agreed task T04. Action: Review handout wording. Owner: Arun. Due: 5 October 2030. Dependency: handout draft received. Status: In progress.
• G6.14: Decision: Use one sign-in desk.
• G6.15: Suggestion: Consider a second projector. No additional task or owner was agreed.

Existing register supplied with guided snapshot G6

The fictional coordinator also provides this existing 12-row register. Treat it as a second input to compare with the meeting notes, not as an answer that is already checked. R6 labels identify register rows; G6 labels identify meeting notes. Empty owner, due or status cells below are genuinely blank in this supplied register. Keep them in the original copy.

----------------------------------------------------------------------------------------------------------------------------------- Register row Task ID Action Owner Due Dependency Original status -------------- ---------- ------------------------------ ---------- ---------------- ---------------------------- ----------------- R6.01 T01 Draft welcome script Mira 3 October 2030 none recorded Complete

R6.02 T02 Prepare sign-in sheet Jo 4 October 2030 none recorded complete

R6.03 T03 Request room confirmation Lee 4 October 2030 none recorded Done

R6.04 T04 Review handout wording Arun 5 October 2030 handout draft received In progress

R6.05 T05 Check projector availability Dev 6 October 2030 venue reply Not started

R6.06 T06 Prepare room layout Sam 7 October 2030 venue confirmation pending Blocked

R6.07 T07 Draft volunteer brief Nia 4 October 2030 none recorded Complete

R6.08 T08 Check access information 6 October 2030 venue reply

R6.09 T09 Review invitation wording Jo 6 October 2030 invitation draft received working

R6.10 T10 Prepare feedback form Lee 8 October 2030 none recorded not started

R6.11 T11 Create signage text Dev 5 October 2030 none recorded done

R6.12 T12 Check supply list Mira none recorded in-progress -----------------------------------------------------------------------------------------------------------------------------------

Compare every R6 row with its corresponding G6 task note. Account separately for the copied T04 mention, decision and suggestion in G6.13 to G6.15. A task appearing once in each input is still one task, not two. If the inputs agree, record that agreement; do not invent a discrepancy to justify a correction. Preserve both original inputs and place any proposed standard values in a separate review register.

The original status strings, task IDs, owners, dates and dependencies must remain recoverable. You may use the status dictionary in Lesson 3 for the review copy. The target is a complete register of 12 distinct tasks, not a sample of the first few rows.

Part A Classify and extract

Spend about 10 minutes.

1. Save the G6 meeting notes and supplied R6 register unchanged.
2. Label each meeting-note entry as an action, duplicate mention, decision or suggestion. Match every register row to its note by task ID.
3. Write a complete prompt using the Lesson 5 structure, adding an explicit instruction to reconcile the existing register against the meeting notes. Include all G6 notes, all 12 R6 rows and the full status dictionary.
4. Produce the full review register with the eight required columns and both G6 and R6 references. Do not stop after an illustrative subset.
5. Compare every field of every R6 row with its G6 note, including owners and dates. Record agreements as well as any genuine differences. Keep T08’s missing owner and status and T12’s missing due date visible.

The completed register should have one row for every ID from T01 to T12. Matching this row count alone is insufficient: a repeated task plus an omitted task could also total 12. Check the actual IDs.

Part B Preserve and explain proposed cleaning

Spend about 7 minutes.

Make a change log containing:

• The original and repeated source labels for T04, the fields you compared and how both sources remain traceable.
• Every status that you standardised, with its original spelling and mapped value.
• Each missing field, the displayed gap and a suggested clarification question. Do not invent an answer or send the question.

A question such as “What is T08’s current status?” is a proposed follow-up, not evidence that it is blocked. List G6.14 and G6.15 separately so neither silently disappears.

Part C Calculate and reproduce

Spend about 8 minutes.

Use the Lesson 4 inclusion rule. Record:

Snapshot: One row represents: Included task IDs: Duplicate, decision and suggestion exclusions: Task IDs recorded Complete: Numerator in tasks: Denominator in tasks: Missing-status task IDs and count: Calculation before rounding: Percentage rounded to one decimal place: Calculator check: One sentence explaining exactly what the percentage means:

Check that the status-group counts sum to the denominator. Count by task IDs rather than relying on the appearance of the table. Independently verify the percentage with a calculator.

Part D Review two tempting mistakes

Spend about 5 minutes.

Explain why each supplied report is wrong for the requested measure:

1. “There are 13 tasks because there are 13 task mentions.”
2. “Five of 11 tasks are complete, or 45.5%; leave out the task with no status.”

Save the original response, any corrected register, the change log, the reconciliation, your calculation record and an accept-or-revise decision. If the AI did not make these supplied mistakes, do not say that it did.

Offline route: build the register yourself before opening the reference answer. Make the same ID, status and calculator checks. Label any comparison with the supplied solution as an offline review.

Independent assignment Organise a fresh snapshot

Suggested time: 20 minutes.

Independent snapshot I6

Snapshot date: 1 November 2030. Do not use G6 facts. The same status dictionary and inclusion rule apply.

• I6.01: Agreed task A01. Action: Draft session outline. Owner: Arun. Due: 3 November 2030. Dependency: none recorded. Status: done.
• I6.02: Agreed task A02. Action: Review session outline. Owner: Nia. Due: 4 November 2030. Dependency: outline draft received. Status: working.
• I6.03: Agreed task A03. Action: Prepare name cards. Owner: Mira. Due: 3 November 2030. Dependency: none recorded. Status: Complete.
• I6.04: Agreed task A04. Action: Draft venue questions. Owner: Sam. Due: 3 November 2030. Dependency: none recorded. Status: Done.
• I6.05: Agreed task A05. Action: Check microphone availability. Owner: Dev. Due: 5 November 2030. Dependency: venue reply. Status: not started.
• I6.06: Agreed task A06. Action: Prepare supply checklist. Owner: Jo. Due: 4 November 2030. Dependency: none recorded. Status: complete.
• I6.07: Agreed task A07. Action: Confirm room layout. Owner: Sam. Due: 6 November 2030. Dependency: room measurements pending. Status: blocked.
• I6.08: Required task A08. Action: Review access wording. Owner: blank. Due: 5 November 2030. Dependency: access information draft received. Status: blank.
• I6.09: Agreed task A09. Action: Draft feedback questions. Owner: Lee. Due: 4 November 2030. Dependency: none recorded. Status: Complete.
• I6.10: Agreed task A10. Action: Check activity timings. Owner: Arun. Due: 6 November 2030. Dependency: session outline draft received. Status: in-progress.
• I6.11: Agreed task A11. Action: Prepare welcome slides. Owner: Dev. Due: blank. Dependency: none recorded. Status: Not started.
• I6.12: Agreed task A12. Action: Draft volunteer checklist. Owner: Mira. Due: 4 November 2030. Dependency: none recorded. Status: Done.
• I6.13: The note taker copied I6.04 again. Agreed task A04. Action: Draft venue questions. Owner: Sam. Due: 3 November 2030. Dependency: none recorded. Status: Done.
• I6.14: Decision: Use paper name cards.
• I6.15: Suggestion: Add a second workshop session. No action was approved.

Your task

Without copying the answer, prepare a complete 12-row register with the eight required columns. Use your own complete prompt, or mark an offline extraction. Keep the source intact and provide a proposed-change log.

Your evidence record must account for every I6 entry, name the exact completed task IDs, show the numerator and denominator, include the missing-status task in the denominator and show a calculator-checked percentage rounded to one decimal place.

Finish with two sentences: one explaining the result, and one naming the unresolved information. Make no claim about overall workshop readiness. Do not assign a missing owner, update a live task list, send follow-ups or make a new commitment.

Suggested allocation: 8 minutes to extract and check rows, 5 minutes to log cleaning and reconcile notes, 5 minutes to calculate and verify, and 2 minutes to record the review decision.

Formative self-assessment rubric

Mark “met” or “needs correction” for each criterion. There is no separate numerical pass score.

• Classification: Actions, repeated mentions, decisions and suggestions are correctly distinguished. An unowned required action stays in the register.
• Complete register: All 12 distinct task IDs appear exactly once. Action, owner, due, dependency, original status, review status and sources are faithfully recorded.
• Traceable cleaning: The original pack is retained. Every changed status, duplicate handling and missing-field display has a reason; proposed standard values do not erase originals.
• Missing values: Unknown owner, due date and status remain visible. A dependency is not used to invent a status.
• Reproducible calculation: Included and completed IDs, exclusions, numerator, denominator, missing-status count and rounding rule are shown. The arithmetic is independently checked.
• Accurate interpretation: The result measures the share of distinct tasks recorded Complete, with tasks as its unit. It does not claim a share of work hours or overall readiness.
• Honest and safe record: Live outputs or offline work are labelled accurately; corrections and the final review decision are saved; no external records are changed.

Correct a missing task, altered value, invented assignment or wrong denominator before accepting the work. A plausible percentage cannot compensate for an incomplete register.

Self-check Before reading the answers

Spend about 5 minutes answering, then 5 minutes reviewing the solutions.

1. How does an agreed action differ from an unaccepted suggestion?
2. What does one row represent in this module’s register?
3. Why keep both an original-status column and a proposed review-status column?
4. Does “none recorded” establish that a task has no dependencies?
5. Can you merge two entries just because their action wording looks similar?
6. Why is a blank status not the same as Not started?
7. Under the module’s rule, does a missing-status task stay in the denominator? Does it enter the numerator?
8. What are the numerator and denominator in a task completion percentage?
9. What should you do with two records that share an ID but have conflicting statuses and no evidence of which is current?
10. Why can “41.7% of tasks are recorded Complete” be supported while “the workshop is 41.7% ready” is unsupported?
11. What is missing from a numeric column headed only “Effort”?

Independent transfer T6 Meeting excerpt

Use this new, complete fictional snapshot. No earlier source applies. The meeting record is the authority for agreed work; there are no hidden task records. One row represents one distinct piece of agreed work. Merge mentions only when they refer to the same deliverable and owner. Status labels are Complete, In progress, Not started, or Not provided; “finished” maps to Complete. Keep missing fields visible and ideas separate. Do not contact anyone.

• T6.1: Mira said, “I finished the welcome sign for the 6 October 2031 workshop yesterday.”
• T6.2: Lee said, “I'll review the handout by 4 October once the draft reaches me. I'm already working on the review.”
• T6.3: The coordinator said, “We need the room access information checked by 5 October before the workshop.” Jo and Arun both said they could help; nobody was assigned.
• T6.4: Later, Jo said, “Mira's welcome sign is finished, so we can move on.”
• T6.5: Dev wondered whether a second sign would help. The group did not agree to add it.
• T6.6: The team chose one sign-in desk.

Build the register and a short note that accounts for every source entry. Calculate the completion percentage for the agreed work, using every distinct agreed task in the denominator. Explain the evidence for each row and the follow-up you would need. Include one item that can be accepted without correction. Choose your own brief and output format; no starter prompt or trap checklist is supplied. Save an attempt before opening the separate answer page.

Read the separate answers and explanations