Ticketing tools, practice suites, or Clivanta: choosing the right weight

You have finally accepted that the email-and-spreadsheet chase has to end, and someone on the team has been told to “find us a tool.” A week later they are three demos deep, a dozen browser tabs open, and more confused than when they started. One vendor is showing them a helpdesk. Another is walking them through a platform that also does billing, a CRM and tax returns. A third is really just a shared drive with a login screen.

The confusion is fair. The document collection problem sits between several categories, and each neighbouring category will happily sell you its version of a fix. The trick is matching the weight of the tool to the weight of the problem.

Ticketing systems: built for a different relationship

Zendesk, Jira and their peers are very good at what they are for. If you run a support desk with a queue of incoming issues and agents working them to an SLA, a ticketing system is the right shape.

The trouble is that the shape does not fit. Collecting a bank confirmation from an audit client is not a support ticket, and your client is not a requester raising an issue. The vocabulary alone gives it away: tickets, agents, queues, resolution times. It reads as IT infrastructure, which is the wrong register for a trust-based professional relationship where the client is paying you and would rather not feel processed. You can bend a helpdesk into a document tracker, but it will always feel borrowed, and it has no real notion of a document, a version, or an accepted piece of evidence.

Generic project management: no side for the client

Asana, Monday and Trello are genuinely useful for running your own internal work. If you want a board where your team tracks its own tasks, they do the job well, and many firms already have one.

But document collection is not an internal problem. It is a two-sided one, and the second side is the client. Generic project tools have no client-side experience worth the name: no per-item upload portal, no passwordless access for an occasional user, no distinction between a raw file and one your firm has reviewed and accepted. You would either give the client a login to your board, which few will use, or you end up back in email to actually gather the files while the board slowly drifts out of date beside it.

Practice suites: the whole platform to fix one workflow

Karbon, TaxDome and Canopy are capable products, and this is not a knock on them. They bundle a CRM, billing, time tracking, tax software and workflow into one platform. If you are ready to replace your entire stack and run the firm on a single system, they are a serious option and worth the look.

That is also the catch. Adopting a suite to fix document collection means adopting the suite. It is a migration, a retraining exercise and a pricing commitment that reaches well beyond the one workflow that was actually hurting. Plenty of firms are not looking to change how they bill, how they track time or how they manage their pipeline. They just want the request-and-response loop with clients to stop living in email. Buying a whole platform to solve one problem is a real decision, and for many it is more than they need.

Shared drives: the tempting non-answer

The fourth instinct is the simplest: just make a folder in Google Drive or SharePoint and share it. It is free, it is familiar, and it is the option most firms reach for first.

It is also answering the wrong question, for reasons worth their own discussion. A folder tells you a file exists, not what you asked for, which version to trust, or whether anyone accepted it. We set out the full argument in why a shared drive isn’t a document collection tool.

The middle weight

Clivanta is built for the space these options miss: light on the surface, structured underneath. It does one job, the request-and-response evidence loop between a firm and its clients, and it does the whole of that job rather than a fragment.

• Light for the client. A passwordless portal that shows exactly what is still needed, with per-item upload. No board to learn, no ticket to raise, no platform to adopt.
• Structured for the firm. Each ask is a Request Item with its own status, versioned files and an immutable activity log. Standard procedures live as reusable Packs. Accepting a file promotes a Document to Evidence on the permanent record, with a name and a timestamp.
• Scoped on purpose. It is not your CRM, your billing or your tax software, and it is not trying to be. That is what keeps it easy to adopt for one workflow without committing the firm to a switch.

The honest way to choose is to name your actual problem. If you want to replace your whole practice stack, look hard at a suite. If you only need your internal task board, a project tool is fine. If a folder and a bit of discipline genuinely covers you, do not let anyone talk you out of it. But if your one real pain is the document chase with clients, you want something the exact weight of that problem, and you can weigh it on the product overview and the pricing page.

Pick the tool that fits the job, not the one that fits the biggest demo.