Lesson 09 · Activity 02

Build the Assembly Line

A safe automation is a sequence of small, checkable steps. Here you'll lay out the assembly line for a recurring report, mark where your sign-off belongs, and identify what must be de-identified.

Work through it

0 of 4 done

Read the recurring task.
Write what each stage does and its control.
Mark the human sign-off and the de-identification point.
Compare to the model answer.

The recurring task

Weekly attendance summary: every Friday you pull attendance from the LMS export, total it by section, drop it into the standard summary template, and post it to the program’s shared site.

Your assembly line

For each stage, write what it does and the control that keeps it safe. Saved on this device.

Stage	What it does	Control
Extract
Verify
Assemble
Sign off
Submit / Post

What here must be de-identified, and why?

Saved automatically on this device.

Reveal model answer

Stage	What / Control
Extract	AI reads the LMS export → ask for a structured table of counts by section.
Verify	Spot-check a couple of section totals against the export.
Assemble	Merge the verified counts into the standard template (fixed format = checkable).
Sign off	YOU review and approve — the gate before anything goes public.
Submit / Post	Posts to the shared site only after sign-off; log that it ran (audit trail).

De-identify: the LMS export lists individual students. Reduce to aggregate counts by section before assembly — the summary needs totals, not names. Takeaway: the sign-off sits right before the one irreversible step (posting), and PII is dropped as early as possible.