A compliance calendar becomes useful when it explains how an obligation will be completed, not merely when it is due. An entry without a clear owner, source dependency or reviewer may create the appearance of control while leaving the actual work to informal reminders. The objective is to make the sequence of preparation, challenge, completion and escalation visible before a deadline becomes urgent.
This example follows Illustrative Bank, a fictional institution, through three internal calendar occurrences at 30 September 2026. All dates and recurrence rules are invented planning assumptions. They are not RBI filing dates. The case is equally useful for an NBFC designing its own calendar, provided the actual obligations, applicability decisions and date rules are verified independently.
Verify the obligation before entering the date
The compliance team begins with the source of each obligation and the entity or activity to which it applies. It records an obligation ID, the relevant requirement and the rule used to determine the due date. Where a document has changed, the team retains the version used and checks whether the change affects the current or next cycle.
For actual regulatory work, consult the relevant direction and associated instructions rather than copying another institution’s calendar. The RBI Master Directions directory helps locate source material, but the applicable text still needs to be examined.[1] A date taken from a prior year may be wrong because of amendments, event triggers or a different institutional category. Internal management reviews should also be labelled as internal. This prevents staff from confusing an earlier preparation target with the external deadline it is intended to support.
Separate obligations from occurrences
An obligation is the continuing requirement or internal control. An occurrence is one dated instance of work under that requirement. The example uses stable IDs OBL-01, OBL-02 and OBL-03, while each cycle receives its own occurrence ID. CAL-09-01 can therefore remain in the history after the next monthly occurrence is created.
The distinction solves a common recordkeeping problem. If September’s row is overwritten with October’s due date, the organisation loses the original status, completion evidence and explanation of any delay. Keeping occurrences separate also permits several related tasks to run concurrently. An event-driven obligation may create an additional occurrence between periodic cycles. The calendar should explain the trigger and the person responsible for recognising it, rather than relying on a monthly recurrence engine to discover events that occur outside the usual schedule.
| Occurrence | Verified internal due date | Position at 30 September |
|---|---|---|
| CAL-09-01 / OBL-01 | 28 September 2026 | In progress; two calendar days overdue |
| CAL-09-02 / OBL-02 | 30 September 2026 | Completed 29 September with evidence |
| CAL-10-01 / OBL-03 | 5 October 2026 | One-off review; still open |
Work backwards from the verified deadline
CAL-09-01 has a fictional internal due date of 28 September and a review lead time of three calendar days. Its calculated review target is therefore 25 September. This target identifies when the reviewer should receive a sufficiently complete package. It is not the date on which the preparer should first request the underlying information.
The finance lead sets earlier milestones for source extraction and branch reconciliation in the dependency record. Those milestones reflect the work needed for this occurrence, including time to resolve a reasonable level of exceptions. The lead time should not be copied mechanically across obligations with different complexity. Some reviews can be completed quickly; others depend on committee scheduling or multiple source owners. Planning backwards exposes whether the proposed sequence is feasible before staff begin to treat every task as an emergency near the final date.
Give ownership and review different roles
Each occurrence has an accountable owner, a reviewer and a deputy. The owner coordinates the inputs and prepares the completion evidence. The reviewer checks the result against the relevant criteria. The deputy provides continuity when the owner is unavailable. These responsibilities are explicit in the register so an absence does not require a fresh search for someone willing to act.
A reviewer’s name in a cell does not establish that a review occurred. The completed occurrence needs a dated evidence reference that can be retrieved. In a small NBFC, the practical arrangements may be proportionate to team size, but the institution should still explain how challenge is achieved and how conflicts are handled. Basel compliance guidance offers context for organising an effective compliance function while recognising that institutions need approaches suited to their circumstances.[2] The calendar supports that organisation; it does not replace judgement about suitable responsibilities.
Make dependencies visible before they fail
The first occurrence depends on a branch reconciliation. At the review target, the source package remains incomplete. The owner records the missing input, the person expected to supply it and the effect on the completion sequence. A general note saying Awaiting data would not explain whether the problem is understood or whether anyone is taking action.
The institution agrees an escalation point before the final deadline, using its own risk and governance arrangements. A useful escalation identifies the decision needed: additional capacity, an alternative verified source, a corrected extract or a management decision about an unresolved exposure. Repeated reminder emails without that decision can consume time without changing the outcome. Dependencies should also include reviewer availability, system access and external service inputs when those are material. An apparently simple calendar task may be blocked by something outside the owner’s direct control.
Read the overdue position accurately
At 30 September, CAL-09-01 remains in progress and is two calendar days overdue against its original internal date of 28 September. CAL-09-02 was completed on 29 September, one day before its 30 September due date. CAL-10-01 is a one-off review due on 5 October and remains open. These are different management situations and should remain distinguishable.
The spreadsheet calculates overdue days for open work using the as-of date. Due today produces zero, not a negative value. Closed rows show zero current overdue days, so historical lateness must be assessed using completion date versus due date. That convention is stated in the instructions. A missing or invalid date produces a review prompt instead of a plausible numeric result. Managers should inspect those exceptions alongside overdue items, because incomplete data can conceal a more serious problem than an accurately recorded delay.
Escalate without rewriting the history
The finance lead escalates the delayed dependency on 29 September and retains reference DEP-01. The original 28 September date stays unchanged. The escalation records the reason, current exposure, next action and the authority expected to decide. A new internal recovery target can be kept in the action record without making the occurrence appear to have been timely.
Where an external obligation is involved, an internal recovery plan cannot retrospectively change the prescribed date. The institution must consider the actual rules governing delayed completion, corrections or communication with the relevant authority. This fictional calendar does not automate those decisions. The point of preserving the history is to support an honest assessment of the event and its cause. It also allows management to distinguish occasional exceptions from a recurring dependency weakness that requires a broader change to the operating process.
Treat recurrence as a suggestion requiring review
The workbook suggests the next date by adding one, three or twelve months to the verified current due date. For the first example, adding one month to 28 September suggests 28 October. This is convenient for planning, but it does not interpret working-day conventions, holidays, changed rules or an obligation tied specifically to the last day of a month.
The user must confirm the next date before creating a new occurrence. A one-off item displays Not recurring, avoiding the assumption that every completed task should repeat. Some obligations arise a specified time after a transaction, incident or governance decision; these need their own verified trigger logic. Staff should retain the calculation basis when it is more complex than a simple monthly pattern. Automation is most helpful when it makes a documented rule repeatable and exposes exceptions, rather than silently converting an uncertain assumption into a deadline.
Define the evidence needed for completion
CAL-09-02 is closed with PACK-02 and REV-02, identifying the prepared evidence and the reviewer’s decision. A completion statement alone would not explain what was checked. The appropriate record depends on the obligation: it might include an approved report, a meeting decision, a reconciled register or a submission acknowledgement. The exact final version should be identifiable.
The reviewer should be able to distinguish successful submission from an attempted upload and a final approval from comments on a draft. If a later correction is required, preserve the original completion record and link the revision. Do not use an ordinary calendar row as a repository for customer data or confidential documents. The row should point to controlled evidence with suitable access and retention arrangements. This keeps the calendar readable while allowing an authorised reviewer to reconstruct the sequence when needed.
Review the calendar as an operating process
The completed example demonstrates a calendar that exposes one overdue item and its cause, rather than presenting a misleading overall completion percentage. A regular management review can examine delays by dependency, repeated requests for extensions, missing evidence and obligations with no credible backup owner. Those patterns help determine whether the process needs redesign or additional capacity.
Use the blank workbook to establish a small, verified set of obligations first. Test a complete cycle, including absence cover and an exception, before expanding the register. Banks should clarify entity and branch contributions; NBFCs should use obligations relevant to their own permissions and activities. Preserve each occurrence, challenge the recurrence suggestion and review the evidence behind closure. The practical result is a calendar that tells people what needs to happen next and leaves a clear record of what actually happened.
PRIMARY REFERENCES
Sources & further reading
Primary-source references checked on 13 October 2026. Follow the relevant authority’s current text for applicability, amendments and commencement dates. International standards provide context and are not automatically identical to domestic requirements.