Fictional teaching practice pack. Replace all example inputs with your own material. Keep unknowns, ownership and approval status explicit.

BLANK OUTLINE
Period, original target version and timing:
Actual results, denominator, evidence and unfinished work:
Gap:
Possible causes, contrary evidence and unknowns:
Reason for choosing KPT or YWT:
Practice to retain or learning (status and evidence):
One proposed change, purpose and output:
Owner, date and time, dependencies and effort cap:
Separate output acceptance from effect observation:
Approval, implementation and observed-result status:
Follow-up timing and continue/adjust/stop conditions:

FICTIONAL MATERIAL AND WORKED STATEMENT

Original fictional teaching material: the overall configuration task contains 12 units. Eight in this week's plan were due by the agreed check-in; six are complete and two await interface information. The exact effect on Friday's demo and the full causes remain open. There are no measurements of customer waiting or efficiency. Today, tomorrow, and Friday are relative exercise times; replace them with actual dates when adapting the material.

At this week's agreed check-in, eight configuration units were planned and six were complete; two await interface information. The 12-unit overall task is not this week's denominator. The gap is two units, while full causes and the exact Friday demo impact are still being checked.

We propose confirming required information, contacts, and availability before the next cycle to expose dependencies earlier. The owner, actual deadline, and effort cap need agreement; the change is not approved or performed. First check the list and follow-up arrangements for unknowns. At the next agreed check-in, inspect delivery status and added effort before deciding whether to continue, adjust, or stop. Current material does not establish an efficiency improvement.

Check: Can each claim be traced to evidence? Are proposals still marked pending? Does the main brief preserve conditions? Is one next action inspectable?