| Task | Owner | Due | Finished | Now finishes | Pushed | Against due date |
|---|
One row per task, shaped to survive a round trip. Field names follow the task table plus the custom columns this scheduler needs: design hours, phase, complexity tier, a peer-review flag, blocked-until, dependencies, and the projected finish it writes back.
Effort comes from the Project Complexity Criteria (form v1.0). Eleven criteria scored 1–5 give a total of 11–55, which sets the tier: 11–18 Simple, 19–27 Standard, 28–38 Complex, 39–55 Highly Complex. The tier and the phase together fix the hour band and the turnaround target, so picking a project and a phase fills the hours in for you. Hours convert to schedule at 7.5 per designer-day. Every project carries the same four gates, on its own rail: peer review, release approved, equipment order cut-off, install starts. The tier decides who must review — nobody at Tier 1, one peer at Tier 2, a formal meeting with Technical PM and Senior Tech at Tier 3, and the ATS Director as well at Tier 4 — and those reviews are scheduled as real work against real people, because reviewer time is the constraint that actually bites. Scheduling: each person has a working-day capacity and a WIP limit; whatever is active on a day splits that day between them, so three concurrent jobs each advance at a third speed. Blocked work stops dead until its resume date and drags its dependents behind it. Weekends are excluded. Dates ruled in red are outside our control — site access, a booked crew, a supplier cut-off. This browser remembers your scenario; Reset restores the baseline.