Capabilities

Penalties and retentions control

Contractor breaches are logged at once, and penalties and retention amounts show on every snag — no manual evidence gathering and no disputes at payment.

Penalties and retentions control

Before and after

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*

With MonStr:

  • Breaches logged at once, with photos and timestamps
  • Penalties applied without delay
  • Transparency: fewer disputes
  • Admin time: 1 hour a week*

* Observations on our own projects, without a control group.

What it gives you

A penalty stops being an argument from memory and becomes a record with a photo, place and time.

How it works

From a breach on site to a retention at payment.

  1. 1

    Log the breach

    The engineer creates a snag with a photo and sets the penalty or the retention amount.

  2. 2

    The contractor sees it

    The assignee gets a notification with a deadline: fix it or face a retention.

  3. 3

    Retention accounted for

    By payment time the summary is ready: what was fixed, what is retained and why.

What changes

1 hour
a week on penalties instead of 5–10*
10–20%
less rework*
90%
lower litigation risk*

* Observations on our own projects, without a control group.

Details

What matters to the QA team and accounts.

  • Quality and safety breaches in one list
  • A retention amount on every snag
  • Reopening when a fix is not good enough
  • Contractor ranking by breaches
  • Export to Excel with any filter
  • A full action history for every snag

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

Request a demo

Leave your contacts — we will show MonStr on your project and help choose the configuration.

By sending the request you confirm that you have read the privacy policy.