Know what is left,and who holds it
Every task has an owner, a date and a history. Suggested tasks wait for a person.
A gap becomes the next task. Testing suggests the follow-up. It waits in Suggested until a person accepts it.
Without AI, rules suggest the same tasks. Zero model calls.
Triage with the keyboard. J and K to move. A to accept. X to cancel.
Every task keeps its history. Who suggested, accepted, linked and closed it.
A file lands, the task moves
Linking a file sets In progress. A person closes it.
Two people, one list. A change on one screen lands on the other, with a name.
Click a status on either screen.
Every task, on one field. Scrub the weeks from kickoff to Export.
Stages carry the dates. Today's line shows what is due and what slipped.
Will it land by 20 Nov? Tasks in scope, started and done, day by day against the target.
Drawn from each task's history
Each bar is a day of tasks closed. Past the target is hatched.
One list, four ways. Group by status, label, assignee or stage.
Also in Tasks
Complete without AIRules suggest tasks. Zero model calls.
Gaps from testing and missing files raise the same suggested tasks by rule. A person on the team accepts each one before it counts.PCI duties by ruleFeedback form, engagement summary.
Duties the PCI program sets land as tasks at kickoff, with the date of their stage. Telling the client about the feedback form is one.Sub-tasks and commentsThreads and mentions.
Split a task into steps, talk it through in its thread and mention a colleague. Every comment stays in the task's history.Copy for the clientEnpasse sends nothing.
A task marked for the client becomes a request. Your lead copies it into their own email.