1
Prepare the real job before the vehicle arrives
A future booking can carry likely labour, parts, checksheets, internal context and workshop planning without pretending the vehicle is already in progress.
The booking remains connected to the repair order that the workshop will run. Reception can resolve missing information and prepare the work while the arrival and live-job states remain truthful.
Open a future booking, prepare the likely work and checks, then confirm the vehicle is still shown as a future arrival rather than active work.
2
Control the day by customer promise time
Live work lists keep customer promise times, technician activity, current status, checksheet progress, approval delays and parts blockers visible together.
Reception can see which customer commitment is at risk instead of relying only on calendar order or asking each technician for an update.
Give two jobs different promise times and ask the system to show which one needs intervention first and why.
3
Give technicians a focused mobile workspace
Technicians see assigned jobs, job and line clocks, checksheets, measurements, notes, photos, video and completion controls without the full office interface.
The same actions update the live repair order used by reception. Active-clock safeguards prevent contradictory technician and job states.
On a normal phone, open an assigned job, clock on, record a measurement, attach evidence, add a note and attempt to finish while the clock is active.
4
Turn inspections into clear customer decisions
Configurable checksheets support green, amber, red and not-checked results, measurements, recommendations, photos, item videos and a workshop walkthrough video.
Findings can become recommended work without losing the evidence or being rebuilt in a separate quoting tool.
Record a failed inspection item with a measurement and video, then turn it into recommended work while preserving its context.
5
Give customers a live, visual service story
A private branded customer portal shows the latest customer-facing job stage, service history, a structured vehicle report, measurements, photos, videos and grouped recommendations with price.
The customer can understand what the technician found, then approve, decline or ask a question. Each response returns to the repair order instead of disappearing into a separate inbox or message thread.
Open the customer view on a phone, confirm the current job stage and visual report, approve one group, decline another and ask a question; then verify the outcomes return to the staff job.
6
Carry authorised work into the invoice
Customer, vehicle, labour, parts, approval context and completed work stay close to the invoice instead of being reconstructed from paper and messages.
Workshop HQ also supports standalone counter-sale invoices when a transaction genuinely has no repair order.
Approve additional work, complete it and prepare the invoice; confirm the job context and Australian GST totals remain coherent.
7
Maintain one auditable job history
Status changes, technician events, inspection activity, customer decisions, communications, invoice events and key staff actions remain traceable.
The timeline gives the workshop a common operational record while sensitive platform and account changes also create audit history.
Follow one test job from arrival to payment and identify who changed each important state and when.
8
Operate as an Australian workshop product
Workshop HQ uses AUD pricing, Australian GST, Australian vehicle-data safeguards, Australian hosting and an Australian company identity.
The product is operated by EA Performance Group Pty Ltd and currently serves Australian automotive workshops from workshophq.au.
Review the invoice tax treatment, pricing currency, official operator, data-hosting position and vehicle-lookup fallback before subscribing.
9
Treat data migration as a controlled operation
Owner-controlled imports can be analysed, previewed, processed with audit records and rolled back when the source data creates a problem.
Migration is designed as a visible workflow rather than an opaque one-off database load. Imported records retain source and audit context so exceptions can be investigated deliberately.
Use a representative export, review the analysis and exception handling, then confirm the rollback boundary before committing to cutover.
