Site diaries and defect reports from BauMaster long after the project ends.

Site diaries, handover and defect reports, site photos and the reports you export from BauMaster go into your knowledge base – still there after the project ends, when warranty questions come up. Access is read-only; nothing in your BauMaster projects is changed.

BauMaster

subject to a feasibility check · folder

Example question

“Which defects from the Sonnenhof handover are still outstanding?”

1 Answer with source

Connection

How the connection works

BauMaster is a cloud service from the Upper Austrian provider PASit software, so your construction documentation is held by the provider, not on your server. Before we start, we check with you and the provider whether and how BauMaster can be connected – that is, which route your package includes and whether it works for ongoing exports. The standard route: you export site diaries and handover and defect reports from BauMaster as PDFs, and junova mirrors the folder they are saved to into your instance, encrypted and over outbound connections only. The vendor also 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. Photos from your phone and voice notes from site can also be uploaded directly, without any connection.

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

Set-upHow much set-up is needed depends on the chosen route – report folder, a fixed export per project or one of the interfaces. Once the feasibility check is done, we estimate the effort and agree it with you before anything is set up, with the provider if needed. The set-up is charged on a time-and-materials basis, agreed in advance.

Documents

Typical content: BauMaster

  • Site diaries with crew numbers, plant used and the day’s work – including the weather line that BauMaster records for the site location, which carries weight if the works are disrupted
  • Handover and defect reports: each defect as a ticket, with deadline, responsible contractor and its status when the report was exported
  • Photos pinned to the plan – the marker on the drawing and the picture that goes with it, instead of a folder full of unnamed phone photos
  • Minutes of site meetings and inspections, with the actions agreed and what had become of them by the next site meeting
  • Plans and plan revisions from the project, with a record of who approved which revision
  • Daywork reports and the hours your team records in the app – in other words, work done outside the construction contract that has to be justified later

Example questions

Questions you might ask your documents

  • “Which defects from the Sonnenhof handover are still outstanding?”

    1 Answer with source

  • “What did the site diary for 14 May say about the reinforcement in building section B?”

    2 Answer with source

  • “Is there a photo showing the insulation before plastering?”

    3 Answer with source

Start

Before a connection is set up

This connection is set up for you rather than switched on in one click. Every source has its own logins, permissions and folder structure – so before we start, we check with you whether and how it can be connected at your company. Set-up and maintenance are charged on a time-and-materials basis, agreed in advance; the amount depends on the source.

You can also upload files, whole folders, emails, photos and voice notes at any time. In the demo you see the answers using sample documents from your industry; you check them against your own documents in the first weeks after go-live.

Preliminary check

What we check in advance

Before we start, we clarify when and how often you export reports – because a report is a snapshot, not a live record: anything that happens to a ticket afterwards, such as a defect being fixed or a deadline being moved, only appears in the next report. For today’s status, BauMaster is still the place to look; the knowledge base shows what applied on the day of the report and who signed it. We also look at how your photos are stored: a photo’s position on the plan comes from the report it belongs to. Only what is on paper can be cited – so an agreement made on the scaffolding or a phone call with the structural engineer belongs in a report or note if you need to prove it later.

FAQ

Frequently asked questions about this connection

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

Whatever you export as reports from closed projects comes across – and that is often where the value lies, because warranty questions come up years after the last day on site. For older projects, you export the reports once, project by project, and save them to the folder; after that, new reports follow as part of day-to-day work. The hours from the reports can also be exported as a spreadsheet if you want to prove daywork hours later. How far back you go is up to you.

How should we file the reports so that people find the right project later?

One folder per project, with the reports inside. The project, date and building section are in the report header, and the system reads them from there; a meaningful file name is nice to have, but it isn’t what the system relies on. The folder level still matters, because it decides which site an answer belongs to and who can see it. If a project was set up twice in BauMaster – once for the quote and once for construction – just tell us which one applies.

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

Nothing in BauMaster itself is touched; the system only reads the folder your reports are saved to. If something changes in the export – a different format, a different route – you’ll usually notice because no new reports arrive; we then work out together how to proceed. The knowledge base itself sits in your own instance, regardless of how you change your package with the provider later. That way, you keep the construction documentation from previous years in your own hands, outside the program too.

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

No: the AI knowledge base is your own instance, and you decide who sees what there – by document type and role, not by individual file. Defect reports and plan revisions for site management, daywork reports and hours for the office – that’s one way to split it. Your permissions in BauMaster stay as they are. There is no access into your knowledge base from outside – the connection only runs outbound from your side.

Request a demo – with examples for BauMaster

In a 30-minute video call, we use sample documents to show what answers with sources look like. Before we start, we check whether and how BauMaster can be connected at your company.