How 501c3.HELP Verifies State Nonprofit Compliance Requirements

Official-government-source evidence, not summaries of summaries

Every fact in a 501c3.HELP state guide is built from a primary or official secondary source: the state statute or regulation itself, an official agency instruction page, an official government form, or an official agency FAQ. Commercial compliance services, law-firm marketing pages, and general nonprofit blogs are never used as final evidence for a published claim. They may be useful for orientation during research, but a claim only becomes publishable once it is traced back to the government source that actually states it.

This matters because compliance requirements change: a fee changes, a form is replaced, an agency reorganizes. A fact that cites the actual current statute or agency page can be re-checked and re-verified directly; a fact that only cites someone else’s summary cannot.

Atomic facts with stable, sequential IDs

Instead of writing one long paragraph of prose per topic, each state guide is built from many small, independently verifiable facts, one for each distinct legal question. Washington’s guide, for example, keeps "file the corporate annual report" and "renew charitable registration" as two entirely separate facts with two separate deadline formulas, rather than merging them into one generic "annual filing" statement, because merging them would hide the fact that they use different calendars and different fees.

Every fact and every source gets a stable identifier that is never renumbered once assigned. In the underlying structured data, a fact’s identifier is built from the state abbreviation plus a canonical fact key (for example, wa.formation.entity_type or ny.solicitation.renewal), so the same kind of requirement can be compared, or eventually cross-referenced, across every state that has it.

Two labels that are never merged

A fact carries a requirement status, meaning what the law or agency process actually requires: required, conditional, not required, application-required, and several other precise values. That status is completely independent of how confident the research is in that finding.

Confidence is tracked separately as verification status. A fact reaches SOURCE VERIFIED only once every claim in it has at least one citation with a written evidence summary (a plain description of what the source actually says, never a copied passage) and a recorded date the research was last checked against that source. A fact that the research team could not fully confirm from official sources, often because the official material is silent on an edge case or because a statute contains an unresolved gap, is instead marked VERIFICATION IN PROGRESS and stays visible on the public page with that qualified label, rather than being hidden or quietly rounded up to a confident answer.

Massachusetts's ST-2 sales tax exemption certificate is a good example of why this separation matters. Current law makes the certificate effective for 10 years and requires the Department of Revenue to give notice 90 days before it expires, and both of those are source-verified. The exact submission path for the renewal itself is not clearly stated in the current public operational materials, so that one fact is held at VERIFICATION IN PROGRESS with its own safe approach on the card, while the 10-year duration is published with full confidence, in the same record.

Exact thresholds, exact fees, exact deadlines, never rounded

Comparison operators are preserved exactly as the underlying law states them. New York’s charity audit-threshold statute, for instance, contains a facial gap at exactly $250,000 between its CPA-review clause and its unaudited-report clause. The guide states that gap explicitly as an open question rather than silently assigning $250,000 to one side or the other.

Deadlines are modeled with an explicit rule type: a fixed calendar date, a date relative to the organization’s own fiscal year end, an anniversary-month rule, an event-triggered countdown, or a combination. None of it is flattened into a single vague word like "annual." Washington’s charity renewal (last business day of the eleventh month after fiscal year end) and its corporate annual report (last day of the anniversary month) are kept as two different rule types for exactly this reason.

When an official source affirmatively states there is no fee, as Washington’s Articles of Dissolution filing does, that is recorded as "no filing fee," never as a guessed $0 filled in because a source happened to be silent. The two are treated as materially different claims.

Contradiction logs and correction passes

Every state’s research includes a contradiction-and-ambiguity log, a record of places where two official-seeming sources appeared to disagree (an older form using superseded terminology, a legacy page describing a print/mail process a current rule has since moved online) and the reasoning used to decide which source controls. This log is kept rather than silently resolved and discarded, so a future reviewer can see why a particular reading was chosen.

Sources themselves carry a lifecycle status independent of the facts they support: active, or needs_recheck when a specific page shows a workflow, portal, or fee inconsistency worth flagging for re-confirmation. A fact cannot sit at the most confident approval tier while citing a source flagged that way; it has to be re-verified or the source has to be resolved first.

Validation before anything is published

Before a state’s data reaches a public page, it passes three separate checks. First, schema validation confirms every fact and source has the required fields in the correct shape. A fee, a deadline rule, or a citation missing a required piece fails immediately. Second, cross-reference validation confirms every citation actually points to a source that exists in that state’s own source list (or the shared federal-source registry), that every fact ID is unique and correctly formed, and that a state cannot be marked published unless it has at least one fact that has cleared the evidentiary bar the public page is allowed to render. Third, a rendering test builds the actual public page and checks that verification labels, fact anchors, and citation links appear correctly, using the same test suite that runs on every production build.

Only after all three checks pass does a state’s guide, or a compliance-update article like this one, become eligible to generate a live public page. The same discipline applies to the articles in this Compliance Updates section: every material legal statement here is required to trace back to a fact and a source in a published, currently-valid state guide. This article does not introduce any new legal conclusion of its own.