Before:
- Human error: mistakes and missed breaches
- Delays: penalties lost their effect
- Conflicts: disputes and manual evidence gathering
- Admin time: 5–10 hours a week*
Contractor breaches are logged at once, and penalties and retention amounts show on every snag — no manual evidence gathering and no disputes at payment.

Before:
With MonStr:
* Observations on our own projects, without a control group.
A penalty stops being an argument from memory and becomes a record with a photo, place and time.
Breach logged at once
A breach with a photo, place and time enters the system when it is found, not at month end.
Penalty on the card
A penalty is attached to the snag — both client and contractor see it.
Retention amount
The snag states the amount of work retained if the defect is not fixed on time.
Evidence base
Photos, geotags, status history and signatures: a dispute is settled with a link to the record.
Penalties on the grid
Penalties and retentions show by flat and by contractor on the building grid.
Summary for payment
Penalties and retentions per contractor are collected for payment with no manual counting.
From a breach on site to a retention at payment.
Log the breach
The engineer creates a snag with a photo and sets the penalty or the retention amount.
The contractor sees it
The assignee gets a notification with a deadline: fix it or face a retention.
Retention accounted for
By payment time the summary is ready: what was fixed, what is retained and why.
* Observations on our own projects, without a control group.
What matters to the QA team and accounts.

We will show how to manage penalties and retentions on your sites