Runbook
Tasks tonight1,284
Result
Crosslane Freight
Dispatch, proof of delivery and the daily figures without a spreadsheet in sight.
- 31 ha week back
- Reporting
- 2025
Result
Crosslane Freight
Dispatch, proof of delivery and the daily figures without a spreadsheet in sight.
- 31 ha week back
- Reporting
- 2025
Result
Crosslane Freight
Dispatch, proof of delivery and the daily figures without a spreadsheet in sight.
- 31 ha week back
- Reporting
- 2025
The result · Result 04 / 06
31 h a week back01234567890123456789 h
a week backThe story
Dispatch, proof of delivery and the daily figures without a spreadsheet in sight.
Two dispatchers rebuilt the same spreadsheet every evening from the TMS, the driver app and the accounts system. Now each proof of delivery files itself against the job, the customer gets a timed update, and the day's margin per route is in Slack at 19:00. Crosslane measured 31 hours a week of admin gone across the office, and invoices go out the same night the job closes.
- Client
- Crosslane Freight
- Sector
- Logistics
- Workflow
- Reporting
- Year
- 2025
What wewired.
- 01Week 1
Mapped the week
We sat with the people who do the work and drew every hand-off on one whiteboard: where a record is typed twice, where a reply waits, where a spreadsheet is rebuilt.
- 02Week 2
Wired the trigger
The workflow starts from the event the team already produces: a booking, a closed job, a form, a payment. Nobody has to remember to press anything.
- 03Week 3
Built the steps
Each step reads from the client's own systems and writes back to them under their own logins. Every run leaves a line in the log.
- 04Week 4
Ran it beside the team
Two weeks in parallel with the old way: the numbers were compared every morning, the edge cases added, and then the manual path was switched off.
Beforeand after.
- Admin hours a week
- Before: 38 h01234567890123456789 h
- After: 11 h01234567890123456789 h
- First reply
- Before: 2 days0123456789 days
- After: 4 min0123456789 min
- Records typed by hand
- Before: 100 %012345678901234567890123456789 %
- After: 0 %0123456789 %
In the client's words“Thirty-one hours a week of admin, gone. The dispatchers still cannot quite believe the evening spreadsheet does not exist any more.
The result · Result 04 / 06
31 h a week back01234567890123456789 h
a week backThe story
Dispatch, proof of delivery and the daily figures without a spreadsheet in sight.
Two dispatchers rebuilt the same spreadsheet every evening from the TMS, the driver app and the accounts system. Now each proof of delivery files itself against the job, the customer gets a timed update, and the day's margin per route is in Slack at 19:00. Crosslane measured 31 hours a week of admin gone across the office, and invoices go out the same night the job closes.
- Client
- Crosslane Freight
- Sector
- Logistics
- Workflow
- Reporting
- Year
- 2025
What wewired.
- 01Week 1
Mapped the week
We sat with the people who do the work and drew every hand-off on one whiteboard: where a record is typed twice, where a reply waits, where a spreadsheet is rebuilt.
- 02Week 2
Wired the trigger
The workflow starts from the event the team already produces: a booking, a closed job, a form, a payment. Nobody has to remember to press anything.
- 03Week 3
Built the steps
Each step reads from the client's own systems and writes back to them under their own logins. Every run leaves a line in the log.
- 04Week 4
Ran it beside the team
Two weeks in parallel with the old way: the numbers were compared every morning, the edge cases added, and then the manual path was switched off.
Beforeand after.
- Admin hours a week
- Before: 38 h01234567890123456789 h
- After: 11 h01234567890123456789 h
- First reply
- Before: 2 days0123456789 days
- After: 4 min0123456789 min
- Records typed by hand
- Before: 100 %012345678901234567890123456789 %
- After: 0 %0123456789 %
In the client's words“Thirty-one hours a week of admin, gone. The dispatchers still cannot quite believe the evening spreadsheet does not exist any more.
The result · Result 04 / 06
31 h a week back01234567890123456789 h
a week backThe story
Dispatch, proof of delivery and the daily figures without a spreadsheet in sight.
Two dispatchers rebuilt the same spreadsheet every evening from the TMS, the driver app and the accounts system. Now each proof of delivery files itself against the job, the customer gets a timed update, and the day's margin per route is in Slack at 19:00. Crosslane measured 31 hours a week of admin gone across the office, and invoices go out the same night the job closes.
- Client
- Crosslane Freight
- Sector
- Logistics
- Workflow
- Reporting
- Year
- 2025
What wewired.
- 01Week 1
Mapped the week
We sat with the people who do the work and drew every hand-off on one whiteboard: where a record is typed twice, where a reply waits, where a spreadsheet is rebuilt.
- 02Week 2
Wired the trigger
The workflow starts from the event the team already produces: a booking, a closed job, a form, a payment. Nobody has to remember to press anything.
- 03Week 3
Built the steps
Each step reads from the client's own systems and writes back to them under their own logins. Every run leaves a line in the log.
- 04Week 4
Ran it beside the team
Two weeks in parallel with the old way: the numbers were compared every morning, the edge cases added, and then the manual path was switched off.
Beforeand after.
- Admin hours a week
- Before: 38 h01234567890123456789 h
- After: 11 h01234567890123456789 h
- First reply
- Before: 2 days0123456789 days
- After: 4 min0123456789 min
- Records typed by hand
- Before: 100 %012345678901234567890123456789 %
- After: 0 %0123456789 %
In the client's words“Thirty-one hours a week of admin, gone. The dispatchers still cannot quite believe the evening spreadsheet does not exist any more.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.
Book a call
Tell us what eats your week. We'll automate it.
Pick what fits. On the call we map the first workflow, the tools it touches and the week it goes live.