What is an MMCR and how is it different from the plans it tracks?

The Mitigation and Monitoring Commitment Register is the single list of every safeguard obligation a project has taken on, drawn from its ESIA, its RAP, its lender agreement and its works contract. The individual plans — SEP, LFMP, OHSSMP and the rest — say how a subject will be managed. The MMCR says what was promised, by whom, by when, how it will be verified, and whether it has been met this period. A project can have ten well-written plans and still be unable to answer the only question a lender asks at disbursement: which commitments are currently unmet.

Why does this register have 47 rows?

Because that is the commitment set the register was built against — the RAP01–RAP47 structure used on Ugandan infrastructure projects, covering workforce, engagement, grievance, health and safety, national content, waste and reporting. The codes matter less than the discipline: one row per commitment, each traceable to the document that created it. Add or remove rows to match your own contract; keep the columns.

What belongs in 'means of verification'?

The specific artefact a reviewer would ask for — a signed attendance sheet, a waste transfer note with a returned disposal confirmation, a payroll record. Not 'monitoring reports' or 'site records'. If the means of verification is written vaguely, the commitment is unauditable, and unauditable commitments are the ones that go unmet without anyone noticing.

Who owns the register — the employer or the contractor?

The employer owns the register; the contractor owns most of the rows in it. That split is what makes the instrument work. A register maintained by the party being assessed becomes a self-report. In practice the contractor files evidence against each commitment and the employer's ESHS team verifies and scores it, with the scored period feeding payment certification.

How does the register connect to payment?

On projects that use it properly, safeguard adherence for the period is a condition of payment certification — the final row of the register. That is what turns a commitment list into a control rather than a reporting exercise. It also means the scoring rule has to be written down in advance, because a percentage that decides money will be argued about.

CSVFree · no registration

Mitigation and Monitoring Commitment Register (MMCR) Template

The 47-commitment safeguard register — RAP01 to RAP47 — with the plan each commitment belongs to, its means of verification, monitoring frequency, responsible party and standard reference.

47 commitments · 10 columns · mapped to eight management plans

The document that answers "what did we promise?"

A large project accumulates safeguard obligations from four or five different places. The ESIA proposes mitigation measures. The RAP commits to entitlements and processes. The lender's agreement adds conditions. The works contract flows obligations down to the contractor. Each document is written by different people, at different times, and none of them is a list.

The consequence is predictable and very common: by year two nobody can state the project's full commitment set without re-reading four documents, so nobody does, and the commitments that were never transcribed into anyone's workplan are simply not delivered. They resurface at completion audit, when the remedy is expensive and the witnesses have moved on.

The register is the transcription. One row per commitment, each traceable back to the document that created it, each with a named owner and a stated means of verification. It is unglamorous and it is the difference between a project that can evidence compliance and one that can only assert it.

Why every commitment carries a plan code

Each row in this register names the management plan it belongs to — SEP, LFMP, OHSSMP, GRMP, GBV/SEA, NCCMP, LEMP or SHWMP. That column does two jobs. It tells the person filing evidence which plan's procedures apply, and it lets the register be read by plan when a reviewer asks how a single subject is performing rather than how the project is performing overall.

It also exposes a common gap. Sort the register by plan code and you will usually find one or two plans carrying commitments that no existing document actually covers — obligations picked up from the works contract that were never written into a management plan. That is worth finding in month three rather than at audit.

Scoring, and why the rule has to be written first

The register is scored per period: each applicable commitment is pending, in progress, met or not met, and adherence is the proportion met of those applicable. The word doing the work there is applicable. A commitment about waste disposal is not unmet during a period with no waste; marking it "not met" understates performance, and quietly dropping it inflates the denominator in the other direction.

Decide the applicability rule and the scoring threshold before the first period, because on projects where adherence gates payment certification, both will be argued about. A register whose scoring rule is settled after the first disputed invoice has already lost the authority it was built to carry.

Questions

What is an MMCR and how is it different from the plans it tracks?: The Mitigation and Monitoring Commitment Register is the single list of every safeguard obligation a project has taken on, drawn from its ESIA, its RAP, its lender agreement and its works contract. The individual plans — SEP, LFMP, OHSSMP and the rest — say how a subject will be managed. The MMCR says what was promised, by whom, by when, how it will be verified, and whether it has been met this period. A project can have ten well-written plans and still be unable to answer the only question a lender asks at disbursement: which commitments are currently unmet.
Why does this register have 47 rows?: Because that is the commitment set the register was built against — the RAP01–RAP47 structure used on Ugandan infrastructure projects, covering workforce, engagement, grievance, health and safety, national content, waste and reporting. The codes matter less than the discipline: one row per commitment, each traceable to the document that created it. Add or remove rows to match your own contract; keep the columns.
What belongs in 'means of verification'?: The specific artefact a reviewer would ask for — a signed attendance sheet, a waste transfer note with a returned disposal confirmation, a payroll record. Not 'monitoring reports' or 'site records'. If the means of verification is written vaguely, the commitment is unauditable, and unauditable commitments are the ones that go unmet without anyone noticing.
Who owns the register — the employer or the contractor?: The employer owns the register; the contractor owns most of the rows in it. That split is what makes the instrument work. A register maintained by the party being assessed becomes a self-report. In practice the contractor files evidence against each commitment and the employer's ESHS team verifies and scores it, with the scored period feeding payment certification.
How does the register connect to payment?: On projects that use it properly, safeguard adherence for the period is a condition of payment certification — the final row of the register. That is what turns a commitment list into a control rather than a reporting exercise. It also means the scoring rule has to be written down in advance, because a percentage that decides money will be argued about.

All RAP templates →

The software behind this

SmartLARMS keeps this as a live record, not a spreadsheet

A template is a starting point. The version that survives a completion audit is one where every change is attributed to a person and a date, and where the numbers reconcile to what was actually paid.

Talk to us → olules@smartlarms.com