Blog – Document Management, Best Practices and Case Studies - LogicalDOC

When AI Becomes a Co-Author

2026-09-23T08:00:04+00:00

How versioning, metadata, search and governance take on a new role in AI-assisted document creation.

Calling AI a "co-author" is deliberately provocative.

Operationally, the term accurately describes what is happening: an increasing portion of a document's content may be proposed, transformed, or generated by an artificial intelligence system; however, accountability remains with humans.

Most international guidelines rule out the possibility of an AI system being formally considered an author, as it cannot assume responsibility for the work's accuracy, integrity, and originality. Consequently, responsibility remains with the individuals who use and review the generated content.
It is precisely this separation between the contribution to creation and accountability for the outcome that makes this issue significant for document management.

Within corporate workflows, a document is no longer merely a final result but also the series of processes and steps that led to that result.
Document management must therefore begin to view the document not just as an object, but as the outcome of an information production process.
This represents a significant shift, placing tools and functions that have long existed in Document Management Systems back at the center of attention.

Versioning: from a history of changes to a history of decisions

Version control is one of the clearest examples. Traditionally, this function prevents revision management from relying on separate copies of the same file—often renamed manually in an imprecise or incorrect manner—which makes it difficult to identify the correct version or track the history of changes. A versioning system, by contrast, keeps revisions within a single document, preserves their history, and allows clear reconstruction of the document's evolution.
With the advent of AI, versioning takes on a secondary function: it becomes a way to reconstruct the content's evolution.

This does not necessarily mean preserving every single prompt or variation produced during an AI session; doing so would be pointless and likely counterproductive. It means identifying the key stages of the document lifecycle: draft generation, human review, substantial modification, approval, and publication.

The distinction LogicalDOC makes between "Document Version" and "File Version" is a useful example. The system also tracks metadata changes that don't necessarily involve replacing the physical file.
This distinction is valuable because a document's evolution may involve not only its content but also its context, status, and provenance information.

Metadata becomes provenance metadata.

The role of metadata is also shifting. Traditionally, metadata describes the document itself—client, project, author, date, document type, department, and status.
In the future, it may increasingly describe the very process by which the document was produced.
For instance, an organization might choose to record whether AI was used during document preparation and what role it played, which documents served as primary sources, and who performed the final review.
This does not necessarily require dozens of new fields. The real value lies in transforming information that is currently implicit into structured, queryable context.

LogicalDOC, for example, allows users to define document classes, attribute sets, and custom metadata, including validation rules and default values. While these features were originally designed to classify business documents, they can also be used to model information regarding the content creation and review process.

Search must find the right document, not just the most similar one.

AI also introduces a seemingly paradoxical issue: the easier it becomes to produce content, the more content we must manage.
A single document could spawn a summary, a translation, a simplified version, a presentation, an FAQ, or a new AI-generated draft.
All of these are semantically very similar documents.
In such cases, effective search cannot simply identify what most closely resembles the query.
It must help determine which document is authoritative.

Semantic search is therefore important, but it does not replace metadata, versioning, permissions, or document status; rather, it makes them even more essential.
Maximum value is achieved when semantic similarity is integrated into a document management system that simultaneously preserves document classification, security, status, and history.

In LogicalDOC, semantic search uses embeddings to locate documents based on meaning rather than just the presence of identical words.

Workflows: where responsibility returns to humans

When part of the work is delegated to AI, it becomes necessary to clearly define where automation ends and human responsibility begins. Workflows are a traditional, well-established feature of DMS platforms, yet they can take on even greater significance with the advent of AI. An approval is no longer merely a bureaucratic or administrative step; it can become the act by which a person assumes responsibility for content produced or modified with AI assistance.
Documentable human review is becoming a key component of the trust architecture surrounding AI-generated content.

In a DMS like LogicalDOC, workflows already enable processes where different users review, approve, or reject a document.
While AI can accelerate document creation or modification, the workflow determines who authorizes the final result.

AI should not have more access than the user.

A less obvious but fundamental issue remains. If an AI assistant is to help draft a document using corporate information, it must first be able to search for that data; however, this cannot entail indiscriminate access to the entire repository. For instance, a user lacking permission to read a confidential contract should not be able to indirectly retrieve its contents by asking the AI to prepare a report.
Authorization must therefore be applied prior to retrieval, not merely to the final document. This effectively makes the DMS permission system a component of the AI architecture.
As agents become increasingly autonomous in searching for and manipulating information, it becomes ever more critical that they operate within the same document boundaries established for human staff and business processes.

A DMS must do more than just "feature AI"

For this reason, evaluating a Document Management System solely based on the presence of AI capabilities risks focusing on the wrong question.
The more compelling question is:
how effectively can the document system govern what the AI creates, modifies, and utilizes?
Features such as AI-powered document processing or semantic search can certainly enhance information classification, extraction, and accessibility.
Yet, in this context, the value of a DMS like LogicalDOC lies not merely in adding AI to the repository, but in the existing infrastructure surrounding those documents—versioning, metadata, security, workflows, audit trails, and search capabilities.
After all, when artificial intelligence enters the creation process, the challenge shifts from producing a better document more quickly to understanding—even months or years later—how that document came to be.
And the more AI contributes to drafting corporate documents, the more vital this record-keeping becomes.

Secure Document Sharing for Clients That Works

2026-09-15T13:32:17+00:00

A client asks for the latest contract, technical drawings or case file. The document is in someone’s inbox, an old shared drive and possibly attached to a chat message. Secure document sharing for clients is designed to remove that uncertainty. It gives clients quick access to the correct information while allowing your organisation to retain control over security, permissions and document history.

For operations teams, the issue is not simply sending files safely. It is creating a dependable process that prevents outdated versions, reduces repeated requests and provides evidence of who accessed sensitive information. For IT and compliance teams, it means extending access beyond the organisation without creating an unmanaged copy of the document estate.

Why email attachments create a control problem

Email remains useful for routine communication, but it is a weak foundation for sharing business-critical documents. Once a file is attached, it can be forwarded, downloaded to unmanaged devices or retained indefinitely in mailboxes. Replacing an outdated document means sending another attachment and trusting every recipient to use it.

“Security is not just about protecting documents — it’s about controlling how they move, who sees them, and what happens next.”
— Laura Mitchell, Information Governance Consultant

This creates a familiar cycle of operational delays. Staff spend time answering requests for files that have already been sent. Clients work from superseded documents. Teams cannot easily confirm whether a recipient received or viewed a file. When a dispute, audit or data-access request arises, reconstructing the history can take far longer than it should.

The risk rises when documents contain personal data, financial information, intellectual property, legal records or commercially sensitive plans. A password-protected archive may provide some protection, but it does not solve version control, permissions management or auditability. The password itself is often sent through the same email channel.

A controlled document management environment changes the model. Rather than distributing multiple copies, authorised users access a governed version held in a central repository. The organisation can update, withdraw or replace a document without losing track of what has happened.

What secure document sharing for clients should provide

A useful client-sharing process balances protection with usability. If access is difficult, clients will continue to request attachments, use personal file-transfer services or ask staff to work around the system. If access is too broad, confidential information becomes unnecessarily exposed.

The right balance depends on the document type, the client relationship and the regulatory environment. A construction project may require controlled access to changing drawings and site records. A legal team may need strict matter-based folders and detailed access history. A healthcare provider may need stronger controls around personal and clinical information. The principle remains the same: each client should see what they need, and nothing more.

Permission-based access

Permissions should be assigned at folder, workspace or document level according to a defined access model. A client may need read-only access to approved documents, while internal project managers need the ability to upload and revise files. External suppliers may require access to only one portion of a project repository.

Role-based access is particularly valuable when client teams change. Instead of managing permissions document by document, administrators can assign access to a client group and remove it when the engagement ends. This reduces the chance that former contacts retain access because an individual permission was overlooked.

Version control that clients can trust

Clients should not need to compare filenames such as “final”, “final_v2” and “final_revised”. A document management system should maintain a clear version history, identify the current approved version and preserve previous versions where policy requires it.

“Clients work faster and make better decisions when they access one trusted source of truth instead of scattered file copies.”
— David Harper, Digital Transformation Advisor

