Sheet-connected pipelines

Build-along · ~12 min at your own keyboard

The pipeline pattern: a workflow gathers or computes, and its last step writes rows into a sheet (via API or file). The sheet stays the interface your business already knows; the filling becomes invisible. Perfect for a lead tracker that fills itself.

Your starter: Exit-ticket tally pipeline

Workflow steps

Make it yours: Name your exit-ticket format and its fields, set the one pattern that counts as a student identifier in your scans, and decide the one reason a batch gets flagged for a person on sight.

EXIT TICKETS: [course], scans at [path], period [n], day [n]

1. Read the scans. Keep the fields: period, day, question, answer tally.
2. Confirm no student goes in by name: any name or ID on a scan is dropped before step 3, and the scan is noted.
3. Flag a batch when: a question has no tally, a tally exceeds the class size, the day is missing, or a scan carried a name.
4. Write the tallies to the [course]-checks tab, one row per question, with the one question a person answers on sight.

Never score a student. Never decide who needs reteaching; tally it, and the decision stays yours. If a batch looks like a placement question, write [YOUR CALL: the reteach group] and stop.

The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.

Do this

0/4

Share what happened

Paste your pipeline description, two-run results, and the threshold rule.