Appearance
Regulatory Sources
Where to find it: Regulatory Compliance, then Regulatory Sources (/reg-intel/sources).
The Source Registry is the record of what OrviQ watches on your behalf. It is also, in its own right, evidence that you maintain a regulatory horizon-scanning process — which many supervisory regimes expect you to demonstrate.
What a source record contains
| Field | Purpose |
|---|---|
| Authority | The supervisory body or standards organisation that publishes here |
| Name | A human-recognisable label, for example "Circulars and Notices" |
| Source type | webpage, document_feed or manual |
| Location | The address or feed being monitored |
| Status | active, paused or retired |
| Last checked | When the source was last swept |
| Owner | Who is accountable for this source remaining correct |
Choosing a source type
| Type | Use when | Trade-off |
|---|---|---|
document_feed | The authority publishes a structured feed | Most reliable; least noise |
webpage | Only a human-readable page exists | Can generate change events for cosmetic edits |
manual | Updates arrive by email, portal login or post | No automated detection; a person records the update, which is still fully audited |
Prefer feeds where they exist
A page monitored as webpage will report a change when the authority updates a footer or rotates a banner. If the same content is available as a feed, register the feed instead and retire the page.
How to register a source
- Open Regulatory Sources.
- Select Add source.
- Choose the authority. If it is not listed, the authority set is administered centrally.
- Give the source a clear name — something a colleague will recognise in two years.
- Choose the source type and provide the location.
- Set the status to
active. - Save, then use Check now to establish a baseline.
Requires reg_intel.manage.
Maintaining the register
Review it on a cadence. Authorities reorganise their websites. A source that has reported no change in eighteen months is more likely broken than the authority silent.
Pause rather than delete. Setting a source to paused keeps the record and its history while stopping sweeps. Use it for seasonal or consultation-specific sources.
Retire deliberately. retired records why monitoring stopped and preserves the historical trail — useful when an auditor asks how far back your scanning coverage extends.
Sweeps
A sweep runs across active sources for your tenant and produces change events where something is detected.
- Check now sweeps a single source immediately.
- Sweep runs across all active sources. Requires
reg_intel.sweep.
Sweeps are technical executions. They do not appear on the GRC Calendar, which is reserved for meaningful governance obligations rather than machine schedules.
Permissions
| Action | Permission |
|---|---|
| View the register | reg_intel.read |
| Add, edit, pause or retire a source | reg_intel.manage |
| Run a sweep | reg_intel.sweep |
Example
A regional bank supervised in two jurisdictions maintains fourteen sources:
| Authority | Source | Type |
|---|---|---|
| Primary prudential supervisor | Circulars | document_feed |
| Primary prudential supervisor | Consultation papers | webpage |
| Primary prudential supervisor | Enforcement actions | document_feed |
| Data protection authority | Guidance | webpage |
| Payments scheme | Operating bulletins | manual |
The payments scheme publishes only to an authenticated member portal, so it is registered as manual: the Operations lead records each bulletin as it arrives. The record is no less auditable for being manually maintained — it carries the same actor, timestamp and triage history.
Troubleshooting
"Last checked has not moved." The source is paused or retired, or no sweep has run. Check the status first.
"A source reports change constantly." It is a webpage with dynamic content. Switch to a feed if one exists, or to manual.
"I cannot add a source." You need reg_intel.manage. Read access alone does not permit registration.