Docutise
API docs Request access
Product

A document audit built around evidence.

Docutise renders every page, examines it across eight lanes, scores it against an audit profile, and hands a reviewer defensible exceptions — not a black-box verdict.

Evidence lanes

Eight lanes, each producing proof you can point to.

Every lane produces its own evidence — anchored to a page and region, stamped with a producer version and confidence — so a finding can be re-examined long after the audit ran.

Page quality

Deterministic visual scoring for blur, low resolution, low contrast, skew, crop issues, exposure, noise and compression artifacts — so a defect can't hide behind a bad scan.

blurskewcontrastunreadable

PDF structure

Page count, encrypted or corrupt containers, AcroForm indicators, unsafe PDF features, annotations, metadata summaries and render failures — the container as evidence.

encryptedacroformannotations

OCR & layout

Extractable text, page-level OCR blocks and layout regions become reusable evidence coordinates that every downstream finding can point to.

ocr_blockslayout_regionscoordinates

Barcodes

Detection and decoding with a masking policy for sensitive values, plus required-barcode exceptions when a barcode must be present and readable on a given document.

detectdecodemaskingrequired

Signature evidence

Wet signatures, initials and electronic signature blocks — kept separate from PDF digital-signature evidence, because a visible mark and a cryptographic signature are different claims.

wet_signatureinitialse_signature

Date evidence

Missing, invalid, future, stale or unparseable dates — evaluated against the active audit profile's present-date policy for the document and loan stage.

missingfuturestale

Notary evidence

Notary language, seal and stamp indicators and commission language — with notary-related uncertainty surfaced explicitly rather than resolved silently.

sealstampcommission

Alteration signals

Strikeout, whiteout, void or cancel marks, obscured text and suspicious blank regions — the signals that separate a clean document from a tampered one.

strikeoutwhiteoutvoid_mark

PDF digital signatures are their own lane. A visible ink mark and a cryptographic PDF signature answer different questions. Docutise keeps them distinct so a reviewer never confuses "someone signed here" with "this container is cryptographically intact."

Review workflow

Catch it, fix it, and sign off with confidence.

Docutise separates observed evidence from business decisions. The system surfaces exceptions; people decide what happens next — with roles that mirror how QC teams already work.

  • Reviewers triageThey work the exception queue, examine evidence panels and recommend actions — but never finalize a document.
  • Admins make the callAcceptance, rejection, override and profile publishing are admin-only, audit-logged actions.
  • Cure & re-uploadSend a defective document back for replacement and track the corrected, re-uploaded version to resolution.
Exception · Closing Disclosure p.4Needs review
Stale date
content.date_stale
Notary seal
0.61 · uncertain
Recommended action
Request re-upload

Every exception carries a page, a region, a producer version and a confidence — visible in the console and in the export.

Audit profiles & scoring

Set the rules once — and know exactly why anything passed.

An audit profile defines the loan stages, required checks, present-date policy, accepted signature evidence, notary indicator policy, barcode policy, redaction policy and override codes for each document class.

Purpose-built for loan documents

Loan Estimate, Closing Disclosure, URLA, Borrower Authorization and Notary Acknowledgment — each with its own required checks, dates, signatures and notary policies.

Nothing passes on a blocker

A blocking finding caps the score and stops an automatic pass cold. The recommended action and any admin-review requirement come with the result.

Change the rules without surprises

Profiles are admin-published, so a rule change is deliberate and reviewable — never a silent shift under a live audit.

audit_package/
# durable, defensible artifacts
manifest.json
audit_report.pdf        # audit report
audit_report.json
compliance_evidence.json # access + review events
findings.csv
evidence/               # checksum-verified bytes
  page_0004.png
  overlays_0004.json
checksums.txt
Exports

Every audit ends in a package you can hand to an examiner.

Docutise exports durable JSON, CSV and PDF reports, compliance-evidence JSON and checksum-verified evidence bundles — through both the console and the API.

  • Immutable audit reportsGenerated from the audit's own report data and stored as immutable artifacts with signed download paths.
  • Compliance evidenceAccess events, review events, final reviews, overrides and model-version metadata — exported for the record.
  • Checksum-verified bundlesZIP evidence bundles carry a manifest and verified artifact bytes — sensitive downloads, audit-logged.

See the evidence model on your own documents.

Request early access for a local pilot — we'll walk your team through the console and the API.

Request early access Read the API guide