--- title: "Automating Document Records and Deadlines" description: "A missed deadline is not down to one person's inattention. It is down to the date living in an email attachment somebody read on a Friday afternoon." canonical: "https://interfase.sk/en/news/automating-document-records-and-deadlines" lang: "en" last_updated: "2026-11-06" --- # Automating Document Records and Deadlines > A missed deadline is not down to one person's inattention. It is down to the date living in an email attachment somebody read on a Friday afternoon. Published: 2026-11-06 - Deadlines get missed not through inattention but because the date exists nowhere as data, only as a sentence in a document. - Every document needs an owner — without one, the reminder goes to everybody and nobody acts. - A reminder one day ahead is useless; deadlines need multi-stage alerts with escalation. - Automation should not decide anything about the content of a document, only make sure somebody reaches it in time. The contract renewed itself for another year, because the notice period expired two weeks ago. Nobody neglected it — that date was on page four of a PDF, and the document sat in a shared folder nobody had opened since signing. This is not a failure of people. It is a failure of record-keeping. ## One place, not four The first and most important step is not deploying a tool but deciding that **there is one place where documents are registered**. Not a mailbox, not a shared drive, not a drawer — one place that is binding. Without that, every further automation is built on sand, because only what the system knows about can be tracked. ## A document without metadata is just a file A PDF on its own tells nobody that something expires in six months. Every entry therefore carries a few mandatory fields: - **Document type** — contract, permit, certificate, insurance policy, licence. - **Counterparty** and internal reference. - **Valid from / to**. - **Deadline for action** — notice, appeal, renewal. This is a different date from the end of validity, and it is the one most often missed. - **Owner** — a specific person, not a department. As long as these fields are filled in, tracking deadlines is trivial. When they are not, it cannot be done at all. ## The owner is the most important field A reminder sent "to the department" moves nobody. Everyone assumes the other person is handling it. So every document has exactly one owner responsible for the action, and a deputy for absences. If the owner leaves the company, their documents have to be reassigned — otherwise reminders go to an empty mailbox. ## A reminder one day ahead is useless An alert 24 hours before a notice period expires only announces that nothing can be done. Deadlines need **a multi-stage regime**: - **a first alert** far enough ahead to decide (for contracts, typically 60–90 days), - **a second** at the moment action is due, - **escalation to a manager** if nothing has happened. The third point is what holds the whole system together. Without escalation, reminders become noise people click past. ## What can be extracted automatically and what cannot Surprisingly much can be extracted from documents by machine — dates, amounts, counterparties, reference numbers. For structured types (invoices, orders) it works reliably, much as with [collecting and processing form data](/blog/ako-automatizovat-zber-a-spracovanie-dat-z-formularov). Contracts are different. **A notice period tends to be phrased as a sentence**, not a field, and its interpretation has legal consequences. The sensible approach is to let the system propose a value and have a person confirm it — not adopt it automatically. And one hard rule: scanned documents that are images with no text layer have to be converted at the point of filing. Otherwise they are in the register but cannot be searched. ## Who sees what Contracts, personnel documents and insurance claims should not be open to the whole company. Permissions follow document type and department, and access to sensitive records is logged — this connects to what we describe in [access audits and security logs](/blog/audit-pristupov-a-bezpecnostne-logy-vo-firemnej-aplikacii). ## Connecting to approvals A register only makes sense once it follows on from how documents come into being. If a contract lands in the register automatically after signing, the system stays current. If somebody has to upload it by hand, it will be incomplete within six months. That part is covered in [automating contract approval and signing](/blog/automatizacia-schvalovania-a-podpisu-zmluv). ## Where to start With an inventory of one document type — ideally the one where missing a deadline hurts most. Usually that means lease and supplier contracts, or permits and certificates with limited validity. List them, add an owner and a deadline, and switch on the alerts. It is a few days of work and it reveals how many documents the company does not actually have under control. If you are working on this, [get in touch](/kontakt). We handle it under [custom development](/riesenia/vyvoj) — examples in our [case studies](/referencie). --- Web version: https://interfase.sk/en/news/automating-document-records-and-deadlines llms.txt: https://interfase.sk/llms.txt