<?xml version="1.0" encoding="utf-8"?>
<!-- generator="" -->
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
	<title type="text">Blog – Document Management, Best Practices and Case Studies - LogicalDOC</title>
	<subtitle type="text"></subtitle>
	<link rel="alternate" type="text/html" href="https://www.logicaldoc.com"/>
	<id>https://www.logicaldoc.com/blog</id>
	<updated>2026-11-16T22:10:01+00:00</updated>
	<author>
		<name>LogicalDOC Website</name>
	</author>
	<generator uri="https://www.joomla.org"></generator>
	<link rel="self" type="application/atom+xml" href="https://www.logicaldoc.com/blog?format=feed&amp;type=atom"/>
	<entry>
		<title>Document control software: features, options, and pricing</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/688-document-control-software"/>
		<published>2026-11-15T10:01:23+00:00</published>
		<updated>2026-11-15T10:01:23+00:00</updated>
		<id>https://www.logicaldoc.com/blog/688-document-control-software</id>
		<author>
			<name>Zapier</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/remote_cache/remote-73979d1a7372de19d0259039a98aafab81dce2592025fd75d864db850189c5c7.webp&quot; alt=&quot;Document control software: features, options, and pricing&quot;&gt;&lt;/p&gt;&lt;p&gt;Document control software manages revisions, approvals, permissions, and activity records so your team can find authoritative documents and trace responsibility for changes. The buying decision starts with five capabilities: reliable &lt;a href=&quot;https://www.logicaldoc.com/software-features/version-control&quot;&gt;version history&lt;/a&gt;, assigned approval tasks, controlled access, usable audit trails, and document retrieval. Your shortlist should also reflect document types, deployment responsibilities, edition requirements, and pricing based on users and storage.&lt;/p&gt;
