01
Map the workflow
Trace who records what, when it changes hands, who reviews it and where the final record needs to land.
Department Design Partnership
Your handover workflow, configured before deployment.
A paid, scoped engagement to map one department’s real handover, recreate its approved format in Shift Copilot and prove it against agreed acceptance tests.
What we do
Start with the department, not a generic rollout.
We document how information currently moves across the shift change, agree the fields and language that matter, and configure Shift Copilot around that operating reality.
02
Agree fields and terminology
Define mandatory fields, department language, escalation cues and the information that must never be lost between shifts.
03
Recreate the approved format
Configure the output to match the department’s existing handover structure rather than forcing a foreign template.
04
Document requirements
Set the voice, connectivity, record-attribution and export requirements that the configured workflow must meet.
05
Build the controlled plan
Define representative test handovers, sponsor approvals, onboarding and the sequence from testing to deployment.
06
Implement with priority
Configure and remediate the agreed scope before annual licensing or wider rollout begins.
What you keep
A durable operating asset, whether or not you deploy.
- The mapped department workflow and handover sequence
- The agreed fields, terminology and escalation requirements
- The approved department handover format
- The documented voice, connectivity and export requirements
- The acceptance-test plan and controlled deployment design
Your organisation owns its source process documentation and retains the mapped workflow, agreed fields and approved department format. Shift Copilot retains its underlying product, configuration methods and non-identifying generic learnings.
Acceptance tests
Deployment is earned against concrete gates.
The configured department workflow moves to deployment only when every agreed test is satisfied and the sponsor approves representative handovers.
Reports are produced in the agreed department format
All agreed mandatory fields are captured or clearly flagged
The workflow functions under the agreed connectivity conditions
Reports export through the agreed operational workflow
Records are attributable, time-stamped and retrievable
Representative test handovers are approved by the department sponsor
What happens next
Design first. Test second. Deploy only after acceptance.
The annual licence and controlled deployment begin at acceptance—not at the start of the design engagement.
STAGE 01
Design and configuration
Map the operating workflow, agree the scope and configure the department format and terminology.
STAGE 02
Acceptance testing
Run representative handovers under the agreed conditions, close gaps and obtain sponsor approval.
STAGE 03
Controlled deployment
Execute the pre-agreed annual licence, onboard the department and move the accepted workflow into operation.
If acceptance is not reached: the customer has 60 calendar days from presentation of the configured workflow to complete testing and provide consolidated feedback. One remediation cycle against the agreed tests is included. If acceptance still is not reached, the parties may agree a written extension or end the engagement cleanly. The annual licence does not begin and no annual licence fee is due. The design fee remains earned for completed design work, and the customer keeps the retained deliverables listed above.
The boundary
The operational handover layer before your existing systems begin.
Shift Copilot does not replace your safety, incident, work-order or corrective-action platform. It captures the shift-change information that exists earlier—before something becomes an incident report or work order. Nothing to rip out and nothing to migrate.
For mine operators
Make the department’s handover system repeatable, written, attributable and easier for supervisors to complete at the end of shift.
For contractors
Drilling, services, hire and maintenance contractors can configure a client-ready record of completed work, outstanding issues and cross-shift commitments.
Partnership terms
What we need from your department.
The engagement works when both sides protect the agreed scope and make the real operating workflow available for testing.
A named internal sponsor
Someone accountable for decisions, consolidated feedback and final approval of representative handovers.
Your current handover format
The template, document or operating convention the department uses today, including approval requirements.
Supervisor access for testing
Representative supervisors released for onboarding, test handovers and practical feedback.
A maintained scope
Fields, workflow and acceptance tests agreed before configuration begins, with changes handled explicitly.
Annual pricing
Licence pricing begins at acceptance.
The applicable annual licence is agreed in writing before design work begins and executed when the configured department workflow passes acceptance.
Start here
One department
A$9,900/yr
One configured department at one operation. Annual, billed upfront.
ApplyTwo departments
A$16,500/yr
Two configured department workflows at one operation. Annual, billed upfront.
ApplyThree departments
A$24,000/yr
Three configured department workflows at one operation. Annual, billed upfront.
ApplyFirst year, one department: A$7,500 design partnership + A$9,900 annual licence − A$5,000 conversion credit = A$12,400 total. Each configured department beyond the first three is A$6,000/year; five departments are A$36,000/year.
Built for procurement
The documents your review team will ask for.
Security, data handling and service commitments are available before design work begins.
Start with one department.
Tell us how handover works today and what acceptance would need to prove.