Why we built Clivanta around request items, not folders

When we started building Clivanta, the obvious design was a shared drive with a nicer login. Firms already think in folders — one per client, one per year — so why not just make that experience better?

We didn’t, and the reason is worth explaining, because it shapes everything else in the product.

A folder answers the wrong question

A folder tells you a file exists. It doesn’t tell you:

• What you actually asked for (the folder has no memory of the request).
• Whether this is the right version (three PDFs, all named final).
• Whether anyone reviewed and accepted it, or it’s just sitting there.
• What’s still missing — the one thing you most need to know.

You can bolt a checklist onto a folder to patch this. But now the checklist and the files are two systems that drift apart, and you’re back to reconciling them by hand.

The request item

So Clivanta’s atomic unit isn’t a file — it’s a request item: a single, explicit ask with instructions, a sample format, and a status of its own. draft → requested → submitted → accepted (or needs revision). The files hang off the item, with full version history. The item, not the file, is the thing your work list and your reminders read from.

This flips the default. Instead of “here are some files, figure out what they mean,” you get “here is exactly what we asked for, and here’s its current state.” Every item carries two comment threads — one you share with the client, one that stays internal — and an immutable activity log.

Structure you can reuse

Because the request item is a first-class thing, you can standardise it. A pack is your firm’s set of items for a service type — the standard VAT return requests, the standard audit confirmations — written once and reused on every engagement. Create a new period, and the right asks are already there, snapshotted so later edits never rewrite past work.

That’s the payoff of not building on folders: the structure is reusable, the status is trustworthy, and “what’s outstanding” is a fact, not a guess.

Evidence, not storage

The last piece is what happens when a document is good enough. In a folder, nothing changes — it’s just another file. In Clivanta, accepting an item promotes its document to evidence on the permanent engagement record, with the reviewer’s identity and a timestamp. Storage becomes a record you can stand behind.

Folders are great at holding files. They’re terrible at running a process. Clivanta is built for the process — and the files come along for the ride.