&lt;h2&gt;Controlled documents and software categories&lt;/h2&gt;
&lt;p&gt;Document control software should match the documents your team governs and the decisions people make about them. An operating procedure needs a clear revision and approval history; a project model may also need coordinated markups and issue tracking.&lt;/p&gt;
&lt;p&gt;A &lt;strong&gt;controlled document&lt;/strong&gt; follows formal review, approval, and revision processes. Examples include standard operating procedures, engineering drawings, quality manuals, and safety instructions.&lt;/p&gt;
&lt;p&gt;The document control process covers drafting, review, approval, distribution, periodic review, and revision or retirement. Named owners and approvers connect those stages to human responsibility: someone prepares the content, someone authorizes its use, and someone owns its next review.&lt;/p&gt;
&lt;p&gt;Document management has a broader remit: storing, organizing, and retrieving information. Document control adds formal approval, revision governance, and traceability.&lt;/p&gt;
&lt;p&gt;Three software categories address different operating needs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enterprise document management systems:&lt;/strong&gt; These combine document organization and retrieval with permissions, revision history, and document-centric workflows. They suit evaluations centered on business documents and procedures across departments.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Quality management systems:&lt;/strong&gt; These connect document control to wider quality processes. For example, &lt;a href=&quot;https://www.mastercontrol.com/quality/document-control-software/&quot;&gt;MasterControl&lt;/a&gt; connects its document-control offering with training, corrective and preventive action (CAPA), supplier management, and audits.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Construction common data environments:&lt;/strong&gt; These address project information coordination. &lt;a href=&quot;https://www.autodesk.com/products/autodesk-docs/&quot;&gt;Autodesk Forma Data Management&lt;/a&gt; includes drawing and model viewing, markups, issue tracking, version control, and permission-based sharing.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Start with your working documents. Decide whether the purchase primarily concerns business records and procedures, connected quality processes, or project drawings and models. That distinction keeps the evaluation focused on work your team actually performs.&lt;/p&gt;
&lt;h2&gt;What to test before buying&lt;/h2&gt;
&lt;p&gt;A document control software evaluation should produce observable evidence using your documents, roles, and review steps. A demonstration becomes more useful when an author, reviewer, and reader follow the same document through a change.&lt;/p&gt;
&lt;p&gt;Use these five tests to compare solutions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Version control:&lt;/strong&gt; Ask two people to attempt an edit to the same document. Observe how the system coordinates their work, then retrieve an earlier revision with its author and timestamp. Compare the revisions and check whether version notes explain the change. A list of numbered files alone gives reviewers little help in understanding what changed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Approval workflows:&lt;/strong&gt; Route a document to a named reviewer, reject it, correct it, and resubmit it. Check who owns the task at every stage, how the decision is recorded, and how deadlines and reminders work. The important distinction is whether a new revision still requires an explicit approval decision.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Access permissions:&lt;/strong&gt; Test reader, author, and administrator accounts against the same document. Check viewing, downloading, editing, and access administration separately. For a reader who needs only an on-screen reference, test whether the required viewing access can be granted independently of permission to extract the file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Audit trails:&lt;/strong&gt; Have several people view, download, and edit a document, then retrieve its activity history. Look for attributable events, timestamps, and details that help reconstruct what happened. Ask the person responsible for reviews to find a particular event rather than relying on an administrator’s prepared demonstration.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Document retrieval:&lt;/strong&gt; Search a text-based file and a scanned document using remembered content and business attributes, such as procedure owner or equipment identifier. Test metadata filters and reusable searches. Optical character recognition (OCR) matters when the words you need are stored inside an image rather than as selectable text.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Record each required capability against the edition you are evaluating. Keep the result concrete: whether the reviewer found the previous revision, whether the author received the returned task, and whether the reader accessed the intended document.&lt;/p&gt;
&lt;p&gt;Use the same test documents across shortlisted systems. Consistent inputs make differences in editing coordination, task ownership, and retrieval easier to judge.&lt;/p&gt;
&lt;h2&gt;How LogicalDOC manages document control&lt;/h2&gt;
&lt;p&gt;LogicalDOC connects document versions, approval assignments, access policies, activity history, and search within one &lt;a href=&quot;https://www.logicaldoc.com/solutions/document-management&quot;&gt;document management platform&lt;/a&gt;. We preserve the relationship between a document’s content, the people working on it, and the decisions governing its use.&lt;/p&gt;
&lt;h3&gt;Revision history and coordinated editing&lt;/h3&gt;
&lt;p&gt;LogicalDOC retains document versions and records who changed a document, when the change occurred, and the associated modifications. Reviewers can examine content and metadata differences rather than infer changes from filenames.&lt;/p&gt;
&lt;p&gt;We support configurable initial revision numbering, historical-version retention, major and minor revisions, and version notes. Those controls let your team establish revision conventions that fit its documents.&lt;/p&gt;
&lt;p&gt;Check-out coordinates editing by reserving a document for one user. Other users retain read-only search and browsing access and can see who holds the checkout. Administrators can release the lock. Check-in supports major or minor versions, and check-in/check-out activity is logged.&lt;/p&gt;
&lt;p&gt;Dos&amp;amp;Donts, an Italian technology company serving cleanroom, GMP, and controlled-contamination environments, adopted LogicalDOC on-premises after using shared folders and manually organized directories. Its implementation introduced versioning and defined permissions and roles. One practical problem was uncertainty over whether an operating manual matched the software version in use.&lt;/p&gt;
&lt;h3&gt;Assigned reviews and approval decisions&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/workflow&quot;&gt;LogicalDOC workflows&lt;/a&gt; assign review work to people and record explicit transitions between tasks. Assignments can go to individual users, groups, or a user identified through a document’s User attribute.&lt;/p&gt;
&lt;p&gt;For a group task, members receive notifications, and the first person taking ownership becomes the assignee. That creates an accountable owner within a shared review queue.&lt;/p&gt;
&lt;p&gt;Users can start workflows manually. Configured folder events can also launch a workflow when a newly created document matches an associated template. Tasks support due dates, configurable reminders, and an overdue script for follow-up.&lt;/p&gt;
&lt;p&gt;A rejected document can return to its author for revision. The author edits it and checks in a new version before a separate approval task. &lt;strong&gt;A checked-in revision and an approved document are separate workflow events.&lt;/strong&gt; Your review design determines who authorizes the revised content.&lt;/p&gt;
&lt;h3&gt;Permissions for viewing and editing&lt;/h3&gt;
&lt;p&gt;LogicalDOC separates document access into distinct rights, including Read, Preview, Download, and Write. We assign folder permissions to groups and individual users.&lt;/p&gt;
&lt;p&gt;Preview displays a document within the interface. Download permits extraction from the platform, while Write permits editing. These distinctions help administrators grant access according to the work a person needs to perform.&lt;/p&gt;
&lt;p&gt;Folder policies can remain local, propagate to subfolders, or inherit another folder’s rights. Inherited policies receive subsequent changes automatically; applying local rights breaks that inheritance link.&lt;/p&gt;
&lt;p&gt;For related procedure folders, inheritance gives administrators a way to maintain a common access policy. Access owners can adjust those policies as teams, responsibilities, and sharing needs change.&lt;/p&gt;
&lt;h3&gt;Activity history with accountable events&lt;/h3&gt;
&lt;p&gt;LogicalDOC records document activity showing who viewed, modified, downloaded, or deleted information and when. History entries include a timestamp, event description, session information, and request origin.&lt;/p&gt;
&lt;p&gt;Document history and version history answer different questions. Versions preserve revisions; activity records capture interactions. A view or download can appear in the activity history without creating a new document version.&lt;/p&gt;
&lt;p&gt;That distinction matters when investigating document use. You can examine access to unchanged content as well as changes to the content itself.&lt;/p&gt;
&lt;p&gt;Access to document history follows the relevant History menu permission, while detailed session inspection requires Sessions menu access. Reports and statistics dashboards provide additional ways to examine document activity.&lt;/p&gt;
&lt;h3&gt;Search across content and metadata&lt;/h3&gt;
&lt;p&gt;LogicalDOC retrieves documents through content, metadata, and structured filters. We support full-text searches across document content and selected metadata, plus searches using tags, standard properties, and custom template fields.&lt;/p&gt;
&lt;p&gt;Filters include language, folder, size, date, and document class. Results can display text snippets. Parametric searches use document metadata, while saved custom searches support recurring retrieval tasks.&lt;/p&gt;
&lt;p&gt;For example, a reviewer can retrieve procedures by a custom equipment field rather than remember a phrase from each file.&lt;/p&gt;
&lt;p&gt;Content indexing runs asynchronously under configurable processing schedules. Supported formats include Microsoft Office, OpenOffice, and PDF. OCR extracts text from images and raster PDFs, extending content retrieval to scanned material. Integrated preview lets users inspect documents within the interface without opening a separate application.&lt;/p&gt;
&lt;h2&gt;Choose your LogicalDOC deployment&lt;/h2&gt;
&lt;p&gt;LogicalDOC offers cloud, on-premises, and hybrid deployment, with different arrangements for repository location, infrastructure ownership, and server administration. Choose the model around who will operate the environment and how users need to reach documents.&lt;/p&gt;
&lt;p&gt;The deployment options divide responsibilities as follows:&lt;/p&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th&gt;
&lt;p&gt;Deployment&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Repository location&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Operational responsibility&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Access method&lt;/p&gt;
&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Cloud&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;External data center&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;LogicalDOC handles server maintenance&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Web interface over an internet connection&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;On-premises&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Your physical or virtual servers&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Your IT team typically manages infrastructure and administration&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Local network; configurable remote access&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Hybrid&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Local and remote cloud installations&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Your team manages the main local application&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;One portal for private- and public-cloud workspaces&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Deployment details: &lt;a href=&quot;https://www.logicaldoc.com/product/cloud-document-management&quot;&gt;LogicalDOC Cloud&lt;/a&gt;, On-Premise DMS, and Hybrid Cloud.&lt;/p&gt;
&lt;p&gt;Cloud suits teams that want hosted operation with server maintenance handled by us. Users access the service through a web interface, without a local server installation to maintain.&lt;/p&gt;
&lt;p&gt;On-premises places the application, documents, and data on infrastructure you manage. Your IT team typically handles hardware, deployment, maintenance, and security protocols. Remote access can be configured alongside local-network access.&lt;/p&gt;
&lt;p&gt;Hybrid combines a local application with repository synchronization to a remote cloud installation. You can publish selected repository content to the cloud site, allowing the cloud workspace to contain the material intended for that audience.&lt;/p&gt;
&lt;p&gt;For organizations using SaaS, the &lt;a href=&quot;https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-saas-securely&quot;&gt;UK National Cyber Security Centre&lt;/a&gt; explains that customers retain responsibility for application-specific configuration and recommends resilient backup arrangements for critical application data. Include access ownership and recovery arrangements in your deployment decision alongside server administration.&lt;/p&gt;
&lt;p&gt;Before selecting a model, assign an administrator, identify remote-access needs, and decide which content belongs in the cloud workspace. Those decisions make the operating responsibilities concrete.&lt;/p&gt;
&lt;h2&gt;LogicalDOC editions and pricing basis&lt;/h2&gt;
&lt;p&gt;LogicalDOC edition selection depends especially on whether your team needs approval workflows, OCR, and saved searches. As of November 2026, our four editions are Community, Business, Enterprise, and Cloud, with the following feature availability.&lt;/p&gt;
&lt;h3&gt;Features across the four editions&lt;/h3&gt;
&lt;p&gt;LogicalDOC includes core versioning, searching, access controls, and event logging across all four editions. The table separates those shared capabilities from features included in specific editions.&lt;/p&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th&gt;
&lt;p&gt;Feature&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Community&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Business&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Enterprise&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Cloud&lt;/p&gt;
&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Version control&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Document searching&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Multilingual full-text indexing&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Users and groups&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Folder and menu security policies&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Events log&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Workflow&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;OCR&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Folder searching&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Saved searches&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Feature availability: LogicalDOC &lt;a href=&quot;https://www.logicaldoc.com/features/comparison-matrix&quot;&gt;Product Features and Comparison Matrix&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Community is free and open source. Business includes OCR, folder searching, and saved searches alongside the shared document-management capabilities.&lt;/p&gt;
&lt;p&gt;For the assigned approval workflows described above, choose Enterprise or Cloud. Enterprise provides our full feature set on customer-managed infrastructure, while Cloud provides hosted operation. Match your evaluation environment to the edition you intend to purchase so the tested review process becomes part of the commercial specification.&lt;/p&gt;
&lt;h3&gt;Costs and quotation inputs&lt;/h3&gt;
&lt;p&gt;LogicalDOC Cloud pricing is based on storage space and user count. Business, Enterprise, and Cloud pricing is supplied through commercial quotations.&lt;/p&gt;
&lt;p&gt;Our quotation form collects the selected product, number of users, repository size, country, and contact details. Prepare those inputs around the working repository you intend to manage, including expected document growth.&lt;/p&gt;
&lt;p&gt;On-premises budgeting includes software licensing and infrastructure, with internal resources for deployment and ongoing administration. Compare that operating model with hosted service costs using the same user population and document requirements small change to trigger imagedownloader.&lt;/p&gt;
&lt;p&gt;A practical comparison combines the required edition, expected storage growth, user count, and deployment responsibilities. For example, a team requiring assigned approvals and scanned-document retrieval should cost the edition that includes both workflow and OCR, together with its chosen hosting arrangement.&lt;/p&gt;
&lt;h2&gt;Evaluate LogicalDOC with your documents&lt;/h2&gt;
&lt;p&gt;Evaluate LogicalDOC by taking a representative procedure or operating manual through editing, rejection, revision, and approval. Include a scanned document and the reader, author, and approver roles involved in everyday work.&lt;/p&gt;
&lt;p&gt;Use the evaluation to complete three checks:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Follow the review cycle and inspect the resulting version and activity records.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Retrieve the document through content and metadata searches.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Open the document using the intended reader account and check its permissions.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Set acceptance criteria before testing: an identifiable approved revision, an accountable reviewer, appropriate user permissions, and a retrievable activity history.&lt;/p&gt;
&lt;p&gt;One evaluation form provides a downloadable 30-day trial and credentials for a demonstration website requiring no local installation. These are separate evaluation routes. Start your LogicalDOC evaluation with one document and the people responsible for changing, approving, and using it. &lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/remote_cache/remote-73979d1a7372de19d0259039a98aafab81dce2592025fd75d864db850189c5c7.webp&quot; alt=&quot;Document control software: features, options, and pricing&quot;&gt;&lt;/p&gt;&lt;p&gt;Document control software manages revisions, approvals, permissions, and activity records so your team can find authoritative documents and trace responsibility for changes. The buying decision starts with five capabilities: reliable &lt;a href=&quot;https://www.logicaldoc.com/software-features/version-control&quot;&gt;version history&lt;/a&gt;, assigned approval tasks, controlled access, usable audit trails, and document retrieval. Your shortlist should also reflect document types, deployment responsibilities, edition requirements, and pricing based on users and storage.&lt;/p&gt;
&lt;h2&gt;Controlled documents and software categories&lt;/h2&gt;
&lt;p&gt;Document control software should match the documents your team governs and the decisions people make about them. An operating procedure needs a clear revision and approval history; a project model may also need coordinated markups and issue tracking.&lt;/p&gt;
&lt;p&gt;A &lt;strong&gt;controlled document&lt;/strong&gt; follows formal review, approval, and revision processes. Examples include standard operating procedures, engineering drawings, quality manuals, and safety instructions.&lt;/p&gt;
&lt;p&gt;The document control process covers drafting, review, approval, distribution, periodic review, and revision or retirement. Named owners and approvers connect those stages to human responsibility: someone prepares the content, someone authorizes its use, and someone owns its next review.&lt;/p&gt;
&lt;p&gt;Document management has a broader remit: storing, organizing, and retrieving information. Document control adds formal approval, revision governance, and traceability.&lt;/p&gt;
&lt;p&gt;Three software categories address different operating needs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enterprise document management systems:&lt;/strong&gt; These combine document organization and retrieval with permissions, revision history, and document-centric workflows. They suit evaluations centered on business documents and procedures across departments.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Quality management systems:&lt;/strong&gt; These connect document control to wider quality processes. For example, &lt;a href=&quot;https://www.mastercontrol.com/quality/document-control-software/&quot;&gt;MasterControl&lt;/a&gt; connects its document-control offering with training, corrective and preventive action (CAPA), supplier management, and audits.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Construction common data environments:&lt;/strong&gt; These address project information coordination. &lt;a href=&quot;https://www.autodesk.com/products/autodesk-docs/&quot;&gt;Autodesk Forma Data Management&lt;/a&gt; includes drawing and model viewing, markups, issue tracking, version control, and permission-based sharing.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Start with your working documents. Decide whether the purchase primarily concerns business records and procedures, connected quality processes, or project drawings and models. That distinction keeps the evaluation focused on work your team actually performs.&lt;/p&gt;
&lt;h2&gt;What to test before buying&lt;/h2&gt;
&lt;p&gt;A document control software evaluation should produce observable evidence using your documents, roles, and review steps. A demonstration becomes more useful when an author, reviewer, and reader follow the same document through a change.&lt;/p&gt;
&lt;p&gt;Use these five tests to compare solutions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Version control:&lt;/strong&gt; Ask two people to attempt an edit to the same document. Observe how the system coordinates their work, then retrieve an earlier revision with its author and timestamp. Compare the revisions and check whether version notes explain the change. A list of numbered files alone gives reviewers little help in understanding what changed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Approval workflows:&lt;/strong&gt; Route a document to a named reviewer, reject it, correct it, and resubmit it. Check who owns the task at every stage, how the decision is recorded, and how deadlines and reminders work. The important distinction is whether a new revision still requires an explicit approval decision.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Access permissions:&lt;/strong&gt; Test reader, author, and administrator accounts against the same document. Check viewing, downloading, editing, and access administration separately. For a reader who needs only an on-screen reference, test whether the required viewing access can be granted independently of permission to extract the file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Audit trails:&lt;/strong&gt; Have several people view, download, and edit a document, then retrieve its activity history. Look for attributable events, timestamps, and details that help reconstruct what happened. Ask the person responsible for reviews to find a particular event rather than relying on an administrator’s prepared demonstration.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Document retrieval:&lt;/strong&gt; Search a text-based file and a scanned document using remembered content and business attributes, such as procedure owner or equipment identifier. Test metadata filters and reusable searches. Optical character recognition (OCR) matters when the words you need are stored inside an image rather than as selectable text.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Record each required capability against the edition you are evaluating. Keep the result concrete: whether the reviewer found the previous revision, whether the author received the returned task, and whether the reader accessed the intended document.&lt;/p&gt;
&lt;p&gt;Use the same test documents across shortlisted systems. Consistent inputs make differences in editing coordination, task ownership, and retrieval easier to judge.&lt;/p&gt;
&lt;h2&gt;How LogicalDOC manages document control&lt;/h2&gt;
&lt;p&gt;LogicalDOC connects document versions, approval assignments, access policies, activity history, and search within one &lt;a href=&quot;https://www.logicaldoc.com/solutions/document-management&quot;&gt;document management platform&lt;/a&gt;. We preserve the relationship between a document’s content, the people working on it, and the decisions governing its use.&lt;/p&gt;
&lt;h3&gt;Revision history and coordinated editing&lt;/h3&gt;
&lt;p&gt;LogicalDOC retains document versions and records who changed a document, when the change occurred, and the associated modifications. Reviewers can examine content and metadata differences rather than infer changes from filenames.&lt;/p&gt;
&lt;p&gt;We support configurable initial revision numbering, historical-version retention, major and minor revisions, and version notes. Those controls let your team establish revision conventions that fit its documents.&lt;/p&gt;
&lt;p&gt;Check-out coordinates editing by reserving a document for one user. Other users retain read-only search and browsing access and can see who holds the checkout. Administrators can release the lock. Check-in supports major or minor versions, and check-in/check-out activity is logged.&lt;/p&gt;
&lt;p&gt;Dos&amp;amp;Donts, an Italian technology company serving cleanroom, GMP, and controlled-contamination environments, adopted LogicalDOC on-premises after using shared folders and manually organized directories. Its implementation introduced versioning and defined permissions and roles. One practical problem was uncertainty over whether an operating manual matched the software version in use.&lt;/p&gt;
&lt;h3&gt;Assigned reviews and approval decisions&lt;/h3&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/workflow&quot;&gt;LogicalDOC workflows&lt;/a&gt; assign review work to people and record explicit transitions between tasks. Assignments can go to individual users, groups, or a user identified through a document’s User attribute.&lt;/p&gt;
&lt;p&gt;For a group task, members receive notifications, and the first person taking ownership becomes the assignee. That creates an accountable owner within a shared review queue.&lt;/p&gt;
&lt;p&gt;Users can start workflows manually. Configured folder events can also launch a workflow when a newly created document matches an associated template. Tasks support due dates, configurable reminders, and an overdue script for follow-up.&lt;/p&gt;
&lt;p&gt;A rejected document can return to its author for revision. The author edits it and checks in a new version before a separate approval task. &lt;strong&gt;A checked-in revision and an approved document are separate workflow events.&lt;/strong&gt; Your review design determines who authorizes the revised content.&lt;/p&gt;
&lt;h3&gt;Permissions for viewing and editing&lt;/h3&gt;
&lt;p&gt;LogicalDOC separates document access into distinct rights, including Read, Preview, Download, and Write. We assign folder permissions to groups and individual users.&lt;/p&gt;
&lt;p&gt;Preview displays a document within the interface. Download permits extraction from the platform, while Write permits editing. These distinctions help administrators grant access according to the work a person needs to perform.&lt;/p&gt;
&lt;p&gt;Folder policies can remain local, propagate to subfolders, or inherit another folder’s rights. Inherited policies receive subsequent changes automatically; applying local rights breaks that inheritance link.&lt;/p&gt;
&lt;p&gt;For related procedure folders, inheritance gives administrators a way to maintain a common access policy. Access owners can adjust those policies as teams, responsibilities, and sharing needs change.&lt;/p&gt;
&lt;h3&gt;Activity history with accountable events&lt;/h3&gt;
&lt;p&gt;LogicalDOC records document activity showing who viewed, modified, downloaded, or deleted information and when. History entries include a timestamp, event description, session information, and request origin.&lt;/p&gt;
&lt;p&gt;Document history and version history answer different questions. Versions preserve revisions; activity records capture interactions. A view or download can appear in the activity history without creating a new document version.&lt;/p&gt;
&lt;p&gt;That distinction matters when investigating document use. You can examine access to unchanged content as well as changes to the content itself.&lt;/p&gt;
&lt;p&gt;Access to document history follows the relevant History menu permission, while detailed session inspection requires Sessions menu access. Reports and statistics dashboards provide additional ways to examine document activity.&lt;/p&gt;
&lt;h3&gt;Search across content and metadata&lt;/h3&gt;
&lt;p&gt;LogicalDOC retrieves documents through content, metadata, and structured filters. We support full-text searches across document content and selected metadata, plus searches using tags, standard properties, and custom template fields.&lt;/p&gt;
&lt;p&gt;Filters include language, folder, size, date, and document class. Results can display text snippets. Parametric searches use document metadata, while saved custom searches support recurring retrieval tasks.&lt;/p&gt;
&lt;p&gt;For example, a reviewer can retrieve procedures by a custom equipment field rather than remember a phrase from each file.&lt;/p&gt;
&lt;p&gt;Content indexing runs asynchronously under configurable processing schedules. Supported formats include Microsoft Office, OpenOffice, and PDF. OCR extracts text from images and raster PDFs, extending content retrieval to scanned material. Integrated preview lets users inspect documents within the interface without opening a separate application.&lt;/p&gt;
&lt;h2&gt;Choose your LogicalDOC deployment&lt;/h2&gt;
&lt;p&gt;LogicalDOC offers cloud, on-premises, and hybrid deployment, with different arrangements for repository location, infrastructure ownership, and server administration. Choose the model around who will operate the environment and how users need to reach documents.&lt;/p&gt;
&lt;p&gt;The deployment options divide responsibilities as follows:&lt;/p&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th&gt;
&lt;p&gt;Deployment&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Repository location&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Operational responsibility&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Access method&lt;/p&gt;
&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Cloud&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;External data center&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;LogicalDOC handles server maintenance&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Web interface over an internet connection&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;On-premises&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Your physical or virtual servers&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Your IT team typically manages infrastructure and administration&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Local network; configurable remote access&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Hybrid&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Local and remote cloud installations&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Your team manages the main local application&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;One portal for private- and public-cloud workspaces&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Deployment details: &lt;a href=&quot;https://www.logicaldoc.com/product/cloud-document-management&quot;&gt;LogicalDOC Cloud&lt;/a&gt;, On-Premise DMS, and Hybrid Cloud.&lt;/p&gt;
&lt;p&gt;Cloud suits teams that want hosted operation with server maintenance handled by us. Users access the service through a web interface, without a local server installation to maintain.&lt;/p&gt;
&lt;p&gt;On-premises places the application, documents, and data on infrastructure you manage. Your IT team typically handles hardware, deployment, maintenance, and security protocols. Remote access can be configured alongside local-network access.&lt;/p&gt;
&lt;p&gt;Hybrid combines a local application with repository synchronization to a remote cloud installation. You can publish selected repository content to the cloud site, allowing the cloud workspace to contain the material intended for that audience.&lt;/p&gt;
&lt;p&gt;For organizations using SaaS, the &lt;a href=&quot;https://www.ncsc.gov.uk/collection/cloud/using-cloud-services-securely/using-saas-securely&quot;&gt;UK National Cyber Security Centre&lt;/a&gt; explains that customers retain responsibility for application-specific configuration and recommends resilient backup arrangements for critical application data. Include access ownership and recovery arrangements in your deployment decision alongside server administration.&lt;/p&gt;
&lt;p&gt;Before selecting a model, assign an administrator, identify remote-access needs, and decide which content belongs in the cloud workspace. Those decisions make the operating responsibilities concrete.&lt;/p&gt;
&lt;h2&gt;LogicalDOC editions and pricing basis&lt;/h2&gt;
&lt;p&gt;LogicalDOC edition selection depends especially on whether your team needs approval workflows, OCR, and saved searches. As of November 2026, our four editions are Community, Business, Enterprise, and Cloud, with the following feature availability.&lt;/p&gt;
&lt;h3&gt;Features across the four editions&lt;/h3&gt;
&lt;p&gt;LogicalDOC includes core versioning, searching, access controls, and event logging across all four editions. The table separates those shared capabilities from features included in specific editions.&lt;/p&gt;
&lt;table&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;th&gt;
&lt;p&gt;Feature&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Community&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Business&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Enterprise&lt;/p&gt;
&lt;/th&gt;
&lt;th&gt;
&lt;p&gt;Cloud&lt;/p&gt;
&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Version control&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Document searching&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Multilingual full-text indexing&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Users and groups&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Folder and menu security policies&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Events log&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Workflow&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;OCR&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Folder searching&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;p&gt;Saved searches&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Not included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;p&gt;Included&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Feature availability: LogicalDOC &lt;a href=&quot;https://www.logicaldoc.com/features/comparison-matrix&quot;&gt;Product Features and Comparison Matrix&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Community is free and open source. Business includes OCR, folder searching, and saved searches alongside the shared document-management capabilities.&lt;/p&gt;
&lt;p&gt;For the assigned approval workflows described above, choose Enterprise or Cloud. Enterprise provides our full feature set on customer-managed infrastructure, while Cloud provides hosted operation. Match your evaluation environment to the edition you intend to purchase so the tested review process becomes part of the commercial specification.&lt;/p&gt;
&lt;h3&gt;Costs and quotation inputs&lt;/h3&gt;
&lt;p&gt;LogicalDOC Cloud pricing is based on storage space and user count. Business, Enterprise, and Cloud pricing is supplied through commercial quotations.&lt;/p&gt;
&lt;p&gt;Our quotation form collects the selected product, number of users, repository size, country, and contact details. Prepare those inputs around the working repository you intend to manage, including expected document growth.&lt;/p&gt;
&lt;p&gt;On-premises budgeting includes software licensing and infrastructure, with internal resources for deployment and ongoing administration. Compare that operating model with hosted service costs using the same user population and document requirements small change to trigger imagedownloader.&lt;/p&gt;
&lt;p&gt;A practical comparison combines the required edition, expected storage growth, user count, and deployment responsibilities. For example, a team requiring assigned approvals and scanned-document retrieval should cost the edition that includes both workflow and OCR, together with its chosen hosting arrangement.&lt;/p&gt;
&lt;h2&gt;Evaluate LogicalDOC with your documents&lt;/h2&gt;
&lt;p&gt;Evaluate LogicalDOC by taking a representative procedure or operating manual through editing, rejection, revision, and approval. Include a scanned document and the reader, author, and approver roles involved in everyday work.&lt;/p&gt;
&lt;p&gt;Use the evaluation to complete three checks:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Follow the review cycle and inspect the resulting version and activity records.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Retrieve the document through content and metadata searches.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Open the document using the intended reader account and check its permissions.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Set acceptance criteria before testing: an identifiable approved revision, an accountable reviewer, appropriate user permissions, and a retrievable activity history.&lt;/p&gt;
&lt;p&gt;One evaluation form provides a downloadable 30-day trial and credentials for a demonstration website requiring no local installation. These are separate evaluation routes. Start your LogicalDOC evaluation with one document and the people responsible for changing, approving, and using it. &lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>Digital Sovereignty: Why Control Over Data Is Changing How Businesses Choose a DMS</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/677-digital-sovereignty-document-management"/>
		<published>2026-11-03T10:20:58+00:00</published>
		<updated>2026-11-03T10:20:58+00:00</updated>
		<id>https://www.logicaldoc.com/blog/677-digital-sovereignty-document-management</id>
		<author>
			<name>Luca</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;&quot;&gt;&lt;/p&gt;&lt;p style=&quot;text-align: justify;&quot;&gt;Growing attention to digital sovereignty is introducing new considerations into business technology decisions. Where are documents stored? Who can access them? Which laws apply to the data? And, above all, how easy is it to switch providers or infrastructure without disrupting business operations?&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;These questions are particularly important when choosing a Document Management System (DMS), because documents are more than just information to be stored. Contracts, projects, technical documentation, administrative records, and internal communications represent a fundamental part of an organization's information assets.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Deciding where and how to manage them is becoming a strategic choice, not just a technological one.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;What Is Digital Sovereignty?&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty is an organization's ability to maintain control over its information, technology infrastructure, and the conditions governing their use, without becoming excessively dependent on external providers, platforms, or third parties.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;It is a broader concept than cybersecurity and personal data protection. A system can be adequately protected against cyberattacks while still leaving a company with limited control over the technologies it uses, how information can be accessed, or whether that information can be moved elsewhere.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In essence, digital sovereignty can be described as an organization's ability to maintain effective control over its data, the technologies it uses, and its dependencies on technology providers.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This does not necessarily mean owning every component of its IT infrastructure or avoiding international services. Rather, it means understanding the conditions under which its systems operate and retaining the ability to make independent decisions.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty therefore raises a fundamental question: &lt;strong&gt;who really controls the digital resources on which an organization depends?&lt;/strong&gt;&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Digital Sovereignty: A Global Concern&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In recent years, digital sovereignty has become part of the technology strategies of numerous countries, although priorities and approaches differ.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In June 2026, the European Commission presented a package of initiatives focused on technological sovereignty, addressing issues related to cloud infrastructure, artificial intelligence, open-source software, and technological dependencies.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Many other countries outside the European Union have also begun addressing digital sovereignty. Despite differences in national approaches, they &lt;a href=&quot;https://www.oecd.org/en/publications/digital-government-outlook_0496b2bc-en.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;share a common underlying concer&lt;/a&gt;n: preventing critical information and services from becoming dependent on conditions that organizations and institutions cannot adequately control.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;For companies operating internationally, this development is particularly significant. Infrastructure used to manage documents and information across multiple countries must accommodate requirements for accessibility, security, governance, and compliance that may vary from one market to another.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty is therefore becoming a consideration in the design of information systems, rather than merely an issue of national technology policy.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;From Data Sovereignty to Operational Autonomy&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;To translate this concept into practical business decisions, it is useful to distinguish three closely related dimensions.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The first is &lt;strong&gt;data sovereignty&lt;/strong&gt;: knowing where information is stored, who can access it, which rules govern its processing, and what options are available for transferring or deleting it.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The second is &lt;strong&gt;technological sovereignty&lt;/strong&gt;: retaining the freedom to choose the platforms, tools, and infrastructure an organization uses, while limiting dependencies that could make future changes difficult.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The third is &lt;strong&gt;operational sovereignty&lt;/strong&gt;: being able to continue using systems and accessing information even when technical problems, contractual changes, or disruptions to external services occur.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty, therefore, does not necessarily mean physically owning servers, nor does it require organizations to abandon cloud services.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Its objective is more practical: enabling organizations to retain control over their information and the freedom to make technology decisions over the long term.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Cloud vs. On-Premises: Different Models, Different Responsibilities&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In the past, discussions about digital sovereignty have often been simplified into a choice between cloud and on-premises deployments. While these two models certainly have distinct characteristics, the issue is more nuanced.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/product/cloud-document-management&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Cloud&lt;/a&gt; solutions continue to offer significant advantages for many organizations.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Using infrastructure managed by specialized providers can reduce internal operational complexity, facilitate access across distributed locations, and make it easier to scale resources according to business needs.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;For companies without a dedicated IT department, these benefits can be particularly important.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;However, adopting a cloud solution also means entrusting part of the technology infrastructure's management to an external provider. Organizations therefore need to understand how service availability, information security, business continuity, and data recovery are ensured.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The &lt;a href=&quot;https://www.logicaldoc.com/product/on-premise-dms&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;on-premises&lt;/a&gt; approach offers a different model.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;By installing a DMS on infrastructure managed directly by the organization, a company can exercise more immediate control over certain aspects of its IT environment, from server configuration to access and retention policies.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This model may be particularly suitable when there are strict requirements for integration, confidentiality, or infrastructure management.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;However, direct control should not be confused with automatically achieving greater security.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;An on-premises installation requires technical expertise, updates, monitoring, backup procedures, and appropriate security measures. Poorly managed internal infrastructure can expose documents to greater risks than a properly managed cloud service.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;strong&gt;The distinction is not between a secure and an insecure technology, but between different models for managing risks and responsibilities.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;strong&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/Cloud%20vs.%20On-Premises_%20Responsabilita%20a%20Confronto.png&quot; alt=&quot;Cloud vs. On-Premise&quot; width=&quot;1448&quot; height=&quot;1086&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/Cloud vs. On-Premises_ Responsabilita a Confronto.png&quot;&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Towards More Flexible Document Management Models&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Market developments suggest that the distinction between cloud and on-premises deployment is &lt;a href=&quot;https://www.logicaldoc.com/product/hybrid-cloud&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;becoming less rigid&lt;/a&gt;.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Organizations do not necessarily need to adopt a single model for all their systems. On the contrary, they may require different solutions depending on their specific circumstances.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In any case, the objective should always be to achieve a balance between accessibility, control, cost-effectiveness, and the ability to adapt over time.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;strong&gt;Flexibility in deployment options is becoming strategically important.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Being able to evaluate different deployment models allows companies to start with their document management requirements, rather than having to adapt their business processes to a predefined infrastructure model.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The ability to integrate the system with existing applications, define access policies, and properly manage data exports also helps preserve organizational autonomy.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;How Digital Sovereignty Is Changing the Way Businesses Choose a Document Management System&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty considerations call for a more comprehensive approach to selecting document management software.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Before comparing features and prices, organizations should clarify several fundamental aspects:&lt;/p&gt;
