Zum Inhalt springen

Digital project file: all project documents in one file, external partners included

A digital project file brings together all documents, emails, drawings and photos of a project in one central electronic file that the whole team uses in the office, on the move and together with external partners.

AWP Consult implements the project file with enaio as a certified enaio partner. The file combines filing structure, versioning, permissions and workflows and can be connected to your ERP or merchandise management system. This way, project managers, specialist departments and partners all work with the same status.

250+
completed projects since 2006
150+
reference customers in the DACH region
12 to 18
months average payback
Project file: new warehouse
  • 01 Order
  • Quotation.pdf
  • Change order 2.pdfnew
  • 02 Planning
  • Ground floor plan.dwgv4 valid
  • 03 Correspondence12
  • 04 Site86 photos
  • 05 Partner uploadsnew
  • 06 Invoicing

Key facts at a glance

01

A digital project file is the central electronic file of a project that bundles contracts, drawings, minutes, emails, photos and invoices according to a fixed filing plan, versions them and protects them with access rights.

02

In the project file, only the most recently approved revision of a drawing is valid. Interim versions remain internal, and superseded revisions are marked as invalid and remain retrievable as evidence.

03

For buildings, defect claims become time-barred under Section 634a of the German Civil Code (BGB) five years after acceptance, or after four years where the German construction contract rules (VOB/B) have been agreed without a different provision. The acceptance date therefore belongs in the file as a mandatory field.

04

Under Section 147 of the German Fiscal Code (AO), invoices and other accounting records must generally be retained for eight years, and commercial and business letters for six years. The project file follows the longest retention period it contains.

05

Planning offices often structure project files by the nine work stages that Section 34 of the German fee structure for architects and engineers (HOAI) defines for buildings and interiors.

06

AWP Consult implements the digital project file with enaio, with Outlook filing, mobile access on the construction site and the AWP Link and Upload Portal for external partners without an enaio licence.

Prefer to talk it through rather than read on?

Request a callback +49 6104 94738-13

What is a project file?

A project file is the complete documentation of a project, organised according to a fixed scheme, with contracts, planning documents, minutes, correspondence, acceptances and invoicing. It proves what was agreed, planned, carried out and invoiced in the project and remains available for warranty claims and audits even after the project has ended. On paper, it was one binder per project. Today, the same information is usually scattered across network drives, email inboxes and smartphones.

The digital project file, often also called an electronic project file, brings these sources back together. It is built on a fixed scheme, identical in every project, and shows all parties exactly the documents they need.

Scattered storage becomes one file Network drive Inbox Smartphone Project file Central Traceable Shared

Central storage

All project-related data and documents in one place, retrievable at any time and from anywhere. No more searching through folders, drives and inboxes.

Traceability

Who changed which drawing when, and who made which decision? The file shows the complete history in an audit-proof way.

Collaboration

Project team, specialist departments, customers and suppliers work on a common basis, even across company boundaries.

What would your project file look like?

We look at two or three typical projects with you and outline which sections, metadata and permissions your project file needs.

Network drive or digital project file: what is the difference in day-to-day project work?

The difference between a network drive and a digital project file is that the project file clearly marks valid versions, captures emails and partner documents with metadata, limits access in time and keeps knowledge with the project rather than with individuals, whereas the network drive only stores files in folders. Many companies already have a folder structure per project on the network drive. The difference from a project file becomes apparent as soon as several people, partners and versions are involved.

Folders on the drive or a project file Network drive Project file New drawing version plan_final.pdf plan_final_v2.pdf final_v2_new.pdf ? Rev. a Rev. b Rev. c valid Email in the inbox in the file Partner third-party services Link with expiry Staff change knowledge leaves stays in the project Years later Searching folders Full-text search
Situation Network drive and inbox Digital project file in enaio
New drawing version Files with names like final_v2_new, unclear which one is valid New version, the valid status is unambiguous
Email with attachment Stays in the inbox of the person who received it Is stored in the project file with metadata
External partner Attachments by email, large files via third-party services Sharing by link and password with a validity period
Staff turnover Knowledge and files leave with the person File, history and tasks stay in the project
Query years later Searching archive folders and old inboxes Full-text search by project number, customer or content

