Answers to your document management questions

What does a DMS do, when do you need records management, and what matters when changing systems? Start with the subject you are working on.

Discuss your project

Data queries in the ELO administration console
Data queries in the ELO administration console

DMS and ECM

A DMS helps people find, edit and approve documents. ECM connects content to wider business processes. Selection should account for applications, interfaces and user needs.

Records and registers

Registration, processing and retention rules need to work in everyday practice. We explain policies, separate registers and the Czech eSSL framework.

Migration and integration

Moving files is only part of a change. Metadata, history, permissions and interfaces also need to be planned.

AI in document workflows

AI can help with classification, extraction and summaries. A useful use case has a verifiable result and a clear response to uncertainty or errors.

Frequently asked questions

How do OCR and AI extraction differ?

OCR recognises text in an image. Extraction identifies fields such as supplier, date or amount. Classification determines the document type. These are different steps that can work together.

What happens if AI gets a document wrong?

The process needs review and correction paths. Uncertain results go to a person, rules check required fields and changes are recorded. A confident-sounding answer is not evidence of correctness.

Will our documents be used to train AI?

That depends on the service, contract and configuration. Before deployment, establish the processor, data location and retention, access controls and permitted use of inputs. The design should answer these questions explicitly.

Does a person have to check every document?

The level of review follows risk, input quality and the consequences of error. Routine steps can be automated; exceptions and important decisions need an owner. Set the rules after testing your documents.

How will we measure the value of automation?

Compare processing time, corrections, completeness and manual interventions before and during the pilot. Include both routine and difficult documents. Benefits should follow measurements, not a general AI promise.

What happens when a connected system is unavailable?

The integration should record failure, distinguish temporary issues and support safe retry. Depending on the scenario, use a queue or a controlled error response. Keep track of what has already been processed.

How do workflow and ELO Flows differ?

We use workflow mainly for user tasks, handovers and decisions. ELO Flows connects automation and integration steps. They can complement each other according to the process and available components.

What does ELO Metadata 2.0 add?

It supports structured data models and reusable parts through aspects. This helps align data across applications. The model still needs to fit users' work and the interfaces that depend on it.

What is a DMS used for?

A document management system stores files together with metadata, versions and access permissions. It can also manage approvals. People can find the document, understand its status and see the information around it.

How do DMS and ECM differ?

DMS focuses on documents. ECM takes a broader view of business content and how it supports processes. The functions often overlap, so evaluate the applications and workflows you need rather than the label alone.

Is a shared drive or cloud folder enough?

It may be enough for simple sharing. A DMS adds controlled metadata, version history, permissions, approvals and links to business applications. It is particularly useful when several people need to know which version to use and what happens next.

What are document metadata?

Metadata describe a document: its type, owner, counterparty, date or status, for example. They support search, filtering and automation. Some can be supplied by another system or extracted from the document rather than entered manually.

How do we avoid using an outdated version?

Keep one recognised location, a version history and a clear approved status. The process defines who can edit and approve. Sharing a link is generally preferable to circulating separate copies.

Can we search inside scanned documents?

Yes, when OCR has recognised the text and it has been indexed. Results depend on scan and recognition quality. Combining full-text search with metadata is useful for important fields.

Who can see sensitive documents?

Access is configured by role, group and application. Checks should include previews, exports, service accounts and role changes. Hiding a menu link is not an access control.

Do we need to replace our ERP or CRM?

Usually not. Document services can connect to existing applications. We first review their interfaces, available data and identity handling, then design the integration.

What moves during migration besides files?

Depending on the source, metadata, versions, folders, relationships and permissions may also be transferred. We agree scope and validation first. A trial shows which data need completing or correcting.

Cloud or on-premises?

Consider data sensitivity, availability, integration, operating capacity and cost. Compare backup, recovery and exit arrangements as well. Public-sector projects also need to check the rules for the specific cloud offering.

What affects implementation cost and timing?

Applications, users, interfaces, data quality and customisation all matter. A proposal should distinguish licences, implementation, migration and support. A useful schedule also accounts for the customer's preparation and participation.

What should we prepare for a demonstration?

Describe one routine process, the people involved and the current problem. An anonymised document and example fields are useful. Sensitive material is not needed for the first conversation; we can agree a separate transfer method.

Can we offer DEPO to our customers?

We can discuss sales cooperation. First we clarify the customer segment, your role and the handover to implementation and support. Terms are agreed for the specific partnership model.

Can our team carry out the implementation?

Your team can take agreed parts according to its experience and capacity. We define responsibilities, handover, documentation and escalation. The customer needs clear ownership of the whole project.

Can we use only the document component?

Yes, cooperation can focus on storage, integration services or a specific application. We first check functional and licensing dependencies. Not every component is a standalone product.

Are all demonstrated modules included in the base licence?

Licensing and delivery scope are defined in the proposal. Distinguish the ELO platform, custom modules, integrations and third-party services. Demonstrated functions are mapped to specific items when preparing an offer.

