Site reports your foreman actually files.

How a report is made

In the mobile app the foreman picks the project and records what they would otherwise type in the evening:

• the recording is transcribed in the language it was spoken in;
• AI organises the text into a structured report;
• weather at the time of recording is added automatically, photos are placed in the right proportions;
• the foreman reviews and corrects the draft — nothing goes out without their confirmation;
• the report is translated into the chosen languages, built into one PDF and emailed to the project recipients.

Groundwork for the site diary — not a replacement

The official site diary is a separate document kept under the applicable regulations, and ConaPlan does not replace it. It does prepare everything you need for it: dated reports with the work done, crews present, problems, photos and weather. Filling in the diary then takes minutes instead of reconstructing the day in the evening.

A report that updates the schedule

A report can be linked to an activity in the schedule while confirming its status: "on plan", a completion percentage, or "behind" with a reason. The daily view lists activities from three days back to seven days ahead.

An entry from site is a proposal the project manager confirms or rejects. The schedule stays reliable while the site keeps it current.

Problem reports with a reason

When work stops, the foreman reports a problem with one tap and picks the reason:

• the previous crew has not finished,
• material is missing,
• too few workers,
• unclear drawings or documents,
• weather or site conditions,
• other (description required).

Multilingual reports and app

The foreman speaks their own language; each recipient reads the report in theirs: one PDF, each language on its own page. The mobile app is available in English, German, Croatian, Slovenian and Albanian.

Works without signal

In a basement, a tunnel or a remote site, reports, status confirmations and problem reports are stored on the phone and sent automatically when a connection is back. Each entry carries its own id, so nothing is duplicated when it is resent.