Payouts from the ticket record
Every completed repair is already attributed to a technician. Payout rules run over that record rather than over a reconstructed list.
Incentives that come off the job cards, not a spreadsheet.
Most repair shops pay technicians a base salary plus something per job — and most calculate that something by hand at month end, from memory and a notebook. It is slow, it is disputed, and it is the single most common source of friction between owners and their benches.
Every completed repair is already attributed to a technician. Payout rules run over that record rather than over a reconstructed list.
Flat amount per job, a percentage of labour, different rates by repair type, or a monthly target with a bonus above it.
Technicians can see their own completed jobs and accrued incentive, which ends the month-end argument about how many repairs they actually finished.
A device returning for the same fault links to the original ticket, so a rework is visible rather than counted as a second completed job.
An incentive scheme designed on paper usually survives about two months. Then a technician disputes a count, the owner cannot reconstruct the month, and the scheme quietly reverts to a negotiated round number.
The scheme was never the problem — the record was. When every completed repair carries a technician, a date and a category, the payout is arithmetic rather than a negotiation.
Volume-only incentives push technicians toward fast, high-count repairs and away from the difficult board-level work that actually differentiates a shop. Worse, they create a mild incentive to rush.
Because rework links back to the original ticket, a technician's return rate is visible alongside their completed count. That makes it possible to weight incentives on repairs that did not come back — a far better proxy for the work you want.
A practical structure most shops land on: a modest flat amount per completed job, a higher rate for board-level and water-damage work, and a quarterly adjustment against rework rate. It rewards the difficult jobs without making a bad month punitive.
A trained repair technician is the hardest thing in this business to replace, and the most common reason they leave is not pay in absolute terms — it is the feeling that their output is not being counted fairly.
Giving a technician a live view of their own completed jobs and accrued incentive removes that suspicion entirely. It converts the month-end conversation from an argument about counts into a discussion about the work.
It also surfaces the quieter problem: a technician whose numbers have been slipping for three months, visible while it is still a coaching conversation rather than a resignation.
Completed jobs per technician per week, tracked over a quarter, is the most honest capacity figure a repair shop has. It answers the question owners usually guess at: whether the bench is genuinely full or simply busy.
The pattern to watch is average days-to-complete rising while completed counts stay flat. That combination almost always means work is queuing rather than the team slowing down — and it is the signal to hire before customers start noticing turnaround.
The product is built around the points where repair teams usually lose time: intake, handovers, parts, approvals, QC, payments, and customer updates.
Per-technician completed-job counts for any period
Base salary plus incentive in one payout statement
Rates configurable per repair category
Advance and deduction entries against a technician
Rework linked to the original job
Payout history retained per month
No. This calculates repair incentives and payout statements. Statutory compliance stays with your accountant or payroll provider, and we would rather say so plainly than imply coverage we do not have.
Yes — rates are per technician and can vary by repair category.
No. Technicians see only their own completed jobs and incentive; the full view is restricted to owners and managers.
Set the incentive rate to zero. The completed-job record still gives you productivity visibility.
Track every device, manage inventory, serve teams in their preferred language, and connect repair work with online sales in one place.