The Grade
Formal Systems Analysis
The condition of a system, stated in a form that can be defended: the whole and every part of it examined, weighed, and scored. The question a Grade answers is what condition is the whole in?
When it is commissioned
A board, a regulator, a legislative oversight body, or an executive needs to know the condition of the whole—not a high-level picture, but a defensible account they can put in front of the people who govern it.
An annual health check of the system.
The board or the executive wants a scored account of the condition of the whole, not a sample.
Diligence before a transaction.
An acquisition, a merger, or a major investment requires knowing what the operating system can and cannot do.
A review after an incident.
Something has failed, and the question is the soundness of the system it sits within.
Evidence for a regulator or an inspector general.
A defensible, function-by-function account of the system, suitable for oversight bodies and legislative committees.
What is delivered
A Grade is the condition of the system you answer for, stated in a form you can stand behind. It begins with the whole and what the system is for, then examines every component and every relation individually and scores each against that purpose. The result can be stated plainly, compared from one year to the next, and defended when it is questioned. A Reading tells you what you have; a Grade tells you what condition it is in.
You receive a profile of the system, function by function, an overall grade, and a written report and briefing suitable for boards, agency leadership, legislative committees, or regulators. Because the profile is by function, a system that scores well overall cannot hide a function that is failing. And where the binding constraint lies outside the system being graded, the Grade says so, and states the ceiling it imposes.
How the scoring works
Each component, each relation, and the whole receive a score, and each score is weighted twice: by the consequence if it fails, and by how far upstream it sits (how much else depends on it). The example below uses a hospital emergency department. The numbers are invented to show the mechanics.
| Object | Type | Score | Consequence | Upstream |
|---|---|---|---|---|
| Component: triage protocol | Range | 8 / 10 | Medium | Low |
| Relation: ED to bed release | Range | 3 / 10 | High | High |
| Component: discharge planning | Range | 4 / 10 | High | High |
| Whole: current demand capacity | Range | 5 / 10 | High | — |
| Community placement (outside boundary) | Flag | — | High | High |
Read the table this way. The triage protocol scores well, and little depends on it: it is not where the problem is. The handoff between the emergency department and inpatient bed release scores poorly, matters greatly if it fails, and sits upstream of much of the rest, so it weighs heavily in the result. Some findings are not a matter of degree at all—such as a permission that should not exist, or a relation that is missing entirely—and a finding like that, if its consequence is high, caps the grade whatever the average.
The last row is not scored. Placement capacity in the community sits outside the department, but it is the binding constraint—patients cannot leave because there is nowhere for them to go. The Grade flags it and states what it means. Here the profile reads Triage 8, Flow 3, Discharge 4, and the overall grade is C, with the ceiling stated: nothing done inside the department moves the grade above B while the constraint sits outside it.
How it runs
The order of the work follows the order in which a system can be judged: first what it is meant to do, then how it holds together as a whole, then each part in its place and in relation to the rest. Every Grade therefore begins by settling the system's purpose and boundary. That first deliverable sets the access required, fixes the fee for the remaining work, and gives you a clean decision point on whether to proceed. Scoring comes last, once you have checked the map of the system and there is something solid to score against.
Charter
The Charter records the system, its purpose as you give it, a proposed boundary, and a not-to-exceed fee.
The signed charter.
First deliverable
We settle the system's purpose and boundary. The purpose is the standard every score is measured against, so it is drawn from the sources that establish it. With them comes an inventory of the access the work requires, and fixed fees for the remaining milestones.
The purpose and boundary judgment, and the access inventory.
Examination
The system is looked at first as it works in practice, rather than as it is described. Then every component and relation that can be reached is inventoried and examined individually: what it does, what depends on it, what it assumes, and whether its workings are tested against what actually happens. Nothing is sampled.
System map
Before anything is scored, you review the map of the system for errors of fact. We correct what the evidence confirms, and the map then stands as the basis for scoring.
The system map.
Draft report
Each component and relation is scored and weighted by consequence and by how much depends on it. The scores are drawn together into a profile by function and an overall grade, with any cap or ceiling stated. You review the draft for errors of fact, and may attach a written response to any finding. We correct the facts the evidence confirms. The findings change only on new evidence, not on request. Your response travels with the final report, together with our reply.
The draft report, with the profile and grade.
Final report
The report sets out the condition of the whole and how the score was reached, and is delivered in a briefing. The scores stand as the baseline the next Grade is measured against.
The final report and briefing.
What it asks of you
Your time at the start to frame the Charter, at the first deliverable to decide whether to proceed, at the system map and the draft for a factual review of each, and at the end for the briefing. Access across the system: its documents, the people who run each part of it, and the system itself in operation, including functions that did not raise the question. Where access is limited, the Grade says so, and nothing it could not see is scored. A named point of contact for the duration, since access is arranged many times over the course of the work. And the understanding that findings may land outside the department that raised the question: they are delivered to you unedited.
Terms
- Fee
- From $120,000 for a system within one department. From $200,000 for a multi-department or multi-site system. From $300,000 for a system spanning organizations, or one that is safety-critical.
- How it is set
- The Charter sets a not-to-exceed ceiling. With the first deliverable, we fix the fee for the remaining work based on the scope and complexity the inventory reveals. Fees are paid by milestone. They change only if the boundary or purpose changes, and are never contingent on findings.
- Timeline
- The first deliverable usually arrives within three weeks. The final report follows three to four months after your decision to proceed.
- Re-grade
- The same system in a later year: 55–65% of the original fee. The structure is already mapped and the scoring has a baseline to measure against.
- Public bodies
- Invoiced in arrears. This work is usually procured as an organizational assessment, an operational review, or a Public Systems Assessment. We supply the scope-of-services language your procurement office requires.
What it is not
Boards and oversight bodies already receive audits and management reviews. An audit tells them whether the rules were followed. A management review tells them how the system is performing. Neither tells them whether the system itself is sound—a system can pass its audit, meet its targets, and still be failing in places no one measures. A Grade gives the account of that: the condition of the whole, scored, part by part.
Where the sponsor needs to understand the system but does not need every fault located and scored, the product is a Reading. Where one specific fault needs to be diagnosed and its remedy defined, it is a Fault Investigation.
Begin with the situation
Tell us what you own and what the situation requires. We will confirm if a Grade is the right instrument, or direct you to the engagement that is.