Fewer errors in the data
Electronic capture reduces manual attendance processing, so payroll inputs do not have to be reconstructed from paper records.
Time-keeping
Which jobs earn, and which quietly do not.
Time recorded against the order it was spent on, not only against the day. That turns attendance data into the figure aftersales runs on: whether the hours you sold are the hours you worked.
Time-keeping
Sample data
The orderSample data
Sold hours vs worked hours · this week
Ceed diagnostics#4495
1.0 sold / 2.6 worked38%Passat clutch#4488
6.0 sold / 8.7 worked69%Kodiaq preparation#4492
2.4 sold / 2.3 worked104%Octavia service#4471
4.4 sold / 4.1 worked107%A code-native recovery list for four sample workshop orders, ordered with the lowest recovery first. Sold and worked hours remain beside the recovery figure so the exception can be checked rather than merely highlighted. Sample concept data, not a measured dealer result.
- Best fit
- Technician · Workshop foreman · Service manager · Payroll or HR
- Operational job
- Record attendance and worked time against the order and order item, compare sold with worked hours, calculate payroll inputs, and expose labour-recovery exceptions by person, job and site.
- What you get
- Worked and sold hours per job, with payroll inputs and exceptions to review.
The problem
Attendance tells you who was here. It does not tell you what you earned.
A clocking terminal can produce a payroll file, but it cannot explain why a clutch took longer than it was sold for unless it knows which order each interval belongs to. Recording time against the work changes that.
Working time in context
Productive and non-productive time are visible against the work and configured statuses, including overtime that otherwise stays hidden.
Order status without asking
Whether work on a car has started, finished or stopped for a reason is visible on the record without walking to the workshop for an update.
The workflow
Every worked hour reaches payroll and reporting
Five stages from an arrival record to labour recovery, payroll inputs and reporting. Select one.
Wherever the work actually starts
Attendance can be recorded from a terminal, PC, tablet or phone, including a remote workplace or a technician starting at a customer's site.
Arrival, departure and transfer can carry a verified location; the lawful configuration and employee process are set per market.
- In
- Five technicians across two sites, one at a customer's premises
- Omnetic
- Records arrival, verifies the configured location and opens the day at the right site
- Out
- Attendance that reflects where the work started
Time against the order, or part of it
The system records the time a technician spends on individual orders and individual order items, making the labour earning visible.
Planned and actual time sit side by side, so an overrun does not have to be reconstructed from memory.
- In
- A technician moving between three orders in one morning
- Omnetic
- Attributes each interval to the order item being worked on
- Out
- Worked hours and recovery per job, not only per person
Standard statuses, and the ones you define
Arrival, departure, holiday and illness are standard; training, a business trip or another locally needed status can be configured separately.
Each status carries its configured pay treatment, keeping productive and non-productive time apart downstream.
- In
- One holiday, one training day and one Saturday shift
- Omnetic
- Applies the configured treatment to each status
- Out
- Recovery based on productive hours and classified payroll inputs
The inputs payroll needs, calculated
Expenses, surcharges and overtime are calculated per employee, including configured public-holiday and on-call treatment.
Documents for invoicing come from the same time records, so billable hours do not need to be entered again.
- In
- A month of attendance, statuses and order time
- Omnetic
- Calculates configured surcharges and overtime, payroll inputs and invoicing documents
- Out
- Payroll and invoicing outputs from one record · local rules per market
Reports people can work from
Attendance and order-time reports can be printed, while graphic overviews export to Excel and PDF for the same conversation across teams.
The journey log can be produced from attendance and configured location records instead of written up afterwards.
- In
- A week of order time across five technicians
- Omnetic
- Builds recovery per job and person, exports the overview and produces the journey log
- Out
- The exceptions worth discussing rather than a whole week to audit
Capabilities
Time capture, order context and usable outputs
The twelve capabilities the source names, grouped by the job they perform rather than presented as twelve equal tiles.
Instant access
Attendance from mobile, tablet, PC or terminal.
Remote workplaces
Attendance records away from the premises too.
Location verification
Configured verification on arrival, departure and transfer.
Status library
Arrival, departure, holiday, illness and statuses you define.
Quick overview
Work on orders readable at a glance.
Order-level time
Time attributed to an order or one of its parts.
Workshop status link
Started, finished or stopped work visible immediately.
Customisation
Statuses and treatments configured for the business.
Invoicing documents
Billable time turned into documents without re-entry.
Journey log
Produced from attendance and configured location records.
Graphic overviews
Attendance views exportable to Excel and PDF.
Calculation
Configured expenses, surcharges and overtime per employee.
By role
Who this changes the day for
Technician
Clocks onto the job rather than only the day, with a record when the work genuinely took longer than it was sold for.
Workshop foreman
Sees the orders that overran and can ask what happened while the work is still remembered.
Service manager
Gets labour recovery per job and per person rather than a monthly estimate.
Payroll or HR
Receives classified inputs with configured surcharges and overtime already applied.
Platform & data connections
What the hours feed
Workshop
Hours land on the order item, which makes labour recovery and invoicing traceable.
Planner
Working time, absences and holidays are availability the plan must respect.
Accounting
Labour cost stays with the job and configured payroll inputs leave from the same record.
Reporting & Rental
Recovery compares people and sites; configured location records can support the journey log.
System relationship
Time-keeping in the connected product system
Time-keeping sits on the same orders, plans and postings as the rest of service operations, so the interval recorded once can be used by four connected contexts.
Time-keeping
Outcome & proof
What we can and cannot claim yet
Labour productivity
The mechanism compares sold and worked hours; a publishable improvement needs a baseline and measurement period.
More accurate payroll
Classified intervals and surcharges are inputs, while local payroll treatment is confirmed during implementation.
Location verification
It is an available option for approved scenarios; lawful basis and scope are configured per market.
Time-keeping customer story
Slot reserved for labour-recovery movement before and after deployment.
Implementation & governance
Secondary product demonstration
Labour recovery by order
Sold and worked hours stay on one order, so the difference keeps its owner and context.
Review Time-keepingOrder 4471 · recorded timesample data
Diagnostics
+0.3 h1.2 h sold · 1.5 h worked
Scheduled service
+0.1 h3.0 h sold · 3.1 h worked
Brake replacement
+0.6 h2.4 h sold · 3.0 h worked
Final check
+0.4 h1.4 h sold · 1.8 h worked
Sold
8.0 hWorked
9.4 hWhat was your labour recovery last month?
If the answer is an estimate, bring one week of sold and worked hours. We will show how the order-level record turns it into a figure.
Book a time-keeping demoThe orders
A representative week of jobs with their sold hours.
The time
How technicians record attendance and job intervals today.
The outputs
The payroll, invoicing and management reports those records must feed.