Not sure where to start? We will assess your starting point with you.

What belongs in a digital project file?

A digital project file should contain all documents that record a project from enquiry to warranty: quotation and order, contract and change orders, drawings and calculations, site diary, minutes and photos, all correspondence as well as acceptance, final invoice and warranty documents. The exact selection depends on the project type, but a basic framework applies almost everywhere. The overview shows how the contents can be organised by project phase.

Contents by project phase Quotation Enquiry Costing Contract Change orders Guarantees Planning CAD drawings Calculations Execution Site diary Photos Communication Emails Minutes Completion Acceptance Final invoice Basic framework, adapted to each project type
Project phase Typical documents What the file does
Enquiry and quotation Enquiry, bill of quantities, costing, quotation, order confirmation Link to customer and order in the ERP system
Contract Project contract, change orders, framework agreements, guarantees Deadlines and acceptance periods via follow-up reminders, linked to contract management
Planning CAD drawings, technical drawings, bills of materials, calculations, permits Versioning, valid status clearly identifiable
Execution Site diary, minutes, photos, delivery notes, notices of concern and obstruction, defect reports Capture directly on site with a timestamp
Communication Emails, meeting notes, correspondence with partners Filing directly from Outlook with metadata
Completion Acceptance report, final invoice, documentation, warranty documents Audit-proof archiving until the retention period ends

Sample structure. We define sections and document types to suit your project types during the analysis.

Sounds right for your company? Let us talk about it.

Request a consultation +49 6104 94738-13

How is a digital project file structured?

A digital project file is built from uniform sections, metadata such as project number, customer and status, a central permissions concept, project-specific workflows and audit-proof storage, and this structure is the same in every project of the same type so that everyone in the team can find every document. A project file only works if it is structured the same way in every project. That is why we define a uniform filing structure in enaio that serves as a template for every new project. The project number links the file to your ERP or merchandise management system.

This way, everyone in the team knows where a document belongs and can find it again, even in a project they were not involved in themselves.

The same structure in every project Order Planning Execution Correspondence Invoicing Project file Customer, location, manager active Project number from the ERP
Uniform sections

Every file has the same sections, such as order, planning, execution, correspondence and invoicing.

Metadata

Project number, customer, location, project manager and status make every file findable via search.

Permission management

Central permission management controls who can see and edit which sections. Costings remain internal.

Workflows

Project-specific workflows assign each step to a person, for example checking incoming invoices or approving a drawing.

Audit-proof storage

Documents are stored in a legally compliant way and according to the rules for GDPR-compliant document management, with a timestamp and unalterable.

Would you like to see this with your own documents?

Request a live demo +49 6104 94738-13

How do documents from partners, Outlook and the construction site get into the file?

Documents reach the project file in three ways: external partners upload them via the AWP Link and Upload Portal, emails are filed from Outlook with their metadata in a few clicks, and photos and minutes from the construction site are saved directly in the file with a timestamp via tablet or smartphone. A project file is only complete if the documents created outside the office also find their way in. Three channels make sure of this.

Three ways into the project file Upload portal With password Outlook Sender, date Construction site With timestamp Project file

External partners via the Link and Upload Portal

With the AWP Link and Upload Portal, you exchange documents with planners, suppliers and customers by link and password. Access has a validity period and its own permissions. External parties upload files without an enaio licence, and large files no longer clog up anyone's inbox.

AWP Link and Upload Portal

Outlook integration

You file emails and attachments from Outlook into the right project file in a few clicks. Sender, date and subject are adopted as metadata. If required, enaio archives emails from Exchange on a rule basis.

Outlook and Microsoft 365

Mobile on the construction site

