Choosing construction documentation software is not a decision about a tool for the next few weeks. It decides how site inspections (Begehungen), defects (Mängel), the site diary (Bautagebuch), change orders (Nachträge) and acceptances (Abnahmen) will be recorded over years, and whether that evidence will still hold up later. The choice is difficult because providers show similar feature lists and the differences only appear in daily use: without reception on site, when exporting a report, when asking where the data is stored. This guide is written for everyone who plans and builds: design firms, architectural practices, engineering firms, site management, trade contractors, construction companies and operators. It deliberately names no products. It sets out which requirements you should clarify, which criteria allow you to compare offers and which pitfalls come up again and again in practice.
Starting point: in the office and on site
The starting point is similar in many firms. Inspection reports are written in a word processor, photos sit on several phones, defect lists are kept in spreadsheets, the site diary is on paper or in a notes app, the fee calculation runs in a spreadsheet and the bill of quantities (Leistungsverzeichnis) in yet another program. The effort arises in between: information is entered several times, connections are lost, and when a piece of evidence is needed, the search begins.
Added to this, the office and the site place different demands. In the office, traceability, orderly filing, billing and evaluation count. On site, what counts is that an observation can be recorded in a few moments, with photo, location and responsibility, even without a network, even with cold hands. Software that serves only one of the two sides well fails on the other: either the site stays with paper notes and voice messages, or the office types everything up afterwards.
Before you compare offers, it is therefore worth taking an honest look at your own workflow: which documents arise in which project step, who records them, who needs them later, and where does the thread break today? The article Digital construction documentation: scope and benefits gives an overview of the documents that arise over the course of a project.
Clarify requirements before you compare
A provider's feature list is not a requirements profile. First write down which processes you want to cover and rate each point as "must", "should" or "could". The following areas occur in most projects:
- Site inspection. How is a walk-through recorded: by photo, note or voice? Does it produce a report with findings, responsibilities and deadlines that you can send to the parties involved? Can a finding be turned directly into a task?
- Defects. Are defects managed with photo, location, trade, responsible party and deadline, and tracked until they are resolved? Can a notice of defects (Mängelrüge) be generated from them?
- Site diary. Can daily entries with weather, trades present, works carried out and obstructions (Behinderungen) be recorded promptly, including from the site? The article Site Diary Duty: Content and Evidence explains what an entry needs to contain and why it has evidential value later.
- HOAI fees. Do you need a fee calculation under the 2021 fee schedule for architects and engineers (HOAI 2021) with fee zones (Honorarzonen), service phases (Leistungsphasen) and interpolation under § 13 HOAI? Are the chargeable costs (anrechenbare Kosten) structured according to DIN 276, and is the calculation path documented traceably?
- AVA and GAEB. Should you create bills of quantities, read in bids and compare them in a bid comparison (Preisspiegel), covering tendering, award and billing (Ausschreibung, Vergabe und Abrechnung, AVA)? Then exchange in the GAEB format is decisive, from the specification (Leistungsbeschreibung) to the bid.
- Change orders. Can changed or additional works be recorded, justified and valued, with reference to § 2 of the German construction contract procedures, part B (VOB/B) or §§ 650b, 650c of the German Civil Code (BGB), and does the client's instruction remain documented?
- Acceptance. Is an acceptance report produced with reservations, outstanding works and deadlines? Acceptance is the pivot: it starts the warranty period (Gewährleistungsfrist), and the burden of proof shifts (§ 640 BGB, § 12 VOB/B).
Not every firm needs everything. A trade contractor weights site inspection, defects and the site diary higher than fee calculation; a design firm needs HOAI and AVA; an operator is more likely to need an operations log (Betriebstagebuch). What matters is that the areas you need are connected: the finding becomes the task, the task becomes the deadline, the met deadline becomes the evidence.
Criteria for the comparison
Once the requirements profile is in place, offers can be measured against the same criteria.
Offline capability
On many sites there is no reliable reception: in the basement, in the shell, in plant rooms. Software that has to be online will not be used there. So check not only whether the provider says "offline" but what that means: can reports, photos and defects be recorded completely without a connection? Are changes merged later without entries being lost? Test this in flight mode, not in the meeting room.
Reports as PDF
The report is the result that you send, file and present in a dispute. It has to come out of the software as a PDF, with photos, location, responsibilities, deadlines and a version that does not change unnoticed. Check whether the layout suits your firm, whether you can control the recipients and whether earlier versions are retained. The acceptance report template shows which content such a document should carry at a minimum.
Deadlines
Deadlines are the core of defect tracking: deadline for rectification, follow-up, limitation of defect claims (§ 634a BGB or § 13 (4) VOB/B). The software should manage deadlines per defect, make overruns visible and trigger reminders, and do so for the right person. Ask how deadlines are changed and whether the change remains logged.
Data sovereignty and hosting in Germany
Project data contains names, addresses, photos of people and contract content. Clarify where the data is stored, who has access and whether a data processing agreement (Auftragsverarbeitungsvertrag) under Art. 28 GDPR (DSGVO) is concluded with the provider. Hosting in Germany simplifies the assessment but does not replace it: also ask about subprocessors, encryption, backups and whether your data is analysed for the provider's other purposes. The answers belong in writing in the contract.
Export and interfaces
Data you cannot get out belongs to you only on paper. Check the export before signing the contract: reports as PDF, lists as tables, photos in original resolution, bills of quantities and bids as GAEB files. For GAEB exchange, the label is not enough; have a real file from your daily work read in and output again, and compare whether item numbers (Ordnungszahlen), quantities and texts are unchanged. The article GAEB Tendering: From AVA to Award describes how a GAEB tender runs cleanly.
Roles and permissions
On a project, site managers, designers, subcontractors, the client (Bauherr) and the office work with different permissions. The software should map who may view, record, change and approve, per project and not only globally. It also matters how parties without their own account are involved, for example a subcontractor who receives a report and is meant to report a defect as resolved.
Rollout and training
A long feature list is of no use if the team does not go along. Ask how the provider supports the rollout: is there training for office and site, templates for your reports, a migration of running projects? How reachable is support, in which language, at what times?
Pricing model and contract
Prices are calculated per user, per project, per module or as a flat rate. Work the model through for your firm, with the actual number of active users including subcontractors and clients. Check the term, notice period, price adjustment clauses and what happens to the data when the contract ends. Example: a price per user looks inexpensive as long as three people work with it, and becomes expensive as soon as every foreman (Polier) and every subcontractor needs an account.
Typical pitfalls
Some mistakes recur regularly during selection.
- Feature list instead of workflow. Anyone who compares offers by the number of ticks chooses the software with the most features, not the one that fits their own workflow. Evaluate your three most frequent processes from start to finish.
- Testing only in the office. The site decides whether the software is used. A test without a real walk-through, without photos, without flight mode says little.
- Too many mandatory fields. A form that demands ten fields on site will be bypassed. Fewer mandatory fields, but photo and location, keep the documentation alive.
- Tools side by side. If defects, site diary and report sit in three programs, double entry remains, only digital. Pay attention to the connection between the documents, not only to the individual module.
- Underestimating the rollout. The software is not rolled out on the day it is activated. Without training, templates and a responsible person in the office, it remains a second filing system.
Selection checklist
The following questions can be answered with yes, no or "partly" for every offer. The more "no" answers there are against your must-have requirements, the clearer the decision.
- Does the software cover the processes we have classified as "must": site inspection, defects, site diary, fees, AVA, change orders, acceptance?
- Can reports, photos and defects be recorded completely offline and merged later without loss?
- Are reports produced as PDF with photos, location, responsibilities and deadlines, and are earlier versions retained?
- Are deadlines managed per defect, overruns made visible and changes logged?
- Is the data stored in Germany, is there a data processing agreement under Art. 28 GDPR, and are subprocessors named?
- Do GAEB import and export work with a real file from our daily work?
- Can all data be exported in common formats, including after the contract ends?
- Does the role model map our project parties, including subcontractors and the client?
- Is there training, are there templates and support during the rollout, and who is responsible for it on our side?
- Have the pricing model, term, notice period, price adjustment and data handover been worked through for our situation and clearly settled in the contract?
A 30-day approach: an example sequence
Example: a firm with a handful of staff and several running projects could approach the selection like this. The periods are for orientation, not a benchmark.
Days 1 to 7: requirements and shortlist. You describe your three most frequent processes from recording to evidence, classify the requirements as must, should and could, and name one responsible person in the office and one on site. Two or three providers remain on the shortlist.
Days 8 to 14: testing on site. With each provider you set up a real project and carry out a real site inspection, with photos, location and deadlines, partly in flight mode. Then you send the report to one of the parties involved and check whether it arrives and is readable.
Days 15 to 21: testing in the office. Now the office requirements take their turn: deadline overview, notice of defects, site diary entries, where applicable fee calculation and GAEB exchange with a file from your archive. And the export: everything you have recorded must come out again.
Days 22 to 30: decision and contract. You complete the checklist for each provider, work through the pricing model, clarify open contract questions in writing and set a rollout plan: which projects start first, who is trained when, which templates are adopted.
Frequently asked questions
Do small firms and trade contractors need their own construction documentation software?
The question is less about size than about the number of records you have to keep. As soon as defects are tracked with deadlines, reports are sent and site diary entries are kept over months, a system that holds these threads together pays off. For a single small project a good template may be enough; for several running projects side by side, rarely.
Which matters more: range of features or usability on site?
Usability on site. A feature that nobody uses because recording is too cumbersome does not exist in practice. First check whether your team can record a walk-through quickly, and only then which evaluations the office draws from it.
Does the software have to work offline?
If you work on sites without reliable reception: yes. Offline capability means that reports, photos and defects are recorded without a connection and merged later without loss. Test this yourself in flight mode instead of relying on the statement in the data sheet.
What should I look for in hosting?
The storage location, the data processing agreement under Art. 28 GDPR, named subprocessors and the question of whether the provider analyses your data for its own purposes. Hosting in Germany simplifies the assessment but does not replace reading the contract.
How do I tell whether GAEB exchange really works?
By reading in a real file from your daily work, editing it and outputting it again. Then compare item numbers, quantities, units and item descriptions with the original. A label saying "GAEB-compatible" says nothing about whether the file arrives cleanly on the other side.
What happens to my data if I change provider?
That should be settled before signing the contract: which formats are exported, how long the data remains available after the contract ends and when it is deleted. Check the export during the test, not only when giving notice.
Structify is software for digital construction documentation that covers many of the criteria named here: site inspection reports are created from voice, photo and note, also offline, on iPhone, iPad and Android; defects are tracked as tickets with photos and deadlines; site diary entries run alongside as a ticket type; and there are HOAI fees with interpolation under § 13, AVA with GAEB import and export and bid comparison, change orders and acceptance. The data is hosted in Germany and is not used for training purposes; details are available under Security. If you would like to check whether this fits your workflow, book a demo, ideally with a real project and a real site inspection.