Automation and Operations
Which processes to automate first: a simple scoring method
Score each process on hours, clarity, data readiness and risk, check payback, then automate the top one or two. Worked example and pass/fail test.
Intake & Extraction
AI Document Validation
Every document is checked for completeness and consistency against your rules before it moves any further.
Documents with missing signatures, wrong totals or blank fields cause trouble two steps later, when they are harder to fix. AI Document Validation checks every document against the completeness and correctness rules you set before it moves on. Anything that fails is held with the exact rule it broke, so a person can fix it quickly. You decide the rules and who reviews the exceptions.
- Missing fields and mismatches caught before documents move on
- Each failure shows the exact rule it broke
- Nothing that fails a rule reaches your system automatically
$5,500
20–30 working days
Optional maintenance $275/mo
What it is
AI Document Validation checks a document's extracted or submitted fields against the completeness and correctness rules you define, catching missing values, mismatches and rule breaks before the document moves to its next step. Each failure names the exact rule it broke, so a reviewer fixes it quickly instead of rereading the whole document.
Why businesses buy it
A document with a wrong date or a missing value rarely causes trouble on day one. It causes trouble later, as a rejected claim, a payment error or a compliance gap that takes hours to trace. Teams that check by hand get tired and inconsistent. After this build, every document passes the same rules every time, and your people only look at the ones that fail. The Scope Card sets out the document types, the rule set and the connected systems in writing before you buy, so you know exactly what will be checked.
Problems this solves
Incomplete documents move forward and problems surface much later
Validation checks each document's fields against the completeness and correctness rules you define. Missing values, mismatches and rule breaks are caught before the document moves to its next step.
Reviewers reread whole documents to find a single mistake
Each failure names the exact rule it broke and the field involved. A reviewer goes straight to the problem in the review queue instead of starting from page one.
Checking rules live in people's heads and vary by reviewer
Your rules are written into the configuration for up to three document types, up to twenty-five fields each. Every document is checked the same way, whoever is on shift.
A good fit if
Documents move on to approval, payment or filing before anyone checks whether required fields are actually present and correct.
You have clear rules in mind, such as required fields, allowed ranges or cross-checks between two values on the same document.
You want a gate that catches problems early, rather than finding out something was wrong after the document was already acted on.
You're comfortable with failed documents going to a person, rather than being silently rejected or silently waved through.
Not the right fit if
You want documents read into your system with checks applied in one build. AI Document Extraction already includes validation rules and a review queue.
You want documents sent for a decision to accept or reject, not just checked against rules. See AI Document Approval, the workflow stage after Validation.
You need to compare two versions of the same document against each other, not check one against fixed rules. See AI Document Comparison, a different analytical job entirely.
Your documents are contracts and you need risk clauses and obligations flagged, not field-level rule checks. See AI Contract Intelligence, built for that.
How it works
- A document's fields arrive already extracted, either from AI Document Extraction or from a form your document was submitted through.
- Validation checks each field against the completeness rules you set: required fields present, formats correct, values inside the ranges you allow.
- Cross-checks run next, such as confirming a total matches its line items, or a date falls after another date on the same document.
- Documents that pass every rule move straight on to the destination system or the next stage in your workflow.
- Documents that fail one or more rules are held in a review queue for the person you named, with the specific rule that failed attached.
- We test validation against 100 real sample documents before launch and hand you a report showing which rules caught which issues.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- Your business information (company basics, hours and brand voice), shared during intake, or confirmation we can reuse what you gave us on an earlier order.
- At least 20 real sample documents for each document type Validation should check, redacted if you need to.
- The exact completeness and correctness rules each field needs to pass, including any cross-field checks.
- Access to the destination system documents move to once they pass validation.
- The name of the person who reviews documents that fail one or more rules.
- Admin access and API keys for every connected system, shared by adding our team as a user or creating a key you control, never by email.
- One decision-maker who can approve the rule set and sign off at launch.
- An API key for your own AI model account (for example OpenAI or Google Gemini), created for this build with a spending limit.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Intake verified, sample documents and rule set confirmed.
Weeks 1–2
Completeness and cross-check rules built for your document types.
Week 3
Source and destination systems connected and review queue configured.
Weeks 3–4
100 sample documents processed, rule-check report shared with you.
Week 4
Your review and two rounds of changes.
Go-live
Live, handover report sent, support starts.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $5,500 |
| Express | 15–25 working days | $6,450 |
| Rush | 10–20 working days | $7,450 |
What you receive at handover
- AI Document Validation configured on one intake route and connected to your source and destination systems
- Written validation rules for up to three document types, up to 25 fields each
- A human review queue showing the exact rule each failure broke
- A test report from 100 sample documents, with an accuracy report
- An admin guide and a written handover report
- 30 days of post-launch support
Expected benefits and how to measure them
- Can stop flawed documents before they cause rework further down the line.
- Helps reviewers fix problems quickly because the broken rule is named.
- Makes checks consistent from one reviewer to the next.
- Failures by rule
- Count review-queue items per rule each week. The most common failures show where to fix things upstream.
- Rework at the next step
- Count documents sent back from the next stage each month, before and after launch.
- Review time per failed document
- Time a sample of reviews before launch and again after.
Before you start: Count documents that are sent back for missing or wrong details in a typical month. Time how long a manual check takes per document.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
The build price is one-time. Running Document Validation costs roughly $30 to $200 a month in your own accounts, covering OCR and AI usage plus storage, and it moves with how many document pages pass through the checks each month.
AI usage during the build and testing is billed to your own accounts too, so every provider relationship stays yours, not ours.
Ask about running costsCustom requirements
If you need more than three document types, more than 25 rule fields per type, or a second intake route than the Scope Card lists, add a note at checkout. You get a written Change Quote, and that work only starts once you accept it. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes, updates, a health report and change hours each month, enough to add or tighten a validation rule. It starts after the 30 days of support end, bills monthly, and can be cancelled any month.
$275/mo (5% of the build price a month, includes 2 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | A rules-engine SaaS charges per workflow or per seat every month | A custom agency quotes after discovery calls | Ours is one fixed price, shown on this page before you buy |
| Scope | A rules-engine SaaS is a general tool you configure and maintain yourself | An agency agrees scope during the project | Ours is written on the Scope Card before purchase |
| Delivery | A rules-engine SaaS is live once you finish building every rule | An agency usually takes several weeks | Ours has a fixed delivery time shown before you buy, with faster options |
| What fails a check | A rules-engine SaaS often rejects silently or logs it for nobody to see | An agency build depends on what was scoped | Ours routes it to a named reviewer with the failed rule attached |
Questions about this product
How much does AI Document Validation cost?
The build is one fixed price, and you can see it for each delivery speed in the price and delivery panel on this page before you order. It covers everything on the Scope Card: the rule set for up to three document types, the cross-checks, the connection to your two systems and the rule-check report before launch. Extra rules or document types are quoted in writing first.
How is AI Document Validation different from AI Document Approval?
Validation checks a document's fields against completeness and correctness rules, a quality gate that catches missing or wrong data. AI Document Approval routes a document that already passed those checks through a decision workflow for sign-off. Most pipelines run Validation first, then Approval on the documents that pass, so approvers only see clean files.
Does AI Document Validation extract the fields it checks, or do I need Extraction first?
It checks fields that are already structured, whether they came from AI Document Extraction or a form submission. If your documents still need fields pulled from raw content, run AI Document Extraction first, since Validation's rules apply to fields that already exist rather than reading the document itself.
How much does AI Document Validation cost to run each month?
Running costs are paid in your own accounts, not to us. Expect roughly $30 to $200 a month for OCR and AI usage plus storage, and the figure scales with how many document pages pass through the checks. Fields that arrive already structured cost less to check than scanned pages. Monthly maintenance is optional if you want rules kept current.
What happens when a document fails an AI Document Validation rule?
It's held in a review queue with the specific rule it failed attached, so the person you named can see exactly what to fix without re-checking the whole document. Nothing that fails a rule moves on to your destination system automatically; it waits for a human decision first.
Is our document content safe with AI Document Validation?
Yes. Every credential and connected account is shared by adding our team as a user or creating a key you control during setup, never by email, and documents move only between the systems you connected. Validation checks field values against rules; it doesn't store or share document content elsewhere, and samples can be redacted before we see them.
How long does AI Document Validation take to launch?
The delivery time for each speed is shown in the price and delivery panel on this page, counted from the day your intake is complete and access is verified. Most of that time goes into writing your rules and testing them against your real documents, so the review you see before launch reflects the files your team actually handles.
Can I add a new validation rule later?
Yes. Adding or tightening a rule within your existing document types fits inside the monthly change hours that come with maintenance. A new document type or a large rule set change is a bigger job and gets a written Change Quote first.
Guides on this topic
All guides Catch a bad document before it costs you something.
Order AI Document Validation and it checks every document against your rules on a fixed delivery date. The scope above is what you get, in writing, before you pay.
Works well with
Intake & Extraction
AI Document Extraction for Real Estate
Extracts structured data from documents into your systems, adapted for Real Estate businesses that re-key data from leases, sale agreements and property…
Intake & Extraction
AI Document Extraction for Recruitment
Extracts structured data from documents into your systems, adapted for Recruitment businesses that key candidate CVs and compliance documents into their ATS…
Intake & Extraction
AI Document Extraction for Construction
Extracts structured data from documents into your systems, adapted for Construction businesses that lose time keying subcontractor invoices, delivery tickets and site…