This is more than an administrative convenience. When clients can access one recognised source of truth, approvals move faster and disputes over which document governed a decision become less likely. Internal teams also gain confidence that a correction or updated specification will reach the right audience.

Audit trails and accountability

For sensitive documents, it is often necessary to know who uploaded a file, changed it, accessed it or approved it. Audit trails create that evidence without relying on scattered email records. They support internal governance and can simplify responses to client queries, quality reviews and compliance investigations.

Audit requirements vary. Some organisations need detailed event records for every action, while others mainly need to demonstrate that documents were shared through an authorised process. Build the level of tracking around the risk involved, rather than applying the same restrictive process to every file.

Expiry, revocation and controlled downloads

Client access should not automatically last forever. Time-limited access is useful for tender packs, due-diligence materials, temporary project collaboration and sensitive reports. When the period ends, access can be removed without asking recipients to delete copies from their inboxes.

Download controls also require judgement. Preventing downloads may be appropriate for highly confidential information, but it can frustrate clients who need offline access to working documents. In many cases, controlled download rights combined with clear permissions, audit records and document retention policies offer a more practical approach.

Secure sharing is not just about sending a file safely. It is about keeping control before, during and after access.

Build the process around the client journey

Technology works best when it reflects how documents move through a real client relationship. Start by identifying the documents that are regularly shared externally, who approves them and when the client needs access. This will usually expose duplicated effort, unclear ownership and folders that mix internal working papers with client-ready content.

Create dedicated client or project workspaces rather than giving external users access to broad internal directories. Within each workspace, separate approved client documents from internal drafts, notes and working files. This simple distinction protects confidential internal material and makes the client experience easier to understand.

Establish naming conventions and document statuses that are meaningful to both staff and clients. For example, a drawing may move from draft to review to approved for construction. A policy may be marked as current, superseded or archived. Clear status labels reduce reliance on informal explanations and prevent users from acting on unfinished material.

Approval workflows are especially useful when documents must be reviewed before external release. A workflow can route a contract, report or technical submission to the appropriate people, record the decision and place the approved version in the client-accessible area. This reduces the risk of a well-intentioned employee sharing an incomplete or unapproved file under time pressure.

Give IT control without creating a burden for users

Secure sharing must fit the organisation’s wider information architecture. IT teams need to consider identity management, authentication, retention, backup, encryption, hosting location and integration with existing business systems. Operations teams need quick retrieval, straightforward upload processes and confidence that clients can use the system without extensive support.

A platform that supports cloud, hybrid-cloud and on-premise deployment gives organisations more choice in meeting operational, security and data-residency requirements. The preferred model may depend on industry rules, internal infrastructure and the sensitivity of the documents involved. There is no universal deployment answer, but there should be a clear rationale for the one selected.

Integration also matters. If client documents originate in a line-of-business system, CRM platform or workflow application, manual exporting and uploading can recreate the errors the new process is meant to remove. API access and well-planned integrations can keep document creation, classification and sharing connected to existing work.

LogicalDOC supports this approach by centralising documents, applying granular permissions and maintaining version histories and audit information in a structured repository. Its modular design allows organisations to introduce the capabilities they need while retaining deployment flexibility and professional support for more complex requirements.

Common mistakes that weaken client document security

The most common mistake is treating a shared folder as a client portal without reviewing its inherited permissions. A folder can appear correctly organised while allowing users to browse material outside their intended scope. Test access from the perspective of each client role before making a workspace available.

Another mistake is focusing entirely on access controls while ignoring document quality. Securely sharing the wrong version still creates commercial and compliance risk. Combine permissions with document statuses, approval workflows and clear ownership for high-value records.

Finally, do not assume adoption will happen on its own. Give internal users a short, practical process for uploading, classifying and releasing documents. Give clients a simple explanation of where to find information and whom to contact if access fails. A system that cuts information retrieval time from hours to seconds only delivers that benefit when people use it consistently.

Start with the documents that cause the most friction

There is no need to migrate every historical file before improving the client experience. Begin with a high-volume or high-risk document process, such as project handovers, client reports, contract packs or compliance evidence. Define the access roles, approval points and retention needs, then measure how much time is spent finding, sending and correcting documents.

A well-designed sharing process gives clients a more professional experience while reducing the daily burden on internal teams. The next client request for a critical file should be answered with controlled access to the right version, not another search through inboxes.

AI knows the answer. But can it prove it? Defensible AI and the new role of document provenance

2026-08-26T10:28:44+00:00

The introduction of Artificial Intelligence into document management immediately raised questions about the system's accuracy and the plausibility of its answers. Today, thanks to rapidly evolving technology toward Intelligent Document Processing and AI agents capable of automating processes and guiding strategic business decisions, it's essential to be able to answer other questions, such as:

What information was that answer derived from? What version of the documents was used? Who approved those documents? What sources were retrieved by the system?

In short, true evolution isn't moving from documents to answers, but from answers to verifiable answers.

It's around these questions that the concept of Defensible AI is emerging: not a formally defined regulatory category or an international standard, but an increasingly useful way to describe AI systems whose results can be reconstructed, verified, and defended with evidence.

Explainable AI and Defensible AI: They're Not the Same

A system may be able to explain, at least in part, how it reached a given conclusion. But an organization may still be unable to demonstrate what evidence was available when that conclusion was reached.

This is an important distinction. Explainability primarily concerns understanding a model's behavior, while defensible AI pertains to the entire context in which that model was used: data, documents, versions, users, permissions, transformations, retrievals, outputs, controls, and subsequent decisions.

In other words, it's not enough to be able to say: "The AI produced this answer."

It should be possible to demonstrate: "The AI produced this answer on March 14th using these specific versions of these documents, retrieving these steps, with this version of the model and these instructions; the result was subsequently verified by this person and used in this process."

This is a fundamental difference.

The NIST AI Risk Management Framework explicitly links trustworthy AI to accountability and transparency, encompassing everything from design decisions and data to how decisions were made during and after deployment. It encourages organizations to document data provenance, including sources, origins, transformations, dependencies, and metadata.

The challenge isn't just to make AI smarter, but to make its relationship with information traceable.

Evidence Provenance: Where Does AI's Statement Come From?

The concept of provenance didn't originate with artificial intelligence, but when applied to document-based AI, this principle becomes particularly interesting.

A response generated by a business system should ideally preserve a true chain of evidence. If the source of the response is a document, it's necessary to identify its precise version, provenance, owner, acquisition date, any approvals, and any changes made over time.

The document can then be converted, OCRed, classified, segmented, enriched with metadata, or transformed into embeddings. The RAG system can then retrieve some of these segments and insert them into the context provided to the linguistic model. The model finally processes a response, which can be accepted, modified, or rejected by a human and, possibly, become the input for a subsequent workflow.

Provenance should ideally span this entire chain.

This is probably one of the most important differences between a simple generative AI application and a true Traceable Document AI.

RAG improves grounding. But it doesn't guarantee traceability.

Retrieval-Augmented Generation is often touted as one of the main solutions to the problem of hallucinations in Large Language Models.

The idea is relatively simple: instead of asking the model to respond solely on the basis of the knowledge contained in its parameters, the system retrieves information from a knowledge base and provides it as context for generation. But connecting an LLM to a document repository doesn't automatically make the system reliable.

The problem simply shifts. You need to know what the repository contains.

A RAG system can perfectly well retrieve the wrong document. It could mistakenly use an outdated procedure or retrieve a draft instead of the approved version. Deliberately manipulated documents could even influence it. (For more information)

In other words: RAG without document governance risks becoming simply a very efficient way to retrieve ungoverned information.

Versioning: A traditional DMS function becomes an AI governance function

Here an interesting paradox emerges. Some of the tools needed to govern advanced AI systems are not new at all.

Version control, for example, has been a fundamental function of document management systems for decades.

With AI, however, it takes on a different meaning. For a human user, it's often sufficient to know the current version of a document, while reconstructing a decision made by AI may require knowing the current version at a specific point in the past. Without versioning, that response becomes difficult to verify. And without the ability to associate retrieval and output with the actual version used, even a seemingly transparent RAG system can lose a crucial piece of its evidence.

Significantly, the NIST Research Data Framework considers versioning essential for data traceability, data reconstruction, change tracking, and error correction.

