Constraints, held properly
Skills, shift patterns, travel time, kit availability, job order, statutory rest. A plan that ignores any one of these looks tidy at eight and falls apart by eleven.
Scheduling systems
Scheduling that holds up when the day stops going to plan.
Intelligentside builds scheduling systems for teams whose people, time and kit must line up. State of the art methods, designed to stay future proof as the work grows.
The model below solves a real schedule in your browser. Nothing gets sent anywhere.
Live model
Move the constraints. Watch the schedule rebuild.
This panel holds a working scheduler, not a picture of one. Set the team size, push the demand up, switch the rules, and it re-plans the day as you watch.
Day plan, 09:00 to 17:00
Rules
Capacity
- Jobs placed
- --
- Last finish
- --
- Team utilisation
- --
- Model solve
- -- ms
Standard Priority Urgent
Demonstration model. Every number here gets computed on this page, and none of it describes client work.
Schedule assignments as text
What gets built
Three things a scheduling system has to get right.
Rebuild, not restart
A no-show at nine should reshape what remains and leave the settled part of the day alone. The system recalculates in milliseconds and shows exactly what moved.
Built to keep pace
Open data formats, documented rules, standard interfaces. The scheduling logic belongs to the business, so the next tool plugs in and nothing needs rebuilding.
Method
How a system gets delivered.
Four stages. Each one ends with something the business can check.
Map the real constraints
Time with the people doing the work, listing every rule the plan must respect, including the ones nobody ever wrote down.
Model the rules
Each rule becomes something testable. Where two rules conflict, the business picks the winner and that decision gets recorded, not buried.
Build and prove
The model runs against weeks already worked before it touches a live day. If it cannot beat the whiteboard, it does not ship.
Hand it back with the manual
Documentation, admin training, and the rule set written in plain English, so the team runs the system without calling anyone.
Future proof, defined
A phrase worth pinning down.
Future proof gets claimed often and tested rarely. Here is what it means at Intelligentside, stated plainly enough to hold us to.
- Data stays in open formats and exports in full, at any time, with no charge for leaving.
- Scheduling rules live in readable configuration, not buried inside compiled code.
- Interfaces follow published standards, so a new tool connects without a rewrite.
- No lock-in clause. The logic and the data belong to the business that paid for them.
- Written handover, so a change of supplier costs weeks and not years.
Tell us what breaks in your week.
A short call, no pitch deck. Describe the scheduling problem and get a straight answer on whether a system helps, or whether a simpler fix does the job.