Outcome & Operations Profile

OOP is a simple diagnostic that looks at how a project is set up and run in practice. It highlights where key project controls are missing or unclear, with a focus on timing and real-world outcomes.

It does not predict legal outcomes and it does not provide legal advice. It is designed to support clearer conversations and better project setup, not to judge or assign blame.

Many project issues are not caused by what was done, but by when it was done. Before work starts, core controls should already be in place. This includes agreeing the scope, setting out how changes will be approved, and confirming who has authority to make decisions.

During the work, evidence should be captured as the work happens. This means keeping clear, time-stamped records rather than trying to reconstruct events later.

At acceptance, clear sign-off and complete deliverable packs help confirm what has been finished, what has been accepted, and when payment can be released.

Each control is assessed using three internal factors. These reflect how much influence the control has on outcomes, how sensitive it is to timing, and how important evidence is for that control.

These factors are combined to produce a severity score on a scale from zero to one hundred. This score is not a probability and should not be read as a prediction. It simply highlights where missing controls are likely to have the greatest impact.

All weights used in OOP v0 are expert-designed heuristics. They are intended to be transparent, conservative, and suitable for early-stage diagnostics.

Each version of OOP is explicitly versioned so changes are clear over time. No project or party is identified and no personal data is stored. Aggregation uses anonymised counts only, without storing report content.

OOP does not provide legal advice, arbitration advice, or insurance advice. It does not declare winners or losers and it does not suggest actions based on alleged breaches. For disputes, formal claims, or legal matters, qualified professionals should always be used.

OOP is a quick, practical check of how clearly a project is set up, from scope and changes through to acceptance and payment.