Audit trail: not just who modified a document

The same reasoning applies to the audit trail. Traditionally, a DMS records operations such as the creation, modification, download, approval, movement, and deletion of documents.

In an AI environment, the audit trail can become much broader, as we gradually move from a document audit trail to an AI evidence trail.

The former describes the document's history. The latter should connect that history to the decision's history.

This principle is very clearly reflected in the EU AI Act.

For systems classified as high-risk, Article 12 provides for the automatic recording of events throughout the system's lifecycle to ensure an appropriate level of traceability. Article 11 also requires updated technical documentation, while Articles 13 and 14 introduce requirements regarding transparency, interpretation of outputs, and human oversight.

From August 2, 2026, the Regulation became generally applicable, and the European Commission and national authorities assumed new enforcement powers. From this date, important transparency obligations under Article 50 also apply.

Naturally, not all AI-based document systems will fall into the high-risk category, and the framework is still progressive, with obligations waived and regulated between 2027 and 2028.

But this does not diminish the importance of traceability; on the contrary, it offers organizations an opportunity to design the necessary infrastructure before auditability becomes a problem to be resolved retroactively.

Document governance and AI governance are converging

Document management has often been seen as a discipline separate from artificial intelligence.

On one side are repositories, metadata, versions, permissions, workflows, and retention; on the other, models, prompts, vector databases, embeddings, and AI agents. This separation is becoming increasingly untenable. An enterprise AI system uses documents as operational evidence. Consequently, the quality of AI governance also depends on the quality of governance of that information.

Documents are no longer used solely by people. They are continuously read, classified, correlated, and retrieved by automated systems. For this reason, metadata, versioning, access control, and audit trails are no longer just administrative tools; they have become part of the organization's AI control plane.

In this scenario, a document management system can take on a much broader role than that of a simple repository. Platforms like LogicalDOC combine versioning, metadata, access control, audit trails, workflows, and AI-powered search and analysis capabilities. These elements can form the information foundation needed to build Document AI systems in which access to sources remains governed and, above all, traceable over time.

From the "single source of truth" to the "single source of evidence"

One of the main objectives of document management has always been to create a single source of truth: a reliable place to find accurate corporate information.

The arrival of artificial intelligence suggests a further evolution of the concept.

We could talk about a single source of evidence: not just the place from which AI retrieves information, but the system that can demonstrate what information existed, which version was valid, who was responsible for it, and how it was used.

The difference may seem semantic, but it is substantial.

A possible architecture for Traceable Document AI

In this scenario, the document repository should not be considered simply a source from which to extract text for transformation into embeddings.

It should remain the authoritative reference for the document.

The vector database can optimize retrieval. The linguistic model can interpret and generate. Agents can orchestrate activities. But alongside this pipeline, there must be a persistent chain that connects the output to the original evidence.

The more AI autonomy increases, the more important this chain becomes.

With a chatbot, an error can produce an incorrect response. With an AI agent, the same response can become the input for another operation: modifying a document, approving a case, starting a workflow, sending a communication, or updating a company system.

The evidence trail must therefore be able to follow not only what the AI says, but also what the AI does.

Provenance does not necessarily mean truth.

Finally, there is an important clarification. Provenance does not automatically prove that information is correct.

Rather, it demonstrates where it comes from and what happened to it; it means being able to identify the source of the error, determine which other outputs were affected, and correct the process.

Without provenance, however, the error risks becoming simply an incorrect response whose cause no one can reconstruct.

Enterprise AI's next challenge could be auditability.

In recent years, we've increasingly asked AI systems to classify, extract, understand, and generate.

Now we're starting to ask them to participate in decision-making processes and, with AI agents, even perform actions. This increased autonomy must be matched by greater auditability.

This is why the next qualitative leap in Enterprise AI may not simply be a more powerful model, but rather the ability to build systems in which every important decision maintains a verifiable link to the information on which it was built.

An organization that maintains reliable, versioned, governed, and auditable documents isn't simply managing its archive better; it's building the information infrastructure necessary for AI to be not only useful, but also traceable, accountable, and, when necessary, defensible.

Version control, full-text search and workflows: how Dos&Donts has taken document management to an enterprise level with LogicalDOC

2026-08-14T15:33:09+00:00

Company	Dos&Donts
Sector	Technology solutions for cleanrooms, GMP environments and controlled-contamination areas
Size	Italian SME specialising in solutions for controlled environments
Role of interviewee	Paolo Alzamira, CTO
Main challenge	No version control, slow document search, no structured access control
Deployment	on-premises
Key outcome	~30% time saved on document searches; manuals and software versions finally aligned

About Dos&Donts

Dos&Donts is an Italian company specialising in the design and implementation of technological solutions for the control, safety and management of cleanrooms, GMP environments and controlled-contamination areas. Its solutions cover access and route control, door interlock systems, environmental parameter monitoring, data analysis and plant maintenance.

“90 per cent of our core business is in the pharmaceutical sector: sterile environments, regulated environments and environments with specific challenges. We create solutions to ensure that processes within these facilities remain compliant with these regulations.”

— Paolo Alzamira, CTO

Operating in the pharmaceutical sector means working in environments where every process must be traceable, every document must be available in the correct version, and every instance of access must be controlled. Document management is not a support function: it is an integral part of compliance.

The starting point: shared folders in a context that demanded more

“Before LogicalDOC, we were managing things via shared folders. Each user could either access or not access certain folders; folder trees, directories and a whole series of structures had been created so that people could write their documentation in those folders.”

— Paolo Alzamira, CTO

Shared folders are the most instinctive solution when a company starts to grow and documentation begins to pile up. They work as long as the team is small, there are few files and processes are simple. Once a certain threshold is exceeded, they become a problem: nested structures that are difficult to navigate, manually managed permissions, no revision history, and no way of knowing whether the file you’re opening is the latest version.

For a company operating in regulated environments, this fragility quickly becomes an operational constraint.

The crux of the matter: document versioning

“Certain issues, such as versioning – which is fundamental for us from a document management perspective – were not being addressed.”

— Paolo Alzamira, CTO

Versioning is often perceived as an advanced feature, reserved for large organisations. In reality, it is one of the most critical requirements for any company managing technical documentation that is constantly evolving.

The problem with shared folders is structural: when a document is edited and saved, the previous version may disappear or continue to circulate in copies downloaded by those who had opened it before the update. The result is the potential coexistence of multiple versions of the same document, with no immediate certainty as to which is the correct one.

For Dos&Donts, which develops software and produces the corresponding technical manuals, this poses a real risk: an operator working with a manual that is not updated to the latest version of the software. In pharmaceutical and sterile environments, where traceability is part of the certification process, the consequences of a discrepancy in documentation can be significant.

The choice of LogicalDOC: a specialised DMS, without the burden of an enterprise management system

“I was familiar with, and still am familiar with, other DMS systems. I chose LogicalDOC because it does exactly what we need. Many DMS systems are tied to business management systems or other software that we didn’t need. LogicalDOC does this, and it does it well — which is why I chose it.”

— Paolo Alzamira, CTO

The market for document management systems is vast, but many solutions are marketed as components of larger ecosystems: integrated into business management systems, ERPs or enterprise suites, with unnecessary features that increase complexity and cost without adding value.

LogicalDOC was chosen because it comprehensively covers all document management needs — folder structure, granular role-based permissions, full-text search with OCR, version control, document workflows — without requiring integrations or irrelevant add-on modules. A choice driven by effectiveness, not by formal completeness.

What has changed with LogicalDOC

“LogicalDOC has enabled me to create a whole range of structures within the DMS, complete with permissions, roles and workflows, but above all with document version control — something that is absolutely essential for us.”

— Paolo Alzamira, CTO

With LogicalDOC, every change to a document automatically generates a new, recorded version, complete with date, author and revision history. The current document is always unambiguously identifiable. Previous versions remain accessible and can be consulted, reducing the risk that out-of-date copies continue to be used.

Access is governed by defined permissions and roles: each user can only view and edit the documents for which they have been authorised. The structure does not depend on the goodwill of those saving files in the correct folder — the system itself ensures order and traceability.

Full-text search: finding the document when you need it