Site managers and fitters access drawings, assembly instructions and wiring diagrams on the tablet. Photos of defects and construction progress are saved directly in the file with a timestamp.

Site diary and construction schedule

If your teams work in Microsoft Teams, collaboration stays there. Final versions are archived in enaio in an audit-proof way and end up in the right project file.

Do you have a specific question about your case?

Which methods keep a digital project file in order over the years?

A digital project file stays in order over the years when a flat filing plan per project type, document classes with mandatory metadata, a clear separation of version and revision, fixed review and approval processes, suitable document classes for the German VOB/B (construction contract rules) and HOAI (fee structure for architects and engineers) and a structured project close-out work together. The basic idea is simple, but the implementation is what counts. These sections describe the methods that keep a project file in order even with many parties, drawing versions and years of warranty.

Flat filing plan, clear revisions Three levels at most Project Trade Section Version or revision Rev. a Rev. b Rev. c Versions stay internal valid drawing
01

Filing plan and project structure

A filing plan defines how each project file is structured. A flat hierarchy with no more than three levels has proven effective: project, if required a sub-project, lot or trade, and below that fixed sections. Deep folder trees like those on the network drive mean that people search for the same document in several places.

  • Template per project type a construction project needs different sections from an IT or logistics project. Within a type, the structure is always the same.
  • Number range the project number comes from the ERP system and is the common link between file, order, invoices and time recording.
  • File status created, active, under warranty, closed. The status controls permissions and retention.
Practical tip

Write the filing plan with examples: which document belongs in which section? Ten borderline cases with answers help the team more than an abstract outline.

02

Metadata and document classes

Sections organise, document classes describe. A document class such as drawing, minutes, change order, inspection report or photo determines which metadata are mandatory and which workflows start. For drawings, these are typically drawing type, trade, floor or building component, scale, drawing author, revision index and drawing status.

A fixed drawing code makes file names superfluous, because all details are available as metadata. For technical drawings, ISO 7200 defines data fields for title blocks and document headers. The metadata model in the DMS can be aligned with it so that the title block and the file carry the same information.

Practical tip

Adopt metadata automatically wherever possible: project number from the file, sender and date from the email, revision index from the drawing code. Every mandatory field filled in by hand is a source of error.

03

Versioning, check-in, check-out and revisions

Version and revision are not the same thing. A version is created technically every time you save. A revision, often labelled with an index a, b, c, is a status approved on its content that is distributed to the parties involved. The file must keep the two apart: interim versions stay internal, and the approved index is the valid drawing.

Check-out locks a document so that others cannot edit it. Check-in stores the modified document as a new version, ideally with a short change note. This prevents parallel copies with different statuses. Superseded revisions are marked as invalid but remain retrievable as evidence.

In engineering, the same applies to bills of materials. A bill of materials refers to the drawing number and index. If the drawing changes, the bill of materials is checked and approved in the same change process.

What this looks like with many drawing versions in architectural and engineering offices is described on the page about CAD drawing archiving in a DMS.

Practical tip

Only allow distribution to external parties for approved revisions. Then no interim version can end up on the construction site by mistake.

04

Review and approval processes for drawings and documents

An incoming drawing passes through fixed stages. Each stage sets a status, so that you can always see where a drawing stands and who has to work on it next.

External parties receive only the rights they need for their role, and only for the duration of the project. Via the AWP Link and Upload Portal, sharing runs by link and password with a validity period, without an enaio licence for the partner.

  • Formal checkTitle block, drawing code, index and drawing list match.
  • Technical review the trades concerned review in parallel, and comments are recorded on the document.
  • ApprovalStatus approved for construction, or returned to the drawing author with conditions.
  • Distribution the approved drawing goes to the drawing distribution list, and receipt is documented.
Practical tip

Set a deadline for each review stage. A drawing that sits in technical review for two weeks is a scheduling risk and should escalate automatically.

05

Construction projects: VOB/B and HOAI in the file

