MCC Rule Change and Public Consultation Procedure v1.0

Instrument: Procedure implementing MCC-001 cl. 0078–0097 (document hierarchy and amendment), MCC-100 v2.2 cl. 0054 (stakeholder consultation), MCC-200 v2.0 Section 3 and cl. 0109–0110 (methodology approval and revision), MCC-700 v3.1 §17, and FD-2026-08-24 item D16 (change discipline) Tier: 5 procedure; it changes no rule, it says how rules are changed Status: v1.0 DRAFT for adoption under FD-2026-08-24 item 3 — NOT ADOPTED Prepared: 25 August 2026

---

1. What this procedure covers

Every change to a programme document with normative effect: the Charter (Tier 1), MCC-700 (Tier 2), the MCC-100 series and its annexes (Tier 3), MCC-200 and the methodologies (Tier 4), and the operational policies, procedures, templates and guidance (Tier 5). It also covers errata (corrections that change no rule) and editorial changes (typography, cross-references), which follow the light path in §7.

It does not cover decisions about individual projects, VVBs or units — those are governance decisions under MCC-700 §11 with their own appeal route.

2. The rules this procedure applies

Tier	Instrument	Proposer	Decision	Threshold	Public notice / consultation	Entry into force
1	MCC-001 Charter	Board; any stakeholder via the Board	Board	Two-thirds of all appointed members (Charter Am1 / MCC-700 Am1 pending; cl. 0093 today)	90 days + at least one public stakeholder forum (cl. 0090–0091)	≥ 30 days after approval (cl. 0095)
2	MCC-700	Board, Standards Committee, affected stakeholder (§17.1)	Board	Two-thirds of votes cast (pending) / 75 % (v3.1)	60 days (Charter cl. 0080)	date fixed in the amendment
3	MCC-100 series, annexes, Definitions Register	Board or delegated committee; administration	Board or delegated committee (cl. 0081)	Two-thirds of votes cast (pending)	30 days (cl. 0054, 0081)	date fixed; ≥ 14 days after adoption
4	MCC-200; methodologies M001–M0xx	Standards Committee; methodology developer	Standards Committee (Board acting in its stead until appointed)	New / major: two-thirds (MCC-200 cl. 0109 says 75 % — aligned by MCC-700 Am1); minor: simple majority	30 days + external peer review (MCC-200 cl. 0040)	date fixed
5	Policies, procedures, templates, guidance	Administration (operational team)	Administration with Board oversight (cl. 0083)	—	14 days	date fixed

Where texts conflict, the higher tier prevails (cl. 0084); pending the D11 amendments, the stricter threshold is applied and minuted.

3. A proposal

A change proposal is a file in 00_Styring_og_Vedtak/ (or 02_Metodikk/ for Tier 4) named <Doc>_Amendment<N>_<slug>_v0.x_UTKAST.md, containing: (a) the instrument and version amended; (b) each change as current text → proposed text with the clause number; (c) the reason, with the audit finding, incident, decision or external development that prompted it; (d) impact on other documents, on the platform (routes, guards, migrations) and on registered projects (transition rule); (e) the tier, decision body and notice period claimed; (f) the proposed entry-into-force rule. The MCC-700 Amendment 1 draft (25 Aug 2026) is the reference form.

4. The consultation, in the platform

1. Open. Staff create the consultation at /portal/admin/consultations with the proposal attached (hash recorded), the tier, the notice period (the module enforces the 30-day floor; 60 and 90 are set explicitly), the decision body and the closing date. The public record appears at /consultations and in the sitemap; the notice is posted on /news and sent to the stakeholder list.
2. Comment. Anyone may comment (rate-limited, same-origin, no login); comments are public with author name, and the author's e-mail is never shown. Comments are categorised on submission (support / objection / amendment / question / other).
3. Forum (Tier 1 only). At least one public stakeholder forum during the period (cl. 0091); notes published as a consultation document.
4. Respond. Staff record a written response to every material comment before closing (cl. 0092 for Tier 1; the same practice for all tiers). "Material" means it proposes a different text, disputes a fact, or raises an effect the proposal did not consider.
5. Close. The closing protocol records: number of comments by category, the responses, changes made to the proposal as a result, and the recommendation to the decision body. The protocol is published on the consultation page.

5. Decision and adoption

The decision body votes on the final text with the closing protocol before it; the vote is minuted by name (MCC-700 §12.2). The adoption instrument states the version number, the entry-into-force date and the transition rule for registered projects and open engagements (non-retroactivity unless integrity requires otherwise, MCC-700 §18.2).

6. Version bump, publication, archive (D16)

On adoption the administration: assigns the new version (major for scope or quantification changes, minor otherwise; MCC-200 cl. 0110); consolidates the text with a change log naming the instrument and date; publishes the file on /transparency/documents with its SHA-256 in the manifest (the platform refuses a listing without a hash); archives the superseded version in 99_Arkiv/ with a cover sheet naming the successor; updates the Definitions Register if a term changed; and, where the platform enforces the rule, ships the code or migration that makes the platform agree with the text in the same release, referenced in the change log. No document is published as adopted without the vote reference; no document is changed in place without a version bump (the fabricated decision references annulled under D16 are the reason this rule exists).

7. Errata and editorial changes

An erratum corrects a calculation, a cross-reference or a factual statement without changing what the rule requires (Guidance Errata No. 1 is the reference form). It follows the Tier 5 path — 14 days' notice on /consultations, administration adoption, version bump to the next minor — whatever the tier of the corrected document, unless the correction changes a threshold, a quantity or an obligation, in which case it is an amendment under §2. Editorial changes (typography, renumbering, broken links) are made with a change-log line and no notice.

8. Emergency changes

Where a rule as written causes an integrity failure (a unit could issue that should not, a claim could be made that is false), the administration may suspend the operation of the clause immediately by public notice on /news, refer the matter to the decision body within 5 business days, and run the ordinary procedure in parallel. A suspension never widens what is permitted.

9. Register of changes

The administration maintains a change register (00_Styring_og_Vedtak/MCC_Change_Register.md, to be created at first adoption under this procedure) listing every proposal, its consultation id, decision reference, version and publication hash, so that the state of the rulebook on any date can be reconstructed.

Change log — v1.0 DRAFT (25 Aug 2026): first issue.