Regulatory Radar is a structured record and review workflow. Watched sources and logged changes are entered by your team.A watch with a URL can also opt into auto-check (off by default). Once a day, WriterzRoom reads the page at that URL and compares its readable text with the previous reading; Check now does the same on demand. When the text differs, a change is opened for review, marked Detected by check — not assessed, with a placeholder severity. Before a detected change can be marked reviewed or actioned, a reviewer sets its real severity; dismissing it needs none. The check establishes only that the text at the URL changed. It does not read the document, judge whether the change is material, or decide what it affects — that remains your team’s call. Auto-check is off by default because a sign-in-walled portal or a page that re-renders a timestamp would otherwise open a review item on every check. Private and internal network addresses are refused.
Watched Sources
A watched source is an agency, standard, law, or body of guidance — for example the SEC, the FDA, or GDPR — optionally scoped to a vertical and jurisdiction, with a reference URL and notes. Inactive sources stay in the record without contributing to the open-review counts.Logging a Change
A change is logged against a specific watched source, with:- A title and summary of what changed
- A source URL and effective date
- A severity —
critical,high,moderate, orinformational - Whether it requires review
new; a reviewer marks it reviewed or dismissed. The dashboard tallies active watched sources, changes still awaiting review, and open critical-or-high severity changes separately, so a backlog of informational items doesn’t bury something that needs immediate attention.
Supervised regulatory cases
A logged change can be assessed in a versioned regulatory case. The case keeps its program, change, evidence, reviewer assignment, actions, proposal versions, and closure review together. Regulatory Cases, under Govern in the sidebar, lists your cases and assigned reviews first, each with its status, review mode, and last update. Open a case starts a new one; program setup sits below the list. A case page keeps its status, revision, and closure readiness in the header, links to its Assessment, Actions, Evidence, and History sections, and keeps the closure checklist and decision beside every section. A case whose closure no longer matches its evidence or reviewer eligibility is flagged at the top, and a viewer who cannot decide an in-review case is told so. Closing a case and approving publication are separate decisions: a closed case never substitutes for an exact-artifact release approval. Case and proposal decisions also create immutable decision versions. Each version records the actor, reason, case revision, input token, exact snapshot, and snapshot hash. Successful publication authorization creates a separate immutable release manifest, including the exact artifact, destinations, applicable policy layers, evidence, reviewer decisions, and current qualification attestations. Workspace administrators can attest a designated reviewer’s role with evidence and an optional expiry. Once an attestation exists for that member and role, expiry or revocation blocks new assignment, decisions, and release until a new attestation is recorded. A role designation without any attestation keeps the previous workspace behavior. Corrections are append-only explanations attached to the affected case, decision, proposal, case policy, or release manifest. A correction never silently edits the original: the server stores the authoritative target snapshot and its hash, and rejects a stale client snapshot. It is case-local by default; organization reuse requires an administrator or owner, an organization already recorded on the case, and explicit rights confirmation. Export complete history downloads every authorized application-history record for the case, including untruncated case events, proposal and decision versions, corrections, case-policy versions, release manifests and events, and generation admissions. If the case exceeds the safe JSON export limit, WriterzRoom rejects the request instead of returning a misleading partial record.Content Requests
Route a regulatory change into a content update through intake.
Verified Claims
Retire or rescope a claim once a regulatory change affects it.