Site Diary & Email Monitors

30,000 emails a project. Something in there is money.

Hevi reads every site diary, daily report and email as it lands — and flags the delays, variations, standby and safety triggers your team doesn't have time to find. You don't check Hevi. Hevi comes to you.

This module answers
01 · What happened on site?02 · What does the contract say?03 · What action is required?04 · What evidence supports it?05 · What value was protected?

How it works

Set it up once. It never stops reading.

01

Your project gets an inbox

Every project gets a unique Hevi email address. CC it, forward to it, add it to distribution lists, or set an Outlook auto-forward rule.

02

Diaries flow through Hevi

Site diaries and daily reports are submitted in Hevi — or forwarded in. Free responder seats mean the whole crew can submit.

03

AI reads against your contract

Every item is scanned for contract-relevant events: delays, weather, standby, safety incidents, variation triggers, resource issues.

04

Flags come to the commercial team

Each flag arrives with the matched clause, the suggested process, and the clock — so the notice window starts being watched immediately.

See it in action

Watch the inbox do the reading.

30,000+
emails on a typical project — too many for any human to read against the contract
$50–100k
in delay claims missed each month when nobody's watching the diaries
0 hrs
of your team's week required — monitors create value passively

See it read

Your site diary just became your best witness.

Every flagged event stays linked to its source — the diary line, the email, the timestamp. The record accumulates into the institutional memory of the project, and it stands up when it counts.

Site diary · NS-227 · day shift
05:50 prestart — 22 crew, all inducted
06:10 crew stood down — client access not provided
09:30 water cart down 1 hr — own maintenance
12:40 access granted — 6.5 hrs lost
14:00 development resumed, cycle normal
DELAYGC 34.2 matched · notice window opened
mn114@projects.hevi.app

One address, every channel: CC it on correspondence, drop it into distribution lists, or auto-forward from Outlook. From that moment, nothing contract-relevant slips past unread — and everything is searchable later.

No behaviour change required from the site. The crew keeps working exactly as they do today. That's the point.

What it catches

The flags that pay for the platform

Delay events buried in diaries

Standby, access delays, weather, client-caused interruptions — flagged the day they're written down, with the notice clock started.

Directions without instructions

“Please proceed as discussed” in an email is a variation waiting to be lost. The monitor catches the language and triggers the VO process.

Patterns humans can't see

The third access delay this month looks like noise day-to-day. Linked together, it's a claim with quantum building behind it.

Safety and compliance triggers

Stand-downs, incidents and inspection items linked to their contractual consequences — not just logged, but actioned.

See what your project record is already telling you.

Bring a representative diary or email export. We'll show the contractual triggers Hevi would flag.