CiVQ Knowledge Guide
Modules · Operations tier

Codification / Municipal Code

Author the municipal code as a tree of titles, chapters, and sections — each section carrying bilingual legal text with full version history.

Resident-facingOperations tierBilingual EN / ES

Titles hold chapters, chapters hold sections, and each section carries bilingual legal text with a citation number. Amending a section snapshots its prior text into the version history; staff batch edits into a supplement and publish them live all at once, so residents always read the current code.

What you can do

Structure

Build the code tree

Create titles (e.g. "Title 5 — Public Safety"), expand a title to add chapters, and expand a chapter to add sections.

Sections

Author bilingual sections

Give each section a citation number, an EN/ES heading, and EN/ES body text. New sections start as drafts.

History

Amend with version history

Amending a section snapshots its prior text; every section shows its version number so the change record is intact.

Supplements

Stage & publish supplements

Batch edits into a supplement and publish them live at once; the dashboard tracks draft supplements.

Lifecycle

Repeal sections

From a section's detail page, amend it, repeal it, or stage it into a supplement — each with its own status badge.

Overview

See the code at a glance

KPIs track titles, chapters, published sections, and draft supplements across the whole code.

A typical workflow

  1. Create a title — give it a number and an EN/ES name (e.g. "Title 5 — Public Safety").
  2. Add a chapter — expand the title and add a numbered chapter with an EN/ES name (e.g. "Ch. 5.12 — Noise").
  3. Add sections — expand the chapter and add sections with a citation number, EN/ES heading, and EN/ES body. They start as drafts.
  4. Amend over time — amending a section snapshots its prior text and bumps the version number.
  5. Stage & publish a supplement — batch the edits into a supplement and publish them live at once.

A closer look

In practice
The home view is an expandable tree: titles open to their chapters, chapters open to their sections. Each section row shows its citation number, heading, a Draft or status badge, and a version number, and links to its detail page to amend, repeal, or stage into a supplement. New title, Add chapter, and Add section open modals (both languages required, §18); KPIs read Titles, Chapters, Published sections, and Draft supplements.
Where it lives
Staff: /dashboard/codification, with each section at /dashboard/codification/sections/<id> for amendments, version history, and supplements. Residents read the published code on the public site.

Works with

Agenda for the meetings that adopt ordinances · Meetings for the public record · Records for public-information requests.

CiVQ
Bilingual civic software for local government — own it or rent it.
Product
Products Pricing Why CiVQ Bilingual
Company
About Contact Platform guide API docs
Legal
Privacy Terms Accessibility
© 2026 CiVQ · Pragmatic Business Solutions, LLC — Rio Grande City, TexasKnowledge Guide
×
↑↓ to navigate↵ to openesc to close