It helps compare who is available, suitable, credentialed, experienced, and reviewable for a job.
Pilot start guide - noindex
Start with the decision before dispatch.
DispatchTalon helps operators structure availability, suitability, credentials, assets, job context, site records, and reviewable reasoning before the job goes out.
1. Structure setupCompany requirements, workers, credentials, assets, and source records.
2. Review fitSmartRank and review factors surface context for human confirmation.
3. Record the dayDaily Site Log records who was onsite and what changed.
What DispatchTalon is
A pilot-stage dispatch intelligence layer for operational businesses that allocate people, assets, credentials, and job context under pressure.
It turns scattered setup data, source records, site logs, and dispatch context into a clearer workflow.
The dispatcher, allocator, supervisor, or admin still reviews the context and confirms the next action.
What DispatchTalon is not
DispatchTalon is not a sign-off authority and does not replace the dispatcher or competent operational judgement.
Use DispatchTalon to support decisions. Do not use it as a substitute for permits, site rules, engineering judgement, safety systems, payroll records, customer instructions, or management review.
The system does not send people, publish instructions, or change live records without the appropriate user action.
Your first review path
Use this order for the first session. It keeps the review practical and stops the pilot from feeling like a generic dispatch board.
Check that the pilot tenant, user label, and navigation feel clear.
Review operating mode, timezone, company requirements, credentials, and asset structure.
Upload source records for assisted pilot setup review. Uploaded files do not create live records automatically.
Check worker records, credential states, custom credential types, and suitability context.
Review required roles, job context, SmartRank output, review factors, and allocation confirmation.
Record who was onsite, sign in and out, note changes, and print the daily report for review.
What feedback matters
Feedback is most useful when it is tied to real operational friction rather than general opinions.
- What felt obvious?
- What felt too technical?
- Where did the user pause?
- Would the review context help an allocator?
- What evidence would increase trust?
- What language should change?
- Which business type would value this first?
- What setup relief is most valuable?
- What should not be built yet?
Helpful links
Use the console for authenticated pilot work. Use the diagnostic and personalisation profile for review context before a call.