Seats — plan first, people second
In Zenoba, the plan doesn’t wait for the team: a task is given to a seat on the team. A seat has a profile (the role); it is held by a person, or left to fill. Six ideas are enough.
Plan with profiles
The assistant proposes the project team as profiles from your catalogue — two developers, a half-time architect — with their periods. You adjust and confirm: these are seats to fill, on which you already plan and estimate.
Take your own seat
When you create the project, “I hold this seat” puts you on your profile: “My work” shows your tasks right away. It’s your morning screen.
Put real people on the seats
On a seat to fill, “Fill”: Zenoba suggests people with the right profile who are available over the period. A name is enough to plan someone — inviting them to get an account is a separate step. The seat’s tasks become theirs without being rewritten.
Nothing gets lost while you wait
The directory shows each account’s status: not invited, invited, active. A seat to fill whose first task starts within two weeks is flagged to you, with a direct link to the action.
Replace without losing history
“Bob replaces Alice from 1 May”: on that seat only, open tasks move to Bob that day; before, they stay with Alice. What Alice completed stays under her name, forever. Before the date, the replacement can be cancelled; the seat’s history shows who held it, and when.
When someone leaves, their work doesn’t leave with them
From their directory card, “Departure”: for each seat, who takes over, or leave it to fill. Everything the person completed stays under their name; their account leaves the workspace.
The action, when you think of it
One assignee picker everywhere — Gantt, table, board — that shows who is free. Giving a task to a seat to fill offers to fill it right away, and the workload panel shows work no one holds yet.
The rule that sums it up: a task is given to a seat, held by a person or left to fill — and the past is never rewritten.