Each reader station runs a small local agent that posts tag taps to this app. Register the station here, then paste its token into the agent's config. A token can only mark people present at its board — it can't read data or mark anyone absent.

Attendance rules. Both are minutes from the start of the shift half (6am / 6pm Eastern). Someone with no tap by the absent cutoff counts absent; there's no job to wait for, the status just resolves once the clock passes it.

The T1 corrections widget shows two fractions over the same denominator — operations corrections pending for the crew at shift start. The early window is the countdown at the top of the shift; the color bands apply to both fractions and the Quality ring segment, as a % of the pending count cleared (green at or above, then amber, red below). Changes apply from now on — past ring segments keep the color they earned.

Bulk-create from a CSV — columns: firstName,lastName,shift,title,role,passcode,line,segment,site,function (header row required; line, segment, site, function optional — function defaults to Operations, and only Operations counts toward the Scorecard headcount).

Add a production line. Lines start empty — batches are created on the Readiness tab, then staged onto a line and started there, so a batch is only ever entered once. The segment drives the tier rollups (Vial = Line 5 & 7, Syringe = PFS2 & 3).

Point value awarded when each task is marked complete — this table edits the currently open line/batch. New batches start from the saved defaults: enter labor once, save it as defaults, and every batch created after that carries the values automatically.

Two non-destructive levers for the scoreboard. Neither edits any module's own records — clearing the date or deleting an adjustment puts everything back.

Score from date

Completions before this date (Eastern) stop counting on every scoreboard period — the fresh-start switch. Leave empty to count everything.

Manual adjustments

Add or deduct points for a person — or a whole shift, without naming anyone — with a reason. An adjustment counts as of the moment it's made, so it lands in the current day/week/month totals like any completion.

Point value awarded when each cleaning item is checked off, per room and cleaning type.

Define reusable cleaning types. The matrix says which surface needs cleaning with which chemical; every "yes" cell becomes a building block you sequence into the flow. Points are derived: FTEs × time (min) ÷ 60 × multiplier — labor hours × multiplier.

Assign a cleaning type to each room at each frequency. Leave a cell "Not applicable" if the room doesn't require a clean at that frequency. Rooms left entirely unassigned fall back to the legacy per-requirement status.

Hide or show top-level tabs and their child features app-wide. Hidden tabs disappear from the top nav for everyone (including Admin).

Checklists a board task must work through before it can be completed. Questions is an ordered list of yes/no, multiple-choice and free-text items. Parts table lists parts by description, photo and identifier, and the operator marks each one suitable or not. Editing a checklist never changes a batch that has already started answering it.

Which task each checklist is attached to:

Standard duration (minutes) per changeover step, used to pace the board (the gold flag = position at shift start + 12h of these standards). A step passes automatically once the board tasks listed under “Completed by” are done — that is what advances the hiker. Tasks marked not needed count as satisfied, so a step whose work is N/A is stepped over rather than stalling the bar.

Icon for the 6am/6pm shift-change markers on the pacing bar:

Pick a color and letter for each shift's scoreboard badge, or upload a small square image to use instead. Original artwork only — no copyrighted logos.

The repeating crew rotation. Each cycle day maps a day crew (6a–6p) and a night crew (6p–6a). The anchor date is what cycle day 0 lands on. Shifts change at 6am/6pm Eastern.

Named manufacturing types, each a list of MFG task steps cascaded onto a batch's manufacturing board when applied. Renaming a step here is treated as a brand-new step for point-value purposes (its old point value stays under the old name) — set its points again after renaming.

One recipe per product. Cascades onto a batch when applied — MFG type and its point values, thaw checks, hold/TOR rows, the pacing template, the parts needed with their descriptions and serial numbers, and documentation forms. Applying a recipe to a batch that already has logged thaw checks, started hold timers or a pacing template preserves that work; it never overwrites it. Duplicate starts a new product from an existing one — everything copies except the name.

Named selections over the master pacing steps. Each template chooses which steps apply for a batch and their timing — the board wiring is shared. Non-applicable cell-mapped steps default their board cells to "not needed" when the template is applied. Editing a template doesn't change live batches automatically; each shows a "refresh" option.

Check a box to grant that capability to a role. Roles are just groupings — you can move any capability to any role. One rule is enforced: at least one active user must always be able to manage permissions (so the system can't lock everyone out).

Download a full copy of everything — users, lines, batches, points, cleaning data, audit log — as one file. Keep it somewhere safe (email to yourself, a shared drive); don't rely on the server's disk alone.

Restore replaces everything currently in the app with the contents of the file you upload — all current users, lines, batches, and history will be gone. This can't be undone.

Run this after changing any point assignments (task points, cleaning types, points per page, the cleaning split) to apply them to history: every completed batch task, documentation page, and logged clean is re-scored against the current point settings, cleaning credit is re-split, and full names are backfilled on old completions where the match is unambiguous.