Back to document management

Requirements assessment · Document management

What do you need from your document management system?

Tell us how you want to work with documents, from signing in to synchronization. Your answers help us prepare a focused discussion and a rollout proposal.

Answer only what you already know. Requirements questions are optional and you can select multiple options. We use your answers to align the key features with your rollout.

Do not provide passwords, trade secrets or personal information in documents. Answers are not saved automatically; you can download your own copy before sending.

01 / 12

Starting situation and goals

We start from the current operation. Estimated data also helps.

What are the top three problems you would solve?
What kind of system do you work in now and what do you want to keep from it?
How many employees would use the document management system?
How many documents do you receive in a month?
What documents do you handle, such as invoices, contracts, delivery notes or HR records? What are typical page counts and file sizes?

02 / 12

Sign-in and work environment

Select your preferred sign-in methods and where you will use the system.

How would you like to sign in?
Where would you use the system?
Which interface languages do you need? Do you have sign-in, session or network requirements?

03 / 12

Organization and permissions

Who can see, modify or share the documents?

What isolation is required?
What roles should there be? Who can upload, edit, delete, share or approve?
How should employee onboarding, cover arrangements and access removal work?

04 / 12

Document intake, mail and digitization

We also assess the path of paper-based and electronic documents.

Where do documents come from?
What postal or digitization help do you need?
What file formats, legacy files and peak volumes need to be handled?

05 / 12

Processing, OCR and sorting

Verifiable data and classifications can be made from the contents of the document.

Which processing steps are important?
What should a document be linked to?
Which fields are required? What language or handwritten documents are received? How is recognized data checked?

06 / 12

Daily work, search and versioning

How do you find documents and collaborate on them?

What daily features are needed?
Which information do you most often search by? How should concurrent edits and older versions be handled?

07 / 12

Approval, tasks and notifications

Describe a typical process from receipt to closing.

What kind of process control is needed?
When would you like to receive notifications?
What is a typical approval process, who is involved and how long does it take to complete? Which notification channels are used?

08 / 12

Sharing, authentication and archiving

Sharing and retention expectations are agreed upon before implementation.

How would the documents be handed over?
What document certification and retention requirements do you have?
What retention periods, archiving rules and evidentiary requirements must be taken into account?

09 / 12

Integration, migration and reports

The related systems and old documents are also part of the needs assessment.

Which systems do you need to connect to?
What should be taken over from the old system?
Which systems do you currently use, how much content do you have, and what reports or exports do you need?

10 / 12

Synchronization

Between which storage locations and systems should the documents be up-to-date?

What do you want to sync?
In which direction should the data move?
How often should you sync?
What should synchronization cover?
Which system should take precedence when changes conflict? How should deletions, connection failures and files with the same name be handled?

11 / 12

AI assistant

What tasks would you entrust to the assistant and under what conditions would you use it?

What would an AI assistant help you with the most?
Under what conditions would it be used?
What specific question or task would you give the assistant? Do you have requirements for AI data handling or languages?

12 / 12

Rollout and priorities

Based on the answers, we can jointly select the first implementation step.

Which NOPA variant are you interested in?
Which three features are essential for launch, and which can wait?
When would you like to go live?
Is there a planned budget, storage or operational requirements? What training, support and trials are required?
What would make the rollout successful? Who makes the decision, and what other requirements should we discuss?

Last step

Contact details and submission

Contact details marked with an asterisk are mandatory.

Review responses

We use the information you provide to respond to your request. See our privacy guidelines (Hungarian).