&lt;table style=&quot;width: 100%; border-collapse: collapse; font-size: 15px; line-height: 1.6;&quot;&gt;
&lt;tbody&gt;
&lt;tr style=&quot;background-color: #f2f4f6;&quot;&gt;
&lt;td style=&quot;width: 35%; padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Data control&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;Where are documents, metadata, and backups stored, and who can access them?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #ffffff;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Operational responsibilities&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;Who manages security, updates, business continuity, and recovery?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #f2f4f6;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Portability&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;How can documents, metadata, and associated information be exported?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #ffffff;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Compliance&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;Which regulatory, contractual, and industry-specific requirements must be met?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #f2f4f6;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Future flexibility&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;How complex would it be to change infrastructure or switch providers?&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;These questions make it possible to evaluate a DMS not simply as an application, but as an integral component of an organization's information governance strategy.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In this context, solutions such as &lt;strong&gt;LogicalDOC&lt;/strong&gt;, available through both cloud and on-premises deployment options, can be considered by organizations with different infrastructure requirements.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The choice of the &lt;a href=&quot;https://www.logicaldoc.com/solutions/document-management&quot;&gt;most appropriate model &lt;/a&gt;should nevertheless be based on a careful assessment of technical requirements, contractual conditions, and the level of control the organization needs.&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;&quot;&gt;&lt;/p&gt;&lt;p style=&quot;text-align: justify;&quot;&gt;Growing attention to digital sovereignty is introducing new considerations into business technology decisions. Where are documents stored? Who can access them? Which laws apply to the data? And, above all, how easy is it to switch providers or infrastructure without disrupting business operations?&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;These questions are particularly important when choosing a Document Management System (DMS), because documents are more than just information to be stored. Contracts, projects, technical documentation, administrative records, and internal communications represent a fundamental part of an organization's information assets.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Deciding where and how to manage them is becoming a strategic choice, not just a technological one.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;What Is Digital Sovereignty?&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty is an organization's ability to maintain control over its information, technology infrastructure, and the conditions governing their use, without becoming excessively dependent on external providers, platforms, or third parties.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;It is a broader concept than cybersecurity and personal data protection. A system can be adequately protected against cyberattacks while still leaving a company with limited control over the technologies it uses, how information can be accessed, or whether that information can be moved elsewhere.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In essence, digital sovereignty can be described as an organization's ability to maintain effective control over its data, the technologies it uses, and its dependencies on technology providers.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This does not necessarily mean owning every component of its IT infrastructure or avoiding international services. Rather, it means understanding the conditions under which its systems operate and retaining the ability to make independent decisions.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty therefore raises a fundamental question: &lt;strong&gt;who really controls the digital resources on which an organization depends?&lt;/strong&gt;&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Digital Sovereignty: A Global Concern&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In recent years, digital sovereignty has become part of the technology strategies of numerous countries, although priorities and approaches differ.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In June 2026, the European Commission presented a package of initiatives focused on technological sovereignty, addressing issues related to cloud infrastructure, artificial intelligence, open-source software, and technological dependencies.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Many other countries outside the European Union have also begun addressing digital sovereignty. Despite differences in national approaches, they &lt;a href=&quot;https://www.oecd.org/en/publications/digital-government-outlook_0496b2bc-en.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;share a common underlying concer&lt;/a&gt;n: preventing critical information and services from becoming dependent on conditions that organizations and institutions cannot adequately control.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;For companies operating internationally, this development is particularly significant. Infrastructure used to manage documents and information across multiple countries must accommodate requirements for accessibility, security, governance, and compliance that may vary from one market to another.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty is therefore becoming a consideration in the design of information systems, rather than merely an issue of national technology policy.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;From Data Sovereignty to Operational Autonomy&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;To translate this concept into practical business decisions, it is useful to distinguish three closely related dimensions.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The first is &lt;strong&gt;data sovereignty&lt;/strong&gt;: knowing where information is stored, who can access it, which rules govern its processing, and what options are available for transferring or deleting it.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The second is &lt;strong&gt;technological sovereignty&lt;/strong&gt;: retaining the freedom to choose the platforms, tools, and infrastructure an organization uses, while limiting dependencies that could make future changes difficult.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The third is &lt;strong&gt;operational sovereignty&lt;/strong&gt;: being able to continue using systems and accessing information even when technical problems, contractual changes, or disruptions to external services occur.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty, therefore, does not necessarily mean physically owning servers, nor does it require organizations to abandon cloud services.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Its objective is more practical: enabling organizations to retain control over their information and the freedom to make technology decisions over the long term.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Cloud vs. On-Premises: Different Models, Different Responsibilities&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In the past, discussions about digital sovereignty have often been simplified into a choice between cloud and on-premises deployments. While these two models certainly have distinct characteristics, the issue is more nuanced.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/product/cloud-document-management&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Cloud&lt;/a&gt; solutions continue to offer significant advantages for many organizations.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Using infrastructure managed by specialized providers can reduce internal operational complexity, facilitate access across distributed locations, and make it easier to scale resources according to business needs.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;For companies without a dedicated IT department, these benefits can be particularly important.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;However, adopting a cloud solution also means entrusting part of the technology infrastructure's management to an external provider. Organizations therefore need to understand how service availability, information security, business continuity, and data recovery are ensured.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The &lt;a href=&quot;https://www.logicaldoc.com/product/on-premise-dms&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;on-premises&lt;/a&gt; approach offers a different model.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;By installing a DMS on infrastructure managed directly by the organization, a company can exercise more immediate control over certain aspects of its IT environment, from server configuration to access and retention policies.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This model may be particularly suitable when there are strict requirements for integration, confidentiality, or infrastructure management.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;However, direct control should not be confused with automatically achieving greater security.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;An on-premises installation requires technical expertise, updates, monitoring, backup procedures, and appropriate security measures. Poorly managed internal infrastructure can expose documents to greater risks than a properly managed cloud service.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;strong&gt;The distinction is not between a secure and an insecure technology, but between different models for managing risks and responsibilities.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;strong&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/Cloud%20vs.%20On-Premises_%20Responsabilita%20a%20Confronto.png&quot; alt=&quot;Cloud vs. On-Premise&quot; width=&quot;1448&quot; height=&quot;1086&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/Cloud vs. On-Premises_ Responsabilita a Confronto.png&quot;&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Towards More Flexible Document Management Models&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Market developments suggest that the distinction between cloud and on-premises deployment is &lt;a href=&quot;https://www.logicaldoc.com/product/hybrid-cloud&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;becoming less rigid&lt;/a&gt;.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Organizations do not necessarily need to adopt a single model for all their systems. On the contrary, they may require different solutions depending on their specific circumstances.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In any case, the objective should always be to achieve a balance between accessibility, control, cost-effectiveness, and the ability to adapt over time.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;strong&gt;Flexibility in deployment options is becoming strategically important.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Being able to evaluate different deployment models allows companies to start with their document management requirements, rather than having to adapt their business processes to a predefined infrastructure model.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The ability to integrate the system with existing applications, define access policies, and properly manage data exports also helps preserve organizational autonomy.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;How Digital Sovereignty Is Changing the Way Businesses Choose a Document Management System&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Digital sovereignty considerations call for a more comprehensive approach to selecting document management software.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Before comparing features and prices, organizations should clarify several fundamental aspects:&lt;/p&gt;
&lt;table style=&quot;width: 100%; border-collapse: collapse; font-size: 15px; line-height: 1.6;&quot;&gt;
&lt;tbody&gt;
&lt;tr style=&quot;background-color: #f2f4f6;&quot;&gt;
&lt;td style=&quot;width: 35%; padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Data control&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;Where are documents, metadata, and backups stored, and who can access them?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #ffffff;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Operational responsibilities&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;Who manages security, updates, business continuity, and recovery?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #f2f4f6;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Portability&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;How can documents, metadata, and associated information be exported?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #ffffff;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Compliance&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;Which regulatory, contractual, and industry-specific requirements must be met?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr style=&quot;background-color: #f2f4f6;&quot;&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;&lt;strong&gt;Future flexibility&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 14px; border-bottom: 1px solid #e2e5e9; vertical-align: top;&quot;&gt;How complex would it be to change infrastructure or switch providers?&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;These questions make it possible to evaluate a DMS not simply as an application, but as an integral component of an organization's information governance strategy.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In this context, solutions such as &lt;strong&gt;LogicalDOC&lt;/strong&gt;, available through both cloud and on-premises deployment options, can be considered by organizations with different infrastructure requirements.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The choice of the &lt;a href=&quot;https://www.logicaldoc.com/solutions/document-management&quot;&gt;most appropriate model &lt;/a&gt;should nevertheless be based on a careful assessment of technical requirements, contractual conditions, and the level of control the organization needs.&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>When AI Becomes a Co-Author</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/669-when-ai-becomes-a-co-author"/>
		<published>2026-09-23T08:00:04+00:00</published>
		<updated>2026-09-23T08:00:04+00:00</updated>
		<id>https://www.logicaldoc.com/blog/669-when-ai-becomes-a-co-author</id>
		<author>
			<name>Luca</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;Robot writing with a quill pen next to floating document management icons&quot;&gt;&lt;/p&gt;&lt;h3 style=&quot;text-align: justify;&quot;&gt;How versioning, metadata, search and governance take on a new role in AI-assisted document creation.&lt;/h3&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Calling AI a &quot;co-author&quot; is deliberately provocative.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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, &lt;a href=&quot;https://www.icmje.org/recommendations/browse/roles-and-responsibilities/defining-the-role-of-authors-and-contributors.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;accountability remains with humans&lt;/a&gt;.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;br&gt;It is precisely this separation between the contribution to creation and accountability for the outcome that makes this issue significant for document management.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;br&gt;Document management must therefore begin to view the document not just as an object, but as the outcome of an information production process.&lt;br&gt;This represents a significant shift, placing tools and functions that have long existed in Document Management Systems back at the center of attention.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Versioning: from a history of changes to a history of decisions&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/version-control&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Version control&lt;/a&gt; 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.&lt;br&gt;With the advent of AI, versioning takes on a secondary function: it becomes a way to reconstruct the content's evolution.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The distinction LogicalDOC makes between &quot;&lt;strong&gt;Document Version&lt;/strong&gt;&quot; and &quot;&lt;strong&gt;File Version&lt;/strong&gt;&quot; is a useful example. The system also tracks metadata changes that don't necessarily involve replacing the physical file.&lt;br&gt;This distinction is valuable because a document's evolution may involve not only its content but also its context, status, and provenance information.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Metadata becomes provenance metadata.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The role of metadata is also shifting. Traditionally, metadata describes the document itself—client, project, author, date, document type, department, and status.&lt;br&gt;In the future, it may increasingly describe &lt;strong&gt;the very process by which the document was produced&lt;/strong&gt;.&lt;br&gt;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.&lt;br&gt;This does not necessarily require dozens of new fields. The real value lies in transforming information that is currently implicit into &lt;strong&gt;structured, queryable context.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Search must find the right document, not just the most similar one.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;AI also introduces a seemingly paradoxical issue: the easier it becomes to produce content, the more content we must manage.&lt;br&gt;A single document could spawn a summary, a translation, a simplified version, a presentation, an FAQ, or a new AI-generated draft.&lt;br&gt;All of these are semantically very similar documents.&lt;br&gt;In such cases, effective search cannot simply identify what most closely resembles the query.&lt;br&gt;It must help determine which &lt;strong&gt;document is authoritative.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/semantic-search&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Semantic search&lt;/a&gt; is therefore important, but it does not replace metadata, versioning, permissions, or document status; rather, it makes them even more essential.&lt;br&gt;Maximum value is achieved when semantic similarity is integrated into a document management system that simultaneously preserves document classification, security, status, and history.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In LogicalDOC, semantic search uses&lt;a href=&quot;https://www.logicaldoc.com/software-features/embeddings&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt; embeddings&lt;/a&gt; to locate documents based on meaning rather than just the presence of identical words.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Workflows: where responsibility returns to humans&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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 &lt;a href=&quot;https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence?utm_source&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;assumes responsibility for content &lt;/a&gt;produced or modified with AI assistance.&lt;br&gt;Documentable human review is becoming a key component of the trust architecture surrounding AI-generated content.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In a DMS like LogicalDOC, &lt;a href=&quot;https://www.logicaldoc.com/software-features/workflow&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;workflows&lt;/a&gt; already enable processes where different users review, approve, or reject a document.&lt;br&gt;While AI can accelerate document creation or modification, the workflow determines who authorizes the final result.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;AI should not have more access than the user.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;br&gt;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.&lt;br&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;A DMS must do more than just &quot;feature AI&quot;&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;For this reason, evaluating a Document Management System solely based on the presence of AI capabilities risks focusing on the wrong question.&lt;br&gt;The more compelling question is:&lt;br&gt;how effectively can the document system govern what the AI creates, modifies, and utilizes?&lt;br&gt;Features such as AI-powered document processing or semantic search can certainly enhance information classification, extraction, and accessibility.&lt;br&gt;Yet, in this context, the value of a DMS like &lt;a href=&quot;https://www.logicaldoc.com/try&quot;&gt;LogicalDOC&lt;/a&gt; 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.&lt;br&gt;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.&lt;br&gt;And the more AI contributes to drafting corporate documents, the more vital this record-keeping becomes.&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;Robot writing with a quill pen next to floating document management icons&quot;&gt;&lt;/p&gt;&lt;h3 style=&quot;text-align: justify;&quot;&gt;How versioning, metadata, search and governance take on a new role in AI-assisted document creation.&lt;/h3&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Calling AI a &quot;co-author&quot; is deliberately provocative.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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, &lt;a href=&quot;https://www.icmje.org/recommendations/browse/roles-and-responsibilities/defining-the-role-of-authors-and-contributors.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;accountability remains with humans&lt;/a&gt;.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;br&gt;It is precisely this separation between the contribution to creation and accountability for the outcome that makes this issue significant for document management.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;br&gt;Document management must therefore begin to view the document not just as an object, but as the outcome of an information production process.&lt;br&gt;This represents a significant shift, placing tools and functions that have long existed in Document Management Systems back at the center of attention.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Versioning: from a history of changes to a history of decisions&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/version-control&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Version control&lt;/a&gt; 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.&lt;br&gt;With the advent of AI, versioning takes on a secondary function: it becomes a way to reconstruct the content's evolution.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The distinction LogicalDOC makes between &quot;&lt;strong&gt;Document Version&lt;/strong&gt;&quot; and &quot;&lt;strong&gt;File Version&lt;/strong&gt;&quot; is a useful example. The system also tracks metadata changes that don't necessarily involve replacing the physical file.&lt;br&gt;This distinction is valuable because a document's evolution may involve not only its content but also its context, status, and provenance information.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Metadata becomes provenance metadata.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The role of metadata is also shifting. Traditionally, metadata describes the document itself—client, project, author, date, document type, department, and status.&lt;br&gt;In the future, it may increasingly describe &lt;strong&gt;the very process by which the document was produced&lt;/strong&gt;.&lt;br&gt;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.&lt;br&gt;This does not necessarily require dozens of new fields. The real value lies in transforming information that is currently implicit into &lt;strong&gt;structured, queryable context.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Search must find the right document, not just the most similar one.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;AI also introduces a seemingly paradoxical issue: the easier it becomes to produce content, the more content we must manage.&lt;br&gt;A single document could spawn a summary, a translation, a simplified version, a presentation, an FAQ, or a new AI-generated draft.&lt;br&gt;All of these are semantically very similar documents.&lt;br&gt;In such cases, effective search cannot simply identify what most closely resembles the query.&lt;br&gt;It must help determine which &lt;strong&gt;document is authoritative.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/semantic-search&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Semantic search&lt;/a&gt; is therefore important, but it does not replace metadata, versioning, permissions, or document status; rather, it makes them even more essential.&lt;br&gt;Maximum value is achieved when semantic similarity is integrated into a document management system that simultaneously preserves document classification, security, status, and history.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In LogicalDOC, semantic search uses&lt;a href=&quot;https://www.logicaldoc.com/software-features/embeddings&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt; embeddings&lt;/a&gt; to locate documents based on meaning rather than just the presence of identical words.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;Workflows: where responsibility returns to humans&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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 &lt;a href=&quot;https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence?utm_source&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;assumes responsibility for content &lt;/a&gt;produced or modified with AI assistance.&lt;br&gt;Documentable human review is becoming a key component of the trust architecture surrounding AI-generated content.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In a DMS like LogicalDOC, &lt;a href=&quot;https://www.logicaldoc.com/software-features/workflow&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;workflows&lt;/a&gt; already enable processes where different users review, approve, or reject a document.&lt;br&gt;While AI can accelerate document creation or modification, the workflow determines who authorizes the final result.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;AI should not have more access than the user.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;br&gt;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.&lt;br&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;&lt;br&gt;A DMS must do more than just &quot;feature AI&quot;&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;For this reason, evaluating a Document Management System solely based on the presence of AI capabilities risks focusing on the wrong question.&lt;br&gt;The more compelling question is:&lt;br&gt;how effectively can the document system govern what the AI creates, modifies, and utilizes?&lt;br&gt;Features such as AI-powered document processing or semantic search can certainly enhance information classification, extraction, and accessibility.&lt;br&gt;Yet, in this context, the value of a DMS like &lt;a href=&quot;https://www.logicaldoc.com/try&quot;&gt;LogicalDOC&lt;/a&gt; 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.&lt;br&gt;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.&lt;br&gt;And the more AI contributes to drafting corporate documents, the more vital this record-keeping becomes.&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>Secure Document Sharing for Clients That Works</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/668-secure-document-sharing-for-clients"/>
		<published>2026-09-15T13:32:17+00:00</published>
		<updated>2026-09-15T13:32:17+00:00</updated>
		<id>https://www.logicaldoc.com/blog/668-secure-document-sharing-for-clients</id>
		<author>
			<name>Alessandro</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/secure-document-sharing-for-clients.webp&quot; alt=&quot;Laptop showing a secure document icon on a desk while two people exchange papers in the background&quot; width=&quot;1536&quot; height=&quot;1024&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Why email attachments create a control problem&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“Security is not just about protecting documents — it’s about controlling how they move, who sees them, and what happens next.”&lt;/em&gt; &lt;br&gt;— &lt;strong&gt;Laura Mitchell, Information Governance Consultant&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A controlled &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=122&quot;&gt;document management environment&lt;/a&gt; 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.&lt;/p&gt;