Planning offices often structure project files by the work stages of the German HOAI (fee structure for architects and engineers). For buildings, Section 34 HOAI lists nine stages: basic evaluation, preliminary design, design planning, permit planning, detailed design, preparation of contract award, assistance with contract award, project supervision with site supervision and documentation, and post-completion services.

In construction contracts under the German VOB/B (construction contract rules), certain documents are of evidential importance. Concerns under Section 4(3) VOB/B and obstructions under Section 6(1) VOB/B must be notified in writing, change orders are based on Section 2(5) and (6) VOB/B, and acceptance is governed by Section 12 VOB/B. These documents belong in the file as separate document classes with proof of receipt.

For warranty, acceptance is what counts. Under Section 634a of the German Civil Code (BGB), defect claims for buildings become time-barred five years after acceptance. If the German VOB/B (construction contract rules) has been agreed and no other period has been specified, it is four years under Section 13(4) VOB/B.

Practical tip

Record the acceptance date as metadata and use it to calculate a follow-up reminder before the warranty expires. Then defects are reviewed in good time.

06

Project close-out, archiving and knowledge retention

At project close-out, the file is cleaned up and set to the status closed. Duplicate working versions are tidied up, while approved revisions, minutes, acceptances and the final invoice are retained in an audit-proof way. Write permissions end, and read permissions are reduced to the group responsible for warranty and queries.

Several clocks run side by side for retention: invoices and other accounting records generally eight years, commercial and business letters six years under Section 147 of the German Fiscal Code (AO), plus the warranty periods from acceptance. The file follows the longest period of the document classes it contains. Unalterable long-term storage is handled by audit-proof archiving software that monitors retention periods per document class.

Knowledge retention means making experience findable. A short close-out note with lessons learned, key figures from the ERP system and references to template documents is filed with metadata such as project type and industry. This way, the next team finds comparable projects via search.

Practical tip

Make the close-out note a mandatory step in the close-out workflow. Experience shows that voluntary lessons learned are rarely written.

We will show you what this looks like with enaio in your company.

Book an appointment +49 6104 94738-13
Define the filing plan and approval processes for your project types

We apply the filing plan, document classes, revisions and review processes to your projects and show you what this looks like in enaio.

Where is the digital project file used?

The digital project file is used wherever projects involve many parties, document versions and documentation obligations, above all in construction and skilled trades, engineering and planning, logistics projects and IT projects. The principle is the same everywhere, but the contents differ. Four typical fields of application:

One principle, four fields of application File Construction, trades Engineering Logistics IT projects

Construction and skilled trades

Order, drawings, site measurements, site diary, photos, acceptance and warranty. Office and construction site access the same file.

Project file for skilled trades

Engineering and planning

Drawings with revision index, bills of materials, calculations, permits, drawing approvals and change order management with a complete version history.

Architecture and engineering

Logistics projects

Tender, quotation, customer contract, process descriptions, site documents and coordination with subcontractors, for example when onboarding a new customer in contract logistics.

DMS for logistics

IT projects

Requirements specification, functional specification, quotations, contracts, concepts, test reports and acceptances. Approvals run as a workflow, and every decision is documented.

Approvals via workflow

Prefer to talk it through rather than read on?

Request a callback +49 6104 94738-13

What does a digital project file need to offer tradespeople?

Above all, a digital project file must offer tradespeople mobile access on the construction site, a simple structure that is the same in every order, archiving compliant with the German GoBD (principles for proper electronic bookkeeping), monitoring of warranty periods from acceptance, integration with the merchandise management system and operation without an in-house IT department. Trade businesses therefore have different requirements from large corporations. You should check these points when selecting project file software.

Important for warranty: for buildings, defect claims generally become time-barred under Section 634a of the German Civil Code (BGB) five years after acceptance, or after four years where the German VOB/B (construction contract rules) has been agreed without a different provision. Acceptance reports and photos should remain quickly retrievable for at least that long.

