All articlesPractice Management

Allocating Work Without Letting the Tracker Lie

The moment a task list can say a return is done, it will say so about a return that is not. Keeping who-is-doing-what separate from what-is-actually-finished is the whole design.

Ajay Suryawanshi7 min read- views
Allocating Work Without Letting the Tracker Lie

Most offices of any size have tried a task list, and most have abandoned at least one. The usual reason given is that nobody updated it, which is true and is not the interesting part.

Nobody updates it because it asks for information it should be working out, and once it has been wrong a few times people stop treating it as the answer. A tracker that is sometimes right is worse than no tracker, because the partner who checks it still has to check the actual work.

The fix is a boundary: the list owns who is doing what, and never owns whether it is done.

Status is not completion

These two look like the same field and they are not.

Status is a human note about intention. Somebody has picked this up. It is waiting on the client. It has been parked until the bank sends the missing month. All of that is useful, none of it is checkable, and all of it belongs to the person who wrote it.

Completion is a fact about the work. The return was filed. The reconciliation ties. The vouchers are in the company. It is not an opinion and it should never be typed in, because typing it is what makes it wrong.

The design rule that follows is uncomfortable and worth holding: the task list must not have a column that says the work is done. Not a checkbox, not a "completed" status value, nothing. Whether the work is done is worked out from the work itself, every time it is asked.

The moment that column exists, there are two answers to the same question. One of them is maintained by a person under deadline pressure, and that is the one that will be wrong.

Important

If your tracker and your books can disagree about whether something is done, somebody will act on the tracker. Usually in the last week of a deadline, which is exactly when it is most out of date.

What a task is actually for

Strip out completion and what remains is small, which is the point.

A task is what the office has added to a piece of the month's work:

  • Who it belongs to. The single most valuable field, and the one most often left implicit.
  • A date, where the statutory calendar cannot give one. Most of the month's work is dated by law. An office only needs to supply a date for the things that are not.
  • A human status. Waiting on the client, parked, in hand.
  • A note. What the next person needs to know.

That is it. The work itself, what it is and whether it is finished, comes from somewhere else.

This is also why a practice does not need to enumerate its own work: the statutory calendar already knows that a GST return is due on a date for every registered client. What the office adds is who and what happened, not what exists.

Allocating across articles

With that boundary in place, allocation becomes a much smaller problem than it usually looks.

Allocate the piece, not the client. "Rahul does Sharma Textiles" sounds organised and means nobody knows who is doing the GST return when Rahul is on leave. Allocating pieces of work means a reallocation is a change to one row, not a renegotiation.

Expect a piece to change hands. The note field is doing real work here: the point of writing down that the bank statement for August is missing is so that the next person does not spend an hour discovering it again.

Keep one place where a partner can see everything with a date in the next fortnight, across every client, sorted by date rather than by client. If answering "what is at risk this week" needs opening clients one at a time, the allocation system has not actually been built yet.

The same test applies to notices with reply dates and certificates about to lapse. Dates coming up are work, whatever produced them, and they belong in one view.

Pro tip

Review allocation weekly, not when something goes wrong. A fifteen minute pass over everything due in the next two weeks catches almost everything that would otherwise become a late filing.

The question to ask any practice tool

If you are evaluating software for this, there is one question that separates the useful from the decorative.

Where does it get "done" from?

If the answer is that somebody marks it, then what you have is a shared spreadsheet with a login, and it will drift from reality at exactly the rate your office is busy.

If the answer is that it reads the state of the work and reports it, then the list can be trusted, and more importantly it can be trusted by somebody who did not do the work.

Greenote keeps this boundary deliberately: a task carries the owner, the date, the human status and the note, and there is no field anywhere in it that asserts the work is finished. Whether a piece of work is done is worked out from what actually ran, so the two can never disagree. What else a practice should keep in one place covers the rest of the ground.

Conclusion

A task list earns trust by being narrow. Who is doing it, by when, and what the next person needs to know.

The moment it also claims to know whether the work is finished, it has taken on a job it cannot do reliably, and the first time it is wrong about something that mattered, the office goes back to checking the actual work.

See what the practice workspace covers.

ca firm task allocationarticle work allocation ca officeca practice task trackerca office workflow managementassigning work to articles
Read on your own PC

Turn bank statements into Tally vouchers on your own PC

Greenote reads 100+ Indian banks and posts clean vouchers straight into Tally, from your own PC. The statement is not uploaded, and nothing is typed by hand.

Free trial: 7 days or 5 statements, no card. Works with Tally Prime & ERP 9.

Share this article