&lt;h2&gt;What secure document sharing for clients should provide&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Permission-based access&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Version control that clients can trust&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“Clients work faster and make better decisions when they access one trusted source of truth instead of scattered file copies.”&lt;/em&gt; &lt;br&gt;— &lt;strong&gt;David Harper, Digital Transformation Advisor&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Audit trails and accountability&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Expiry, revocation and controlled downloads&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;Secure Client Document Sharing: Five Essential Controls&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/secure-client-document-sharing-infographic.png&quot; alt=&quot;Secure client document sharing infographic showing five essential controls: access permissions, version control, controlled distribution, time-limited access, and audit trail&quot; width=&quot;1484&quot; height=&quot;1060&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/secure-client-document-sharing-infographic.png&quot;&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Secure sharing is not just about sending a file safely. It is about keeping control before, during and after access.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;Build the process around the client journey&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Give IT control without creating a burden for users&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A platform that supports cloud, &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=964&quot;&gt;hybrid-cloud and on-premise&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;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 &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1734&quot;&gt;well-planned integrations&lt;/a&gt; can keep document creation, classification and sharing connected to existing work.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;div class=&quot;sl-embed&quot; style=&quot;position: relative; padding-bottom: calc(47.46% + 25px); width: 100%; height: 0; transform: scale(1);&quot;&gt;&lt;iframe class=&quot;sl-demo&quot; style=&quot;position: absolute; top: 0; left: 0; width: 100%!important; height: 100%!important; border: 1px solid rgba(63,95,172,0.35); box-shadow: 0px 0px 18px rgba(26, 19, 72, 0.15); border-radius: 10px; box-sizing: border-box;&quot; src=&quot;https://app.storylane.io/demo/hdrafxpvef2y?embed=inline&quot; name=&quot;sl-embed&quot; allow=&quot;fullscreen&quot; allowfullscreen=&quot;allowfullscreen&quot; loading=&quot;lazy&quot;&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;div style=&quot;display: none; visibility: hidden; width: 1px; height: 1px;&quot; tabindex=&quot;-1&quot; aria-hidden=&quot;true&quot;&gt;LogicalDOC allows users to share documents via download tickets, which are secure, time-limited, access-controlled links that do not require recipients to have an account. To create a ticket, sign in to the LogicalDOC workspace and navigate to the Documents section. Open the relevant folder, select the target document, and open its document panel. From there, access the Versions tab to select the specific document version to share, then open the Ticket option to generate a secure download link. When configuring a ticket, the following access controls are available: choose between download access or view-only access, set an expiry date after which the link becomes inactive, limit the number of times the file can be downloaded, cap the number of views, and add a password that recipients must enter to access the link. Once settings are confirmed, LogicalDOC generates a shareable URL that can be distributed via email, chat, or any other channel. From the recipient's perspective, the link opens a secure access page where they enter the password to unlock the document. The document then opens within the defined access limits, with no LogicalDOC account required. Admins can monitor ticket usage by navigating to Administration and opening the Reports section. The Tickets report lists all active and expired tickets. Each ticket entry provides an activity log showing the ticket ID, number of views, number of downloads, and access timestamps. Tickets can be revoked or modified at any time after sharing.&lt;/div&gt;
&lt;/div&gt;
&lt;h2&gt;Common mistakes that weaken client document security&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Start with the documents that cause the most friction&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/secure-document-sharing-for-clients.webp&quot; alt=&quot;Laptop showing a secure document icon on a desk while two people exchange papers in the background&quot; width=&quot;1536&quot; height=&quot;1024&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Why email attachments create a control problem&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“Security is not just about protecting documents — it’s about controlling how they move, who sees them, and what happens next.”&lt;/em&gt; &lt;br&gt;— &lt;strong&gt;Laura Mitchell, Information Governance Consultant&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A controlled &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=122&quot;&gt;document management environment&lt;/a&gt; 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.&lt;/p&gt;
&lt;h2&gt;What secure document sharing for clients should provide&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Permission-based access&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Version control that clients can trust&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;“Clients work faster and make better decisions when they access one trusted source of truth instead of scattered file copies.”&lt;/em&gt; &lt;br&gt;— &lt;strong&gt;David Harper, Digital Transformation Advisor&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Audit trails and accountability&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Expiry, revocation and controlled downloads&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;Secure Client Document Sharing: Five Essential Controls&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/secure-client-document-sharing-infographic.png&quot; alt=&quot;Secure client document sharing infographic showing five essential controls: access permissions, version control, controlled distribution, time-limited access, and audit trail&quot; width=&quot;1484&quot; height=&quot;1060&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/secure-client-document-sharing-infographic.png&quot;&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Secure sharing is not just about sending a file safely. It is about keeping control before, during and after access.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;Build the process around the client journey&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Give IT control without creating a burden for users&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;A platform that supports cloud, &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=964&quot;&gt;hybrid-cloud and on-premise&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;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 &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1734&quot;&gt;well-planned integrations&lt;/a&gt; can keep document creation, classification and sharing connected to existing work.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;div&gt;
&lt;div class=&quot;sl-embed&quot; style=&quot;position: relative; padding-bottom: calc(47.46% + 25px); width: 100%; height: 0; transform: scale(1);&quot;&gt;&lt;iframe class=&quot;sl-demo&quot; style=&quot;position: absolute; top: 0; left: 0; width: 100%!important; height: 100%!important; border: 1px solid rgba(63,95,172,0.35); box-shadow: 0px 0px 18px rgba(26, 19, 72, 0.15); border-radius: 10px; box-sizing: border-box;&quot; src=&quot;https://app.storylane.io/demo/hdrafxpvef2y?embed=inline&quot; name=&quot;sl-embed&quot; allow=&quot;fullscreen&quot; allowfullscreen=&quot;allowfullscreen&quot; loading=&quot;lazy&quot;&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;div style=&quot;display: none; visibility: hidden; width: 1px; height: 1px;&quot; tabindex=&quot;-1&quot; aria-hidden=&quot;true&quot;&gt;LogicalDOC allows users to share documents via download tickets, which are secure, time-limited, access-controlled links that do not require recipients to have an account. To create a ticket, sign in to the LogicalDOC workspace and navigate to the Documents section. Open the relevant folder, select the target document, and open its document panel. From there, access the Versions tab to select the specific document version to share, then open the Ticket option to generate a secure download link. When configuring a ticket, the following access controls are available: choose between download access or view-only access, set an expiry date after which the link becomes inactive, limit the number of times the file can be downloaded, cap the number of views, and add a password that recipients must enter to access the link. Once settings are confirmed, LogicalDOC generates a shareable URL that can be distributed via email, chat, or any other channel. From the recipient's perspective, the link opens a secure access page where they enter the password to unlock the document. The document then opens within the defined access limits, with no LogicalDOC account required. Admins can monitor ticket usage by navigating to Administration and opening the Reports section. The Tickets report lists all active and expired tickets. Each ticket entry provides an activity log showing the ticket ID, number of views, number of downloads, and access timestamps. Tickets can be revoked or modified at any time after sharing.&lt;/div&gt;
&lt;/div&gt;
&lt;h2&gt;Common mistakes that weaken client document security&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Start with the documents that cause the most friction&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>AI knows the answer. But can it prove it? Defensible AI and the new role of document provenance</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/667-defensible-ai-and-document-provenance"/>
		<published>2026-08-26T10:28:44+00:00</published>
		<updated>2026-08-26T10:28:44+00:00</updated>
		<id>https://www.logicaldoc.com/blog/667-defensible-ai-and-document-provenance</id>
		<author>
			<name>Luca</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;&quot;&gt;&lt;/p&gt;&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;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?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In short, true evolution isn't moving from documents to answers, but from answers to verifiable answers.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It's around these questions that the concept of &lt;strong&gt;Defensible AI&lt;/strong&gt; 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.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Explainable AI and Defensible AI: They're Not the Same&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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. &lt;/p&gt;
