Operational workflow system
A service business replaced spreadsheets, email, and WhatsApp with a single system for tracking jobs, assigning work, and surfacing overdue items automatically.
Context
The situation before
A UK-based service business with a growing team was tracking active jobs across a mix of spreadsheets, email threads, and WhatsApp groups. There was no shared view of what was in progress, what was overdue, or who owned what.
Managers spent a significant portion of their day chasing team members for status updates. Overdue jobs were only noticed when a client complained. Handoffs between stages relied on memory, not a process. Capacity was invisible. Some people were overloaded while others had slack, and nobody could see it.
Pain points
- No shared visibility over jobs
- Manual status chasing daily
- Overdue work discovered too late
- Unclear job ownership
- No capacity or workload view
- Reporting assembled by hand
What we built
A central operational system
We built a web-based job tracking and operations system that replaced the scattered spreadsheets and chat threads. The system was designed around how the team actually worked, not how a generic project tool assumes they should.
Job tracking with live status
Every job visible in one place. Status board showing New, Assigned, In Progress, Waiting, and Closed. No more asking 'where's that job at?'.
Automated assignment
New jobs assigned based on team capacity and rules. No manual allocation or round-robin spreadsheets.
SLA monitoring and overdue alerts
Jobs flagged automatically when SLA risk approaches. Overdue alerts sent to owners and managers. Nothing slips through unnoticed.
Owner visibility
Clear ownership on every active job. Managers can see who's holding what without asking. Capacity and workload visible at a glance.
Weekly summary generation
Automated weekly report: jobs completed, overdue items, team workload, performance metrics. Generated and sent without anyone touching a spreadsheet.
Searchable activity log
Full audit trail for every job: who did what, when, and what changed. Searchable and exportable for compliance and review.
System flow
Why it worked
What made this project land
Narrow first scope
We started with one thing: job visibility. Didn't try to automate everything on day one.
Matched to the existing workflow
The system was shaped around how the team actually worked, not how a tool assumed they should.
Visible ownership from day one
Every job got an owner. That single change removed most of the daily chasing.
Practical rollout
Launched with the team, got feedback in the first week, adjusted before habits formed around workarounds.
What the client needed from us
- Mapping the existing workflow across tools
- Designing the status board and job model
- Building assignment and routing logic
- Setting up SLA monitoring and alert rules
- Building the automated weekly report
- Team onboarding and handover
Outcome
What changed
Status chasing eliminated
The team stopped asking each other for updates. Job status was visible to everyone on the board.
Overdue jobs surfaced automatically
SLA alerts meant overdue work was flagged before clients noticed. Response improved measurably.
Job ownership became visible
Every job had a clear owner. Managers could see workload distribution without meetings or messages.
Reporting became automatic
The weekly summary that used to take someone an afternoon was generated and sent automatically every Monday.
Type
Operational software
Sector
Service business
Services used
Workflow, Internal Tools, Reporting
Status
In production
Running into the same problems?
If your team is tracking work across spreadsheets, email, and chat, and losing visibility in the process, we've seen this before. Let's talk about your version.
Discuss a similar system