Skip to content
RelySign in

Request coverage

Missing a program, a state overlay, a limit table or a specific rule? Requests are how we decide what to acquire next, so the question you were trying to answer matters more than the label you put on the gap. What this covers, and what it does not sets out the known boundaries first — your gap may already be named there, which is still worth telling us.

What happens to this

  1. We fetch the agency’s own documents — the code, the regulation, the compliance manual, the limit schedule — and hash each one.
  2. Each is checked for being genuinely readable: a page that returns a bot wall, a PDF that extracts as nonsense, or a republisher serving old law under a “latest version” label is rejected rather than quoted.
  3. Rules are written only from text we could actually read, each carrying a verbatim quote and a locator specific enough to follow.
  4. Whatever we could not reach is recorded as an open question against that jurisdiction, and shows on the coverage page. A gap we know about is stated; it is never filled in from memory.

No date is promised. Some agencies publish nothing, and some publish only behind a paywall — when that is the answer, we say so rather than going quiet.