The answers are not what matters. The time it takes to get them is the diagnostic.

The Benchmark

There are five questions about document operations that every serious operations leader should be able to answer quickly, accurately, and without having to ask anyone else. Not because the questions are complicated, but because the answers reflect the health of the infrastructure that the entire operation runs on.

If the answer to any of these questions requires a phone call, an email, a search through three different systems, or a conversation with the person who was last involved, the process architecture has a problem. Not a crisis. A structural weakness that will become a crisis at the moment it is most inconvenient.

Question One: Where Is This Document Right Now?

Pick any document currently in a workflow within your organisation. A contract awaiting signature. An invoice awaiting approval. A purchase order that has been submitted but not confirmed. Where is it? Who has it? What is the current status?

In a well-designed process, this information is visible in real time from a single location without requiring anyone to be asked. In most organisations, the honest answer involves checking an email thread, messaging the person who sent it last, and waiting for a response that may or may not arrive before the enquiry is forgotten.

A document whose location you have to ask about is a document whose process is held together by human attention rather than system design.

Question Two: Who Approved It, and When?

For a document that has already been approved and acted upon, can you identify who approved it, at what time, on what version of the document? Not from memory, and not by asking the approver. From the system record.

The reason this matters is not academic. When an invoice is queried six months after payment, the ability to answer this question determines whether the response is a confident retrieval from the audit trail or a laborious reconstruction from email history that may not yield a definitive answer.

Question Three: What Version Is It?

For a document currently in review or recently signed, is the version being acted upon the same version that was approved? In organisations that circulate documents by email, version confusion is endemic. Multiple people receive different copies. Someone annotates a version that is not the current one. The version that gets signed is not always the version that was reviewed.

A document workflow that cannot definitively answer the version question is a workflow that creates legal risk every time a complex document moves through it.

Question Four: When Was the Last Action Taken?

For a document sitting in a workflow right now, how long has it been inactive? Is it waiting for someone who has forgotten about it? Has the deadline passed? Is there an SLA breach in progress that nobody has noticed?

In most organisations, the answer requires manually checking when the document was last touched and by whom. The check itself is the problem: it should not require checking because the system should surface overdue actions automatically.

Question Five: Can You Prove It?

If a counterparty, auditor, or regulator asks you to demonstrate that a specific document was approved by a specific person with the appropriate authority, on the correct version, at a recorded time, can you produce that evidence from your system in under five minutes?

This is the compliance question that most organisations answer with confidence until they are actually asked. The combination of email approvals, informal sign-offs, and version-ambiguous documents means that the evidential record is often weaker than assumed.

What the Answers Reveal

A 2025 compliance research study by Zignt found that 31 percent of organisations cannot demonstrate compliance if challenged on a specific document decision. That is not a technology gap. It is a process architecture gap: the events happened, but they were not recorded in a way that makes them demonstrable.

31%	Of organisations cannot demonstrate compliance if challenged on a specific document decision Zignt compliance research, 2025

The five questions in this article are not a checklist for compliance officers. They are a diagnostic for operations leaders who want to understand whether their process infrastructure is as strong as their team’s performance suggests it is.
Flowmono’s AI Workflow Builder makes all five answers available in real time, from a single platform, without requiring anyone to be asked. Book a demo to see what that visibility looks like.