The work list
One table of every task your firm has, across every client and every engagement, with what is overdue and what is unassigned visible without hunting for it.
Open Work and you get every task the firm has in one table — not this client's, not this job's. Everything.
This is the screen for the question a Monday morning actually asks, which is not "what is happening on the Tremblay file" but "what is late, and who is not carrying anything".
What each row tells you
- Due — when it is owed. This is what the list sorts and warns on.
- Assigned to — who owns it, or Unassigned if nobody does.
- Status — where it has got to, in your firm's own words.
Overdue and This week are the two cuts worth living in. Overdue is the list you fix; this week is the list you plan.
Unassigned is the one to watch. A task nobody owns is not waiting for a person, it is waiting for somebody to notice it exists — and it will keep waiting, because no individual's list is missing it.
It is the same list as everywhere else
This is worth being precise about, because it changes how you use Vylan. A task belongs to a client. Its engagement is optional. So the tasks card on a client's profile, the tasks on an engagement, and this work list are three views of one list — not three lists that need keeping in step.
Create a task anywhere and it appears everywhere it belongs, immediately. Close it anywhere and it is closed everywhere. Nobody re-enters a task to make it show up on another screen, and there is no version of a task that is done on one page and open on another.
That includes tasks Vylan makes itself. A stage in an automation that creates its team tasks puts them in this list beside the ones you typed.
A task has its own page
Click one and you get more than a row. A task has a page of its own, with its files, its comments and everything that has happened to it — which is where a task that turned into a conversation belongs, rather than in somebody's inbox.
Reminding yourself about one
Remind me on a task sets a private nudge. It is yours alone: nobody else sees it, and nothing goes to the client. For the task you cannot do until Thursday and do not want to think about until then.
Making one do something on its own
A task can carry rules — when it reaches a status, put someone on it, tell someone, or message the client. One sentence each. See task automations.
Deleting one is not final
Deleted tasks go to Recently deleted rather than vanishing. Deleted tasks stay here for 30 days, then they're gone for good. Restore one from there, or end it early with Delete forever.
Tasks a stage creates are described in what happens when a stage starts.