An EDMS (electronic document management system) is software that stores an organization's documents in a controlled repository, tracking versions, access rights, metadata, and approval status. In architecture, engineering, and construction, an EDMS is the system of record for drawings, specifications, contracts, and correspondence across a project's life.
What an EDMS does
The core functions are consistent across vendors:
- Repository and metadata. Documents live in one indexed store, tagged by project, discipline, document type, and status, so retrieval does not depend on knowing which folder someone chose three years ago.
- Version control. Each revision is kept with its history; the current version is unambiguous, and superseded sets remain retrievable for the record.
- Access control. Permissions by role and party, which matters when owners, consultants, and contractors share one environment.
- Workflow and audit trail. Reviews, approvals, and transmittals are logged, producing the delivery evidence that disputes turn on.
EDMS in AEC specifically
Generic document management (the category built for contracts, HR files, and office records) handles files one at a time. AEC work strains that model in specific ways: drawing sets revise as coordinated packages, a single issue can involve hundreds of sheets, and the parties needing access change with every project. AEC-oriented systems add drawing-set logic, markup viewing, and issue workflows on top of the generic repository functions.
The practical failure mode in design firms is not the absence of an EDMS but the work that never enters it. Project decisions increasingly happen in email threads and meetings; if those are not filed to the record, the EDMS holds the drawings but not the reasoning behind them. This is why document control policy matters as much as the system choice.
EDMS, CDE, and PIM
Three overlapping terms, three scopes:
- An EDMS is the software category: controlled document storage and workflow, for any organization.
- A CDE (common data environment) is a project-level concept from ISO 19650: the agreed single source of information for a specific project, shared by all parties. A CDE is typically implemented on an EDMS or similar platform, but the CDE is the arrangement, the platform is the tool.
- Project information management (PIM) is the wider discipline: managing all project information, including the email, meeting, and field records that traditional document systems miss.
Related terms
- CDE: the ISO 19650 project-information arrangement an EDMS often implements.
- Document control: the discipline an EDMS supports.
- Transmittal: the issue record an EDMS automates.
- PIM: the broader project-information discipline.
Frequently asked questions
What does EDMS stand for? Electronic document management system. Some vendors and agencies use the same abbreviation for engineering document management system; the functions substantially overlap, with the engineering variant emphasizing drawing-set handling.
What is the difference between an EDMS and a CDE? An EDMS is a software category; a CDE is a project arrangement defined in ISO 19650, the agreed single source of project information shared by all parties. A project's CDE is usually implemented on an EDMS or a construction platform, but the terms name different things.
Is SharePoint an EDMS? SharePoint provides the core repository, versioning, and permission functions, and many firms use it as their EDMS. What it lacks out of the box is AEC-specific behavior: drawing-set revision logic, transmittal workflows, and markup review, which firms add through configuration or purpose-built tools.
What should a design firm look for in an EDMS? Version and set control for drawings, an audit trail strong enough to stand up in a dispute, access control that handles external parties, and a realistic path for email and meeting records to reach the project record rather than staying in inboxes.
Markdown version of this entry, for AI assistants and agents.