“We’ve definitely saved about 30 per cent of our time. Think of a search on Windows, which wasn’t full-text — and compare it with a search within the DMS.”

— Paolo Alzamira, CTO

“Document search and version control for the documents we manage are the main benefits we’ve gained.”

— Paolo Alzamira, CTO

The difference between a file system search and a full-text search isn’t a question of speed: it’s a question of method. Searching for a document in a shared folder means remembering the file name, or which subfolder it was saved in. As the archive grows — and in a technical company it grows rapidly — both of these become progressively less reliable.

LogicalDOC’s full-text search works on the content of documents: every uploaded file is indexed based on the text it contains, extracted either directly or via OCR for scanned documents. Searching for the name of a component, a product code or a technical specification returns all documents containing it — regardless of what the file is called or where it is saved.

The real value lies not in the accumulation of minutes saved, but in the certainty of finding the right document, in the correct version, exactly when you need it — whether it’s for an audit, an urgent technical intervention or a customer enquiry.

Getting started: independent implementation, without external support

“We did it all using the published manuals.”

— Paolo Alzamira, CTO

The entire implementation and go-live process was carried out in-house, without the need for dedicated external consultancy. The CTO configured the system, organised the folders, set up permissions and roles, and subsequently trained the team on how to use it — drawing on the documentation and resources provided by LogicalDOC.

This is a clear indication of just how accessible the system is: no external integrator was needed to get the DMS up and running. The time required was entirely down to internal reorganisation and changing operational habits — not the complexity of the software.

What we discovered whilst using it: Enterprise features that an SME can actually use

“We’ve started to implement document workflows — the routing and authorisation of specific documents. We’re trying to understand how it all fits together. As a growing company, we’re reviewing all our workflows and processes.”

— Paolo Alzamira, CTO

The fact that Dos&Donts is now evaluating document workflows — a feature that wasn’t part of the initial plans — highlights an important aspect of LogicalDOC.

Document approval and authorisation workflows are tools typically associated with structured organisations: they require defined processes, clear roles and a system capable of managing them without adding operational complexity. In many companies, adopting them means switching to a different platform.

With LogicalDOC, this evolution takes place within the same system. The company can start with basic document management — versioning, search and permissions — and gradually introduce workflows, comprehensive audit trails and structured process management when the organisation is ready. Enterprise-grade capabilities, accessible without changing platforms.

Key results at a glance

Area	Before	After
Versioning	None. Multiple versions in circulation without control	Every change generates a version that is tracked with the date and author
Document search	Manual navigation between folders, no full-text search	Search by content across the entire archive, with results in seconds
Manual alignment	Frequent misalignment between software version and documentation	Consistent versioning: the manual remains aligned with the correct version
Access control	Basic permissions at shared folder level	Granular roles and permissions by user and document type
Scalability	Structure difficult to maintain as the archive grows	Document workflows currently being introduced, without changing the platform
Deployment	Folders on a shared server	on-premises with direct control over data, backups and access

The recommendation

“Yes, I would recommend it — for all technical and document management of manuals and datasheets. We’re also using it to catalogue quotations and orders. I would definitely recommend it.”

— Paolo Alzamira, CTO

Based on Dos&Donts’ first-hand experience, LogicalDOC is particularly well-suited to companies that:

manage technical documentation with multiple versions that need to be kept in line with the product
operate in regulated environments where document traceability is a requirement
are looking for a comprehensive, specialised DMS without the complexity of an enterprise suite
want to start with basic document management, knowing that advanced features will be available when the organisation is ready to use them

About Dos&Donts

Dos&Donts is an Italian company specialising in the design and implementation of technological solutions for the control, safety and management of cleanrooms, GMP environments and controlled-contamination areas. It operates primarily in the pharmaceutical and biotech sectors, offering systems for access and route control, door interlocking, environmental parameter monitoring, data analysis and plant maintenance.

About LogicalDOC

LogicalDOC is a document management system founded in 2006, available both in the cloud and on-premises. It offers full-text search with OCR, version control, document workflows, integration with Microsoft Office, REST API and WebDAV. It is used by companies worldwide in regulated, manufacturing, technical and professional sectors.

To find out more about how LogicalDOC can support more traceable and scalable document processes, you can start by assessing your business context and operational requirements.

Book a demo | Request a quote | Free trial

Document Management System Software That Scales

2026-08-10T10:25:40+00:00

A finance team approves a contract using an attachment that was saved locally six months ago. A project manager spends half an hour finding the latest drawing. A records manager cannot prove who accessed a sensitive file. These are not isolated administration problems. They are signs that document management system software is needed to bring business information under control.

For organisations handling contracts, invoices, technical drawings, HR files, case records, quality documents and operational procedures, the issue is rarely a lack of storage. The issue is that information is spread across inboxes, shared drives, desktops, paper archives and disconnected applications. The result is slower work, repeated effort and unnecessary risk.

The right system creates a controlled environment where people can find, use, share and govern documents without creating further copies or uncertainty. It should make routine work easier for users while giving IT, compliance and operational leaders the visibility they need.

What document management system software should deliver

A document management platform is more than an online filing cabinet. It establishes a single source of truth for documents across their working life: capture, classification, review, approval, distribution, retention and disposal. That lifecycle matters because a document can be operationally useful and legally sensitive at the same time.

"Split your metadata from your files, and suddenly your sluggish document system becomes fast, scalable and surprisingly cheap to run."
Prasanna Kumar Ramachandran - InforWorld

At a practical level, users should be able to scan paper records, import electronic files, apply metadata and store documents in a logical folder structure. They should then be able to retrieve the right item in seconds through full-text search, filters, document properties and saved searches. When retrieval depends on asking the person who originally saved a file, the organisation does not have a reliable information process.

The value grows when document control is connected to daily work. Version control prevents staff from editing outdated copies. Permissions ensure a user sees only the information relevant to their role. Workflow automation routes documents to the right people, records decisions and keeps approvals moving. Audit trails provide evidence of activity when questions arise later.

The operational cost of unmanaged documents

Poor document control is often accepted as an inconvenience until it affects a deadline, an audit or a customer commitment. In reality, the cost accumulates every day. Staff search for files, recreate documents they cannot locate, send large attachments by email and wait for manual approvals. Managers make decisions with incomplete or obsolete information.

Paper-heavy processes add further friction. Physical storage takes space, filing is inconsistent and access is limited to where the archive is held. Remote and multi-site teams can be left working from scanned copies, couriered files or informal workarounds. These arrangements may keep a process running, but they do not provide dependable control.

There is also a governance concern. Organisations need to know which version is authoritative, who has changed it, whether a record must be retained and when it can be disposed of. A shared drive may be suitable for basic file storage, but it does not necessarily provide the structured permissions, retention controls, auditability or workflow needed for business-critical records.

Capabilities that make a measurable difference

Not every organisation needs the same configuration. A small operations team may prioritise fast retrieval and secure sharing, while a regulated enterprise may need detailed retention schedules, delegated administration and integration with line-of-business systems. The core capabilities, however, should work together rather than sit in separate tools.

Central access without losing structure

Centralisation does not mean putting every file into one large folder. It means providing one managed repository with a structure that reflects how the organisation works. Department folders, document templates, metadata fields and naming standards give users a consistent place to store information.

A well-designed system also supports controlled access from the office, home or field. Browser-based and mobile access can help distributed teams respond quickly, but permissions must follow the document wherever it is viewed. Convenience without access control simply moves the risk elsewhere.

Search that works with real business language

Search is one of the clearest tests of a system's value. Users should not need to remember an exact filename or folder path. They may know a supplier name, project number, customer, date, document type or a phrase inside the document.

Full-text indexing and metadata search allow teams to combine those clues and reach the correct information quickly. Optical character recognition is particularly useful for scanned archives, turning image-based documents into searchable business records. This can reduce information retrieval from hours to seconds, especially where years of paper files have been digitised.

Version control and workflow automation

A document often changes hands before it is final. Policies require review, contracts require approval, invoices require matching and engineering documents require technical checks. Email can support these processes at low volume, but it provides little control when workloads increase or approvers are absent.

Workflow automation defines the route, responsibilities and status of each task. It can notify the next reviewer, escalate overdue actions and maintain a complete record of decisions. Version Control ensures contributors work on the current document and makes earlier versions available when needed. This reduces duplicate files, approval delays and errors caused by uncontrolled edits.

