Most teams start looking at a document validation tool for the same reason: something small got through, and it cost more than it should have. The search usually begins with a feature list. A feature list tells you what a tool says it does. These five questions tell you whether it fits the way your team actually works, and what you're trusting it with.
They apply to any tool, including ours.
1. Does it check across documents, or only inside each one?
A tool that reviews one document at a time can catch an empty required field. It cannot catch a name spelled one way on a form and another way on a supporting document, or an income figure updated on one document and not on the other. Some of the most easily missed errors exist only in the relationship between documents and reading each file on its own will never surface them.
Ask: "Can this tool compare the same information across the documents in a case?" Then ask which forms and supporting documents it covers today, and what it leaves alone. A vendor that is clear about its edges is easier to trust than one that claims to cover everything.
2. When does the check happen: before or after submission?
A check that runs after a filing has gone out documents a problem. It does not prevent one. An error caught before submission is a quick fix. The same error caught afterward is a resubmission cycle, a delay and a client conversation nobody wanted. Both kinds of tool "find errors" in a demo, so the timing is easy to miss.
Ask: "Does this run before submission, or does it review filings that have already gone out?"
3. When something is flagged, what does the flag actually say?
A flag that reads "possible issue" sends someone off to hunt for the problem. A useful flag names the field, the document and the reason, for example that the employer name on one document does not match the name on a supporting letter. Ask where the rule behind a flag comes from. A flag you can trace to a form requirement is one you can act on, and one you can explain to a colleague, a client or a supervising attorney. Ask, too, whether the same checks run the same way whoever is using the tool. A flag that depends on who set it up is just a new source of variation.
Ask: "Can I see real examples of flags, and where each rule comes from?"
4. Who makes the decision?
A validation tool checks documents. It does not practice law. Be wary of any tool that presents its output as a ruling, or that rejects or approves anything on its own. The healthier setup surfaces a specific point of attention and stops there, leaving the decision with the people accountable for the filing.
Ask: "Does this tool decide anything, or does it flag points for a reviewer?" If anything is decided automatically, ask who is accountable when it is wrong.
5. What happens to our clients' documents?
Immigration files hold sensitive personal information, so this is a trust question before it is a feature question. Before anything is uploaded, ask for the current Privacy Policy and Terms of Service and check them on three points:
- Where are files stored, and for how long?
- Who on the vendor's side can access them and are they used for anything beyond the service, including training?
- Can your organization delete or export everything cleanly when the engagement ends?
If the answers are not clear in writing, treat that as a finding on its own. Have the person responsible for client confidentiality read the documents, not just the sales page.
Using the Questions
None of these questions needs technical knowledge. They need a vendor who will answer plainly and a vague answer is information too.
CIRIS is focused on legal services. It checks across documents in a case, runs before submission, flags the specific field and the reason and leaves the decision with your team. You are welcome to put all five questions to us in a demo.
Curious what that looks like for your workflow? Schedule a demo →
CIRIS by Kiungor, document validation infrastructure, currently focused on legal services.