Sign In
Every Bluework feature, replayed live.
This is the demo manual: twenty-six interactive walkthroughs, one per feature. Nothing here is a screenshot — each panel replays the actual workflow, and the buttons are real: click them to drive the demo yourself, or just watch.
Roster & scheduling
See the risk before you publish the roster
Every draft week is graded 0–100 per person against the Safe Work Australia fatigue Code of Practice — long weeks, short rest, night work, no day off. Fix it in one click, then publish with a defensible record that you checked.
Roster fatigue risk — before you publish
1 of 9 staff at elevated (High/Severe) fatigue risk this week.
Ask for next week’s roster. Review why every name was picked.
Aegis drafts the week with a deterministic engine — the AI never picks people silently. Every candidate is scored on cost, fatigue, reliability, task performance, hazards and stated preferences, and every pick carries its reasons. You review, you apply — and applying creates the assignments without ever publishing.
- Deterministic scoring — same roster, same inputs, same draft, every time
- A one-line reason trail on every pick, with swap alternatives ranked
- Apply creates draft assignments only — publishing stays with you
The award says no — so Bluework says no
Pick an award rule pack and every roster change is checked against it: daily caps, rest floors, minimum engagements, qualification gating. Set each rule to advise — or to block the change outright, citing the exact clause.
- Rule packs for Retail, Hospitality and Building & Construction awards
- Off / Advisory (warn) / Extreme (block) — per module
- Every block cites its clause — “the actual clause, not a vibe”
Sam Lee: 11.5h on Thu 16 Jul exceeds the 11h daily limit (General Retail Industry Award 2020)
Shifts that fill themselves
Workers accept or decline their shifts, claim open ones, and trade through a swap marketplace — every claim re-checked for qualifications and overlaps, every swap approved by a manager before it moves.
- Open shifts are qualification-gated — unqualified claims bounce
- Swap pick-ups wait for manager approval, then reassign atomically
- Accept / decline states visible to the manager in real time
Upcoming shifts
14 JUL 06:00–14:30 · Morning run
Main Yard · 8h Assigned
Open shifts
15 JUL 10:00–18:00 · Floor cover
North Site · OPEN · 2 slots
Shift swaps offered
16 JUL 14:00–22:00 · Close
Offered by Sam Lee
Leave balances that accrue themselves
Annual and personal leave accrue pro-rata from approved timesheet hours — the NES floor, computed, not guessed. Workers request in two taps; managers approve with the balance right in front of them.
- NES-accurate accrual from ordinary hours worked (4 weeks/yr, pro-rata)
- Casual variant: no accrual, 25% loading applies instead
- Approved leave blocks the roster and the fatigue scorer sees it
“Family trip” · requested just now Pending
Time & pay
Clock in where the work is
One tap starts the day — GPS-checked against the job site’s 150m geofence. Pauses need a reason, every punch keeps its full event trail, and anything left running auto-closes at 23:59 flagged for review.
- Geofence check on every punch — off-site clock-ins get flagged, not blocked
- Pause / resume with reasons — the break record writes itself
- Forgot to clock out? Auto-close + “needs review”, never silent
Every minute priced against the award
Geofenced clock-ins land against the roster and flag themselves — over hours, short breaks, off-site punches. Approve the week and the award engine splits every shift across penalty rates, with super, on the spot.
- Variance chips per punch — “+0.4h vs roster”, “break 15m short”, “off-site”
- Penalty rates applied minute-by-minute, single highest rate per hour
- Approving locks the week and prices it — one CSV to payroll
Pay rules applied — award interpretation
| Rule | Hours | Rate | Pay |
|---|---|---|---|
| Base hourly rate | 29.5h | ×1.00 | $885.00 |
| Saturday penalty | 6.0h | ×1.25 | $225.00 |
| Evening (after 6pm) | 4.0h | ×1.25 | $150.00 |
Forgot to clock out? Fix it with a paper trail.
Workers don’t beg the manager to “just change it” — they send a change request. The manager sees the exact old → new diff with the reason, approves or rejects, and the original times stay in the audit history forever.
- Every edit is a request with a reason — no silent rewrites
- Approving a change re-opens the entry for re-approval, never auto-locks
- Original punch times preserved in the entry’s audit trail
Employee — My Timesheet
08 JUL 08:00–16:00 · Harbourside Site
30m break 7.5hCompleted
Manager — Change Requests (1)
08:00–16:00 → 08:00–16:30 · “Forgot to clock out”
08 JUL 08:00–16:30 · Harbourside Site
30m break · updated 8.0hPending re-approval
New pay guide? Upload the PDF.
When Fair Work moves the rates, drop the pay guide in. Bluework parses it, scores its own confidence, and shows you an old → new diff. Nothing applies without your review — and one click rolls it all back.
- Confidence-scored extraction — low-confidence rows are never pre-ticked
- You approve the diff; the live pay engine updates instantly
- Full rollback restores every prior rate, field for field
- Rates and award packs can differ per shop — same shift, right rate, every state
| Pay component | Current | New | Confidence | Apply |
|---|---|---|---|---|
| Saturday penalty | ×1.25 | ×1.50 | high | |
| Sunday penalty | ×1.50 | ×1.75 | high | |
| Public holiday penalty | ×2.25 | ×2.50 | high | |
| Casual loading | 25% | 25% | no change | |
| Overtime penalty | ×1.50 | ×1.60? | low confidence |
Bluework Protect
A record a regulator can replay
Psychosocial hazards are detected from work design — roster patterns, fatigue signals, site events. Every detection, verification and response lands in a hash-chained audit trail, exportable as a contemporaneous evidence pack.
- Structural signals from the roster — no surveillance of people required
- Every entry hash-chained to the last: tamper-evident by construction
- One-click evidence pack, mapped to the Code of Practice clause
Audit trail — hash-chained, tamper-evident
Bluework contemporaneous record
Detection you could defend in a tribunal
With the worker’s consent, on-shift audio is transcribed and screened against a protected lexicon — 77 phrases drawn from Australian court and tribunal decisions on workplace harm. Every hit keeps its context, its speaker, and its case citation, and a human approves before anything becomes a hazard.
- Consent-gated three times over: opt-in, clocked-in, PII redacted before analysis
- Each phrase cites the decision it came from — admins can’t water the list down
- AI verifies in context (“banter” gets rejected); a human makes the call
“Low job control” is a hazard. Bluework treats it like one.
Low job control is a named psychosocial hazard in the SWA Code of Practice. Bluework catches the situational signals workers actually say, aggregates repeated exposure across a crew, and points the fix at the work design — not the people who spoke.
- Situational signals, not accusations — “situations, not people”
- Repeated exposure aggregates: one remark is noise, a pattern is a hazard
- Recommended controls come from the Code of Practice, ready to assign
No consent, no monitoring. Provably.
Monitoring starts with a signed agreement, not a buried setting. Every worker’s consent lives in a register with its evidence — and where state law requires notice (NSW/ACT), Bluework serves the 14-day statutory period automatically before anything records.
- Consent recorded with evidence; workers without it are simply never recorded
- NSW/ACT: 14-day workplace-surveillance notice counts down, then auto-activates
- APP 11 erasure honoured — the consent evidence itself is retained
Consent register
Detection is half the duty. Here’s the other half.
Every confirmed hazard opens a guided response plan — the seven steps a WHS regulator expects, in order, with owners and dates. Sign-off seals the whole response into the tamper-evident record.
- Consultation step is mandatory — a WHS Act ss.47–49 duty, tracked
- Controls follow the hierarchy, cited to the Code of Practice
- Sign-off writes the final hash — the response becomes evidence
77 phrases. Every one survived a courtroom.
The detection baseline isn’t a vibes list — each protected phrase appeared in the evidence of an Australian court or tribunal decision, and admins can’t edit or delete them. Your own additions sit alongside, clearly marked.
- Protected rows are locked — the defensible baseline can’t be watered down
- Every phrase carries its case citation, visible in the admin
- Add custom categories — your own phrase sets go live for the next scan
Add your own
Comms on the floor
The whole crew, one thread away
Rooms for every crew, iMessage-style bubbles, photos inline, unread badges that tick live over WebSockets — no refresh, no “did you see my text”. Built for phones in high-vis pockets.
- Live delivery over WebSockets — the room reorders itself as messages land
- Photos and files inline; system messages track joins and leaves
- Unread counts per person, reset the moment they open the room
Hold to talk. Release to listen.
A browser-based radio: pick a channel, hold the big button, and your voice streams live to everyone on it — with earphone-button push-to-talk for gloved hands. Channels scope to everyone, a shop, or a hand-picked crew.
- Half-duplex live audio — one tap to join, instant to transmit
- Live speaker attribution: “🔊 Alice is talking…” on every listener’s screen
- Wired or Bluetooth earphone: short-press starts and stops transmit
Knowledge & work items
Say it on the floor. It becomes procedure.
A worker records a voice note; Bluework transcribes it, drafts the Document rewrite with AI, and queues it for human approval. Every paragraph stays traceable to the numbered recording that produced it — audit-grade by default.
- Voice → transcript → AI merge into the right Document section
- Nothing goes live without an admin’s Approve
- Reference index [1][2][3] ties every change to its source recording
Document Approval 1 pending review
That laminated binder page? It’s a Document now.
Drag in a scanned PDF or a photo of the old procedure, hit the magic wand, and Bluework OCRs it into a real, editable Document — reviewed in a preview before anyone relies on it.
- PDF or image in, structured Document out
- Extracted text lands in an auto-created section, ready to edit
- Preview the OCR before it joins the library
Quoted the wrong warranty? The Document catches it.
The micromanagement Bluework does so managers don’t have to: what’s said on the floor is data-matched against your own company documents. Tell a customer their repair carries a 12-month warranty when your standard says 6, and the mismatch — with the Document clause beside it — lands with the supervisor as a retraining flag, not a disciplinary one.
- Your Documents are the source of truth — every customer-facing claim checked against them
- Side-by-side evidence: what was said vs what the standard says, with confidence
- Routes to the supervisor for coaching — a knowledge-gap loop, and if the Document itself is stale, fix the Document
Off by default and switched on per worker — same consent gate as psychosocial detection.
Work items that keep the score
Folder-grouped task boards with priorities, due dates and overdue alarms — spawned from voice notes, form submissions or by hand. Compliance Mode even blocks assigning a task to someone who isn’t qualified for it.
- Live To Do / In Progress / Done tiles that recount on every action
- OVERDUE badges and a one-tap overdue filter
- Start-to-done time on every card — live while it runs
- Qualification-gated assignment — “requires Supervisor” means it
Forms that go somewhere
Build an incident report or checklist in minutes — nine field types, required flags, live preview. Then route every submission where it belongs: into a Document, a task with an assignee, a chat room, or the admin report inbox.
- Fields save as you add them — no “save form” step
- Workers fill on mobile; validation names exactly what’s missing
- One submission can fan out to Document + Task + Chat + Report
Build — fields save as you add them
Submissions (1)
Route this submission
Training & qualifications
Pass the course, hold the shift
Build courses by hand, or generate them straight from your Documents, section by section — the procedure is the curriculum. A quiz pass plus approved assignments completes the course, and completion auto-grants the mapped roster qualification. Until then, the shift training gate can flag the roster — or block it outright.
- Courses built by hand or generated from your own Documents, section by section
- Quiz pass + approved assignments = completion — the mapped qualification grants itself
- Shift training gate: an unfinished required course flags or blocks rostering — your choice
26 JUL 06:00–14:00 · Forklift shift
Shift training gate — Forklift Basics required Blocked — course incomplete
Setup & switching
Leave Deputy on Friday. Run Bluework on Monday.
Upload the raw export from Deputy, Tanda or KeyPay — Bluework auto-maps their messy column headers, dry-runs the whole file before a single record is written, then imports with one-click rollback and passwordless invites.
- Competitor presets map their headers to your fields automatically
- Dry-run preview: create / update / skip counts before you commit
- Employees claim invite links — no passwords ever imported
Column mapping — matched automatically, editable
AI assistant
An assistant that already knows the roster
Aegis sees each worker’s shifts, tasks and leave. Ask by text or hold-to-talk voice — and when it offers to do something, nothing executes until the worker taps Confirm. Try the chips yourself.
- Grounded in live worker context — shifts, tasks, leave balances
- Actions proposed as confirm cards; never silent execution
- PII minimised before anything reaches the model
Coming soon
The camera that files a report
Next for the Protect tier: Argos will watch the site, not the people. A worker down on the dock becomes a verified event with a dwell timer, an annotated snapshot, and an escalated hazard — supervisors notified in seconds, duplicates deduped at the door.
- AI-verified events with confidence scores — no raw feeds stored
- Escalation rules by category and severity; every event HMAC-authenticated
- Replayed webhooks bounce as duplicates — one event, one hazard
In development — this simulation previews the planned workflow. Early access ships with the Protect tier.
Panels 01–25 replay the live product, not mockups — 26 previews what ships next. Bluework by ArchonX.ai · Made for Australian workplaces