Systems Audit Siesie
Twelve questions
The weighting is published because a score you cannot check is a score you cannot use.
Each question is worth 0 to 4 points, multiplied by the weight below. Owner dependence and invoicing carry the heaviest weight because both stop money: work that halts when you are away, and work already finished that never gets paid for. Follow-up and re-entered information carry less, because those cost time and margin rather than the job itself.
The arithmetic. Your score is the points you earned divided by the points that were available, as a percentage. A question you skip is left out of both halves, so a partial run is scored against what you actually answered rather than marked down for what you did not reach.
score = earned ÷ available × 100
Gaps are ranked by what each one costs, which is (4 − your points) × weight. That is why a heavy area answered badly always sits above a light one, and why two people with the same score can get a different first move.
Nothing here is a benchmark against other businesses. There is no dataset behind this and it would be dishonest to imply one. It is a structured read of twelve answers you gave, and the value is in the order it puts them in.
Twelve answers show you the shape. The map shows you the business.
The audit works from what you can recall in four minutes. The Operations Map works from what actually happens: every handoff drawn, every task that still waits on you named, timed and costed, and the build that removes them, in the order it should happen. It is credited in full against a Siesie build.