Security, records and accountability

Security should be designed around roles and responsibilities, not just folders. Finance, HR, legal and project teams may all need access to a shared record set while having different rights to view, edit, download or approve individual documents.

A capable platform supports granular permissions, authentication controls, audit trails and records handling policies. Retention rules help organisations preserve documents for the required period and apply disposal consistently afterwards. The precise requirements depend on sector, geography and internal policy, but the principle is constant: governance should be built into the process rather than added during an audit.

How to choose the right system

A successful purchase starts with the processes causing the greatest friction. Rather than beginning with a long feature checklist, identify the documents that are hard to find, the approvals that regularly stall and the records that create compliance exposure. These use cases reveal what the implementation must achieve.

Consider the full operating model. Cloud deployment may suit organisations that want rapid access and reduced infrastructure administration. On-premise deployment can be appropriate where internal policy, data residency or integration requirements demand greater local control. Hybrid-cloud options may be the better fit when teams need both flexibility and defined control over selected repositories. There is no universal answer, so deployment portability matters.

Integration should be evaluated early. A document management system may need to connect with accounting software, CRM platforms, enterprise resource planning tools, scanners, email services or custom applications. API access can prevent staff from exporting, renaming and re-uploading files between systems, which is where many avoidable errors begin.

Usability is equally important. If filing is slow or search is unreliable, users will return to desktop folders and email attachments. Ask how documents are captured, how metadata is applied and how new staff learn the process. Good configuration should make the controlled route the easiest route.

LogicalDOC supports cloud, hybrid-cloud and on-premise deployments, allowing organisations to select an operating model that fits their technical, security and business requirements without tying their document strategy to one hosting approach.

Plan implementation around adoption, not migration alone

Moving documents into a new repository is only part of the work. Before migration, decide which documents are active, which should be archived and which can be securely disposed of under the organisation's retention policy. Carrying years of duplicated, poorly labelled material into a new system can recreate the old problem in a newer interface.

Start with a department or process where the benefit is visible. Contract approvals, quality documentation, accounts payable and project records are common candidates because delays and ownership are easy to measure. Define the folder structure, metadata, permissions and workflow with the people who do the work, then test practical scenarios before wider rollout.

Training should focus on outcomes: how to save a document correctly, find the latest approved version, complete an assigned task and share information securely. IT teams need administration and integration training, while business users need confidence that the system will save time rather than create more steps.

Measure the improvement

Document management should produce evidence of progress. Useful measures include average retrieval time, approval turnaround, number of duplicate files, percentage of documents classified correctly and volume of paper storage reduced. Teams can also track overdue workflow tasks and the time spent responding to audit or customer information requests.

These measures help leaders improve the configuration over time. If search results are poor, metadata or scanning quality may need attention. If workflows are bypassed, the route may be too complex. A system should evolve with the organisation rather than remain a static archive.

The most useful document management system software is the one people trust when the pressure is on. Build it around the documents and decisions that keep your organisation moving, and every approved file, completed workflow and quick retrieval becomes a small but meaningful gain in operational control.

Why Agentic AI Fails Without Document Governance

2026-07-17T08:20:57+00:00

Many companies are investing time and resources in AI adoption, convinced that a true competitive advantage depends on choosing the most advanced AI model. They aim to integrate Agentic AI - intelligent agents capable of making decisions, performing tasks autonomously, and collaborating to complete increasingly complex processes - into their operations.

But there's a question that's asked much less frequently, yet it should be the first one: Is your company really ready to entrust its information assets to an AI agent?

The success of Agentic AI depends not only on the intelligence of the model used but also on the quality of the information the agent will work with.

Beyond Chatbots: Understanding Agentic AI

Unlike traditional chatbots or the more recent AI Copilots, an Agentic AI system doesn't simply answer a question.

It can analyze a goal, plan sequences of activities, consult various information sources, use company software and services, make decisions within defined contexts and rules, and collaborate with other specialized agents.

In other words, it's not just an assistant, but a true digital collaborator.

The introduction of this technology raises an often overlooked issue: document management.

Consider, for example, an agent tasked with preparing all the documentation needed to participate in a tender. To complete this task, they will need to retrieve contracts, certifications, procedures, technical documentation, price lists, templates, and attachments, and verify that they are up to date, accurate, and authorized for use. Clearly, the problem isn't so much the agent's ability to reason.

The challenge is understanding where they'll find this information and how much they can trust it.

The real obstacle isn't AI. It's the document heritage.

Many organizations imagine they can quickly introduce Agentic AI by connecting a linguistic model to their archives.

In practice, however, far more fundamental challenges quickly emerge: duplicate documents; different versions of the same contract; obsolete procedures still present in shared folders; PDFs scanned without OCR; files simultaneously saved on file servers, SharePoint, NAS, local folders, and cloud services; inconsistent permissions; information lacking metadata.

In such a scenario, even the best AI agent in the world will inevitably produce unreliable results.

The principle is always the same: Garbage In, Garbage Out.

If the input data is incomplete, messy, or out of date, the AI's decisions will also be inaccurate. With Agentic AI, this risk increases. A chatbot can suggest the wrong answer, while an autonomous agent could instead use that wrong document to make decisions or authorize incorrect processes.

Errors aren't confined to a single response; they can ripple throughout the entire business process. If we're unable to provide accurate information, artificial intelligence doesn't eliminate clutter; it simply makes it faster.

Before building intelligent agents, we need to build a reliable information asset. In other words, before Agentic AI, we need true Information Governance.

Why an AI Agent Needs a "Single Source of Truth"

Every intelligent agent must be able to know which document represents the official version.

This means having a Single Source of Truth: a single, reliable reference point for all corporate information.

This doesn't necessarily mean concentrating all data in a single physical archive, but ensuring there is an authoritative, governed, and constantly updated source from which agents can retrieve accurate information. Without this foundation, every AI-generated response risks varying depending on the source consulted. Learn more about Knowledge Mangement

The New Role of Document Management

A modern Document Management System can no longer be a simple electronic archive; it must become the reference point for the entire corporate information asset.

The goal is to ensure that all information is contextualized, verifiable, up to date, and available only to authorized people—and agents. Document management systems must become AI knowledge layers, managing the context that will allow agents to understand documents, relationships, procedures, authorizations, and processes.

Preparing today means building a competitive advantage. Many organizations rely on intelligent agents. Few are investing as carefully in the quality of their document assets.

Conclusions

Agentic AI represents one of the most promising evolutions in artificial intelligence, and many companies are investing time and resources in its development, but few are investing as carefully in the quality of their document assets.

Yet, it will be precisely the latter that will have a concrete advantage in the coming years, because AI agents will continue to evolve rapidly, while the ability to manage reliable information will remain a much more stable and difficult-to-replicate distinguishing feature.

No agent, no matter how sophisticated, can compensate for a fragmented, disorganized, or ungoverned document asset. Before deciding which AI platform to adopt, every company should ask itself: is the information that agent will work with truly reliable?

Agentic AI won't fail because agents are unintelligent. It will fail because many companies are not yet able to provide them with reliable information.

This is precisely where a document management system like LogicalDOC takes on a new strategic role.

How Lesepidado Eliminated One Man-Week per Month by Digitizing Nearly 200,000 Production Sheets with LogicalDOC

2026-07-07T07:40:53+00:00

Lesepidado is an Italian chemical company specializing in the food sector, headquartered in Castel San Pietro Terme (Bologna), in the Emilia-Romagna region. With a workforce of 80 to 100 employees, the company operates through two main business units: the production of food colorants for pastry decoration (both sweet and savoury), and the design and manufacture of edible inks and food printers, with a range that spans from small devices for artisan pastry shops to complex industrial systems.

Before adopting LogicalDOC, Lesepidado managed a massive volume of paper documents, relying on disorganized shared folders and manual archiving processes that consumed significant resources and put at risk the operational responsiveness required by the strict quality certifications of the food industry.

The turning point came with the introduction of LogicalDOC, now used as the central, secure system for automating document workflows and managing company compliance.

Lesepidado at a Glance

