Does it follow the rules?
Check the rules independently, including edge cases and situations where no plan can work. If we call a result optimal, we need to show what it optimizes and why the claim holds.
How we work
We work out what you need, build and test the tool, then help your team use it on their own.
We agree on what you’ll receive, the timeline, fees and support before we start.
A clear problem to solve, a comparison with your current process and a proposal for the work.
The people who make the decision, a walkthrough of the current process and a few examples to work with.
Can existing software, a simpler spreadsheet or a process change already do the job?
A working tool, a comparison of the options and an explanation of how we checked the results.
Your team’s rules, the information needed to build the tool and feedback from the people who will use it.
Does the tool respect the actual rules and compare fairly with the existing process?
Exports, instructions and training, with checks to pass before use and a backup process if something goes wrong.
Time for staff to try the tool on representative work, plus someone who can approve its use.
Can staff operate it independently, handle exceptions and recognize when not to use it?
An agreed plan for updates or support, including who handles each part and what needs testing again.
Feedback from daily use, changes to your rules or plans to bring in more teams or locations.
What needs checking again when the work changes, and who will provide support?
Example of what you receive
This sample shows a schedule and the instructions that go with it. For your team, we would agree on the inputs, rules and checks the tool needs to pass.
Check the rules independently, including edge cases and situations where no plan can work. If we call a result optimal, we need to show what it optimizes and why the claim holds.
Give both approaches the same inputs and rules. Compare what matters to your team: unfilled sessions, rule violations, cost, planning time or the work of rearranging a schedule.
Staff need to run the tool, understand exceptions and know when to use the backup process. We distinguish the model’s estimates from what happens in a trial and in everyday use.
A few common questions.
No. A schedule can start with who is available, what they can do and the rules you need to follow. A forecast usually needs past records. We’ll look at what you have and agree whether anything else is needed.
When your team makes the same decision regularly and the current process struggles with important rules. We first check whether an existing app, spreadsheet or process change could do the job.
Usually, a tool with inputs you can change, a schedule or allocation you can export, and instructions and training for your team. The proposal sets out exactly what you’ll receive, who owns it and how you’ll access it.
Once we understand the problem, we agree on the work, timeline, fees and checks the tool needs to pass. You’ll know what is included before we begin.
We agree on any ongoing support separately. New locations or changes to your rules may need updates and another round of testing.
Your team does. The tool helps you compare options; the person responsible for the work reviews the plan, checks exceptions and approves its use.
Describe how you handle it now and what gets in the way.