> ## Documentation Index
> Fetch the complete documentation index at: https://docs.officeridge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance and notifications

> Annual corporate governance checklists and per-user notification preferences.

These two tabs cover your annual governance obligations and who gets told about what.

## Annual Checklists

Annual corporate governance compliance checklists by year.

**Columns:** Year

One checklist per year, tracking the governance obligations your agency has to meet annually —
filings, board reviews, policy renewals, and attestations.

<Tip>
  Create the coming year's checklist before the year starts. Working from a list you built in
  advance is considerably easier than reconstructing what was due in December.
</Tip>

## Notifications

User notification preferences with subscription types and advance notice settings.

**Columns:** User · Type · Subscribed · Advance Days

| Field            | What it controls                           |
| ---------------- | ------------------------------------------ |
| **User**         | Who receives the notification              |
| **Type**         | What kind of event it covers               |
| **Subscribed**   | Whether they receive it                    |
| **Advance Days** | How far ahead of the event they are warned |

**Advance Days** is the setting that determines whether a notification is useful. A licence expiry
warning with 3 days' notice arrives too late to act on; 90 days gives you time to renew.

<Warning>
  Notification subscriptions are per user. When someone leaves, their subscriptions leave with them —
  and nobody receives those warnings until you reassign them. Check subscriptions whenever a staff
  member with compliance responsibilities changes.
</Warning>

## Setting up notifications

<Steps>
  <Step title="Decide who owns each notification type">
    Compliance deadlines to your compliance officer, billing to finance, credentials to HR.
  </Step>

  <Step title="Subscribe them">
    Set **Subscribed** for each relevant type.
  </Step>

  <Step title="Set advance days to match lead time">
    Base it on how long the task actually takes. Licence renewals need months; a document review
    needs weeks.
  </Step>

  <Step title="Add a second subscriber for critical types">
    A single subscriber means a single point of failure during leave.
  </Step>
</Steps>

## Working the annual checklist

<Steps>
  <Step title="Create the checklist for the year">
    Do this before the year begins.
  </Step>

  <Step title="Cross-reference the compliance calendar">
    Regulatory deadlines live there. See [Quality and audits](/compliance/quality).
  </Step>

  <Step title="Assign items">
    Unassigned governance obligations are the ones that get missed.
  </Step>

  <Step title="Review progress at board meetings">
    See [Governing body](/corporate/governing-body).
  </Step>
</Steps>

## Troubleshooting

| Problem                              | What to check                                                                                 |
| ------------------------------------ | --------------------------------------------------------------------------------------------- |
| Notifications are not arriving       | Confirm **Subscribed** is set and check the recipient's email in [Account](/account/profile). |
| A warning arrived too late to act on | Increase **Advance Days** for that type.                                                      |
| Nobody was warned about an expiry    | The subscriber may have left. Reassign subscriptions.                                         |
| A governance item was missed         | Check whether it was on that year's checklist and whether it was assigned.                    |

## Related

<CardGroup cols={2}>
  <Card title="Governing body" icon="landmark" href="/corporate/governing-body">
    Board oversight and meetings.
  </Card>

  <Card title="Quality and audits" icon="clipboard-check" href="/compliance/quality">
    The regulatory compliance calendar.
  </Card>
</CardGroup>