&lt;p&gt;In other words, it's not enough to be able to say: &quot;The AI ​​produced this answer.&quot;&lt;/p&gt;
&lt;p&gt;It should be possible to demonstrate: &quot;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.&quot;&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;&lt;strong&gt;This is a fundamental difference.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://airc.nist.gov/airmf-resources/airmf/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;NIST AI Risk Management Framework&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;The challenge isn't just to make AI smarter, but &lt;strong&gt;to make its relationship with information traceable.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Evidence Provenance: Where Does AI's Statement Come From?&lt;/h2&gt;
&lt;p&gt;The concept of provenance didn't originate with artificial intelligence, but when applied to document-based AI, this principle becomes particularly interesting.&lt;/p&gt;
&lt;p&gt;A response generated by a business system should ideally preserve a true &lt;strong&gt;chain of evidence&lt;/strong&gt;. 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.&lt;/p&gt;
&lt;p&gt;The document can then be converted,&lt;a href=&quot;https://www.logicaldoc.com/software-features/ocr-optical-character-recognition&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt; OCRed&lt;/a&gt;, 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.&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;&lt;strong&gt;Provenance should ideally span this entire chain.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;&lt;strong&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/Traceable%20Document%20AI.png&quot; alt=&quot;Traceable document AI&quot; width=&quot;1448&quot; height=&quot;599&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/Traceable Document AI.png&quot;&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is probably one of the most important differences between a simple generative AI application and a true &lt;strong&gt;Traceable Document AI.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;RAG improves grounding. But it doesn't guarantee traceability.&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/blog/651-retrieval-augmented-generation-dms&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Retrieval-Augmented Generation&lt;/a&gt; is often touted as one of the main solutions to the problem of hallucinations in Large Language Models.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The problem simply shifts. You need to know what the repository contains.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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. &lt;a href=&quot;https://cheatsheetseries.owasp.org/cheatsheets/RAG_Security_Cheat_Sheet.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;(For more information)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In other words: &lt;strong&gt;RAG without document governance risks becoming simply a very efficient way to retrieve ungoverned information.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Versioning: A traditional DMS function becomes an AI governance function&lt;/h2&gt;
&lt;p&gt;Here an interesting paradox emerges. Some of the tools needed to govern advanced AI systems are not new at all.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/version-control&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Version control&lt;/a&gt;, for example, has been a fundamental function of document management systems for decades.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Significantly, the NIST Research Data Framework considers versioning essential for data traceability, data reconstruction, change tracking, and error correction.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h3&gt;Audit trail: not just who modified a document&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The former describes the document's history. The latter should connect that history to the decision's history.&lt;/p&gt;
&lt;p&gt;This principle is very clearly reflected in the &lt;a href=&quot;https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;EU AI Act.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Document governance and AI governance are converging&lt;/h2&gt;
&lt;p&gt;Document management has often been seen as a discipline separate from artificial intelligence.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;In this scenario, a document management system can take on a much broader role than that of a simple repository. Platforms like &lt;a href=&quot;https://www.logicaldoc.com/product/overview&quot;&gt;LogicalDOC&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;From the &quot;single source of truth&quot; to the &quot;single source of evidence&quot;&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The arrival of artificial intelligence suggests a further evolution of the concept.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The difference may seem semantic, but it is substantial.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;A possible architecture for Traceable Document AI&lt;/h2&gt;
&lt;p&gt;In this scenario, the document repository should not be considered simply a source from which to extract text for transformation into &lt;a href=&quot;https://www.logicaldoc.com/software-features/embeddings&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;embeddings&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It should remain the authoritative reference for the document.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The more AI autonomy increases, the more important this chain becomes.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The evidence trail must therefore be able to follow not only what the AI ​​says, but also what the AI ​​does.&lt;/p&gt;
&lt;h3&gt;Provenance does not necessarily mean truth.&lt;/h3&gt;
&lt;p&gt;Finally, there is an important clarification. Provenance does not automatically prove that information is correct.&lt;/p&gt;
&lt;p&gt;Rather, it demonstrates &lt;strong&gt;where it comes from and what happened to it&lt;/strong&gt;; it means being able to identify the source of the error, determine which other outputs were affected, and correct the process.&lt;/p&gt;
&lt;p&gt;Without provenance, however, the error risks becoming simply an incorrect response whose cause no one can reconstruct.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Enterprise AI's next challenge could be auditability.&lt;/h2&gt;
&lt;p&gt;In recent years, we've increasingly asked AI systems to classify, extract, understand, and generate.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;&quot;&gt;&lt;/p&gt;&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;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?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;In short, true evolution isn't moving from documents to answers, but from answers to verifiable answers.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It's around these questions that the concept of &lt;strong&gt;Defensible AI&lt;/strong&gt; 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.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Explainable AI and Defensible AI: They're Not the Same&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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. &lt;/p&gt;
&lt;p&gt;In other words, it's not enough to be able to say: &quot;The AI ​​produced this answer.&quot;&lt;/p&gt;
&lt;p&gt;It should be possible to demonstrate: &quot;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.&quot;&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;&lt;strong&gt;This is a fundamental difference.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The &lt;a href=&quot;https://airc.nist.gov/airmf-resources/airmf/&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;NIST AI Risk Management Framework&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;The challenge isn't just to make AI smarter, but &lt;strong&gt;to make its relationship with information traceable.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Evidence Provenance: Where Does AI's Statement Come From?&lt;/h2&gt;
&lt;p&gt;The concept of provenance didn't originate with artificial intelligence, but when applied to document-based AI, this principle becomes particularly interesting.&lt;/p&gt;
&lt;p&gt;A response generated by a business system should ideally preserve a true &lt;strong&gt;chain of evidence&lt;/strong&gt;. 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.&lt;/p&gt;
&lt;p&gt;The document can then be converted,&lt;a href=&quot;https://www.logicaldoc.com/software-features/ocr-optical-character-recognition&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt; OCRed&lt;/a&gt;, 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.&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;&lt;strong&gt;Provenance should ideally span this entire chain.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;&lt;strong&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/Traceable%20Document%20AI.png&quot; alt=&quot;Traceable document AI&quot; width=&quot;1448&quot; height=&quot;599&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/Traceable Document AI.png&quot;&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is probably one of the most important differences between a simple generative AI application and a true &lt;strong&gt;Traceable Document AI.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;RAG improves grounding. But it doesn't guarantee traceability.&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/blog/651-retrieval-augmented-generation-dms&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Retrieval-Augmented Generation&lt;/a&gt; is often touted as one of the main solutions to the problem of hallucinations in Large Language Models.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The problem simply shifts. You need to know what the repository contains.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;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. &lt;a href=&quot;https://cheatsheetseries.owasp.org/cheatsheets/RAG_Security_Cheat_Sheet.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;(For more information)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In other words: &lt;strong&gt;RAG without document governance risks becoming simply a very efficient way to retrieve ungoverned information.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Versioning: A traditional DMS function becomes an AI governance function&lt;/h2&gt;
&lt;p&gt;Here an interesting paradox emerges. Some of the tools needed to govern advanced AI systems are not new at all.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/software-features/version-control&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Version control&lt;/a&gt;, for example, has been a fundamental function of document management systems for decades.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Significantly, the NIST Research Data Framework considers versioning essential for data traceability, data reconstruction, change tracking, and error correction.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h3&gt;Audit trail: not just who modified a document&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The former describes the document's history. The latter should connect that history to the decision's history.&lt;/p&gt;
&lt;p&gt;This principle is very clearly reflected in the &lt;a href=&quot;https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;EU AI Act.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Document governance and AI governance are converging&lt;/h2&gt;
&lt;p&gt;Document management has often been seen as a discipline separate from artificial intelligence.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;In this scenario, a document management system can take on a much broader role than that of a simple repository. Platforms like &lt;a href=&quot;https://www.logicaldoc.com/product/overview&quot;&gt;LogicalDOC&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;From the &quot;single source of truth&quot; to the &quot;single source of evidence&quot;&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The arrival of artificial intelligence suggests a further evolution of the concept.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The difference may seem semantic, but it is substantial.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;A possible architecture for Traceable Document AI&lt;/h2&gt;
&lt;p&gt;In this scenario, the document repository should not be considered simply a source from which to extract text for transformation into &lt;a href=&quot;https://www.logicaldoc.com/software-features/embeddings&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;embeddings&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It should remain the authoritative reference for the document.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The more AI autonomy increases, the more important this chain becomes.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The evidence trail must therefore be able to follow not only what the AI ​​says, but also what the AI ​​does.&lt;/p&gt;
&lt;h3&gt;Provenance does not necessarily mean truth.&lt;/h3&gt;
&lt;p&gt;Finally, there is an important clarification. Provenance does not automatically prove that information is correct.&lt;/p&gt;
&lt;p&gt;Rather, it demonstrates &lt;strong&gt;where it comes from and what happened to it&lt;/strong&gt;; it means being able to identify the source of the error, determine which other outputs were affected, and correct the process.&lt;/p&gt;
&lt;p&gt;Without provenance, however, the error risks becoming simply an incorrect response whose cause no one can reconstruct.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;Enterprise AI's next challenge could be auditability.&lt;/h2&gt;
&lt;p&gt;In recent years, we've increasingly asked AI systems to classify, extract, understand, and generate.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>Version control, full-text search and workflows: how Dos&amp;Donts has taken document management to an enterprise level with LogicalDOC</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/665-dosdonts-logicaldoc-case-study"/>
		<published>2026-08-14T15:33:09+00:00</published>
		<updated>2026-08-14T15:33:09+00:00</updated>
		<id>https://www.logicaldoc.com/blog/665-dosdonts-logicaldoc-case-study</id>
		<author>
			<name>Alessandro</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/dosanddonts-logicaldoc-case-study-hero.webp&quot; alt=&quot;Dos&amp;amp;Donts and LogicalDOC case study hero image about document management and compliance&quot; width=&quot;1672&quot; height=&quot;941&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;table style=&quot;width: 100%; border-collapse: collapse; border: medium none currentcolor;&quot; border=&quot;1&quot;&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Company&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border: solid #C8D8E8 1.0pt; border-left: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;a href=&quot;https://dos-donts.com/&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Dos&amp;amp;Donts&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Sector&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Technology solutions for cleanrooms, GMP environments and controlled-contamination areas&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Size&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Italian SME specialising in solutions for controlled environments&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Role of interviewee&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Paolo Alzamira, CTO&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Main challenge&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;No version control, slow document search, no structured access control&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Deployment&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;on-premises&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Key outcome&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;~30% time saved on document searches; manuals and software versions finally aligned&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;About Dos&amp;amp;Donts&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;Dos&amp;amp;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.&lt;/p&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The starting point: shared folders in a context that demanded more&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;For a company operating in regulated environments, this fragility quickly becomes an operational constraint.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The crux of the matter: document versioning&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“Certain issues, such as versioning – which is fundamental for us from a document management perspective – were not being addressed.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;For Dos&amp;amp;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The choice of LogicalDOC: a specialised DMS, without the burden of an enterprise management system&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;What has changed with LogicalDOC&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;Full-text search: finding the document when you need it&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“Document search and version control for the documents we manage are the main benefits we’ve gained.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;Getting started: independent implementation, without external support&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“We did it all using the published manuals.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;What we discovered whilst using it: Enterprise features that an SME can actually use&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;The fact that Dos&amp;amp;Donts is now evaluating document workflows — a feature that wasn’t part of the initial plans — highlights an important aspect of LogicalDOC.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;Key results at a glance&lt;/h2&gt;
