Site diaries and defect reports from BauMastereven after the project ends.

Site diaries, handover and defect reports, site photos and the reports you export from BauMaster are meant to come into your knowledge base — even after the project ends, when the warranty question comes up. Read-only access is planned; nothing is changed in your BauMaster projects.

Request a demo Cost check

BauMaster

after clarification · folder

Example question

“Which defects from the handover on the Sonnenhof project are still open?”

1 Answer with source

Connection

How the connection is designed

BauMaster is a cloud service from the Upper Austrian provider PASit software; your construction documentation is therefore held by the provider, not on your server. The plan is to export site diaries and handover and defect reports from BauMaster as PDF and to mirror the storage folder, encrypted, into your instance — only via outgoing connections. In addition, the manufacturer mentions an open REST interface, a SharePoint connection for the digital construction file and export to Excel and MS Project, with custom interface solutions available on request in the Enterprise package, according to the manufacturer. Which route is enabled in your package and usable for an ongoing export, we check with you and the provider before we start. Photos from your phone and voice memos from the site can also be uploaded directly without any connection.

Once set up, synchronisation runs automatically: new and changed documents from BauMaster are added by themselves, without anyone having to upload anything.

Set-upHow much setup is needed depends on the chosen route — report folder, fixed export per project or one of the interfaces. We estimate the effort after the preliminary check and discuss it with you before anything is set up, together with the provider if needed. It is billed by effort.

Documents

Which documents may be stored in BauMaster

Site diaries with crew numbers, equipment used and the day's work — including the weather line that BauMaster records for the project location and which carries weight in the event of a disruption
Handover and defect reports: each defect as a ticket, with deadline, responsible contractor and the status it had when the report was exported
Photo documentation located on the plan — the marker on the plan and the picture that goes with it, instead of a folder full of unnamed phone photos
Minutes from site meetings and inspections, with the tasks that arose from them and what had become of them by the next regular site meeting
Plans and plan revisions from the project, with the note of who approved which revision
Daywork reports and the working hours your people record in the app — in other words, what was incurred beyond the construction contract and has to be justified later

Example questions

Examples of questions to your documents

“Which defects from the handover on the Sonnenhof project are still open?”
1 Answer with source
“What did the site diary of 14 May say about the reinforcement in building section B?”
2 Answer with source
“Is there a photo showing the state of the insulation before plastering?”
3 Answer with source

Start

Before a connection is set up

A connection is set up for you, not activated in one click. Every source comes with its own logins, permissions and folder logic — whether and how it can be connected at your company, we check together beforehand. Set-up and maintenance are billed by effort; how much that is depends on the source and is discussed beforehand.

Until then, and independently of it, you can upload files, whole folders, emails, photos and voice memos. Before we start, we go through real questions with you to see how the answers look.

Preliminary check

What we check in advance

Beforehand, we clarify when and how often you export reports — because a report is a snapshot, not a real-time record: what happens to the ticket afterwards, such as a defect being fixed or a deadline being moved, only appears in the next report. For today's status, BauMaster remains the place to look; the knowledge base is about what applied on the day of the report and who signed it. We also look at how your photos are stored: the location on the plan comes via the report a photo is part of. What can be cited is what is on a sheet — an agreement made on the scaffolding or a call to the structural engineer therefore belongs in a report or a note if it needs to be provable later.

FAQ

Frequently asked questions about this connection

Our projects from 2019 to 2023 are closed in BauMaster. Will they come along?

The plan is that what you export as reports from the closed projects comes along — and that is often where the value lies, because the warranty question comes years after the last day on site. For the older projects, you export the reports once, project by project, and put them in the folder; after that, new reports are meant to follow with day-to-day business. The working hours from the reports can also be exported as a table if you want to prove daywork hours later. How far back you go is up to you.

How do we file the reports so that someone hits the right construction project later?

One folder per construction project, with the reports inside — that is how it is intended. Construction project, date and building section are in the report header, and the system is meant to read them from there; a meaningful file name is nice, but it is not the basis. The folder level still matters, because it determines which site an answer belongs to and who is allowed to see it. If a project was created twice in BauMaster — once for the quote, once for execution — just tell us which one applies.

What if the provider changes something in the app or in our package?

Nothing is touched in BauMaster itself; what is read is the folder your reports end up in. If something changes in the export — a different format, a different route — it usually shows because no new reports arrive; we then look together at how to proceed. The knowledge base itself sits in your own instance, regardless of how you later tailor your package with the provider. That way you have the construction documentation from previous years in your hands outside the program as well.

On some projects the client also has access to BauMaster. Will they then see our knowledge base too?

That is not planned: the AI knowledge base is your own instance, and you decide who sees what there — by document type and role, not by individual files. Defect reports and plan revisions for site management, daywork reports and hours for the office — that is how it can be divided. This does not change anything about your permissions in BauMaster. The setup does not provide for any access from outside into your knowledge base — the connection only goes outwards from you.

Industries

Typical for these industries

Guides

Request a demo — and clarify how BauMaster fits in

In thirty minutes by video we show what answers with sources look like, and clarify whether and how BauMaster can be connected at your company.