Why these nine questions
An ERP project almost never breaks all at once. It drifts: one date slips, then a second, billing moves to hourly, one fix breaks something else, and the team who will have to use the system starts to distrust it. Any one of those is survivable. Together they form a pattern we see in nearly every rescue.
The first six questions are about what you can see: dates, money, code, data, people. The last three are about whether you can see it at all. A written weekly update, a tracker you can read, and a dated roadmap fix no bugs by themselves, but without them nobody can say whether the project is late, by how much, or what is left.
How the score is weighted
Technical and budget signals outweigh user friction: a team grumbling about a new interface is normal, basic workflows breaking after the partner called them done is not. The technical build carries 29 percent of the total, timeline and budget 26 percent, governance 24 percent, and people and adoption 20 percent.
The per-section breakdown appears with your result, against the 172 weighted points of the scale. A tool that hides its arithmetic is asking to be taken on faith.
What the score does not do
This is an indicator, not an audit. It reads nine answers, not your database or your git history. A high score tells you the pattern is present and worth a third party looking at; it does not tell you which line of code is at fault, or what stabilising it will cost. That takes reading the code.
And a low score is a real answer. If your answers show no red flags, do not buy an audit: the friction you are feeling is normal for an ERP rollout.