The Project Manager has rejected my compensation event
Contractor side: Compensation events
Where the contract stands
Under NEC4 61.4 the reasons have to be stated, and only the reasons on the contract's list count. Note the date you got the reply: a rejection is still probably a reply, so it does not restart the failure route, and any dispute time limit in your contract may already be running.
Read the guide: PM rejects a compensation event
This is our plain-English summary, not legal advice. Your own contract, including any Z clauses, decides.
In Contract Status, step by step
Read the decision and the reason
The record shows the decision chosen from the contract's list and the words the Project Manager wrote, with the date. It also shows when you became aware and when you notified.
NCE-0003: refused because the compound was not needed until a later date on the Accepted Programme.
Ask for what is missing
If you think facts were overlooked, send them in a general communication, with a reply date, so they sit on the contract.
General Communications keeps the exchange dated.
Keep it findable
The register keeps the rejected notification with its status, and the register reports can go to PDF or CSV for whoever takes the next decision.
Rejected notifications stay on the register.
What it does not do: Contract Status does not decide who is right, and it does not run the dispute. It keeps a clean record for whoever does.
All screens are from the upgraded app, using a fictional water company, Kestrel Valley Water, and its made-up contractors.
What happens next on the other side
The reply form the Project Manager used offers a fixed set of decisions: notified correctly, or a reason such as no effect on Defined Cost, Completion or Key Dates. Each one goes with a status, so a refusal always carries its reason.
See it on a contract you can click through
The guided tour lets you walk the same fictional account yourself. Or book a demo, and bring the situation you are dealing with.