CenterPointe — Requirements Source of Truth

Last updated: 2026-05-07 (post-discovery call — added 6 features, 1 audience path, updated org stats) Purpose: One canonical list of every page, feature, constraint, and audience path that's been agreed to or requested. This is the spec every artifact (flowchart, wireframes, design comps, CMS build) gets graded against.

Legend: - Source: which file/meeting/doc the line came from - Stated by: Client (asked for it) · G&M-rec (we recommended, not yet confirmed) · G&M-confirmed (we recommended, client agreed) · Proposal (in signed scope) - Phase: which phase the requirement is verified against — IA (flowchart), Wireframes, Design, CMS, SEO, QA - Status: Confirmed · Pending · Deferred · Open

When reviewing a flowchart, filter to Phase: IA rows. Anything in those rows that the artifact doesn't reflect is a gap.


Header / Navigation Structure

Locked when nav is decided (often kickoff). Update if it changes.

Main nav: TBD

Header secondary nav: TBD (often Donate / Careers / Translation toggle / Search affordance)

Search affordance: TBD


Site Anchors

Item Value Source
Total pages allowed in design (cap) from proposal notes.md
ACF modules allowed (cap) from proposal notes.md
Custom post types allowed (cap) from proposal notes.md
Programs / sections to represent from discovery source
Sites consolidated (if any) from proposal notes.md
Tagline / mission line from discovery source
Primary audience to grow from discovery source

Required Pages (IA)

The page roster lives in SITE-ROSTER.md — it has the full list of URLs, templates, and per-phase build status. This doc is for decisions about pages (caps, audience paths, what NOT to build); SITE-ROSTER is the canonical "what pages exist."

When a page changes status (added, removed, renamed), update SITE-ROSTER. Update REQUIREMENTS only if the change affects a decision (cap math, audience path, constraint).


Features

Feature Stated by Source Phase Status Notes
Federal-language word filter (real-time, fail-safe) Client 2026-05-07 discovery CMS Confirmed New administration restricts terms like "harm reduction" and certain LGBTQ phrasing. Catch prohibited words BEFORE publish. AI-powered (~$30/mo token cost). Marin to send the word list.
AI-powered intake / program-matcher G&M-rec → Client agreed 2026-05-07 discovery Strategy → CMS Confirmed Users don't know which of 40+ programs they need. Few-question quiz routes them to the right intake.
BlackBaud integration for email lists Client 2026-05-07 discovery CMS Confirmed Currently manual export/import. Eric to get login or screenshots before May 19 to confirm scope.
Event registrations Client 2026-05-07 discovery CMS Confirmed Currently runs through site. Decide payment processor: Nelnet (current), BlackBaud, or Stripe.
Sticky/persistent 24/7 crisis bar G&M-rec → Client agreed 2026-05-07 discovery Design / CMS Confirmed Marin: "If someone was in crisis, that could pop up right away." Keyboard + screen-reader accessible.
Training videos (Loom walkthroughs) G&M deliverable 2026-05-07 discovery Launch Confirmed Brooke records dashboard walkthroughs as part of handoff.
Easy-to-edit modular CMS Client 2026-05-07 discovery CMS Confirmed "Staff changes, leadership changes, program changes" — they edit a lot. ACF flexible content.
Donor storytelling alongside healthcare focus Client 2026-05-07 discovery Strategy Confirmed Site has to do both jobs without one drowning the other.
Three-front-doors IA (patient/referrer/donor) G&M-rec Scout brief Strategy Pending Pitched in scout brief, not directly confirmed on call. Validate at strategy phase.

Audience Paths

These are the user journeys the IA must actually support. If the flowchart doesn't have a path for one of these, that's a gap.

Audience Journey Source Notes
Person seeking help (or family member) Land → understand they're in the right place → find the right service (mental health / SUD / primary care / housing / crisis) → get to walk-in info, intake form, or 24/7 line G&M-rec, scout brief Crisis line must be reachable from every page. Walk-in hours, sliding-fee, "no insurance? we can help" should be near the top of the help path.
Referrer (clinician, social worker, law enforcement, school) Land → confirm services + eligibility + service area → submit referral / get fax line G&M-rec, scout brief Lincoln PD co-responder partnership and SquareOne suggest referrer traffic is meaningful.
Donor / funder / community partner Land → understand impact → donate or learn about partnership / events (Centered Together) G&M-rec, scout brief Impact dashboard (6,265 served / 247 housing units / 3,330 crisis calls) sits here.
Job seeker Land → see day-in-the-life / mission framing → apply G&M-rec, scout brief Behavioral health hiring is brutal; current site treats Careers as a footer link.
Press / reporter Land → press kit, recent news, leadership bios, contact for media Existing site has this Currently /about/press-room/ — link list, no Article schema.
Person in crisis (988 caller) Receives 988 routing → may also visit site for follow-up resources, walk-in info, or to refer family 2026-05-07 discovery CenterPointe operates Lincoln's 988 line. Crisis users are real on-site traffic, not hypothetical.