Documented on site Defect photo with timestamp Warranty from acceptance BGB 5 years VOB/B 4 years GoBD-compliant No in-house IT
Mobile use

Drawings and documents on tablet or smartphone, photos straight into the file.

Simple structure

A fixed folder logic for every order that everyone in the business understands.

GoBD-compliant

Invoices, quotations and orders archived in an audit-proof way under the German GoBD (principles for proper electronic bookkeeping), with a timestamp and unalterable, as a GoBD-compliant DMS provides.

Warranty in view

Acceptance reports and photos as evidence, deadlines with follow-up reminders.

Integration

Link to merchandise management or ERP so that order data is not entered twice.

Operation without in-house IT

Maintenance and operation by the partner, on request as enaio Cloud from German data centres.

Not sure where to start? We will assess your starting point with you.

What distinguishes a project file, a project management tool and a Common Data Environment?

A project management tool plans tasks, deadlines and resources, a Common Data Environment is used for the joint editing of models and project information in the BIM process, and the project file documents all of a project's records in an audit-proof way beyond the end of the project and the warranty period. The three tools complement each other but do not replace each other. In the BIM context, the ISO 19650 series of standards, adopted in Germany as DIN EN ISO 19650, describes information management with a shared data environment, the Common Data Environment. There, information passes through the states work in progress, shared, published and archived.

Three tools, three time horizons Project duration Handover Warranty PM tool Tasks, deadlines CDE Models, BIM Project file All documents, verifiable ISO 19650: published versions into the file
Criterion Project management tool Common Data Environment Digital project file
Purpose Plan tasks, deadlines and resources Jointly edit and exchange models and project information Keep all project documents complete and verifiable
Typical contents Tasks, milestones, workload BIM models, drawings, information containers with status Contracts, drawings, correspondence, minutes, invoices, acceptances
Time horizon Project duration Project duration, handover to operation Project duration plus retention and warranty
Strength Control Model-based collaboration Audit-proof storage, deadlines, ERP integration

A CDE under ISO 19650 and a project file in the DMS can be combined: published and archived versions are transferred into the project file.

Sounds right for your company? Let us talk about it.

Request a consultation +49 6104 94738-13

Typical mistakes when introducing a project file

We see these mistakes particularly often in projects with many drawing versions and parties involved.

01

Folder structure copied from the drive

Consequence
Deep trees, inconsistent filing, documents in several places.
Better
Flat filing plan per project type with document classes and metadata.
02

Version and revision not separated

Consequence
Interim versions reach external parties or the construction site.
Better
Only distribute approved revisions and keep interim versions internal.
03

External parties with permanent access

Consequence
Former partners can still see project documents years later.
Better
Access with a validity period and role-based permissions.
04

Emails stay in the inbox

Consequence
Agreements and commitments are missing from the file.
Better
Make filing from Outlook with metadata a fixed step in the workflow.
05

No acceptance date recorded

Consequence
Warranty periods cannot be monitored.
Better
Acceptance date as a mandatory field with a follow-up reminder before the deadline.
06

Project close-out without clean-up

Consequence
Write permissions remain open, and working versions cause confusion in later queries.
Better
Close-out workflow with status change, permission adjustment and close-out note.

Would you like to see this with your own documents?

Request a live demo +49 6104 94738-13

Checklist: project file from creation to close-out

These points ensure that every project file is complete from day one and remains findable after the project ends.

01

Project start

  • Project number adopted from the ERP system
  • File created from the project type template
  • Project manager, team and deputy entered
  • External partners authorised with role and validity period
  • Drawing code and drawing distribution list defined
02

Ongoing project

  • Emails with commitments and changes filed from Outlook
  • Only approved revisions distributed to external parties
  • Concerns, obstructions and change orders as a separate document class with proof of receipt
  • Photos and minutes with timestamp in the file
  • Review stages with deadlines and escalation
03