How does DMS differ from Czech eSSL?

A DMS supports document work and workflows. Czech eSSL also addresses the statutory registration and lifecycle requirements of the organisation concerned. The systems can work together, but a general DMS is not automatically an eSSL.

Who has statutory records management duties in Czechia?

The organisation's status and Act No. 499/2004 Coll., particularly sections 3 and 63, determine the duties. Retaining documents, performing statutory records management and using attested eSSL are different requirements with their own conditions and exceptions.

What happens to paper documents after implementation?

Their existence, location and link to the electronic record still need to be managed. A scan can help everyday work but does not necessarily replace the original. Conversion and retention must follow the applicable rules.

Does a Czech data box replace records management?

No. The data-box service is a communication channel. The organisation still needs to receive messages and attachments, register them, retain relevant information and manage the document lifecycle.

Does every email need to be registered?

The content and its connection to the organisation's work matter, not email as a channel alone. Procedures should define what must be captured, where and by whom. Routine technical traffic and substantive business records need to be distinguished.

How are a document and a case file related?

A document is an individual record; a case file brings related records together. Storing files side by side is not enough. Relationships, completion status and closure and retention rules also matter.

Can a contract application act as a separate register?

Define the records, metadata, responsibilities, retention and any link to the main records system. Czech separate registers have specific requirements. Being a standalone application does not by itself establish that legal status.

Can records be deleted as soon as retention expires?

Not automatically. Follow the applicable appraisal and disposal procedure, including archival selection where required. Other retention duties or a hold may prevent deletion even after the scheduled period.

What is a SIP package?

A Submission Information Package carries documents and related metadata into an archival process. It is not simply a ZIP of files. Its structure and validation depend on the applicable standard and receiving archive.

What does Czech eSSL attestation establish?

It assesses a system against specified Czech requirements. Check the actual product, version and validity. It does not confirm that every customer has configured and used the system correctly, or that another country's rules are met.

Where can we verify a Czech eSSL attestation?

Consult the official information from the Czech Standardization Agency's attestation centre and the Ministry of the Interior. Match it to the offered system and request the relevant evidence from the supplier.

Does an attested product remove the need for an organisational review?

No. Product assessment and review of an organisation's practices serve different purposes. A review can reveal gaps between internal procedures, configuration and what staff actually do.

Does a signature image prove an electronic signature?

The visible mark alone does not establish the signer's identity or document integrity. Distinguish appearance, the signing technology and the level required for the transaction, including in a signing workspace.

What matters most when replacing a records system?

Obtain data descriptions and exports early, map document and case relationships, and agree how open work will continue. Trial migration and result checks belong in the plan before the old system is retired.

How can we reduce vendor lock-in?

Agree export of documents, metadata and relationships, interface documentation and exit assistance. Test whether the export is usable. Being able to download files is not the same as transferring the whole solution.

Is long-term preservation the same as backup?

No. Backup primarily supports recovery after loss or failure. Preservation also addresses readability, metadata, provenance and controlled handling over time. Both are needed, but they serve different purposes.

What information is needed for an assessment?

Usually internal procedures, a system description, application and interface lists, and representative work examples. Access is agreed in advance. Sensitive documents should not be sent through a public enquiry form.

What will the assessment deliver?

Findings with impact, priority and recommendations. Depending on scope, it also includes an action plan, responsibilities and follow-up checks. The aim is to support practical change, not just list shortcomings.

Can you advise on another vendor's system?

Yes. Guidance, analysis and assessments do not require ELO or DEPO. We focus on your processes and requirements. Changes to another vendor's product need to be agreed with that supplier.

Must every application go live at once?

No. A DMS can often start with one application. Statutory records management also needs continuity of registration and operation. Plan stages around those duties and dependencies, not just screens.

Can DEPO suit a smaller organisation?

We also prepare smaller implementations. The required registration scope, roles, integrations and operating model matter. A demonstration helps separate essential functions from extensions you do not yet need.

What support response times do you offer?

Response times, service hours, priorities and escalation are defined in the support contract. They reflect the system's importance and responsibilities shared by the customer, ALTAIR and other suppliers.

What should system handover include?

Configuration, interfaces, roles, operating procedures and custom-extension documentation, as well as the application. Agree administrator access, backup, support and upgrade arrangements in the requirements.

How should users prepare for the change?

Training should follow their roles and real tasks. A pilot group, short guides and a clear support contact help. Administrators and records staff need their own training, not just an end-user demonstration.

Does an English interface make a records system suitable for any country?

No. Language is separate from legal requirements. Retention, disposal, signatures, access and archival transfer must be designed for the jurisdiction and sector in which the system is used.

Is the UK's section 46 Code of Practice a product certificate?

No. It is guidance for records management by public authorities. A supplier's software and the organisation's procedures need to be assessed against the requirements that actually apply to the project.