The construction diary writes itself from the construction day.

↳ Who was there, what was done, what happened? This is pieced together later.

→ The AI writes the daily entry from the site's clock times, the day's reports, and the daily report upon clocking out. You add the weather for past days manually.

↳ A construction diary in Word can be changed at any time and is never seen by the client.

→ You release the entry, it is locked with a checksum, and the history remains immutable. The client countersigns via link on a tablet or raises an objection.

↳ Photos and notes end up on the foreman's private mobile phone.

→ The foreman clocks in with location rules per construction site, sends reports with photos and dictation, and writes the daily report upon clocking out. Clocking in, reporting with photos, defects, overhead drafts, and clocking out work without a network; data is resent with the recording time. Available today in the web app on mobile, in the AIRIS app for iPhone and Android from the next app update.

↳ Defects, supplements, and orders are communicated verbally and get lost.

→ The foreman records a message, optionally with a photo. AIRIS creates cards from it: construction diary entry, defect, supplement against the item in the bill of quantities with contract price, purchase order request. Nothing happens without confirmation per card.

↳ Defect lists without location and photos lead to discussions.

→ You place defects with photos, tasks, and notes as pins on the plan, with filters. A new plan version adopts the pins.

↳ Overhead hours are signed on paper and get lost before invoicing.

→ The overhead report comes with a proposal from time tracking; the signature locks it, and the invoice draft is created with one click. The acceptance protocol adopts the defects, both parties sign; the warranty period, according to the stored national rule, reminds 90 days before expiration.