Who can do this: City Administrator. Pick the person to act as them from Demo controls.

Go to Rules and fees

1. Run a what-if as described in the guide on what-ifs.
2. On the results page, under "Draft handoff", click "Save as a draft rule change".
3. Read the table. The draft is in force nowhere. It lists its author and who can approve it.
4. Click "Open the draft", or open "Rules and fees" in the left menu and choose the view Drafts.
5. Select the draft version and click "Submit for review".
6. Click "Approve version". Tick the box that confirms you wrote the version, give a reason and submit. The record says "Approved by the author (single-administrator policy)".
7. Click "Publish version". The draft becomes the version in force.
8. The line "Approval policy: single administrator" at the top of Rules and fees shows which policy applies. A city can switch to independent approval. Then the author of a version cannot approve or publish it, the buttons "Approve version" and "Publish version" are guarded for the author, and the reason reads "You authored this version; another administrator must approve it." beside "Approve version" and "You authored this version; another administrator must publish it." beside "Publish version". A second administrator then does both steps.

What you get: Nothing changes in the live rules until the version is approved and published. Under the single-administrator policy, which is the default, one City Administrator can do all of it with the demo persona, and the history and the audit log record that the author approved it. The city sets the policy in config/approval_policy.json, and the environment variable ACME_APPROVAL_POLICY overrides it.

All how-to guides