Outcome & Operations Profile
Protect the project before problems become expensive. OOP is a simple snapshot of how a project is set up in practice — scope, changes, acceptance, evidence and payment confidence — turning messy project risk into clear next actions.
OOP is the lightweight diagnostic. Bespea is the structured workflow that helps you act on the result.
OOP Methodology (v0)
Transparent, conservative, and built for early-stage diagnostics.
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.
What is measured
Twelve practical project controls across four stages — before work starts, during work, acceptance & payment, and the evidence / decision record. Each control is a Yes/No on whether a setup practice is actually in place.
What is not measured
No legal merits, no fault, no probability of any outcome. OOP does not read your contract, judge a dispute, or predict who would “win”. It only highlights where common project controls are missing.
How the score works
Each missing control has a severity from its impact, timing sensitivity and evidence importance (each 0–100), normalised by their average. The overall score is the weighted share of missing-control exposure, clamped to 0–100. Lower is stronger.
- Strong setup0–25
- Some weak points26–45
- Material control gaps46–65
- High project-risk exposure66–100
Why timing matters
Many issues are about when a control was in place, not just whether it existed. Controls grouped by stage:
- Before work starts: Signed, agreed scope, Changes priced before work, Clear change-approval process, Baseline programme agreed
- During work: Timely delay notices, Defects logged with rectification
- Acceptance & payment: Measurable acceptance criteria, Milestone acceptances recorded, Payment linked to acceptance, Complete handover pack
- Evidence & decision record: Evidence captured as work happens, Decisions confirmed in writing
How anonymous aggregation works
When a report is generated, only anonymous counts are recorded — the score, severity band, which control codes were missing, the timing windows, and Yes/No totals. No report text, personal data, company names or project details are stored. The live benchmark is built from these counts alone.
How OOP connects to Bespea
OOP is the lightweight diagnostic. Each gap maps to a structured Bespea response — scope baselines and decision records, variation approval, milestone acceptance, evidence capture and proof packs, and milestone-linked payment confidence. Start with OOP; move to Bespea when the project needs structured protection.
Version block
- • OOP v0
- • Heuristic, expert-designed weights
- • Anonymous aggregate counts only
- • No personal data required or stored
This methodology is a heuristic operational diagnostic. It is not legal advice, arbitration advice, insurance advice, or a prediction of legal outcome.