DORA

Document Recognition & Analysis

DORA is a configurable document-recognition framework that helps organizations digitize documents, extract structured fields, review OCR results, and make document data searchable and usable in business workflows.

  • OCR-enabled digitization
  • Human-in-the-loop review
  • Search & export

surat-contoh-0001.pdf

Recognising…

Document type

Detecting…

Recognise · extract · review · verifySynthetic sample · illustrative values

The document problem

PDFs and scans arrive every day. Someone still has to read them, type the values, check them and find them again later.

  1. 01

    Read by hand

    PDFs and scanned images still need a person to read them before the data can be used.

  2. 02

    Typed again

    The same values are re-entered from documents into systems, one file at a time.

  3. 03

    OCR misreads

    Text recognition can confuse characters, especially on scanned pages.

  4. 04

    Unchecked values

    Extracted data has to be validated before anyone relies on it.

  5. 05

    Every type differs

    Letters, forms and reports each follow their own layout.

  6. 06

    Every field differs

    What matters in one document type is irrelevant in the next.

  7. 07

    Every workflow differs

    Each organization reviews and approves documents by its own SOP.

  8. 08

    Hard to find again

    Filed documents and their values need to be searchable later.

What DORA is

DORA is a Framework Code Product: a reusable document-recognition core, configured to each organization’s document types, business fields, verification workflow and SOP.

DORA is not assumed to replace your ERP, DMS or main archive without an agreed integration scope.

Your configurationper organization

  • Document types
  • Field templates
  • Extraction fields
  • Verification statuses
  • Confidence handling
  • Search filters
  • Export formats
  • Roles & permissions
  • Integration boundaries

DORA corereusable

  • 01Document intake
  • 02OCR & recognition
  • 03Field extraction
  • 04Verification workspace
  • 05Search & export
  • 06Operational dashboard

The FCP path

  1. 01UnderstandRequirement baseline
  2. 02DesignFunctional blueprint
  3. 03CustomizeConfigured DORA
  4. 04DevelopApproved extensions
  5. 05IntegrateIntegration specification
  6. 06DeployRelease & handover

How DORA works

Ten steps take a document from upload to usable data. People and system each own their part.

OCR & structured extraction

DORA turns unstructured document content into structured field data, based on the document templates configured for your organization.

01 · Document intakesurat-contoh-0001.pdf

  • PDFsurat-contoh-0001.pdf Accepted
  • TIFFscan-contoh-07.tiff Accepted
  • JPGfoto-dokumen-03.jpg Accepted
  • DOCXcatatan-contoh.docx Rejected · file type

Synthetic sample · illustrative values

Fields depend on the configured document type. Templates, required fields and confidence handling are defined during implementation.

Human-in-the-loop verification

OCR output is reviewed, not assumed correct. Every extracted field sits next to its place on the source page — checked, corrected and decided by a person.

surat-contoh-0001.pdf

Waiting verification

Document type

Official letterAuto-detected

Reject

01 / 05Open from the queue

Opened from the verification queue. Every extracted field is listed with its confidence.

Markers appear where field mapping is configured. The confidence method and review rules are agreed per implementation. · Synthetic sample, not a product screenshot

Operational dashboard

Volume, the verification queue, quality and recent documents in one view — so operations see where documents are before the queue grows.

Processed documents

128904 pages

Waiting verification

17Verified 104 · Rejected 7

Quality

91%avg. field confidence

14-day volume · documents per day

Needs attention

17 documents waiting verification

Open the verification queue

Recent documents

  • surat-contoh-0002.pdfWaitingOfficial letter · 2 pages
  • formulir-contoh-014.pngVerifiedOther · 1 page
  • laporan-unit-contoh.pdfWaitingOther · 12 pages

Illustrative values · KPI definitions, aggregation and refresh are agreed per implementation.

Configurable document model

Each document type carries its own template — fields, required flags, validation, confidence handling, statuses, review path, search and export fields. Types are configured with you, not assumed to be prebuilt.

Field template4 fields

  • Document No.RequiredRule · Pattern
  • DateRequiredRule · Date format
  • SubjectRequiredRule · Length
  • NameOptionalRule · Text
Statuses · Single review
Waiting verificationVerifiedRejected— final status, as configured
Search fields
Document No.SubjectName
Export fields
File nameDocument No.DateSubjectName
DORA One core for every typeIntake · OCR · extraction · verification · search · export

Sample configurations. Document types and templates are defined with you during discovery.

Access, privacy & governance

Who can upload, correct, decide, search and export is set per role and data scope. Sensitive data is handled according to your organization’s policy.

  • Access follows role and data scope.
  • Field correction is limited to permitted roles.
  • Verification decisions are limited to authorized roles.
  • Search, preview and export follow the same scope.

Verifier / Reviewer

Reviews and corrects extracted fields, and completes verification by workflow.

Baseline access

  • Verification queue
  • Field correction
  • Verification decision

Role baseline. Final permissions are agreed per implementation.

Privacy follows your policy

Sensitive data needs access control. Masking, retention, deletion and export rules follow your organization’s policy and applicable regulation.

Integration & enterprise fit

Designed to integrate with enterprise systems through agreed data contracts and integration boundaries.

DORAProduct core
  • Document repository / storage

    Retrieve or store files and results.

  • Business application · ERP · DMS

    Receive extracted fields or status.

  • Identity provider

    Central identity and role mapping.

  • API consumer

    Submit documents, query results or status.

  • Notification channel

    Queue or failure notifications.

Dashed = agreed data contract · Possible boundaries, scoped per project. DORA is not assumed to replace ERP, DMS or archive systems.

Agreed before build.

  • Source of truth for files, metadata and fields
  • Field names, types, formats and mapping
  • Authentication and authorization between systems
  • Retry, timeout, duplicate and error handling
  • Sync timing, monitoring, reconciliation and ownership

Why DORA

  • 01

    OCR-enabled digitization

    Digital and scanned documents become text.

  • 02

    Structured field extraction

    Values land in fields, by template.

  • 03

    Human-in-the-loop review

    People check what OCR returns.

  • 04

    Visual verification

    Each field is shown on the source page.

  • 05

    Searchable output

    Text and field values can be found again.

  • 06

    CSV · Excel · JSON export

    Data leaves in a usable format.

  • 07

    Configurable document model

    Types and fields fit your documents.

  • 08

    FCP customization approach

    A proven core, shaped to your SOP.

Request a demo

Discuss how DORA can be configured around your document types, extraction fields, verification workflow, and business process.

What happens next

  1. 01Discovery
  2. 02Blueprint
  3. 03Configuration & build
  4. 04Integration
  5. 05SIT & UAT
  6. 06Deployment & handover

Request a demo.

Fields marked * are required. Your request opens in WhatsApp, ready to send.

DORA