A compliance calendar should tell an institution what must happen, why it must happen, who is responsible and what evidence will establish completion. Many calendars record only a description and a due date. They are useful reminders, but they leave important questions unanswered when an owner is absent, a return is rejected or an obligation is triggered outside the monthly routine.
For banks and NBFCs, reliability begins with understanding the obligation population. Reporting, committee reviews, licence conditions, customer notifications and event-driven obligations do not all follow the same timetable. They also have different completion criteria. Preparing a document, approving it and successfully submitting it are separate milestones.
The operating model below is intended to help teams build a calendar they can use under pressure. It does not provide a universal schedule of statutory deadlines.
Build an obligation register before scheduling tasks
Start with the requirement itself. Each obligation needs an identifier, authoritative source, applicable entity, responsible function, frequency or trigger, external deadline rule and evidence requirement. Record the relevant source version and the reason the obligation applies. The calendar should generate work from this register, rather than becoming the only place where the requirement exists.
Keep internal management activities distinguishable from externally required obligations. Both can be important, but a missed internal target and a missed statutory deadline need different interpretations. An earlier internal deadline can provide time for review without replacing the external one.
The RBI supervisory-return directions for commercial banks and NBFCs contain institution-specific reporting requirements. Their scope and schedules should be checked against the entity profile, rather than copied into one generic lender calendar. [3] [4]
Distinguish recurring obligations from events
A recurring task follows an identifiable reporting period or review cycle. Examples include preparing a periodic return, reviewing access rights or presenting a scheduled committee paper. Store the period covered separately from the task's due date. Otherwise, a reviewer may see a completed task without knowing which period it relates to.
An event-driven obligation begins when something happens: a change in control, a material incident, a new product, an appointment or a contractual event. The calendar needs a reliable way to capture the trigger and its time of occurrence. Creating reminders is ineffective if the triggering event never reaches the compliance team.
Map each event to its source team. Company secretarial staff, security operations, human resources and business teams may identify different triggers. Define how they notify the obligation owner and how the owner confirms whether an external action is required.
Calculate deadlines transparently
A date calculation can be wrong even when it looks precise. The underlying rule may use calendar days, working days, a period-end reference, an event date or an authority-specific holiday convention. Store the rule and its interpretation alongside the generated date. Test month ends, leap years and holiday boundaries where relevant.
Separate external due dates from preparation, checking and approval milestones. Work backwards from the filing deadline using realistic time for corrections. If source data arrives too late to permit review, that is a dependency problem requiring management attention, not a reason to compress review silently.
Record extensions only when there is a valid basis. An internal manager moving a task does not change a regulator's deadline. Preserve the original due date, the revised internal target and any formally applicable external extension as distinct facts.
Assign ownership that survives absence and turnover
A task should have one accountable owner even when several teams contribute. Identify the preparer, checker, authorised approver and submission role where relevant. Shared responsibility without a named decision owner often produces a gap precisely when a problem needs escalation.
Maintain deputies and a handover process. When an employee leaves, review open tasks, access rights, future scheduled work and evidence stored in personal locations. Reassignment should leave an audit trail showing who held responsibility at each stage.
Avoid assigning a senior executive as the nominal owner of every obligation. The accountable executive may oversee a portfolio, but operational ownership needs someone who can obtain the sources, resolve questions and progress the work. Escalation should connect these levels without confusing their responsibilities.
Define completion in observable terms
Write an acceptance test for each obligation. For a committee review, evidence might include the approved paper, meeting record and resulting actions. For a return, it may include the reviewed working paper, submitted version and relevant portal acknowledgement. For a customer communication, delivery evidence and exceptions may matter.
Use statuses that reflect these distinctions. “Prepared,” “under review,” “approved,” “submitted,” “rejected” and “completed” carry different meanings. A rejected submission should reopen the required work while preserving the original deadline and the first submission attempt.
Some obligations remain open until a later event confirms completion. Do not force every process into a single upload-and-close step. The calendar should represent the real completion condition, including externally dependent outcomes and any residual actions.
A worked example: a quarterly reporting cycle
Consider a hypothetical return due after quarter end. Finance provides the accounting control totals, operations provides the account-level extract and risk supplies approved classification information. The reporting team combines these sources and investigates differences before sending the working paper for independent review.
The calendar contains linked milestones for source delivery, reconciliation, checking, approval and submission. If a source is delayed, the task shows the dependency owner and the effect on the remaining review window. The external deadline remains visible throughout.
Suppose the portal rejects the first submission because a validation rule fails. The record retains the rejected file and error message, opens a correction action and captures the eventual accepted version. A task marked complete at the first upload would conceal the actual reporting outcome.
Escalate early enough to change the outcome
Escalation is useful only if it reaches someone who can resolve the problem. Define routes for missing data, interpretation questions, approval delays, system outages and capacity constraints. Sending the same overdue reminder repeatedly to the original owner is usually insufficient.
Use leading indicators as well as overdue counts. A high-risk task with an unresolved dependency and little review time may need attention before its preparation deadline is missed. Different obligations can justify different escalation windows, based on consequences and the time needed to intervene.
The escalation record should state the issue, impact, decision needed and next action. Keep it short enough for a manager to use. A clear request to approve an additional reviewer is more actionable than a long email chain describing that the task is urgent.
Control calendar changes and exceptions
Changes to frequency, scope or completion criteria can alter the institution's compliance coverage. Require review proportionate to their significance. Deleting an obligation because it has not generated work recently is particularly risky when it is event-driven.
Periodically reconcile the obligation register to current requirements and business activities. New products, acquisitions, licence changes and changes in institution classification can add or remove obligations. A calendar copied from the previous year without an applicability review accumulates errors.
Keep cancelled, superseded and non-applicable obligations in history with their reasons. This helps explain why a task existed in an earlier period but not in a later one. It also prevents an obsolete requirement from reappearing when someone imports an old spreadsheet.
Use management reporting to expose weaknesses
A completion percentage can be misleading if every task receives equal weight. Separate material obligations, routine activities, late completions and items whose evidence has not been checked. Show overdue ageing and concentration by function to reveal capacity or ownership problems.
Examine repeated deadline changes and repeated returns from review. These may indicate poor planning, incomplete instructions or weak source quality. A team that closes many tasks on time but regularly needs post-submission corrections may have a reliability problem that a simple timeliness measure misses.
The Basel compliance guidance supports an effective compliance function tailored to the institution. [1] In practice, management reporting should help leaders decide where to allocate attention and resources, rather than rewarding a cosmetically clean calendar.
Test the calendar as an operating system
Choose a sample containing a recurring return, an event-driven obligation and a committee review. Ask whether another qualified person could complete each task using the recorded instructions, sources and evidence criteria. If critical knowledge exists only in the original owner's memory, strengthen the record.
Run an absence scenario. Confirm that a deputy receives the task, has appropriate access and understands the approval route. Then test a failed submission or a late source. The calendar should preserve the history and make the next responsible action obvious.
A dependable calendar does more than prevent forgotten dates. It makes obligations executable, exceptions visible and completion defensible. That combination allows compliance work to remain reliable when the volume increases or the operating environment becomes less predictable.
PRIMARY REFERENCES
Sources & further reading
Primary-source references checked on 12 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.
- Basel Committee: Compliance and the compliance function in banks (opens in a new tab)
- Reserve Bank of India: Master Directions directory (opens in a new tab)
- RBI: Commercial Banks – Supervisory Returns Directions, 2026 (opens in a new tab)
- RBI: NBFCs – Supervisory Returns Directions, 2026 (opens in a new tab)