Company	Lesepidado Srl
Industry	Food-grade chemicals (colorants, edible inks, and food printers)
Headquarters	Castel San Pietro Terme (Bologna), Italy
Employees	80–100
System users	16 active licenses, approx. 20 users
Daily output	140–160 production sheets
Documents digitized	Nearly 200,000
Quality certification	BRC (British Retail Consortium)
Interviewee	IT Systems Administrator and in-house developer
Chosen DMS	LogicalDOC (on-premise)

What Challenges Did Lesepidado Face Before LogicalDOC?

The main challenge was the daily management of a continuous flow of sensitive paper documents. Every day the company produces between 140 and 160 paper production sheets: in addition to containing the recipes and preparation instructions, these sheets include handwritten notes recorded by operators about quality controls and technical observations.

To meet the requirements of the BRC food certification, the company must guarantee complete and immediate traceability of every batch: in the event of a non-conformity or a product recall, the reaction times are extremely tight.

Challenge	Impact
140–160 paper production sheets per day	One man-week per month dedicated solely to orderly archiving
Manual searches in physical archives	Slow, cumbersome retrieval during audits, non-conformities, or recalls
Handwritten notes not indexed	Quality-control information remained isolated on the paper sheet
Bulky paper archives	Cabinets and physical storage space constantly growing
Disorganized shared folders	Supporting documentation (contracts, supplier certificates) scattered and unstructured

“The real problem was that we were spending almost one man-week per month just archiving the production sheets. With BRC certification, if there is a recall you have very tight deadlines to retrieve all the documentation for a batch.”

Stefano Cassanelli — IT Systems Administrator, Lesepidado

Why Did Lesepidado Choose LogicalDOC as Its Document Management System?

During the selection phase, Lesepidado evaluated the document module integrated into its ERP system (a solution based on a modified version of Alfresco). However, that system immediately proved too closed, rigid, and expensive: even creating a new document class required a paid intervention from the vendor. LogicalDOC was chosen for three decisive factors.

1. An Open, Flexible, and Customizable System

LogicalDOC offered an open environment that allows the in-house IT team to interact directly with the system and its database (including read-only access) to develop custom integrations and applications. A concrete example: an internally developed control panel that compares the sheets recorded in the ERP with the scanned documents stored in LogicalDOC, allowing the shift supervisor to see at a glance whether any sheet is missing.

“When we found LogicalDOC, we immediately saw it as an open, customizable, and very solid system. We really like to tinker: having an open system, where the database can also be queried in read-only mode to build integrations, is essential for us.”

Stefano Cassanelli — IT Systems Administrator, Lesepidado

2. On-Premise Deployment to Protect the Recipes

Lesepidado deliberately opted for an on-premise installation. The choice was initially driven by historical connectivity limitations, but it has been maintained over time for a strategic reason: the production sheets contain the company’s proprietary formulas and recipes, which the company prefers to keep inside its own server room, under the full control of the internal IT team.

3. Ease of Use and Complete Documentation

The software proved intuitive from day one. Thanks to complete, accessible technical documentation, the systems administrator was able to proceed entirely through self-training, and then trained his colleagues without the need for expensive external training sessions. The initial rollout with the production sheets was up and running very quickly.

How Does Lesepidado Use LogicalDOC Across the Organization?

Today LogicalDOC manages an impressive historical archive, with nearly 200,000 digitized and indexed documents. The main use cases include:

Automated Production Sheet Processing

The workflow is almost fully automated: at the end of processing, the operator scans the production sheet. An intermediate software reads the barcode printed on the form and renames the file with the sheet’s unique number — a capability LogicalDOC also offers natively, through its barcode reader and zonal OCR. LogicalDOC then monitors the destination folder, automatically picks up the files, and loads them into the system, making them immediately available and searchable.

Result: the man-week per month previously dedicated to manual archiving has been completely eliminated.

Quality Department and Supplier Certificates

The Quality department paved the way for expanding the software. Today, suppliers send their raw-material certificates of origin directly in PDF format, and the Quality team archives them in LogicalDOC with structured metadata, also setting expiration dates for each document.

Automated Expiration Tracking and Excel Reports

Using LogicalDOC’s automated procedures, the company configured a periodic extraction of expiring documents, which generates a report in Excel format. The Quality department no longer has to perform weekly or monthly manual checks, drastically reducing the risk of working with expired certifications.

Automatic Reorganization of Nearly 200,000 Documents

When the archive reached the file-per-folder limit, the systems administrator — helped by the official documentation and by artificial intelligence — created custom scripts that automatically reorganized nearly 200,000 production sheets into a year/month folder structure, with no data loss and no interruption to operations.

Company Contract Management

After a thorough cleanup of the old shared folders, Lesepidado is progressively extending LogicalDOC to contract management as well, benefiting from the same centralized, searchable structure.

Before and After: The Transformation of Document Management

Area	Before	After (LogicalDOC)
Sheet archiving	Paper-based, manual: 1 man-week per month	Eliminated: scanning and automatic import
Search for BRC audits	Slow, dependent on the accuracy of the physical archive	Immediate: by sheet number, batch, or metadata
Search technology	None: only visual inspection of paper sheets	Full-text with OCR, including document contents and batch numbers
Physical space	Cabinets and archives constantly growing	Paper destroyed one week after scanning
Expiration monitoring	Periodic manual checks on certificates	Automatic expiration tracking with Excel reports
IT integration	Closed system, paid customizations	Open database, in-house scripts and integrations

What Results Has Lesepidado Achieved with LogicalDOC?

• A net saving of one man-week per month: the production employee previously dedicated to physically sorting the sheets has been completely freed from this task.

• Faster, stress-free BRC audits: during inspections, retrieving production sheets and the associated batches takes just moments, in full compliance with traceability time constraints.

• Advanced OCR indexing: the system indexes not only the sheet number but also the document’s contents, making it possible to locate a sheet starting from a specific batch code — unthinkable with paper.

• Elimination of physical archives: once digitized, the paper sheets are destroyed after one week, freeing up the cabinets previously used for storage.

• An autonomous IT team: a complete migration to a new server was carried out in half a day by following only the official documentation, licenses included; on the rare occasions technical support was needed, it responded and resolved the issues very quickly.

“For the Quality department it is an essential tool. Going back would mean not only losing one man-week per month again, but managing nearly 200,000 production sheets on paper: today that would simply no longer be possible.”

Stefano Cassanelli— IT Systems Administrator, Lesepidado

About Lesepidado

Founded in 1999 with the idea of applying ink-jet printing to the food world, Lesepidado Srl is headquartered in Castel San Pietro Terme (Bologna), Italy. The company operates through two divisions: Vivy, dedicated to colorants and products for professional food decoration, and Vivitech, specializing in printing systems and edible inks, from countertop devices for pastry shops to industrial systems. Its plants are BRC and IFS certified and operate according to the highest international food-safety standards.

About LogicalDOC

LogicalDOC is a document management system founded in 2006 by Marco Meschieri and Alessandro Gasparini. Available both in the cloud and on-premise, the platform offers full-text search with OCR, version control, workflow automation, Microsoft Office integration, REST APIs, and WebDAV. These capabilities make it well suited for teams that need searchable archives, controlled access, and structured collaboration on business-critical documents. Request a free trial to see it in action.

Frequently Asked Questions

[widgetkit id="74"]

• How Kugler GmbH Managed 171,800 Files Using LogicalDOC

From Paperless to Digital Sustainability: The New Role of Document Management Systems

2026-06-18T14:46:09+00:00

For many years, the concept of sustainability in document management was almost exclusively associated with paper reduction. Digitizing documents, eliminating physical archives, and limiting printing were the primary objectives of any dematerialization initiative.

The debate is now shifting to a new challenge: digital sustainability.

The growing amount of information generated every day by companies and organizations is creating an often underestimated environmental impact. Duplicate files, unused data, redundant archives, and oversized storage systems require ever-increasing computational resources, storage capacity, and electricity.

In this scenario, the concept of Sustainable Information Management emerges: an approach that aims to manage information more efficiently, responsibly, and sustainably, also leveraging the potential of Artificial Intelligence.

From dematerialization to digital sustainability