&lt;table style=&quot;width: 100%; border-collapse: collapse; border: medium none currentcolor;&quot; border=&quot;1&quot;&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; background: #2E75B6; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: white;&quot;&gt;Area&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border: solid #C8D8E8 1.0pt; border-left: none; background: #2E75B6; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: white;&quot;&gt;Before&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border: solid #C8D8E8 1.0pt; border-left: none; background: #2E75B6; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: white;&quot;&gt;After&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Versioning&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;None. Multiple versions in circulation without control&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Every change generates a version that is tracked with the date and author&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Document search&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Manual navigation between folders, no full-text search&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Search by content across the entire archive, with results in seconds&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Manual alignment&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Frequent misalignment between software version and documentation&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Consistent versioning: the manual remains aligned with the correct version&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Access control&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Basic permissions at shared folder level&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Granular roles and permissions by user and document type&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Scalability&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Structure difficult to maintain as the archive grows&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Document workflows currently being introduced, without changing the platform&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Deployment&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Folders on a shared server&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;on-premises with direct control over data, backups and access&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The recommendation&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;Based on Dos&amp;amp;Donts’ first-hand experience, LogicalDOC is particularly well-suited to companies that:&lt;/p&gt;
&lt;ul style=&quot;margin-left: 36.0pt;&quot;&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;manage technical documentation with multiple versions that need to be kept in line with the product&lt;/li&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;operate in regulated environments where document traceability is a requirement&lt;/li&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;are looking for a comprehensive, specialised DMS without the complexity of an enterprise suite&lt;/li&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;want to start with basic document management, knowing that advanced features will be available when the organisation is ready to use them&lt;/li&gt;
&lt;/ul&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;About Dos&amp;amp;Donts&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;Dos&amp;amp;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;About LogicalDOC&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: center; margin-top: 10.0pt;&quot;&gt;&lt;span style=&quot;color: #aaaaaa;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=426&quot;&gt;Book a demo&lt;/a&gt;  |  &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=124&quot;&gt;Request a quote&lt;/a&gt;&lt;/span&gt;&lt;span style=&quot;color: #aaaaaa;&quot;&gt;  |  &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=133&quot;&gt;Free trial&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/dosanddonts-logicaldoc-case-study-hero.webp&quot; alt=&quot;Dos&amp;amp;Donts and LogicalDOC case study hero image about document management and compliance&quot; width=&quot;1672&quot; height=&quot;941&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;table style=&quot;width: 100%; border-collapse: collapse; border: medium none currentcolor;&quot; border=&quot;1&quot;&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Company&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border: solid #C8D8E8 1.0pt; border-left: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;a href=&quot;https://dos-donts.com/&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Dos&amp;amp;Donts&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Sector&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Technology solutions for cleanrooms, GMP environments and controlled-contamination areas&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Size&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Italian SME specialising in solutions for controlled environments&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Role of interviewee&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Paolo Alzamira, CTO&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Main challenge&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;No version control, slow document search, no structured access control&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Deployment&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;on-premises&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 153.45pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #D6E8F7; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Key outcome&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 297.85pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;~30% time saved on document searches; manuals and software versions finally aligned&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;About Dos&amp;amp;Donts&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;Dos&amp;amp;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.&lt;/p&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The starting point: shared folders in a context that demanded more&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;For a company operating in regulated environments, this fragility quickly becomes an operational constraint.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The crux of the matter: document versioning&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“Certain issues, such as versioning – which is fundamental for us from a document management perspective – were not being addressed.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;For Dos&amp;amp;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The choice of LogicalDOC: a specialised DMS, without the burden of an enterprise management system&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;What has changed with LogicalDOC&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;Full-text search: finding the document when you need it&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“Document search and version control for the documents we manage are the main benefits we’ve gained.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;Getting started: independent implementation, without external support&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“We did it all using the published manuals.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;What we discovered whilst using it: Enterprise features that an SME can actually use&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;The fact that Dos&amp;amp;Donts is now evaluating document workflows — a feature that wasn’t part of the initial plans — highlights an important aspect of LogicalDOC.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;Key results at a glance&lt;/h2&gt;
&lt;table style=&quot;width: 100%; border-collapse: collapse; border: medium none currentcolor;&quot; border=&quot;1&quot;&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; background: #2E75B6; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: white;&quot;&gt;Area&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border: solid #C8D8E8 1.0pt; border-left: none; background: #2E75B6; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: white;&quot;&gt;Before&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border: solid #C8D8E8 1.0pt; border-left: none; background: #2E75B6; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: white;&quot;&gt;After&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Versioning&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;None. Multiple versions in circulation without control&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Every change generates a version that is tracked with the date and author&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Document search&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Manual navigation between folders, no full-text search&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Search by content across the entire archive, with results in seconds&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Manual alignment&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Frequent misalignment between software version and documentation&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Consistent versioning: the manual remains aligned with the correct version&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Access control&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Basic permissions at shared folder level&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Granular roles and permissions by user and document type&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Scalability&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Structure difficult to maintain as the archive grows&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: white; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Document workflows currently being introduced, without changing the platform&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;width: 99.3pt; border: solid #C8D8E8 1.0pt; border-top: none; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Deployment&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;Folders on a shared server&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;td style=&quot;width: 176.0pt; border-top: none; border-left: none; border-bottom: solid #C8D8E8 1.0pt; border-right: solid #C8D8E8 1.0pt; background: #F5F7FA; padding: 4.0pt 6.0pt 4.0pt 7.5pt;&quot; valign=&quot;top&quot;&gt;
&lt;p style=&quot;margin: 0;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; color: black;&quot;&gt;on-premises with direct control over data, backups and access&lt;/span&gt;&lt;/p&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;The recommendation&lt;/h2&gt;
&lt;div style=&quot;border-left: solid #2E75B6 1.75pt; padding-left: 6.0pt; margin-left: 32.0pt;&quot;&gt;
&lt;p style=&quot;margin-top: 12.0pt; margin-bottom: 4.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;color: #222222;&quot;&gt;“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.”&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin-left: 32.0pt; margin-bottom: 15.0pt;&quot;&gt;&lt;em&gt;&lt;span style=&quot;font-size: 10.0pt; color: #555555;&quot;&gt;— Paolo Alzamira, CTO&lt;/span&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;Based on Dos&amp;amp;Donts’ first-hand experience, LogicalDOC is particularly well-suited to companies that:&lt;/p&gt;
&lt;ul style=&quot;margin-left: 36.0pt;&quot;&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;manage technical documentation with multiple versions that need to be kept in line with the product&lt;/li&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;operate in regulated environments where document traceability is a requirement&lt;/li&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;are looking for a comprehensive, specialised DMS without the complexity of an enterprise suite&lt;/li&gt;
&lt;li style=&quot;margin-top: 3.0pt; margin-bottom: 3.0pt;&quot;&gt;want to start with basic document management, knowing that advanced features will be available when the organisation is ready to use them&lt;/li&gt;
&lt;/ul&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;About Dos&amp;amp;Donts&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;Dos&amp;amp;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.&lt;/p&gt;
&lt;div style=&quot;border-bottom: solid #DDDDDD 1.0pt; margin: 12.0pt 0;&quot;&gt; &lt;/div&gt;
&lt;h2 style=&quot;font-size: 14pt; color: #1a4f8a; margin-top: 24pt; margin-bottom: 8pt;&quot;&gt;About LogicalDOC&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 9pt;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: center; margin-top: 10.0pt;&quot;&gt;&lt;span style=&quot;color: #aaaaaa;&quot;&gt;&lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=426&quot;&gt;Book a demo&lt;/a&gt;  |  &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=124&quot;&gt;Request a quote&lt;/a&gt;&lt;/span&gt;&lt;span style=&quot;color: #aaaaaa;&quot;&gt;  |  &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=133&quot;&gt;Free trial&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>Document Management System Software That Scales</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/663-document-management-system-software-that-scales"/>
		<published>2026-08-10T10:25:40+00:00</published>
		<updated>2026-08-10T10:25:40+00:00</updated>
		<id>https://www.logicaldoc.com/blog/663-document-management-system-software-that-scales</id>
		<author>
			<name>Alessandro</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/document-management-system-software-that-scales.webp&quot; alt=&quot;Document management system connecting digital files, cloud storage and paper documents&quot; width=&quot;1536&quot; height=&quot;1024&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;What document management system software should deliver&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&quot;Split your metadata from your files, and suddenly your sluggish document system becomes fast, scalable and surprisingly cheap to run.&quot; &lt;br&gt;&lt;a href=&quot;https://www.infoworld.com/article/4092063/building-a-scalable-document-management-system-lessons-from-separating-metadata-and-content.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Prasanna Kumar Ramachandran - InforWorld&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;The operational cost of unmanaged documents&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;How a scalable DMS supports business growth&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/scalable-dms-vs-shared-drives-business-growth.png&quot; alt=&quot;Scalable document management chart showing how shared drives increase operational complexity faster than a centralized DMS as a business grows&quot; width=&quot;1491&quot; height=&quot;1055&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/scalable-dms-vs-shared-drives-business-growth.png&quot;&gt;&lt;/p&gt;
