Document Workflow Automation: Capture, Version, Renew

A customer asks for a copy of the contract signed three years ago. Someone opens the shared drive and finds four files named final, final_v2, final_signed and final_signed_REAL, and nobody can say which one was actually countersigned. In the same week an inspection certificate for one site expired eleven days ago, and the first person to notice it will be the inspector. Neither is a filing discipline problem; both are the predictable output of a setup where documents are stored but not managed.

Where corporate documents actually live

In most mid-sized companies the document estate is spread across four places, and the same document often exists in three of them at once:

• A shared network drive with a folder tree designed by whoever set up the server, and a naming convention that stopped being observed in year two.
• Email attachments. The signed copy exists only inside one person's mailbox, which becomes a retention and continuity problem the day that person leaves.
• Personal cloud folders. Convenient for the individual, invisible to everyone else, and outside your backup and access policy.
• Paper. Delivery notes signed at the customer site, certificates issued by an inspection body, wet-ink contracts in a filing cabinet.

The five document classes that cause the most operational pain are contracts, delivery notes, invoices, quotations and certificates. Each of them is attached to something else in the business: a contract to a customer, a delivery note to an order, a certificate to a piece of equipment or a person. A file store cannot express that relationship, and that is the whole of the gap.

Capture the document where it is created

The design decision that determines whether the system gets used is where capture happens. A separate capture step performed later by someone else will be skipped under load, and a partly complete register is worse than none because people still check the drive first.

Capture at source means the technician photographs the signed delivery note before leaving the site and it attaches to that job, not to a folder to be sorted later. It means the quotation is generated by the system rather than assembled in a word processor and emailed, so the sent copy and the stored copy are the same object by construction. Elevatora SAHA works this way for lift maintenance and field service; Elevatora İMALAT does the same for lift-component manufacturing documentation.

Where a document must travel between two systems you already run, the connection matters more than the storage: reading the customer record from the CRM and the order from the ERP is usually the first work item, not the last.

Version control: one current copy, everything else superseded

Versioning is not a nice-to-have in contract and document management; it is the reason the system exists. Three rules cover most of the requirement.

1. 1. One record, many versions

   The contract is a record with an identity that never changes. Draft 1, draft 4 and the countersigned copy are versions of that record, not four separate files. Anyone opening the record sees the current version first and the history underneath it.

2. 2. Status is a field, not a filename

   Draft, out for signature, executed, amended, superseded, terminated. When status is a field you can list every executed contract in one query. When status lives in a filename you can only search for text patterns and hope.

3. 3. Every change is attributable

   Who uploaded the version, when, and what changed. This is the same audit trail requirement that applies to any administrative process, covered in more depth in the back office automation guide. Auditors ask for it, and so does the first colleague who disputes which terms were agreed.

Anything with an expiry date is a workflow, not a field

Certificates, contracts, inspections, insurance policies and warranties all expire, and storing the expiry date achieves nothing on its own. The date has to be a real date field rather than text inside a PDF, assigned to a named owner, and connected to a schedule that fires before the date rather than after it.

Configure more than one reminder point rather than a single alert on the day: a long-lead reminder so the commercial team can renegotiate, a medium one to trigger the paperwork, a short one that escalates to a manager. Send them to a person, not a shared mailbox — a reminder addressed to everyone is addressed to nobody.

What OCR does, and where it stops being enough

Optical character recognition turns an image of a page into machine-readable text. That is the whole of its job, and it is not the whole of yours — after OCR you still hold an undifferentiated block of text. Four further steps stand between that text and an automated process:

• Classification. Is this an invoice, a delivery note or a certificate? Supplier documents arrive in dozens of layouts and rarely announce their own type in a fixed place.
• Field extraction. Which number on the page is the total, which is the tax, which is the order reference, and which is the supplier's internal code. Position-based rules break the first time a supplier redesigns a template.
• Validation. Does the extracted total agree with the purchase order and the goods receipt? Extraction without a three-way match simply moves the error earlier in the chain.
• Exception handling. A confidence threshold, below which the document goes to a named person with the extracted values pre-filled for correction instead of being accepted silently.

Those four steps are where a language model earns its place, because the input has no fixed shape. How that layer sits on top of systems you already run is covered in AI integration. Build the confirmation step before the extraction step; an extraction pipeline with no human review path gets switched off after its first bad month.

Search and permissions

Search has to work on metadata as well as content: every executed contract for one customer, every certificate expiring next quarter, every delivery note for one order. Full-text search alone answers none of those questions reliably.

Permissions have to be modelled on the record, not the folder. Salary letters, commercial terms and legal correspondence each have a different audience, and folder-level access control degrades into either over-sharing or a queue of manual access requests. Segregation of duties applies here as in finance: uploader and approver should be separable, and both recorded.

Budget and timeline

• Single focused module: $3,000–6,000, 2–4 weeks. One document class, capture at source, versioning and renewal reminders.
• Multi-department system: $8,000–15,000, 4–8 weeks. Several document classes on a shared data model and one permission structure.
• Platform with an AI extraction layer: $20,000+, 3–6 months.
• Annual maintenance: optional, 12–25% of build cost.
• Licence: perpetual, unlimited users, source code delivered.

The first clickable prototype arrives within 2–4 weeks, so your document owners judge the capture flow by using it rather than by reading a specification.

Bring one document class and the question you most often fail to answer about it, and we will scope the first module against that. Request a quote, or review the delivery bands on the pricing page.

Frequently asked questions

What is document workflow automation?

Software that captures a document at the moment it is created or received, attaches it to the record it belongs to — a customer, a site, a purchase order — and then drives what happens next: approval, versioning, retention and renewal reminders. It is different from a file store, which only holds the file.

Is OCR enough to automate document handling?

OCR converts an image into text. It does not tell you which of the numbers on a page is the invoice total, whether this version supersedes the one signed last March, or who is allowed to see it. OCR is the first step; classification, field extraction, validation and routing are the parts that produce the time saving.

How do renewal reminders work for certificates and contracts?

Any document with an expiry date carries that date as a structured field, not as text inside the PDF. The system schedules reminders at points you configure ahead of expiry, sends them to a named owner rather than a shared mailbox, and escalates when the date passes without action.

Do we need to migrate every old document first?

No. Start with documents created from the go-live date forward, and backfill only the categories with a legal or commercial reason — active contracts, valid certificates, open disputes. A full historical migration is a separate project with its own budget and rarely belongs in the first release.

What does a document workflow module cost at KodDelta?

A single focused module is $3,000–6,000 and ships in 2–4 weeks. A multi-department system covering several document types with a shared permission model is $8,000–15,000 over 4–8 weeks. Annual maintenance is optional at 12–25% of build cost. The licence is perpetual, users are unlimited and source code is delivered.