What you're about to see
During a large action, the local has to know — every week, for every member — who actually walked the line and for how long, because that record decides who receives strike benefits. Strike TimeKeeper replaces the paper sign-in sheet: members check in and out from their phones, the system verifies they're at the site, and every week the local gets a finished eligibility report.
This walkthrough is the real interface with sample data. Every button label, screen, and rule is what runs at Local 332 today — roughly 550 members, about 2,600 verified check-ins a week, in daily use since March 2026. No real member appears here.
Steps 1–4 · The member
Log in, clock in and out, fix a missed punch, get help — all from a phone.
Steps 5–9 · The local's staff
Who's on the line, any member's week, correction requests, things worth a look, the GPS map.
Step 10 · The weekly report
What the benefits process actually receives every Sunday.
Step 11 · Shuttle
The companion app that keeps drivers moving members to the sites.
How to use this
Click through the steps on the left (or use → and ← on your keyboard). Anything highlighted in amber is something you can try — tap the clock button, submit a request, approve one.
About ten minutes end to end.
Logging in takes an email and a PIN
Log in
Enter your email and PIN to continue.
What you're seeing
No app store, no passwords to manage. A member opens the link on their phone once, adds it to their home screen, and signs in with email and a 4–8 digit PIN.
Why it matters
New accounts require a registration code issued by the local — “From your strike captain” is the placeholder on the field. Only people the local has admitted can create an account, and members who resign are deactivated by staff and can no longer sign in or see the roster.
One button. Two taps. GPS-verified.
| 09/09/2026, 09:12 PM | OUT |
| 09/09/2026, 03:00 PM | IN |
| 09/08/2026, 01:05 PM | OUT |
| 09/08/2026, 06:58 AM | IN |
What you're seeing
The clock button is deliberately a two-tap control. The first tap arms it (it turns amber and says “Tap again to Clock IN”); the second tap punches. If you don't tap again within ten seconds it quietly resets. That's what stopped accidental punches from a phone in a pocket.
Why it matters
Every punch records the time and the member's GPS position against the local's registered picket sites. GPS never blocks a punch — a member with a dead location service still gets their time recorded — but every punch is classified on-site or off-site, and off-site ones are visible to staff for review rather than silently counted.
Forgot to clock out? Ask, don't edit.
Report Missing Punch
What you're seeing
A member can't change their own record. They can only request a correction — which punch, what time, and a reason from a fixed list. The request goes to the local's staff. Nothing changes until someone approves it.
Why it matters
This is the difference between a spreadsheet and a system of record. The member sees the same numbers the office sees; corrections are made on the record, by staff, with a reason attached — and every one of them is in the audit trail.
A help desk that answers at 3 AM
What you're seeing
The Need Help? button opens a built-in assistant. It answers the routine questions in plain English — timecard, GPS, missing punches, login. If it can't handle something, the thread goes straight to the support team, who reply in the same conversation.
Why it matters
An office of two people can't field 550 members' questions by text. Most of those questions have the same answer. This takes them off the staff's phones and leaves them the cases that actually need a person.
Staff get a version of the same thing — a lookup assistant that answers “who's on shift right now?” or “show me everyone under 23 hours” from the live data.
Who's on shift, right now
Who's ON SHIFT now · 4
| Name | Site | Location | Last Punch | |
|---|---|---|---|---|
| Whitfield, Dana | d.whitfield@example.com | Teamster Tent (Holly Rd) | ON SITE | 06:58 AM |
| Cole, Terrence | t.cole@example.com | ER Entrance | ON SITE | 07:04 AM |
| Nandan, Priya | p.nandan@example.com | Main Entrance | NEARBY | 07:11 AM |
| Okafor, Ruth | r.okafor@example.com | Teamster Tent (Holly Rd) | ON SITE | 07:15 AM |
What you're seeing
The staff console. The first tab is the live picket line — every member currently clocked in, which site, how their location classified, and when they punched.
Why it matters
A captain at the tent, or Kelly at the office, can see the whole line without walking it. The count badge is the active roster — 547 members with live accounts.
The tabs across the top are the whole staff workflow: look anyone up, review corrections, see what needs a look, run the weekly report.
Any member. Any week. Every punch.
View / Edit Punches
| Time (Detroit) | Type | Site | Location | Source | Actions |
|---|---|---|---|---|---|
| 09/09/2026, 09:12 PM | OUT | ER Entrance | ON SITE | clock | |
| 09/09/2026, 03:00 PM | IN | ER Entrance | ON SITE | clock | |
| 09/08/2026, 01:05 PM | OUT | Teamster Tent (Holly Rd) | NEARBY | clock | |
| 09/08/2026, 06:58 AM | IN | Teamster Tent (Holly Rd) | ON SITE | clock | |
| 09/07/2026, 01:10 PM | OUT | — | UNAVAILABLE | EDIT | |
| 09/07/2026, 07:02 AM | IN | Teamster Tent (Holly Rd) | ON SITE | clock |
What you're seeing
Type an email, pick a week, and the member's whole record is there: total hours, progress against the 24-hour goal, Met or Not Met, and every punch with its site, its GPS classification, and where it came from.
Why it matters
That EDIT chip on Monday's clock-out is the audit trail showing itself — that punch was added by staff, not by the app, and it says so. Trail opens the member's whole day, view-only. A member's hours can be re-derived from this table at any time; the weekly total is never a number someone typed.
Corrections go through a queue
Punch Edit Request Queue
| Worker | Original Punch | Requested Times | Reason | Created | Status | Actions |
|---|---|---|---|---|---|---|
| Baptiste, Kevin k.baptiste@example.com |
OUT @ 09/08 07:41 PM | Actual: 6:55 AM → 7:41 PM Requested: 6:55 AM → 1:30 PM UPDATE_OUT 1 punch |
Forgot to clock out | 09/08 7:42 PM | Pending | |
| Marchetti, Lena l.marchetti@example.com |
— (missing IN) | Actual: — → 9:05 PM Requested: 3:00 PM → 9:05 PM ADD_IN 1 punch |
Phone died | 09/09 9:06 PM | Pending |
What you're seeing
Every correction a member asks for lands here. The row shows what's on the record now, what they're asking for, and — computed by the system — the exact action approving it would take: update one punch, add one, or flag it for review.
Why it matters
Staff approve or reject with one click and a reason stays attached. Approving writes the punch marked as a staff edit and recalculates the member's week. The member sees the result on their phone. Nothing is retyped, nothing is lost.
Patterns, not accusations
Needs Attention
What you're seeing
The system watches for things worth a second look — two members on one phone, repeated off-site punches, a shift that never closed — and writes each one as a plain sentence with the innocent explanation already in it.
Why it matters
That disclaimer at the top isn't decoration; its wording is fixed. This is a union tool used by union staff on union members. It surfaces the record and lets a person decide. It never labels anyone. See the evidence opens the punches behind the sentence; Looks fine closes it.
Every punch, on the map
Punch Maps — GPS Diagnostics
What you're seeing
One real day at one Local 332 site. Each dot is a check-in, colored by how it classified. The blue circle is the geofence the local drew around the site. The green cluster is the tent; the second cluster down the road is the other gate.
Why it matters
The red dots are the point. Those punches were recorded — nobody lost their time — but they're marked off-site, and staff can see them. A paper sign-in sheet can't tell you where the pen was.
Behind this map: a GPS accuracy dashboard by site and hour, and a per-member integrity audit that exports to Excel, sorted by risk.
What the benefits process receives
Weekly Report — Sep 6 – Sep 12, 2026 .xlsx · three sheets
| Last Name | First Name | Total Hours | Days Worked | Missed Punches | |
|---|---|---|---|---|---|
| Cole | Terrence | t.cole@example.com | 24.02 | 3 | 0 |
| Nandan | Priya | p.nandan@example.com | 24.10 | 4 | 0 |
| Okafor | Ruth | r.okafor@example.com | 26.35 | 4 | 1 |
| Vega | Marisol | m.vega@example.com | 24.05 | 4 | 0 |
| Whitfield | Dana | d.whitfield@example.com | 24.00 | 2 | 0 |
What you're seeing
At the close of each week — Sunday, 7 AM — staff download one Excel file. Sheet one: everyone who met the goal. Sheet two: everyone who didn't, and by how much. Sheet three: every punch behind every number, paired into shifts, with a flag on anything that looks off.
Why it matters
This is the deliverable. The local sends it to the benefits process as-is. The goal (24 hours here), the week boundary, and the grace threshold are all set by the local. The format can be shaped to match what your department already takes in.
Keeping the line supplied with rides
Today's Drivers - Thursday, September 10, 2026
Live shuttle lineup for today.
What you're seeing
The picket sites aren't where members park. Shuttle is the board that keeps drivers moving people between them. Anyone on the line can open it and see who's driving right now with a one-tap Call or Text. Drivers claim hourly slots themselves off a capacity-limited grid — two cars by day, one at night — instead of a coordinator running a spreadsheet.
Why it matters
Same email-and-PIN sign-in as the clock. Staff can import a roster, override capacity, and cap weekly hours per driver. It's small, it's boring, and it's the thing that answers “how do I get to the tent?” at 5:45 AM.
What it takes to run this somewhere else
Nothing to install on site
Members use their own phones. No hardware, no kiosks, no servers for the local to run.
Hosted and maintained
Fully hosted on managed cloud infrastructure. Local 332 runs ~550 members and a few thousand check-ins a week with headroom well beyond that.
Configured per local
Picket sites and geofences, the weekly hours goal, the week boundary, and the registration code are all set per local. A new action can be live in days.
Fits the benefits workflow
The weekly report was built around what the benefits process needs. Its format can be adapted to an existing intake.
The short version
Verified digital check-in replaces the sign-in sheet. The weekly eligibility report is produced automatically. Staff review and correct records on the system, with a full audit trail. Members see the same numbers the office sees.
Built by a striking RN during a live strike, because the Local needed it. In daily use since March 2026.
The fastest way to see the rest is a 30-minute walkthrough on the live deployment.