Brand & positioning
AuraScore 83/100

Civic Program Voice and Accessibility Brand Specification

Establish plain-language standards, tone dimensions, and inclusive communication rules for public service delivery programs.

Deploy this specification when standardizing public agency communications across civic portals, notices, and community campaigns. It ensures consistent public trust and aligns editorial style with statutory accessibility standards.

Template

Role: Public Sector Communications Director specializing in civic clarity and plain-language design.

Context

  • Department or Agency: {{agency_name}}
  • Public Mandate: {{public_service_domain}}
  • Target Population: {{citizen_demographics}}
  • Literacy Benchmark: {{reading_comprehension_target}}
  • Sensitive Themes: {{sensitive_topic_areas}}
  • Distribution Channels: {{channel_mix}}

Task

Develop an accessibility-first verbal brand specification that establishes plain-language communication parameters, tone adaptations, and trauma-informed guidance for public agency touchpoints.

Method

  1. Translate {{public_service_domain}} and {{reading_comprehension_target}} into concrete vocabulary constraints and sentence complexity rules.
  2. Establish tone spectrum parameters spanning everyday operational notices to high-urgency crisis alerts.
  3. Map {{citizen_demographics}} to inclusive terminology standards, including gender-neutral framing and multilingual adaptation principles.
  4. Design communication guidelines for {{sensitive_topic_areas}} that balance regulatory accuracy with empathetic delivery.
  5. Set microcopy and instructional syntax standards for digital forms across {{channel_mix}}.
  6. Define a terminology substitution table replacing bureaucratic jargon with citizen-centric language.
  7. Detail review criteria for testing public clarity before publishing.

Constraints

  • MUST enforce {{reading_comprehension_target}} readability across all general public communications.
  • MUST NOT use legalistic disclaimers where plain language satisfies statutory mandates.
  • Prohibited terms list MUST contain at least 5 standard civil service idioms with direct replacements.
  • Tone boundaries MUST preserve institutional authority while avoiding punitive framing.

Output format

1. Tone & Register Spectrum

A four-part matrix defining Tone, Context, Allowed Phrasing, and Banned Phrasing.

2. Plain Language Rulebook

Five mandatory editorial rules with before-and-after civic examples.

3. Sensitive Context Protocol

Direct guidance for communicating {{sensitive_topic_areas}} (under 250 words).

4. Plain Language Terminology Index

Tabular glossary with 5+ bureaucratic terms mapped to accessible civic replacements.

Self-review

  • Ensure no passive voice exists in the before-and-after sample pairs.
  • Verify readability thresholds match {{reading_comprehension_target}}.
  • Confirm all sections maintain practical applicability for civil service writers.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

marketing
marketing-brand
public-sector-nonprofit
civic
voice-and-tone
accessibility