Hours of allocation work
Match tasks with available people who have the right capabilities.
Why MP-Opt exists
A session plan can change quickly. MP-Opt helps organisers rebuild assignments, catch conflicts and share the updated schedule without starting over.
The problem
I tend to build where a process creates the same friction again and again. In a masterplan, that means checking availability, capabilities, locations, daily hours and overlaps by hand—then repeating the work when one part of the programme changes.
That work often arrives when the team is already busy. MP-Opt reduces the repetitive search, makes workload easier to inspect and gives the team a clearer route from a change to an updated schedule.
Organising and computer science
I am a computer scientist and an EYP organiser. MP-Opt brings those two sides together: using code to untangle a difficult planning problem, while keeping the result understandable to the people who will actually use it.
The optimiser can search through combinations far faster than a person. Organisers still decide what makes sense for their team.
What it tries to make easier
Match tasks with available people who have the right capabilities.
Catch overlaps, unavailable people, impossible locations and overlong days before publishing.
Compare assignments, breaks and fatigue instead of judging the balance by eye.
Re-run the plan and publish an updated schedule without rebuilding everything by hand.
Safety belongs in the plan
The working project stays on the planning workstation until an organiser publishes. The Server uses passkeys, clear audiences, deployment-specific privacy information, controlled deletion and encrypted recovery.
Those safeguards belong in the project for the same reason as conflict checking: organisers should be able to rely on the plan without creating a new problem elsewhere.
The final call
Every proposed assignment can be inspected, changed and discussed before it is finalised or shared. MP-Opt is there to make the difficult combinations easier to work through, not to remove people from the decision.
Open source
The source, release history and detailed technical guides are public. Each component keeps its own instructions and verification material close to the code it describes.