Notice & Report
Management
Control incoming regulator notices, stakeholder complaints and outbound regulatory submissions through dated, assigned and auditable correspondence lifecycles.
External communication and replies
Triage, action and resolution
Transmission and agency responses
Owners, due dates and reminders
See what needs attention.
Act before deadlines slip.
A combined dashboard brings status, age and deadline signals across all three registers into one view.
Compliance dashboard
Overview · Notices, complaints and report submissions
Open work by status
Recent activity
Illustrative UI preview — figures shown here are sample values, not live system data.
From first receipt to final closure.
Keep ownership, response history and current status connected to the record. Teams can understand what happened, what is due next and who is responsible.
Every notice or submission has a linked correspondence chain.
Organisation unit and assignee support scoped access and operational ownership.
Lifecycle actions move records between valid states; ordinary Save does not change status.
Correspondence and governed attachments retain context for review and archive.
Initial external communication
Owner assigned, facts checked
Outgoing entry recorded
Next response is tracked
Different communication types.
One consistent discipline.
Use the right register for the direction and purpose of the communication.
Notices
Manage official incoming regulator or stakeholder communication, response deadlines, escalation and every reply in the correspondence chain.
View notice workflow →Complaints
Track grievances from receipt and triage through corrective action, resolution summary, closure or a documented rejection/withdrawal.
View complaint workflow →Report submissions
Prepare a private draft, record transmission and acknowledgement, manage agency queries and replies, then accept and close.
View submission workflow →Taxonomies
Administrators maintain Notice Types and Regulator categories, with stable slugs, sort order and active state.
Explore controls →Every state has a next step.
Actions are state-aware and create the corresponding audit trail. Use the offered action rather than manually editing status.
Useful controls, grounded in clear rules.
Designed around everyday register work, without treating a visual label as a substitute for server-side permission.
Find the right record
Search, filter by columns, show only your work, inspect overdue records and open a full-page detail from each row.
Track dates and age
Use received dates, deadlines and resolution dates consistently. Overdue excludes closed and withdrawn notices.
Respect OU scope
Organisation unit is an authorisation anchor. Users outside the permitted subtree must not gain access by knowing a record ID.
Keep evidence governed
Attachments require tenant ownership, a clean scan state and binding to the relevant record or correspondence entry.
Use valid transitions
Lifecycle buttons invoke configured workflow actions. Ordinary Save cannot force a record into a later state.
Manage reminders
Due-date reminders use the assignee and configured reminder rules. A configured source alone does not prove delivery succeeded.
Permission-aware by design.
Reference roles provide a starting point. Actual access depends on assigned grants, row scope, record state and server decisions.
Quick answers for teams.
Make every response traceable.
Connect ownership, deadlines, correspondence and lifecycle status in one consistent operating process.
Back to overview ↑