Example sketch
Crew scheduling for trade businesses
“Our field technicians learn about jobs through a group chat, and when someone calls in sick in the morning, I spend half the morning on the phone.”
This sketch is an example. We wrote the sentence; the concept was generated by an AI and edited by us; our renderer draws it.
ConceptScheduling
Crew Board
Weekly scheduling for field technicians that rebuilds itself in minutes when someone calls in sick.
How we understood your problem
Weekly scheduling lives in one person's head and a group chat. When someone is out, there is no overview: which jobs are affected, who is free, who is even qualified to take over? Every absence costs a morning on the phone.
Who it's for
- DispatcherPlans the week, assigns jobs and reacts to absences.
- Field technicianSees assigned jobs on the phone and reports illness or delays.
- OwnerReviews utilisation and overtime per crew.
Interface
Data model
| Entity | Field | Type |
|---|---|---|
| Crew | name | Text |
| vehicle | Text | |
| Field Technician | name | Text |
| qualifications | Text | |
| crew | Reference | |
| active | Yes/No | |
| Work Order | customer | Text |
| address | Text | |
| trade | Text | |
| material_list | File | |
| Job | date | Date |
| duration_hrs | Number | |
| status | Text | |
| technician | Reference | |
| work_order | Reference | |
| Absence | technician | Reference |
| start_date | Date | |
| end_date | Date | |
| reason | Text |
| From | Cardinality | To | Relation |
|---|---|---|---|
| Crew | 1:n | Field Technician | consists of |
| Field Technician | 1:n | Job | takes on |
| Work Order | 1:n | Job | is carried out in |
| Field Technician | 1:n | Absence | reports |
Market value
What this problem would be worth on the market: how the product could be offered if it were sold. Not our price, and not an offer.
Billed per user per technician
-
Board
9 €
per month · per technician
- Most likely fit
Board + absences
14 €
per month · per technician
-
With reporting
19 €
per month · per technician
Value grows with every technician scheduled. Office seats stay free.
Roadmap
-
Stage 1
Weekly board
Plan jobs and push them to the phone. The group chat becomes redundant.
-
Stage 2
Absences
Sick notes, open jobs and replacement suggestions in one flow.
-
Stage 3
Reporting
Hours and utilisation per technician, exported to payroll.
Core features
- Weekly boardAll jobs per technician at a glance, reschedule by dragging.
- Report an absenceA sick note instantly marks the affected jobs as open.
- Replacement suggestionShows who is free, qualified and working nearby.
- Job details on the phoneAddress, contact and materials, without a group chat.
- Hours overviewPlanned versus worked hours per week and technician.
Deliberately left out
- No payroll: hours are exported to the existing payroll system.
- No route optimisation: with few vehicles, the dispatcher plans better than an algorithm.
- No customer portal: only worth it once internal scheduling is reliable.
What the AI does
Suggests a replacement for an absence, ranked by qualification and distance.
What the AI explicitly does not doThe AI never reassigns on its own. The dispatcher confirms every schedule change.
Integrations
- Payroll (export)
- Calendar subscription
- SMS sending
Three questions we would ask you first
-
Who may reschedule jobs: only the office, or also crew leads?
-
Which qualifications really decide who may take on a job?
-
Do all technicians have a work phone, or must this run on personal devices?
A sketch, not an offer. Generated by an AI, rendered by us.