Project close-out

  • Acceptance date recorded and warranty period calculated
  • Working versions cleaned up, revisions complete
  • Write permissions ended, access for external parties deactivated
  • Close-out note with lessons learned filed
  • File status set to closed

Do you have a specific question about your case?

How is project file software introduced?

Project file software is introduced in four steps: analysis of project types and storage locations, definition of the filing plan, metadata, permissions and workflows, a pilot project with real documents and then a step-by-step rollout with training for project managers and key users. We introduce the digital project file in a way that does not disrupt ongoing projects. If required, we clarify beforehand how it fits into the rest of your document landscape in an enterprise content management consultation. New projects start in the new structure, and existing ones are migrated as needed.

Four steps, ongoing projects undisturbed Analysis Filing plan Pilot project Rollout New projects start fresh Existing ones as needed
01

Analysis

We record project types, parties involved, document types and existing storage locations.

02

Filing plan

Sections, metadata, permissions and workflows are defined and signed off by you.

03

Pilot project

One project team starts with the new file. The structure is tested with real documents.

04

Rollout

Further teams follow, and project managers and key users are trained.

Learn more: enaio implementation and training

How long will it take in your case? We will estimate it with you.

Request an estimate +49 6104 94738-13

Glossary: terms relating to the project file

The most important technical terms from project documentation, construction and engineering, briefly explained.

Filing plan
Binding structure of all project files of one type with sections, document classes and filing rules.
Document class
Category such as drawing, minutes or change order that determines mandatory metadata, permissions and workflows.
Revision
Status of a document approved on its content, usually marked with an index. Not every version is a revision.
Check-out and check-in
Locking a document for editing and returning it as a new version. Prevents parallel copies.
Drawing distribution list
List of recipients who receive an approved drawing, with proof of receipt.
Bill of materials
Structured list of the parts of a product that refers to the drawing number and index.
Work stages
Structure of architects' and engineers' services under the German HOAI (fee structure for architects and engineers), in nine stages for buildings.
Acceptance
Approval of the construction work by the client. It starts the limitation period for defect claims.
Common Data Environment
Shared data environment under ISO 19650 in which project information is exchanged with defined states.
Lessons learned
Documented experience from a completed project, filed so that it can be found for follow-up projects.

We will show you what this looks like with enaio in your company.

Book an appointment +49 6104 94738-13

What customers say about working with AWP Consult

Feedback from companies with document-intensive processes that use and develop enaio together with AWP Consult.

Due to document-intensive processes, we have a strong need for a reliable DMS solution. With AWP's support, we were able to master a number of challenges, including tailored interface adjustments and company-wide enaio updates. AWP's uncomplicated hands-on mentality was particularly helpful.
Labom Mess- und Regeltechnik GmbHMEASUREMENT TECHNOLOGY
With AWP, we were able to successfully modernise and further develop our enaio and continuously adapt it to our business processes and new challenges. Together we have already achieved a great deal, and we are very much looking forward to continuing our collaboration.
Noerpel SELOGISTICS
Noerpel logoDUO-Technik logoCargoLine logoKissel Spedition logoDFB logoEvangelischer Michaelshof logo
Shape your project file in a personal conversation

We discuss project types, current storage and external partners and derive an initial filing plan from this as a starting point.

  • Filing plan per project type
  • Outlook and construction site connected
  • Partners without an enaio licence
Arrange a call +49 6104 94738-13Mon to Fri 08:30 to 17:00

Sources and legal basis

The legal statements on work stages, acceptance, warranty and retention are based on the following official sources. Review date: October 2026.

  • § 34 HOAI German fee structure for architects and engineers: scope of services for buildings and interiors with nine work stages
  • § 640 BGB German Civil Code: acceptance of the work
  • § 634a BGB German Civil Code: limitation of defect claims, five years from acceptance for buildings
  • § 147 AO German Fiscal Code: retention periods for accounting records and business letters

Frequently asked questions about the digital project file

What is a digital project file?

