Dispatch without the spreadsheet stack.
A regional freight operator replaced four shared workbooks with an exception-first operations layer their night shift could actually use.
Halcyon ran a competent operation on software that did not match the work.
Halcyon ran a competent operation on software that did not match the work. Loads lived in a TMS. Exceptions lived in email. Invoices lived in a finance tool that nobody in dispatch opened. Night shift managers kept a private spreadsheet because it was faster than the official system. The company was not failing — it was leaking hours, and those hours were becoming policy.
Problem, approach, and what shipped.
A case study is a named week with a handover — not a mood board. The record below is what the operator still runs.
- 01
The problem
Halcyon ran a competent operation on software that did not match the work. Loads lived in a TMS. Exceptions lived in email. Invoices lived in a finance tool that nobody in dispatch opened. Night shift managers kept a private spreadsheet because it was faster than the official system. The company was not failing — it was leaking hours, and those hours were becoming policy.
- 02
The approach
We sat the night desk for two cycles before drawing a screen. The product was not 'a better TMS.' It was a command layer for the moments the TMS goes quiet: a late truck, a split load, a customer who changed the window after the truck left. Northframe became the place exceptions are owned, assigned, and closed — with an audit trail finance could read in the morning.
- 03
The build
We shipped Northframe as the exception and approval spine, integrated with Halcyon's existing TMS and invoicing tools rather than replacing them. Roles were written as they exist on the floor: dispatcher, night lead, finance closer. Every exception has a state, an owner, and a reason it can be reopened. The first release was deliberately small: inbound exceptions, assignment, and a morning digest. The second cut added customer-visible notes so sales stopped asking dispatch for screenshots.
Outcomes the team can still point at.
- 01
Night shift stopped maintaining a private workbook.
- 02
Finance closed the day from the same record dispatch used overnight.
- 03
Exception reopenings dropped because the reason lived with the load.
Numbers from the operating week.
- Workbook usage after 30 days
- Retired
- Morning close time
- 41 min → 12 min
- First production cut
- 6 weeks
Role
Discovery on the floor, product design, and the first two production cuts.
Stack
The product this engagement shaped.
Other operator records.
Have a similar operating problem?
Tell us what the team still runs at 2am. We will say whether it is a product, a build, or a no.