Tasks and weeks
Adding work, estimating it, putting it on a week, and saying what is owed on it.
The grid
Tasks opens as three columns: the task, the weeks it is on, and what is owed on it. Filters across the top cut it down to open work, work that can be done now, blocked work, work with no estimate, and so on. The Person filter shows one person's work.
Three views are offered at the top right: a flat list in week order, grouped by room, and a board with a column per status.
Putting a task on a week
Press schedule on a row. One box takes the weeks, the days of work, who owns it and which crew does it. A task can sit on several weeks.
If a task waits on something, the register works out the earliest week it could start and will not let it be booked before that. Choosing an earlier week asks whether to chase what is holding it up.
Proposed weeks
A task nobody has booked is shown on a proposed week, drawn dashed. The proposal comes from the sequence, the delivery dates of the orders it needs, and how much work each crew can take. A question mark means nobody has estimated it, so its length is a default guess.
A proposal is not stored. It moves whenever the sequence or the dates move, and it becomes a real week only when somebody presses book.
Asking somebody
Separately from the work itself, anybody can be asked to do something about a task or an order: chase, check, decide, confirm and so on, by a date, with a line saying what it is about. Each ask is its own thing, and a task or an order can have several at once. This is how the register knows what each person owes today.
An ask is on that person's list, in their daily summary and in the weekly close-out until it is closed. Whoever it is on closes it with Done, saying what they found out, which goes on the thread. If something follows, such as an order to place once a decision is made, they ask the next person in the same step. An ask that is no longer needed is closed and says so. Cancelling an order, delivering it or finishing a task closes what is asked on it.