Constitution
§9.5.a — Compliance Standards and Findings
Read the operative provision in the annotated Constitution.
Open provision →The LM's Year 11 annual legislative audit measured the Legislature's revenue-projection accuracy against the fiscal-accuracy standard the JMC had published for that audit category the year before — a standard the JMC, not the LM alone, had defined and made public in advance, together with the methodology behind it. Revenue projections had overstated collections in seven of the prior nine budget cycles, by an average of 6.2%. Against the published standard, the aspect failed.
The Fail was published to the NRS on a Wednesday, under §9.5.a, and reported to Assembly leadership — the body responsible for that aspect. §9.5.a required the responsible body to publish its own account within the period defined by statute. It did not require agreement with the finding or a prescribed remediation plan. The finding existed permanently and publicly, on a record built from a standard the Assembly had known about since before the audit began.
The Assembly leadership initially argued the LM's methodology was flawed — that revenue projections inherently involve uncertainty and that the standard was set too strictly. The argument had nowhere to land. The standard and its methodology had been published by the JMC, jointly, before the audit cycle began; the Legislature had exactly as much opportunity to contest it then as any citizen reading the NRS did. Disputing it now, after failing it, read as what it was.
Two months later, the Assembly published its own account of the matter, as §9.5.a requires the responsible body to do. It committed to an independent revenue-forecasting methodology review, Monetary Authority co-certification of projections for the next three budget cycles, and LM verification of each cycle before tabling. Those policy commitments were its own choices. The Assembly published them because a Fail sitting alone on the permanent record, unanswered, is a worse thing to run on at the next election than a Fail with a stated plan attached to it.
This scenario demonstrates the LM functioning correctly. Three Monitors operating independently, publishing findings continuously, against standards fixed and made public before the fact — creating a permanent NRS record of government performance that no political actor, including the audited one, ever gets to edit, dispute after the fact, or force silent.
§9.7.a addresses serious misconduct or abuse of office by a Monitor General. Where two Monitor Generals jointly determine that the third has engaged in it, they publish the determination with its stated evidence, and the affected Monitor General’s authority is suspended immediately. Disagreeing with a Monitor’s findings — including a Fail like the Year 11 finding above — is not grounds. The affected Monitor General may seek expedited SC review limited to lawful invocation and whether the stated evidence concerns serious misconduct or abuse of office. The most senior eligible member of the affected Monitor’s candidate pool by continuous pool tenure who accepts designation serves as Acting Monitor General, who may not be appointed as successor to the Monitor General for whom they act. Suspension is not removal; removal is governed exclusively by §9.9.
The annual audit cycle is more responsive than a scheduled periodic review. The LM's Year 11 Fail was possible because the Monitor had been tracking the pattern continuously — not waiting for a scheduled moment to look. Had the Assembly done nothing at all, the next audit would simply have reported the same Fail again, on the same public record, under the same standard. Nothing in the constitution would have forced their hand. The Legislature's actual exposure was never to the Monitor — it was to the voters reading the record, and to whatever the Assembly itself chose to do about a Civic Consul or colleagues presiding over a Legislature that kept failing its own fiscal-accuracy test and never answered for it.