Tasks, statuses and due dates

Tasks, statuses and due dates

Add a task against a client or a job, give it an owner and a date, and move it through the statuses your firm actually uses rather than a fixed set somebody else chose.

Adding one

  1. From a client or an engagement, choose Add task — or New task from the client's own page.
  2. Say what it is. A title somebody else could act on beats a note to yourself.
  3. Set Assigned to and Due. Both are optional and both are what make it findable later.

A task attached to an engagement belongs to that job. A task attached only to a client is the work that is real but does not sit inside a job — the call you owe them, the letter to chase.

Your firm's own statuses

Statuses are yours to name. What Vylan fixes is not the words but the three buckets underneath them, so that every screen agrees on what "in flight" means:

  • Not started — accepted, nobody has begun.
  • In progress — somebody is on it.
  • Done — finished.

Call yours whatever your firm says out loud. The bucket is what the work list counts and what an automation checks when a stage is waiting for its tasks to be finished, so a status you invent still behaves correctly everywhere.

Kinds are the other half of the vocabulary: what sort of thing this is. They are worth keeping short — a list of forty kinds is a list nobody picks from accurately.

One status, everywhere

A task's status, the colour of its dot and how its due date reads are the same on every screen that shows it. "In progress" is not one colour on the client page and another on the work list.

That sounds like a detail and is not. Two screens quietly disagreeing about what a task's state means is how a firm ends up trusting neither of them.

Whether a task can be assigned to somebody else depends on your firm having more than one person in it — see assigning work.

Still stuck?

If you can't find it here, write to us. A real person reads it.