How we research and verify procedural content.

1. Start with one real process question

Each guide is scoped to one task a self-represented court user may need to complete, such as verifying a defendant name, checking service, organizing exhibits, preparing for a hearing, or collecting a judgment. We avoid stretching one keyword into multiple pages that answer the same question.

2. Prefer primary court and government sources

We prioritize state judiciary self-help pages, official forms, court rules pages, and government resources. Third-party summaries are not used as the controlling source for a state-specific limit, form, deadline, service method, appeal rule, or collection procedure.

3. Separate nationwide process from state-specific rules

General workflow may be described across jurisdictions, but dollar limits, filing fees, service timing, e-filing requirements, appeal rights, and enforcement tools are not presented as nationwide constants. A state example is labeled, and the filing court remains the final procedural check.

4. Build a source trail instead of copying a summary

Guides explain what a reader should verify, what record can support that check, what administrative failure can occur, and which official source to consult next. The goal is to add a usable process framework rather than rewrite a court page in different words.

5. Review for duplication and generated-template artifacts

Content QA checks duplicate titles, slugs, headings, repeated long sentences, source keys, and cross-article 6-gram similarity. Structural variety is also reviewed so a batch of articles does not rely on one rigid heading pattern with only the keyword changed.

6. Update only when there is a real reason

An article update date should reflect a substantive review or revision. A changed form, official page, statewide e-filing rule, service instruction, or enforcement procedure can trigger review of affected pages; dates are not refreshed merely to make old content appear new.