Digital transformation has allowed companies to drastically reduce paper consumption, improve collaboration, and streamline processes.
However, indiscriminate digitization has created a new problem: the uncontrolled accumulation of data.
Many organizations store documents that are never accessed, maintain multiple copies of the same files, and archive obsolete information without any real operational or regulatory need.
While in the past the problem was paper archives that took up physical space, today the risk is posed by digital archives that consume storage space, computing power, and energy.
Sustainability is no longer just about paper; it's about the entire information lifecycle.

The Hidden Cost of Useless Data

According to numerous industry analyses, a significant portion of corporate data falls into the category of so-called "dark data": information archived but never used for operational, decision-making, or compliance purposes.

Added to this is ROT Data (Redundant, Obsolete, Trivial), which consists of redundant, obsolete, or otherwise valueless data.

Although the unit cost of storage continues to decline, managing huge volumes of data still entails:

increased data center energy consumption;
the need for larger infrastructure;
increased backup and replication;
higher data security and protection costs;
increased complexity in finding information.

Every document stored unnecessarily generates an impact that, multiplied by millions of files and thousands of organizations, becomes significant.

The Role of AI in Reducing Digital Waste

Artificial Intelligence is not automatically synonymous with sustainability. AI models require significant computational resources to train and run.
However, when applied to information management, AI can help reduce digital waste and improve the overall efficiency of document systems.

Main applications include:

Automatic document classification

AI can automatically identify document content, assign categories and metadata, and apply appropriate retention rules.
This reduces the accumulation of disorganized information and improves the quality of archives.

Identification of Duplicates and Obsolete Versions

Algorithms can identify multiple copies of the same document, flag outdated versions, and promote the preservation of a single official version.

Intelligent Retention

AI can support the enforcement of retention policies by identifying documents that have exceeded the timeframes established by regulations or company procedures.

Improved Document Search

More effective search reduces the need to create local copies, personal archives, and parallel repositories that further fuel uncontrolled data growth.

Sustainable Information Management and ESG Strategies

ESG (Environmental, Social, and Governance) issues are increasingly playing an important role in corporate strategy.
In this context, document management is not just an operational tool, but is becoming a fundamental component of information governance.

A modern document system can contribute to ESG objectives through:

greater control over the document lifecycle;
traceability of activities and access;
support for audits and compliance checks;
structured management of sustainability and compliance documentation;
reducing information inefficiencies.

Digital sustainability is not just about energy consumption but also about managing information responsibly and transparently.

Green IT and Document Management

Green IT initiatives aim to reduce the environmental impact of information technology.

While the focus is often on data centers, servers, and cloud infrastructure, the way information is created, stored, and managed also impacts the overall efficiency of the digital ecosystem.

Smarter document management helps limit uncontrolled storage growth, reduce duplication and redundant storage, optimize data backup and replication, and improve the use of available IT resources.

In other words, improved information management can indirectly reduce the need for infrastructure and energy resources.

Modern document management systems, thanks to the integration of AI-based features, can help manage information assets more efficiently, sustainably, and in compliance with regulations.

The focus is no longer simply eliminating paper, but improving the entire information lifecycle.

The challenge of the coming years will not be to digitize more, but to better manage what is digitized.

Conclusions

Digital sustainability is becoming a new priority for companies and organizations. In a world where data volume continues to grow rapidly, accumulating information without a strategy is not only an operational problem but also a source of economic and environmental inefficiency.

Artificial Intelligence can play an important role in identifying useless data, optimizing archives, and improving information governance. Combined with a modern document management platform, it can help build a Sustainable Information Management model in which efficiency, compliance, and sustainability work together.

How Healthropy Srl Centralized ISO 9001 Quality Evidence and Project Documentation with LogicalDOC

2026-06-11T13:25:14+00:00

Healthropy Srl is an Italian medical informatics company based in Savona. Founded in 2014 as a recognized spin-off of the University of Genoa, it develops healthcare interoperability solutions that support clinical data reuse for care continuity, education, and research. Its work is closely tied to public healthcare data standards and regional health authority projects.

Before LogicalDOC, Healthropy managed documents across email inboxes, shared folders, and local archives. That slowed audit evidence retrieval and increased the risk of duplication, information loss, and outdated versions as public administration subcontracting work expanded.

That changed when Healthropy adopted LogicalDOC as its central document management system.

Healthropy Srl at a Glance

Company	Healthropy Srl
Industry	Medical informatics
Location	Savona, Italy
Founded	2014 (spin off of the University of Genoa)
Company size	1 to 10 employees
Quality certification	UNI EN ISO 9001:2015, certified by RINA [VERIFY]
Standards membership	HL7 Italy and HL7 Europe
Flagship product	HQuantum© cloud platform
Deployment	On-premise
DMS chosen	LogicalDOC (Alfresco was also evaluated)
Website	healthropy.com

What Challenges Did Healthropy Srl Face Before LogicalDOC?

Before adopting LogicalDOC, Healthropy stored company documents across email inboxes, shared folders, and local archives. For a company supporting public administration projects under a certified quality system, this fragmentation created operational risk.

The pressure came from three areas: growing project documentation, traceable audit evidence, and strict public-sector subcontracting requirements.

Challenge	Impact
Fragmented information storage	Documents and evidence were spread across email inboxes, shared folders, and local archives
Slow evidence retrieval	Operational activities, internal audits, and inspections took longer because information had to be searched across multiple locations
Risk of data loss or duplication	The same document could exist in multiple versions across systems, with no single source of truth
Incomplete traceability	Risk of failing to ensure complete traceability for ISO 9001 audits
Audit preparation overhead	Preparing documentation became increasingly time consuming
Growth pressure	Increasing volume of public administration subcontracting documentation

"Information management was fragmented across email inboxes, shared folders, and local archives. This made it more difficult to quickly retrieve documents and evidence during operational activities, internal audits, and inspections, increasing the time needed to search for information and raising the risk of data loss or duplication."

Norbert Maggi — Board Member, Healthropy Srl

Why Did Healthropy Srl Choose LogicalDOC as Their Document Management System?

Healthropy evaluated Alfresco before selecting LogicalDOC. LogicalDOC's metadata flexibility, on-premise option, centralized storage, and fast migration aligned more closely with Healthropy's needs.

On-Premise Deployment for Data Sovereignty

Keeping the full infrastructure on-premise was a determining factor for Healthropy. The company needed direct control over data, backups, document access policies, and role-based permissions for documentation tied to clinical and public administration projects.

Flexible Cataloging with Labels and Metadata

LogicalDOC's metadata and label management helped Healthropy organize ISO 9001 quality evidence in a searchable, traceable way. This supported audit-ready documentation without forcing the team to abandon familiar folders and processes.

Centralization of Documents and Email Communications

One of Healthropy's core requirements was to keep documents and email exchanges together. LogicalDOC's email and attachment import and Outlook integration helped archive communication evidence in the same repository, organized through folders, labels, and metadata.

Automatic Import of the Existing Folder Structure

LogicalDOC's automatic import preserved Healthropy's existing folder structure, enabling adoption without forcing the team to redesign its archiving workflows.

How Does Healthropy Srl Use LogicalDOC Across the Organization?

Healthropy uses LogicalDOC as the central repository for company documentation. The system supports ISO 9001 quality evidence management, email archiving, public administration subcontracting files, and document classification through folders, labels, and metadata for fast retrieval.

ISO 9001 Quality Evidence Management

ISO 9001 evidence management is the primary use case at Healthropy. LogicalDOC holds process records, revision histories, and supporting communications so the team can retrieve evidence from one organized location during internal audits, inspections, or project reviews.

Email and Document Centralization in One Repository

Email exchanges are part of the audit trail at a quality certified company. Healthropy archives documents and related email communications inside LogicalDOC, removing the need to cross reference inboxes, attachments, and standalone folders when reconstructing a project history.

Documentation for Public Administration Subcontracting

Italian public sector projects require strict documentation, and their growing volume was one of the original triggers for adopting LogicalDOC. The system now keeps project files, deliverables, and supporting documentation in a centralized, traceable, on-premise repository.

Cross Department Usage

Five departments at Healthropy use LogicalDOC as part of their daily work. The table below shows which areas of the company depend on the system and the kinds of documents each one manages.