&lt;h2&gt;Capabilities that make a measurable difference&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Central access without losing structure&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;Moving from shared drives to a centralized DMS helps organizations scale document access without losing control, structure or governance&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/shared-drives-vs-dms.png&quot; alt=&quot;Shared drives vs centralized document management system repository: comparison of version control, permissions, workflows and audit trails.&quot; width=&quot;1491&quot; height=&quot;1055&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/shared-drives-vs-dms.png&quot;&gt;&lt;/p&gt;
&lt;h3&gt;Search that works with real business language&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/index.php?option=com_content&amp;amp;view=article&amp;amp;id=220&amp;amp;catid=98&quot;&gt;Full-text indexing&lt;/a&gt; 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.&lt;/p&gt;
&lt;h3&gt;Version control and workflow automation&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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. &lt;a href=&quot;https://www.logicaldoc.com/index.php?option=com_content&amp;amp;view=article&amp;amp;id=217&amp;amp;catid=98&quot;&gt;Version Control&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;Workflow before and after with a scalable DMS&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/workflow-before-after-scalable-dms.png&quot; alt=&quot;Workflow before and after showing how a scalable DMS replaces email attachments with version control, workflow automation and audit trail&quot; width=&quot;1491&quot; height=&quot;1055&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/workflow-before-after-scalable-dms.png&quot;&gt;&lt;/p&gt;
&lt;h3&gt;Security, records and accountability&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;How to choose the right system&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Consider the full operating model. &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=130&quot;&gt;Cloud deployment&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Plan implementation around adoption, not migration alone&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Measure the improvement&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/document-management-system-software-that-scales.webp&quot; alt=&quot;Document management system connecting digital files, cloud storage and paper documents&quot; width=&quot;1536&quot; height=&quot;1024&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;What document management system software should deliver&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&quot;Split your metadata from your files, and suddenly your sluggish document system becomes fast, scalable and surprisingly cheap to run.&quot; &lt;br&gt;&lt;a href=&quot;https://www.infoworld.com/article/4092063/building-a-scalable-document-management-system-lessons-from-separating-metadata-and-content.html&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Prasanna Kumar Ramachandran - InforWorld&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;The operational cost of unmanaged documents&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;How a scalable DMS supports business growth&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/scalable-dms-vs-shared-drives-business-growth.png&quot; alt=&quot;Scalable document management chart showing how shared drives increase operational complexity faster than a centralized DMS as a business grows&quot; width=&quot;1491&quot; height=&quot;1055&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/scalable-dms-vs-shared-drives-business-growth.png&quot;&gt;&lt;/p&gt;
&lt;h2&gt;Capabilities that make a measurable difference&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3&gt;Central access without losing structure&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;Moving from shared drives to a centralized DMS helps organizations scale document access without losing control, structure or governance&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/shared-drives-vs-dms.png&quot; alt=&quot;Shared drives vs centralized document management system repository: comparison of version control, permissions, workflows and audit trails.&quot; width=&quot;1491&quot; height=&quot;1055&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/shared-drives-vs-dms.png&quot;&gt;&lt;/p&gt;
&lt;h3&gt;Search that works with real business language&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;https://www.logicaldoc.com/index.php?option=com_content&amp;amp;view=article&amp;amp;id=220&amp;amp;catid=98&quot;&gt;Full-text indexing&lt;/a&gt; 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.&lt;/p&gt;
&lt;h3&gt;Version control and workflow automation&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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. &lt;a href=&quot;https://www.logicaldoc.com/index.php?option=com_content&amp;amp;view=article&amp;amp;id=217&amp;amp;catid=98&quot;&gt;Version Control&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;&lt;img title=&quot;Workflow before and after with a scalable DMS&quot; src=&quot;https://www.logicaldoc.com/images/blog2026/workflow-before-after-scalable-dms.png&quot; alt=&quot;Workflow before and after showing how a scalable DMS replaces email attachments with version control, workflow automation and audit trail&quot; width=&quot;1491&quot; height=&quot;1055&quot; loading=&quot;lazy&quot; data-path=&quot;local-images:/blog2026/workflow-before-after-scalable-dms.png&quot;&gt;&lt;/p&gt;
&lt;h3&gt;Security, records and accountability&lt;/h3&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;How to choose the right system&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Consider the full operating model. &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=130&quot;&gt;Cloud deployment&lt;/a&gt; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Plan implementation around adoption, not migration alone&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h2&gt;Measure the improvement&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>Why Agentic AI Fails Without Document Governance </title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/661-why-agentic-ai-fails-without-document-governance"/>
		<published>2026-07-17T08:20:57+00:00</published>
		<updated>2026-07-17T08:20:57+00:00</updated>
		<id>https://www.logicaldoc.com/blog/661-why-agentic-ai-fails-without-document-governance</id>
		<author>
			<name>Luca</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;&quot;&gt;&lt;/p&gt;&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;But there's a question that's asked much less frequently, yet it should be the first one: &lt;strong&gt;Is your company really ready to entrust its information assets to an AI agent?&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The success of Agentic AI depends not only on the &lt;a href=&quot;https://www.logicaldoc.com/software-features/artificial-intelligence&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;intelligence of the model&lt;/a&gt; used but also on the quality of the information the agent will work with.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Beyond Chatbots: Understanding Agentic AI&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Unlike traditional chatbots or the more recent AI Copilots, an Agentic AI system doesn't simply answer a question.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In other words, it's not just an assistant, but a true digital collaborator.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The introduction of this technology raises an often overlooked issue: &lt;strong&gt;document management.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The challenge is understanding where they'll find this information and how much they can trust it.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;The real obstacle isn't AI. It's the document heritage.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Many organizations imagine they can quickly introduce Agentic AI by connecting a linguistic model to their archives.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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 &lt;a href=&quot;https://www.logicaldoc.com/software-features/ocr-optical-character-recognition&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;OCR&lt;/a&gt;; files simultaneously saved on file servers, SharePoint, NAS, local folders, and cloud services; inconsistent permissions; information lacking metadata.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In such a scenario, even the best AI agent in the world will inevitably produce unreliable results.&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;The principle is always the same: &lt;span style=&quot;font-size: 18px;&quot;&gt;&lt;strong&gt;Garbage In, Garbage Out.&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Errors aren't confined to a single response; they can ripple throughout the entire business process. If we're unable to provide accurate information, &lt;a href=&quot;https://www.nist.gov/itl/ai-risk-management-framework&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;artificial intelligence doesn't eliminate clutter&lt;/a&gt;; it simply makes it faster.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Before building intelligent agents, we need to build a reliable information asset. In other words, &lt;strong&gt;before Agentic AI, we need true Information Governance.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Why an AI Agent Needs a &quot;Single Source of Truth&quot;&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Every intelligent agent must be able to know which document represents the official version.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This means having a &lt;strong&gt;Single Source of Truth&lt;/strong&gt;: a single, reliable reference point for all corporate information.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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. &lt;a href=&quot;https://www.logicaldoc.com/solutions/knowledge-management&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Learn more about Knowledge Mangement&lt;/a&gt;&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;The New Role of Document Management&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;A modern&lt;a href=&quot;https://www.logicaldoc.com/product/overview&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt; Document Management System&lt;/a&gt; can no longer be a simple electronic archive; it must become the reference point for the entire corporate information asset.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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 &lt;strong&gt;AI knowledge layers&lt;/strong&gt;, managing the context that will allow agents to understand documents, relationships, procedures, authorizations, and processes.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Conclusions&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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?&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This is precisely where a document management system like &lt;a href=&quot;https://www.logicaldoc.com/try&quot;&gt;LogicalDOC&lt;/a&gt; takes on a new strategic role.&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/&quot; alt=&quot;&quot;&gt;&lt;/p&gt;&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;But there's a question that's asked much less frequently, yet it should be the first one: &lt;strong&gt;Is your company really ready to entrust its information assets to an AI agent?&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The success of Agentic AI depends not only on the &lt;a href=&quot;https://www.logicaldoc.com/software-features/artificial-intelligence&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;intelligence of the model&lt;/a&gt; used but also on the quality of the information the agent will work with.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Beyond Chatbots: Understanding Agentic AI&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Unlike traditional chatbots or the more recent AI Copilots, an Agentic AI system doesn't simply answer a question.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In other words, it's not just an assistant, but a true digital collaborator.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The introduction of this technology raises an often overlooked issue: &lt;strong&gt;document management.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;The challenge is understanding where they'll find this information and how much they can trust it.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;The real obstacle isn't AI. It's the document heritage.&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Many organizations imagine they can quickly introduce Agentic AI by connecting a linguistic model to their archives.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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 &lt;a href=&quot;https://www.logicaldoc.com/software-features/ocr-optical-character-recognition&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;OCR&lt;/a&gt;; files simultaneously saved on file servers, SharePoint, NAS, local folders, and cloud services; inconsistent permissions; information lacking metadata.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;In such a scenario, even the best AI agent in the world will inevitably produce unreliable results.&lt;/p&gt;
&lt;p style=&quot;text-align: center;&quot;&gt;The principle is always the same: &lt;span style=&quot;font-size: 18px;&quot;&gt;&lt;strong&gt;Garbage In, Garbage Out.&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Errors aren't confined to a single response; they can ripple throughout the entire business process. If we're unable to provide accurate information, &lt;a href=&quot;https://www.nist.gov/itl/ai-risk-management-framework&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;artificial intelligence doesn't eliminate clutter&lt;/a&gt;; it simply makes it faster.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Before building intelligent agents, we need to build a reliable information asset. In other words, &lt;strong&gt;before Agentic AI, we need true Information Governance.&lt;/strong&gt;&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Why an AI Agent Needs a &quot;Single Source of Truth&quot;&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;Every intelligent agent must be able to know which document represents the official version.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This means having a &lt;strong&gt;Single Source of Truth&lt;/strong&gt;: a single, reliable reference point for all corporate information.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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. &lt;a href=&quot;https://www.logicaldoc.com/solutions/knowledge-management&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;Learn more about Knowledge Mangement&lt;/a&gt;&lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;The New Role of Document Management&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;A modern&lt;a href=&quot;https://www.logicaldoc.com/product/overview&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt; Document Management System&lt;/a&gt; can no longer be a simple electronic archive; it must become the reference point for the entire corporate information asset.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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 &lt;strong&gt;AI knowledge layers&lt;/strong&gt;, managing the context that will allow agents to understand documents, relationships, procedures, authorizations, and processes.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt; &lt;/p&gt;
&lt;h2 style=&quot;text-align: justify;&quot;&gt;Conclusions&lt;/h2&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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?&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;text-align: justify;&quot;&gt;This is precisely where a document management system like &lt;a href=&quot;https://www.logicaldoc.com/try&quot;&gt;LogicalDOC&lt;/a&gt; takes on a new strategic role.&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
	<entry>
		<title>How Lesepidado Eliminated One Man-Week per Month by Digitizing Nearly 200,000 Production Sheets with LogicalDOC</title>
		<link rel="alternate" type="text/html" href="https://www.logicaldoc.com/blog/660-lesepidado-logicaldoc-case-study"/>
		<published>2026-07-07T07:40:53+00:00</published>
		<updated>2026-07-07T07:40:53+00:00</updated>
		<id>https://www.logicaldoc.com/blog/660-lesepidado-logicaldoc-case-study</id>
		<author>
			<name>Alessandro</name>
		</author>
		<summary type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/logicaldoc-lesepidado-case-study.png&quot; alt=&quot;An industrial food printer in a professional bakery kitchen printing the LogicalDOC and Lesepidado logos on a large white sheet, with a decorated three-tier cake in the foreground showcasing both company logos.&quot; width=&quot;1376&quot; height=&quot;768&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The turning point came with the introduction of LogicalDOC, now used as the central, secure system for &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=206&quot;&gt;automating document workflows&lt;/a&gt; and managing company compliance.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Lesepidado at a Glance&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;table style=&quot;border-collapse: collapse; width: 100%; border-width: 1px; border-spacing: 6px;&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Company&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Lesepidado Srl&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Industry&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Food-grade chemicals (colorants, edible inks, and food printers)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Headquarters&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Castel San Pietro Terme (Bologna), Italy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Employees&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;80–100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;System users&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;16 active licenses, approx. 20 users&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Daily output&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;140–160 production sheets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Documents digitized&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Nearly 200,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Quality certification&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;BRC (British Retail Consortium)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Interviewee&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;IT Systems Administrator and in-house developer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Chosen DMS&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;LogicalDOC (on-premise)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;What Challenges Did Lesepidado Face Before LogicalDOC?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;table style=&quot;border-collapse: collapse; width: 100%; border-width: 1px; border-spacing: 5px;&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 5px;&quot;&gt;&lt;strong&gt;Challenge&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 5px;&quot;&gt;&lt;strong&gt;Impact&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;140–160 paper production sheets per day&lt;/td&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;One man-week per month dedicated solely to orderly archiving&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Manual searches in physical archives&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Slow, cumbersome retrieval during audits, non-conformities, or recalls&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Handwritten notes not indexed&lt;/td&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Quality-control information remained isolated on the paper sheet&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Bulky paper archives&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Cabinets and physical storage space constantly growing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Disorganized shared folders&lt;/td&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Supporting documentation (contracts, supplier certificates) scattered and unstructured&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p style=&quot;margin-top: 8.0pt;&quot;&gt; &lt;/p&gt;
