Three Cities, No Black-Box Score: A Municipal Advisory Comparison

Cross-jurisdiction briefs often fail at the point of compression. One city enacted a law. Another approved a request to a state legislature. A third adopted an ordinance with several application dates. Calling all three passed policies is concise and wrong.

A defensible advisory output keeps three layers separate: documented public evidence, analyst interpretation, and the client's eventual recommendation. The source layer should remain visible even when the engagement needs a short answer.

The decision-status matrix

New York City: enacted, then administered

The City Council's official history for Int. 1894-2020 records introduction, hearing, committee amendment, Council approval on November 10, 2021, charter-rule adoption, and return unsigned by the mayor. The enacted text used a January 1, 2023 effective date.

The administrative record continued. The Department of Consumer and Worker Protection's rule archive lists a May 6, 2023 rule effective date and a later updated entry. Its current program page says enforcement began July 5, 2023.

An advisory note can say the law is enacted and the agency began enforcement. It should not infer compliance by any company, legal validity in a specific fact pattern, enforcement intensity, or business impact from those records alone.

Boston: local support did not supply state authority

Boston's official project history records advisory work, public sessions, the mayor's February 2023 submission, and Council approval on March 8. The action was approval of a home-rule petition to the Massachusetts Legislature.

The Legislature's H.3744 history records referral, a hearing, reporting-date extensions, and placement with a study order in September 2024. The local vote therefore established Boston's approved request. It did not itself create an operative rent-stabilization rule.

A black-box score that treats Council approval as policy implementation would rank the case on the wrong authority. The dependency belongs in the main table, not in a footnote.

Austin: enacted, with staged practical dates

Austin's May 16, 2024 Council record publishes staff and commission drafts, recommendations, motion sheets, public comments, late backup, and the executed ordinance. The official minutes record approval as amended on a 9 to 2 vote.

Ordinance 20240516-006 took effect May 27. It separately applied to most covered applications filed on or after August 16, with a November 16 date for specified areas. A client brief that stores only one effective date will lose a material operational distinction.

Why one composite score obscures the work

A numerical policy momentum score could assign points for introduction, hearing, passage, and implementation. That would make the three records look comparable while hiding the feature that most changes the answer: who had authority to make the policy operative.

A visible matrix is more useful. It can show:

• Decision object: local law, home-rule request, or zoning ordinance
• Acting body: committee, council, executive, agency, or outside legislature
• Version: introduced, amended, approved, executed, or later rule
• Status: requested, enacted, operative, enforced, pending outside action, or superseded
• Dates: action, formal effect, application, enforcement, and last verification
• Unknowns: implementation, litigation, compliance, market effect, or facts outside the public record

The three-layer advisory brief

1. Evidence

Quote or paraphrase the exact public action, body, version, date, vote, and source. Keep official text and linked documents available for review.

2. Interpretation

Explain what the action means in the procedural model. Label any normalized stage, cross-record match, or status summary as an analyst classification rather than an official term.

3. Recommendation

Let the advisory team decide materiality, client exposure, strategy, and next steps using its subject-matter expertise and nonpublic facts. Do not make the data vendor's status code silently perform that professional judgment.

A review checklist before delivery

• Does every factual sentence have a direct source or a clearly labeled derivation?
• Does passed name the object that passed and the body that acted?
• Are introduced, amended, approved, enacted, effective, applied, and enforced separate events?
• Is outside authority displayed in the principal finding?
• Are current status and last verification date visible?
• Are missing facts and unresolved questions listed rather than scored as zero?
• Can a reviewer reproduce the sentence without relying on the analyst's private notes?

What this comparison supports

• Official records can support concise cross-jurisdiction briefs when authority and stage remain visible.
• A standard matrix can compare unlike procedural paths without declaring the policies equivalent.
• The evidence layer can be reused while interpretation and recommendations remain engagement-specific.

What it does not support

• No jurisdiction is ranked as favorable, risky, business-friendly, restrictive, or likely to act next.
• No policy effect, causal influence, stakeholder motive, or client exposure is established.
• No status summary replaces current legal, regulatory, economic, or operational review.
• The three purposefully selected cases are not representative.

Sources and method

Sources were checked through August 3, 2026. Each case was coded for decision object, body, version, local authority, outside dependency, formal effect, practical date, current status, and unknowns.

1. New York City: Council history and enacted text; agency rule archive; current agency implementation page.
2. Boston and Massachusetts: city project history; Council hearing notice; H.3744 history.
3. Austin: Council record and backup; minutes; executed ordinance.

This is a public-record advisory-method example. It is not legal, regulatory, investment, economic, political, or strategic advice.