Brand & Voice Constraints

Constraint Source Notes
Color palette Brand guide
Typography Brand guide
Tone direction Discovery

Constraints / Defaults (what NOT to build)

Don't Why Source
Don't install an accessibility overlay (AccessiBe, UserWay, AudioEye, EqualWeb) FTC fined AccessiBe $1M April 2025; 22.6% of sites sued in 2025 already had overlays installed; HHS OCR doesn't accept them as compliance evidence; courts in Murphy v. Eyebobs and LightHouse v. ADP explicitly named them as inadequate. Scout brief, FTC consent order
Don't use ACF url field type Project default — text type works around the placeholder save issue. G&M default per CLAUDE.md
Don't ship anything below WCAG 2.1 AA HHS Section 504 final rule, May 11, 2026 deadline. CenterPointe is HHS-funded, 188+ employees, CCBHC certified — squarely in scope. HHS Section 504 final rule
Don't bury the 24/7 crisis line Currently small text in header. Sticky/persistent crisis bar is a UX + accessibility win. Competitors (Bridge, Community Alliance) do this. Scout brief
Don't lead with "About" in the global nav Person in crisis lands and sees About before Get Help. Three-front-doors IA (patient / referrer / donor) should drive the nav. Scout brief

Design Decisions Deferred to Designer

Item Why deferred Source
TBD

Open Decisions (rolling list — answer each, don't lose any)

# Question Owner Phase impact Source Status
1 Has any accessibility complaint, demand letter, or HHS OCR notice already arrived? Marin Pre-engagement Scout brief ~~Open~~ Did not surface on call — ask before proposal lands
2 Has counsel given a position on Section 504? Marin Pre-engagement Scout brief ~~Open~~ Did not surface on call — ask before proposal lands
3 Locked into Firespring contractually, or is exit on the table? Marin Engagement shape Scout brief Open — ask before proposal
4 What does the ED need to walk into the May 12 board / staff meeting saying? Marin Pitch framing Scout brief Superseded — they're focused on proposal review and vendor comparison, not a single-meeting deliverable
5 Budget shape for short-term posture + long-term rebuild Marin Quote Scout brief Open — never directly discussed; budget conversation is alive
6 Brand handling: match existing / refresh / full rebrand Marin Design Standard kickoff ask Open — did not come up; ask in proposal phase
7 Grant web@grainandmortar.com admin on current site for content audit Marin Discovery Standard kickoff ask Open — ask in proposal package
8 Top traffic pages and intake-conversion data from current Firespring analytics Marin IA priority Scout brief Open
9 Who owns content updates internally today (40+ program pages) Marin CMS governance Scout brief Confirmed — Marin's team edits frequently across staff/leadership/program changes. ACF flex content is the right fit.
10 CCBHC reporting cadence and whether the website should feed any of that data Marin CMS, dashboards Scout brief Open — Marin didn't mention CCBHC explicitly
11 Megan's last name and email address G&M Contacts 2026-05-07 discovery Open — confirm before sending proposal
12 Federal-language restriction word list Marin Word filter scope 2026-05-07 discovery Open — Marin to send
13 BlackBaud login or screenshots for integration scoping Marin / Eric Quote 2026-05-07 discovery Open — Eric to follow up before May 19
14 Payment processor preference for events: Nelnet (current), BlackBaud, or Stripe Marin CMS / events 2026-05-07 discovery Open

Source Documents

Source Path Date
Original proposal scope notes.md signing date
Project hub README.md current
Pre-call Scout brief assets/2026-05-07-scout-brief.html 2026-05-07
Inbound inquiry email Gmail thread subject:"Project Inquiry" Marin King 2026-04-30 → ongoing
HHS Section 504 final rule https://www.hhs.gov/sites/default/files/new-requirements-accessibility-web-content-mobile-apps-kiosks.pdf 2024-07-08 (effective 2026-05-11 for 15+ employee recipients)
FTC v. accessiBe consent order https://search.ftc.gov/legal-library/browse/cases-proceedings/2223156-accessibe-inc 2025-04-21

How to use this doc

Before sending any client artifact (flowchart, wireframe, design comp, CMS preview): 1. Filter this doc to the rows tagged with the current phase 2. Walk through every Confirmed row — does the artifact reflect it? 3. Walk through Pending/Open rows — does the artifact resolve any of them, or punt them clearly? 4. Anything in Constraints/Defaults — does the artifact violate it? 5. Audience Paths — can you trace each one through the artifact?

When new info comes in (meeting, email, Basecamp message): 1. Add new requirements to the right table with Source citation 2. Move Open Decisions to Confirmed when answered 3. Update Last updated at the top 4. Don't delete superseded info — strike it through and note when/why it changed