Action Register — User's Manual

1. What this tool is

The house action-item and punch-list register: everything somebody has to do, with a responsible person, a baseline date, a rolling forecast, and verified closure — an item is only closed when the person who raised it (or the owner) has verified the work is actually done. Three working rules make it honest:

The baseline target is frozen the day the item is raised. The forecast is the rolling, current best estimate — and every forecast move requires a reason, kept forever in the item's forecast history.
Classification gates everything. Every person has a maximum clearance; an item classified above your clearance does not exist for you — not in the list, not in the detail, not in print.
The register is append-only where it matters: diary notes are never edited, and a forecast move never erases the previous date.

2. Signing in

Open action.uerllc.com. You land on a Cloudflare Access sign-in page.
Enter your work email address exactly as registered, and ask for the code.
Cloudflare emails a one-time PIN. Enter it and you are on the register.

If the address is wrong or not authorized, nothing happens. No error message, no code — the gate gives nothing away. Check spelling and spam first; if still nothing, email the CTO (rainer.tesch@uerllc.com) — your address is probably not on this tool's list yet.

If sign-in succeeds but the page says Not authorized with your email address, you passed the gate but are not in the register's people list — email the CTO. Your first sign-in on a new browser sends the tool operator a one-line notification — normal monitoring, not an alarm.

3. Who can do what

Role	What you can do
Viewer	Read the register and item sheets. The raise form and all update controls are hidden.
Editor	Raise items, update status/priority/responsible, move forecasts (with a reason), write diary notes, and verify & close items you raised.
Owner	Everything an editor can do, plus cancel items, close any item, and maintain the People & clearances page (a nav link appears for the owner only).

On top of the role, your clearance (1 Public · 2 Commercial in Confidence · 3 Internal · 4 Controlled · 5 Confidential, per UER-2026-COR-STD-0012) caps what you see and what classification you may give a new item — the picker simply does not offer levels above yours. The top right of the header shows your name, clearance, and role.

4. The register

One row per item: serial, subject, priority, status, responsible, date raised, baseline, forecast, variance, and classification. Priority pills run Critical High Medium Low; status pills run Open In progress Blocked Closed Cancelled.

Reading the dates:

Baseline — the target frozen at raise. It never moves.
Forecast — today's honest date. Red with a ⚠ when an open item's forecast has passed.
Variance — "on baseline", "+n d slip", "−n d early", or the closed date for finished items.

The toolbar: + Raise item, Print register (A4 landscape, with a print header naming who printed, when, the clearance the view was limited to, and the item count), a show closed checkbox (closed and cancelled items are hidden unless ticked), and filters by responsible, status, and priority.

5. Raising an item

Field	What to enter
Subject *	Verb-led, one line: "Submit …", "Confirm …", "Repair …".
Details	What does done look like? Write it so the raiser can later verify it.
Responsible *	Who does it. Only people flagged assignable appear; it defaults to you.
Baseline target date	The committed date — frozen the moment you raise. Choose honestly; slips show against it forever.
Priority	Critical / High / Medium (default) / Low.
Classification	Defaults to Internal; capped at your own clearance.

Raising assigns the serial AIR-YYYY-NNNN — serials are never reused. Click a serial anywhere to open the item sheet.

6. The item sheet

Everything about one item: the full details, the meta block (raised by, responsible, baseline, rolling forecast, closed-by), then the working cards:

Update — change status (setting Blocked asks what it is waiting on), priority, or reassign the responsible person, then Apply.
Move forecast — new date plus a mandatory reason. No reason, no move. Every move lands in the forecast history below (an item never moved reads "still on baseline").
Verify & close — visible only to the raiser and the owner, and only while the item is open. Closing means: I have verified the work is done. The responsible person can never close their own item unless they also raised it.
Cancel item — owner only, with a cancel note.
Diary — dated notes, append-only. "Called the vendor, delivery slips to Thursday" — write it the day it happens. A correction is a new note, never an edit.

The sheet prints A4 portrait (Print item, top right) with a header naming the serial, the classification, and who printed when.

7. People & clearances (owner only)

The owner page lists every person with name, email, maximum clearance, role, and an assignable flag (assignable people appear in the Responsible picker — no app access needed for that). Changes are saved per row; new people are added with the form. App entry itself is governed by the Cloudflare Access policy — adding a person here does not by itself let them through the gate.

8. When something is wrong

The gates fail closed on purpose: an expired session means sign in again, and an item link that errors for you may simply be classified above your clearance. Anything else — a wrong date, a missing person, a close that should be possible but is not offered — email the CTO (rainer.tesch@uerllc.com) with the serial, the time, and what you were doing.