Department	Document types managed
Administration	Company records, contracts, internal policies, administrative documents
Operations	Project documentation, deliverables, operational records
Quality and Compliance	ISO 9001 evidence, audit records, inspection documentation
Sales	Commercial documents, proposals, customer communications
Customer Support	Customer correspondence, support records, service documentation

Classification with Folders, Labels, and Metadata

Healthropy uses LogicalDOC's labels and metadata to classify documents by project, process, revision, audit cycle, and other attributes the team defines. This makes retrieval faster and supports audit traceability as the archive grows.

Before vs After: Healthropy Srl Document Management Transformation

The table below summarizes Healthropy's document management before and after adopting LogicalDOC across the areas that mattered most during selection and daily operations.

Area	Before (email, shared folders, local archives)	After (LogicalDOC)
Information storage	Documents scattered across inboxes, shared folders, and local archives	Centralized repository with structured folders, metadata, and labels
Evidence retrieval	Slow searches across multiple systems	Fast retrieval through metadata, labels, and full-text search
Version control	Multiple versions stored in different locations	Single source of truth with versioning and audit trails
Traceability	Incomplete traceability for ISO 9001 audits	Full traceability of documents, revisions, and communications
Audit preparation	Time-consuming manual searches and document consolidation	Audit-ready documentation stored in a single organized system
Email archiving	Emails stored separately from documents	Emails and attachments archived directly into LogicalDOC
Scalability	Growth increased fragmentation and complexity	Scalable structure supporting growing public administration projects

What Results Has Healthropy Srl Achieved with LogicalDOC?

Since adopting LogicalDOC, Healthropy reports clearer retrieval, stronger ISO 9001 audit readiness, fewer version conflicts, and improved collaboration. The company did not formally measure KPIs, so results remain qualitative, but the operational impact is visible in daily work, internal audits, and project documentation routines.

Faster Document and Evidence Retrieval

Evidence can now be retrieved from one classified repository rather than several inboxes, shared folders, and local archives. That reduces the time spent searching for documents and makes it easier to reconstruct the history behind a project, decision, or audit request.

Stronger ISO 9001 Audit Readiness

Documents, revisions, and supporting communications are traceable from one place, making ISO 9001 audit preparation more controlled. Instead of rebuilding evidence manually before each review, the team can work from a structured repository with folders, labels, metadata, and version history.

Reduced Duplication and Version Confusion

A single source of truth reduced duplication, information loss, and outdated copies.

Improved Cross Team Collaboration

Teams across Administration, Operations, Quality and Compliance, Sales, and Customer Support now use the same document history instead of relying on personal archives. This improves handoffs between departments and reduces dependency on individual inboxes or local folders.

Full Data Control Through On-Premise Deployment

The on-premise setup keeps data, backups, and access policies under Healthropy's control, which is critical for clinical and public-sector documentation.

"We are pleased to have structured document management more efficiently without disrupting existing operational processes, while maintaining full control over data thanks to the on-premise infrastructure."

Norbert Maggi — Board Member, Healthropy Srl

About Healthropy Srl

Healthropy is a member of HL7 Italy and HL7 Europe. Its quality management system is certified to UNI EN ISO 9001:2015.

Its flagship product, HQuantum©, enables clinical data reuse through standards such as HL7 FHIR, HL7 CDA R2, LOINC, SNOMED, ICD 9, and ICD 10. Healthropy also develops i-Macula Web and an eCRF platform.

Founded	2014
Origin	Spin off of the University of Genoa
Headquarters	Corso Vittorio Veneto 14B, 17100 Savona, Italy
Industry	Medical informatics, healthcare data interoperability
Standards membership	HL7 Italy, HL7 Europe
Quality certification	UNI EN ISO 9001:2015 (RINA - verify)
Standards membership	HL7 Italy and HL7 Europe
Flagship product	HQuantum© cloud service platform
Additional products	i-Macula Web, eCRF for Clinical Trials
Website	healthropy.com
LinkedIn	linkedin.com/company/healthropy

The trademark "Spin off of the University of Genoa" testifies exclusively to the university derived relationship of the spin off company. This case study is not directly attributable to the University itself.

About LogicalDOC

LogicalDOC is a document management system founded in 2006 by Marco Meschieri and Alessandro Gasparini. Available in cloud and on-premise deployments, the platform provides full text search with OCR, version control, workflow automation, Microsoft Office integration, REST API, and WebDAV. These capabilities make it suitable for teams that need searchable records, controlled access, and structured collaboration around business-critical documents.

Founded	2006
Founders	Marco Meschieri, Alessandro Gasparini
Headquarters	Fair Lawn, New Jersey, USA
European office	Carpi, Modena, Italy
Deployment	On-premise (Windows, Linux, macOS) and cloud
Languages supported	26 plus, including English, German, Italian, French, Spanish, Chinese, Japanese, Korean
Awards	InfoWorld Bossie Award 2010, CMS Critic Award 2016, SourceForge Top Performer Spring 2026, SourceForge Community Awards

Frequently Asked Questions

[widgetkit id="72"]

Blog – Document Management, Best Practices and Case Studies - LogicalDOC

When AI Becomes a Co-Author

How versioning, metadata, search and governance take on a new role in AI-assisted document creation.

Versioning: from a history of changes to a history of decisions

Metadata becomes provenance metadata.

Search must find the right document, not just the most similar one.

Workflows: where responsibility returns to humans

AI should not have more access than the user.

A DMS must do more than just "feature AI"

Secure Document Sharing for Clients That Works

Why email attachments create a control problem

What secure document sharing for clients should provide

Permission-based access

Version control that clients can trust

Audit trails and accountability

Expiry, revocation and controlled downloads

Build the process around the client journey

Give IT control without creating a burden for users

Common mistakes that weaken client document security

Start with the documents that cause the most friction

AI knows the answer. But can it prove it? Defensible AI and the new role of document provenance

Explainable AI and Defensible AI: They're Not the Same

Evidence Provenance: Where Does AI's Statement Come From?

RAG improves grounding. But it doesn't guarantee traceability.

Versioning: A traditional DMS function becomes an AI governance function

Audit trail: not just who modified a document

Document governance and AI governance are converging

From the "single source of truth" to the "single source of evidence"

A possible architecture for Traceable Document AI

Provenance does not necessarily mean truth.

Enterprise AI's next challenge could be auditability.

Version control, full-text search and workflows: how Dos&Donts has taken document management to an enterprise level with LogicalDOC

About Dos&Donts

The starting point: shared folders in a context that demanded more

The crux of the matter: document versioning

The choice of LogicalDOC: a specialised DMS, without the burden of an enterprise management system

What has changed with LogicalDOC

Full-text search: finding the document when you need it

Getting started: independent implementation, without external support

What we discovered whilst using it: Enterprise features that an SME can actually use

Key results at a glance

The recommendation

About Dos&Donts

About LogicalDOC

Document Management System Software That Scales

What document management system software should deliver

The operational cost of unmanaged documents

Capabilities that make a measurable difference

Central access without losing structure

Search that works with real business language

Version control and workflow automation

Security, records and accountability

How to choose the right system

Plan implementation around adoption, not migration alone

Measure the improvement

Why Agentic AI Fails Without Document Governance

Beyond Chatbots: Understanding Agentic AI

The real obstacle isn't AI. It's the document heritage.

Why an AI Agent Needs a "Single Source of Truth"

The New Role of Document Management

Conclusions

How Lesepidado Eliminated One Man-Week per Month by Digitizing Nearly 200,000 Production Sheets with LogicalDOC

Lesepidado at a Glance

What Challenges Did Lesepidado Face Before LogicalDOC?

Why Did Lesepidado Choose LogicalDOC as Its Document Management System?

1. An Open, Flexible, and Customizable System

2. On-Premise Deployment to Protect the Recipes

3. Ease of Use and Complete Documentation

How Does Lesepidado Use LogicalDOC Across the Organization?

Automated Production Sheet Processing

Quality Department and Supplier Certificates

Automated Expiration Tracking and Excel Reports

Automatic Reorganization of Nearly 200,000 Documents

Company Contract Management

Before and After: The Transformation of Document Management

What Results Has Lesepidado Achieved with LogicalDOC?

About Lesepidado

About LogicalDOC

Frequently Asked Questions

Related Articles