Work Planner
Work Planner
An application to plan, simulate and communicate workload.
The problem
When new requests arrive, the real question is: what happens to the plan if I accept? A task manager or a time tracker cannot answer, because they do not say what capacity is allocated to.
I wrote Work Planner to answer that question with numbers and dates, before saying yes.
What I built
- 01
The queue is the priority
The order of the queue decides what matters most: no scores or algorithms choosing for you.
- 02
The scheduler
It pours the queue forward into the available capacity, splitting the effort over several days when needed.
- 03
The plan never moves on its own
Every change first produces a proposal whose impact you can see: only after approval does the plan change.
- 04
Explicit conflicts
A fixed date does not reorder the queue: if the plan misses it, a conflict appears and you decide what to move.
My role
Personal project: concept, planning rules and development.
Technologies
Python · Vue · TypeScript · Docker
Stating what the program does not do (it is neither a task manager nor a time tracker) made the rules simpler. A system that proposes and never decides on its own is slower to use, but changes stay under control.
A workload to organise
Write to me and we can talk, even just to work out where to start.
Stock image: perpetual calendar from a museum collection, CC0 (Wikimedia Commons), cropped. It does not show the project.