&lt;div style=&quot;mso-element: para-border-div; border: none; border-left: solid #2E75B6 2.25pt; padding: 0cm 0cm 0cm 12.0pt; margin-left: 24.0pt; margin-right: 0cm;&quot;&gt;
&lt;p style=&quot;margin-bottom: 2.0pt; border: none; mso-border-left-alt: solid #2E75B6 2.25pt; padding: 0cm; mso-padding-alt: 0cm 0cm 0cm 12.0pt;&quot;&gt;&lt;em&gt;“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.”&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin: 0cm 0cm 8.0pt 24.0pt;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; line-height: 115%; color: #595959;&quot;&gt;Stefano Cassanelli — IT Systems Administrator, Lesepidado&lt;/span&gt;&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Why Did Lesepidado Choose LogicalDOC as Its Document Management System?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;1. An Open, Flexible, and Customizable System&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;mso-element: para-border-div; border: none; border-left: solid #2E75B6 2.25pt; padding: 0cm 0cm 0cm 12.0pt; margin-left: 24.0pt; margin-right: 0cm;&quot;&gt;
&lt;p style=&quot;margin-bottom: 2.0pt; border: none; mso-border-left-alt: solid #2E75B6 2.25pt; padding: 0cm; mso-padding-alt: 0cm 0cm 0cm 12.0pt;&quot;&gt;&lt;em&gt;“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.”&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin: 0cm 0cm 8.0pt 24.0pt;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; line-height: 115%; color: #595959;&quot;&gt;Stefano Cassanelli — IT Systems Administrator, Lesepidado&lt;/span&gt;&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;2. On-Premise Deployment to Protect the Recipes&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;Lesepidado deliberately opted for an &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1928&quot;&gt;on-premise installation&lt;/a&gt;. 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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;3. Ease of Use and Complete Documentation&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;How Does Lesepidado Use LogicalDOC Across the Organization?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;Today LogicalDOC manages an impressive historical archive, with nearly 200,000 digitized and indexed documents. The main use cases include:&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Automated Production Sheet Processing&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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 &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=197&quot;&gt;barcode reader&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;and &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1038&quot;&gt;zonal OCR&lt;/a&gt;. LogicalDOC then &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=172&quot;&gt;monitors the destination folder&lt;/a&gt;, automatically picks up the files, and loads them into the system, making them immediately available and searchable.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;&lt;strong&gt;Result: &lt;/strong&gt;the man-week per month previously dedicated to manual archiving has been completely eliminated.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Quality Department and Supplier Certificates&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Automated Expiration Tracking and Excel Reports&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Automatic Reorganization of Nearly 200,000 Documents&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Company Contract Management&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Before and After: The Transformation of Document Management&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;table style=&quot;border-collapse: collapse; border-width: 1px; border-spacing: 6px; width: 100%;&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 6px;&quot;&gt;&lt;strong&gt;Area&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 6px;&quot;&gt;&lt;strong&gt;Before&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 6px;&quot;&gt;&lt;strong&gt;After (LogicalDOC)&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Sheet archiving&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Paper-based, manual: 1 man-week per month&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Eliminated: scanning and automatic import&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Search for BRC audits&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Slow, dependent on the accuracy of the physical archive&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Immediate: by sheet number, batch, or metadata&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Search technology&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;None: only visual inspection of paper sheets&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Full-text with OCR, including document contents and batch numbers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Physical space&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Cabinets and archives constantly growing&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Paper destroyed one week after scanning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Expiration monitoring&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Periodic manual checks on certificates&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Automatic expiration tracking with Excel reports&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;IT integration&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Closed system, paid customizations&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Open database, in-house scripts and integrations&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;What Results Has Lesepidado Achieved with LogicalDOC?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;A net saving of one man-week per month: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;the production employee previously dedicated to physically sorting the sheets has been completely freed from this task.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;Faster, stress-free BRC audits: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;during inspections, retrieving production sheets and the associated batches takes just moments, in full compliance with traceability time constraints.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;Advanced &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=205&quot;&gt;OCR indexing&lt;/a&gt;&lt;/span&gt;&lt;/strong&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;Elimination of physical archives: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;once digitized, the paper sheets are destroyed after one week, freeing up the cabinets previously used for storage.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;An autonomous IT team: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;margin-top: 6.0pt;&quot;&gt; &lt;/p&gt;
&lt;div style=&quot;mso-element: para-border-div; border: none; border-left: solid #2E75B6 2.25pt; padding: 0cm 0cm 0cm 12.0pt; margin-left: 24.0pt; margin-right: 0cm;&quot;&gt;
&lt;p style=&quot;margin-bottom: 2.0pt; border: none; mso-border-left-alt: solid #2E75B6 2.25pt; padding: 0cm; mso-padding-alt: 0cm 0cm 0cm 12.0pt;&quot;&gt;&lt;em&gt;“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.”&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin: 0cm 0cm 8.0pt 24.0pt;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; line-height: 115%; color: #595959;&quot;&gt;Stefano Cassanelli— IT Systems Administrator, Lesepidado&lt;/span&gt;&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;About Lesepidado&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;Founded in 1999 with the idea of applying ink-jet printing to the food world, &lt;a href=&quot;https://www.lesepidado.it&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&lt;span style=&quot;color: #0563c1;&quot;&gt;Lesepidado Srl&lt;/span&gt;&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #c05600;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;About LogicalDOC&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;LogicalDOC is a &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1735&quot;&gt;document management system&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;founded in 2006 by Marco Meschieri and Alessandro Gasparini. Available both in the cloud and on-premise, the platform offers &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=177&quot;&gt;full-text search&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;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. &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=133&quot;&gt;Request a free trial&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;to see it in action.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Frequently Asked Questions&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;[widgetkit id=&quot;74&quot;]&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Related Articles&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p class=&quot;MsoNormal&quot; style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;a href=&quot;https://www.logicaldoc.com/index.php?option=com_content&amp;amp;view=article&amp;amp;id=657&amp;amp;catid=187&quot;&gt;How Kugler GmbH Managed 171,800 Files Using LogicalDOC&lt;/a&gt;&lt;/p&gt;</summary>
		<content type="html">&lt;p&gt;&lt;img src=&quot;https://www.logicaldoc.com/images/blog2026/logicaldoc-lesepidado-case-study.png&quot; alt=&quot;An industrial food printer in a professional bakery kitchen printing the LogicalDOC and Lesepidado logos on a large white sheet, with a decorated three-tier cake in the foreground showcasing both company logos.&quot; width=&quot;1376&quot; height=&quot;768&quot; loading=&quot;lazy&quot;&gt;&lt;/p&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The turning point came with the introduction of LogicalDOC, now used as the central, secure system for &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=206&quot;&gt;automating document workflows&lt;/a&gt; and managing company compliance.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Lesepidado at a Glance&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;table style=&quot;border-collapse: collapse; width: 100%; border-width: 1px; border-spacing: 6px;&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Company&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Lesepidado Srl&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Industry&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Food-grade chemicals (colorants, edible inks, and food printers)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Headquarters&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Castel San Pietro Terme (Bologna), Italy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Employees&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;80–100&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;System users&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;16 active licenses, approx. 20 users&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Daily output&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;140–160 production sheets&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Documents digitized&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Nearly 200,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Quality certification&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;BRC (British Retail Consortium)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Interviewee&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;IT Systems Administrator and in-house developer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Chosen DMS&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;LogicalDOC (on-premise)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;What Challenges Did Lesepidado Face Before LogicalDOC?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;table style=&quot;border-collapse: collapse; width: 100%; border-width: 1px; border-spacing: 5px;&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 5px;&quot;&gt;&lt;strong&gt;Challenge&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 5px;&quot;&gt;&lt;strong&gt;Impact&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;140–160 paper production sheets per day&lt;/td&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;One man-week per month dedicated solely to orderly archiving&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Manual searches in physical archives&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Slow, cumbersome retrieval during audits, non-conformities, or recalls&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Handwritten notes not indexed&lt;/td&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Quality-control information remained isolated on the paper sheet&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Bulky paper archives&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 5px;&quot;&gt;Cabinets and physical storage space constantly growing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Disorganized shared folders&lt;/td&gt;
&lt;td style=&quot;padding: 5px;&quot;&gt;Supporting documentation (contracts, supplier certificates) scattered and unstructured&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;p style=&quot;margin-top: 8.0pt;&quot;&gt; &lt;/p&gt;
&lt;div style=&quot;mso-element: para-border-div; border: none; border-left: solid #2E75B6 2.25pt; padding: 0cm 0cm 0cm 12.0pt; margin-left: 24.0pt; margin-right: 0cm;&quot;&gt;
&lt;p style=&quot;margin-bottom: 2.0pt; border: none; mso-border-left-alt: solid #2E75B6 2.25pt; padding: 0cm; mso-padding-alt: 0cm 0cm 0cm 12.0pt;&quot;&gt;&lt;em&gt;“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.”&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin: 0cm 0cm 8.0pt 24.0pt;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; line-height: 115%; color: #595959;&quot;&gt;Stefano Cassanelli — IT Systems Administrator, Lesepidado&lt;/span&gt;&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Why Did Lesepidado Choose LogicalDOC as Its Document Management System?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;1. An Open, Flexible, and Customizable System&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;div style=&quot;mso-element: para-border-div; border: none; border-left: solid #2E75B6 2.25pt; padding: 0cm 0cm 0cm 12.0pt; margin-left: 24.0pt; margin-right: 0cm;&quot;&gt;
&lt;p style=&quot;margin-bottom: 2.0pt; border: none; mso-border-left-alt: solid #2E75B6 2.25pt; padding: 0cm; mso-padding-alt: 0cm 0cm 0cm 12.0pt;&quot;&gt;&lt;em&gt;“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.”&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin: 0cm 0cm 8.0pt 24.0pt;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; line-height: 115%; color: #595959;&quot;&gt;Stefano Cassanelli — IT Systems Administrator, Lesepidado&lt;/span&gt;&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;2. On-Premise Deployment to Protect the Recipes&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;Lesepidado deliberately opted for an &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1928&quot;&gt;on-premise installation&lt;/a&gt;. 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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;3. Ease of Use and Complete Documentation&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;How Does Lesepidado Use LogicalDOC Across the Organization?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;Today LogicalDOC manages an impressive historical archive, with nearly 200,000 digitized and indexed documents. The main use cases include:&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Automated Production Sheet Processing&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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 &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=197&quot;&gt;barcode reader&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;and &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1038&quot;&gt;zonal OCR&lt;/a&gt;. LogicalDOC then &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=172&quot;&gt;monitors the destination folder&lt;/a&gt;, automatically picks up the files, and loads them into the system, making them immediately available and searchable.&lt;/p&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;&lt;strong&gt;Result: &lt;/strong&gt;the man-week per month previously dedicated to manual archiving has been completely eliminated.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Quality Department and Supplier Certificates&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Automated Expiration Tracking and Excel Reports&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Automatic Reorganization of Nearly 200,000 Documents&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h3 style=&quot;margin: 12.0pt 0cm 5.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #2e75b6;&quot;&gt;Company Contract Management&lt;/span&gt;&lt;/strong&gt;&lt;/h3&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Before and After: The Transformation of Document Management&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;table style=&quot;border-collapse: collapse; border-width: 1px; border-spacing: 6px; width: 100%;&quot; border=&quot;1&quot; cellspacing=&quot;0&quot; cellpadding=&quot;5&quot;&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 6px;&quot;&gt;&lt;strong&gt;Area&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 6px;&quot;&gt;&lt;strong&gt;Before&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #1f4e79; color: white; padding: 6px;&quot;&gt;&lt;strong&gt;After (LogicalDOC)&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Sheet archiving&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Paper-based, manual: 1 man-week per month&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Eliminated: scanning and automatic import&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Search for BRC audits&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Slow, dependent on the accuracy of the physical archive&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Immediate: by sheet number, batch, or metadata&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Search technology&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;None: only visual inspection of paper sheets&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Full-text with OCR, including document contents and batch numbers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;Physical space&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Cabinets and archives constantly growing&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Paper destroyed one week after scanning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;&lt;strong&gt;Expiration monitoring&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Periodic manual checks on certificates&lt;/td&gt;
&lt;td style=&quot;padding: 6px;&quot;&gt;Automatic expiration tracking with Excel reports&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;&lt;strong&gt;IT integration&lt;/strong&gt;&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Closed system, paid customizations&lt;/td&gt;
&lt;td style=&quot;background: #f2f2f2; padding: 6px;&quot;&gt;Open database, in-house scripts and integrations&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;What Results Has Lesepidado Achieved with LogicalDOC?&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;A net saving of one man-week per month: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;the production employee previously dedicated to physically sorting the sheets has been completely freed from this task.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;Faster, stress-free BRC audits: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;during inspections, retrieving production sheets and the associated batches takes just moments, in full compliance with traceability time constraints.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;Advanced &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=205&quot;&gt;OCR indexing&lt;/a&gt;&lt;/span&gt;&lt;/strong&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;Elimination of physical archives: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;once digitized, the paper sheets are destroyed after one week, freeing up the cabinets previously used for storage.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;!--[endif]--&gt;&lt;strong&gt;&lt;span style=&quot;color: black;&quot;&gt;An autonomous IT team: &lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color: black;&quot;&gt;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.&lt;/span&gt;&lt;/p&gt;
&lt;p style=&quot;margin-top: 6.0pt;&quot;&gt; &lt;/p&gt;
&lt;div style=&quot;mso-element: para-border-div; border: none; border-left: solid #2E75B6 2.25pt; padding: 0cm 0cm 0cm 12.0pt; margin-left: 24.0pt; margin-right: 0cm;&quot;&gt;
&lt;p style=&quot;margin-bottom: 2.0pt; border: none; mso-border-left-alt: solid #2E75B6 2.25pt; padding: 0cm; mso-padding-alt: 0cm 0cm 0cm 12.0pt;&quot;&gt;&lt;em&gt;“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.”&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;p style=&quot;margin: 0cm 0cm 8.0pt 24.0pt;&quot;&gt;&lt;span style=&quot;font-size: 10.0pt; line-height: 115%; color: #595959;&quot;&gt;Stefano Cassanelli— IT Systems Administrator, Lesepidado&lt;/span&gt;&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;About Lesepidado&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;Founded in 1999 with the idea of applying ink-jet printing to the food world, &lt;a href=&quot;https://www.lesepidado.it&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot;&gt;&lt;span style=&quot;color: #0563c1;&quot;&gt;Lesepidado Srl&lt;/span&gt;&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #c05600;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;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.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;About LogicalDOC&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p style=&quot;margin-bottom: 7.0pt; text-align: justify;&quot;&gt;LogicalDOC is a &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=1735&quot;&gt;document management system&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;founded in 2006 by Marco Meschieri and Alessandro Gasparini. Available both in the cloud and on-premise, the platform offers &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=177&quot;&gt;full-text search&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;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. &lt;a href=&quot;https://www.logicaldoc.com/index.php?Itemid=133&quot;&gt;Request a free trial&lt;/a&gt;&lt;strong&gt;&lt;span style=&quot;font-size: 7.5pt; line-height: 115%; color: #2e7d32;&quot;&gt; &lt;/span&gt;&lt;/strong&gt;to see it in action.&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Frequently Asked Questions&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p&gt;[widgetkit id=&quot;74&quot;]&lt;/p&gt;
&lt;h2 style=&quot;margin: 16.0pt 0cm 7.0pt 0cm;&quot;&gt;&lt;strong&gt;&lt;span style=&quot;color: #1f4e79;&quot;&gt;Related Articles&lt;/span&gt;&lt;/strong&gt;&lt;/h2&gt;
&lt;p class=&quot;MsoNormal&quot; style=&quot;text-indent: -18.0pt; mso-list: l0 level1 lfo1; border: none; mso-padding-alt: 31.0pt 31.0pt 31.0pt 31.0pt; mso-border-shadow: yes; margin: 0cm 0cm 3.0pt 36.0pt;&quot;&gt;&lt;!-- [if !supportLists]--&gt;&lt;span style=&quot;mso-list: Ignore;&quot;&gt;•&lt;span style=&quot;font: 7.0pt 'Times New Roman';&quot;&gt;         &lt;/span&gt;&lt;/span&gt;&lt;a href=&quot;https://www.logicaldoc.com/index.php?option=com_content&amp;amp;view=article&amp;amp;id=657&amp;amp;catid=187&quot;&gt;How Kugler GmbH Managed 171,800 Files Using LogicalDOC&lt;/a&gt;&lt;/p&gt;</content>
		<category term="Blog" />
	</entry>
</feed>