A digital project file is the electronic collection of all documents of a project, from quotation and contract through drawings and minutes to acceptance and invoicing. It follows a fixed filing plan, is versioned and is protected by access rights. All parties work with the same status, in the office, on the move and with external partners. After the project ends, it remains archived in an audit-proof way.

What belongs in a project file?

Enquiry and quotation, contract and change orders, planning documents, execution documents such as minutes and photos, all correspondence as well as acceptance, final invoice and warranty documents. Construction projects add notices of concern and obstruction, and engineering projects add bills of materials and change processes. The exact structure depends on the project type and is defined in the filing plan.

What does a digital project file need to do for trade businesses?

It must work on mobile devices on the construction site and capture photos directly. It also needs a simple, uniform structure, archiving of invoices compliant with the German GoBD (principles for proper electronic bookkeeping) and monitoring of warranty periods from acceptance. Integration with the merchandise management system prevents duplicate data entry. Ideally, it runs without in-house IT, for example in the cloud.

How do external partners work with the project file?

Via the AWP Link and Upload Portal. You share documents by link and password, with a validity period and permissions. Partners can also upload files themselves without needing an enaio licence. It makes sense to provide external parties only with approved revisions and to end their access when the project ends.

Can I file emails from Outlook in the project file?

Yes. You file emails and attachments in the right file in a few clicks, and sender, date and subject are adopted as metadata. Rule-based archiving from Exchange is also possible. This way, commitments, change requests and approvals are stored in the file and not in individual people's inboxes.

Does the digital project file also work on the construction site?

Yes. Drawings, assembly instructions and wiring diagrams can be accessed on the tablet. Photos of defects or construction progress are saved directly in the file with a timestamp. This replaces photo collections on private smartphones and makes defects provable later.

How does the project file prevent people from working with outdated drawings?

Through versioning and a clear separation of version and revision. Every status is retained, but only the most recently approved revision is valid. Superseded drawings are marked as invalid but remain retrievable as evidence. If only the approved revision is distributed to the site and partners, no interim version goes into circulation.

What do check-in and check-out mean?

Check-out locks a document while someone is editing it. Others can see that it is being edited and cannot make changes in parallel. Check-in stores the modified document as a new version, ideally with a change note. This prevents competing copies of the same drawing or document.

Can the project file be connected to ERP or merchandise management?

Yes. enaio is connected to existing merchandise management and ERP systems, such as SAP, Microsoft Dynamics 365 or proALPHA. The project number links the file and the order. This allows invoices, purchase orders and delivery notes to be assigned to the project without entering data twice.

How long do project documents have to be retained?

Invoices and other accounting records generally eight years under Section 147 of the German Fiscal Code (AO), commercial and business letters six years. For buildings, defect claims generally become time-barred under Section 634a of the German Civil Code (BGB) five years after acceptance, or after four years for contracts under the German VOB/B (construction contract rules) without a different agreement. The project file should follow the longest of these periods.

What is the difference between a project file and a Common Data Environment?

A Common Data Environment under ISO 19650 is used for the joint editing of models and project information in the BIM process, with states such as work in progress, shared, published and archived. The project file documents all of a project's records in an audit-proof way, including contracts, correspondence and invoices. The two can be connected by transferring published and archived versions into the file.

Do I need project file software in addition to a project management tool?

Yes, because the two have different tasks. A project management tool plans tasks, deadlines and resources. The project file documents everything created in the project in an audit-proof way and remains available for warranty claims and audits after the project ends. The two complement each other: the tool steers, the file provides evidence. They can be linked via the project number.

Prefer to talk it through rather than read on?

Request a callback +49 6104 94738-13

Your projects, brought together in one file

In a conversation, we record which project types you have, where the documents are stored today and who collaborates from outside. You receive a proposal for file structure, permissions and integration.

  • In person in Dietzenbach or online
  • With project management and specialist departments
  • Result: a concrete filing plan as a starting point