Stop Chasing Deadlines: Build a Compliance Calendar That Runs Itself

Aashok F&C Advisory

8 min read

·

1 day ago

--

Listen

Share

ARTICLE 62 OF 100 | MEDIUM EDITION | COMPLIANCE, PRODUCTIVITY, SMALL BUSINESS, MANAGEMENT, ACCOUNTING

Boeing’s 1935 crash led to the pilot’s checklist. Compliance needs the same thing: owners, evidence and escalation instead of memory.

By Aashok Kumar Sharma · Founder, Aashok F&C Advisory

Every business has deadlines it can’t afford to miss: tax returns, payroll deposits, licence renewals, annual filings. In most small companies, they live in someone’s head.

That works until the person is on leave, unwell or simply busy. Aviation solved the same problem nearly a century ago with a simple tool. It applies to compliance anywhere in the world.

On 30 October 1935, the US Army Air Corps tested a new bomber, Boeing’s Model 299, at Wright Field in Ohio. It was the most advanced aircraft of its time. Shortly after take-off, it stalled and crashed, killing two of the crew.

The cause was not a mechanical failure. The experienced pilot had forgotten to release a locking mechanism on the controls.

The aircraft was said to be “too much airplane for one man to fly.” Instead of giving up, test pilots created something simple: a checklist for take-off, flight and landing. With it, the aircraft — later known as the B-17 — flew safely for many thousands of hours.

The surgeon and writer Atul Gawande retold this story in The Checklist Manifesto (2009) to make a point that applies to every business: when a task has too many steps for memory, the answer is not a smarter person. It is a better system.

Too much compliance for one person to remember

A typical Indian business with employees and a company structure faces:

• Monthly GST returns and payments.
• Monthly tax-deduction deposits and quarterly statements.
• Monthly provident fund and ESI contributions.
• State professional tax and labour welfare fund.
• Quarterly advance tax.
• Annual income-tax returns and audits.
• Annual company filings, board meetings and AGM.
• Licence renewals, trade registrations, environmental and factory permissions.
• Event-based filings whenever something changes.

That is well over a hundred dates a year — for a business that is not even large. Most owners keep them in memory, in a consultant’s head or in scattered emails.

That is not a system. It is a hope.

A lesson from history: the calendar was invented for obligations

In ancient Egypt, the rising of the star Sirius signalled that the Nile was about to flood. Officials measured the river with Nilometers — stone staircases and columns marked with levels — and used the flood height to predict the harvest and set taxes.

The calendar, the measurement and the obligation were linked. Societies have always used calendars not just to tell time, but to manage duties. A compliance calendar is the modern version of the Nilometer: it tells you what is coming before it arrives.

Why deadlines get missed

1. No single list. Obligations are spread across GST, tax, payroll, company law and licences — each handled by different people.

2. No named owner. “The accountant handles it” — which accountant, which return?

3. No evidence of completion. Nobody checks for the challan, acknowledgement or receipt.

4. No escalation. If a filing is not done three days before the deadline, nobody is told.

5. No update when the law changes. Due dates, forms and rates change regularly.

6. Cash conflicts. Payments are delayed to manage working capital.

A missed deadline is rarely a knowledge problem. It is almost always an ownership problem.

The uncomfortable part

Penalties for missed deadlines are usually small at first: a late fee, a few days’ interest.

Then they multiply. Interest compounds. Daily fees continue. Notices arrive. Input tax credits are blocked for customers. Directors are disqualified. Licences lapse.

Small penalties are the system’s way of asking whether anyone is watching. Large penalties arrive when the answer is no.

The OWNER Calendar

Build your calendar with five columns for every obligation:

O — Obligation

What exactly is required? Name the law, form and frequency — for example, “GSTR-3B, monthly, GST law.”

W — When

The statutory due date, plus an internal deadline several days earlier. Work to the internal date, never the legal one.

N — Named owner

One person responsible — not a team, not “accounts.” Plus a backup owner.

E — Evidence

What proves completion? Acknowledgement number, challan, receipt or filed form — stored in a shared folder linked to the calendar entry.

R — Reminder and escalation

Automatic reminders to the owner at, for example, 7 days and 3 days before the internal deadline. If evidence is not uploaded by the internal deadline, an escalation goes to the CFO or owner.

An obligation without all five columns is not in your calendar. It is in your risk register.

Building it in practice

Step 1 — List every obligation

Go law by law: GST, income tax, payroll, labour codes, company law, state laws, industry licences, environmental permissions, import-export registrations, insurance renewals and contracts with renewal dates. Include event-based triggers — director changes, new branches, capital changes.

Step 2 — Add dates and internal deadlines

Use official calendars from tax and regulatory authorities. Set internal deadlines 3 to 5 working days earlier.

Step 3 — Assign owners and backups

Include external consultants — but always with an internal owner who checks their work.

Step 4 — Define the evidence

Decide where proof is stored and how it is named.

Step 5 — Automate reminders

A shared calendar, task-management tool or compliance software. Spreadsheets work for small businesses if reviewed weekly.

Step 6 — Review monthly

A 30-minute monthly compliance meeting: what was filed, what is pending, what changed in law.

Step 7 — Update for changes

Assign someone to track regulatory updates — new laws, revised due dates, new forms — and update the calendar.

Step 8 — Ring-fence payments

Treat statutory payments as first-priority outflows, approved separately from ordinary payables.

A worked example (illustrative)

Consider an illustrative 150-employee manufacturer with two factories in different states. In one year, it paid late fees and interest on 23 occasions, and one factory licence lapsed for six weeks.

The OWNER Calendar rebuild:

• 186 obligations listed across central, state and local laws.
• Every entry given an internal deadline, an owner, a backup and an evidence requirement.
• Reminders set in the company’s task tool; escalation to the CFO for any entry without evidence by the internal date.
• Statutory payments moved to a dedicated weekly approval run.

The next year: two late filings, both caught by escalation within a day. No lapsed licences. The CFO describes the change simply: “We stopped remembering and started checking.”

How you’ll know it’s working

A self-running calendar shows up in a short list of numbers:

• Late filings and payments — close to zero each quarter.
• Escalations — rare, and resolved within a day.
• Evidence completeness — every completed obligation has proof stored.
• Updates — the calendar reflects changes in law within weeks.

Where this is heading

Compliance management software, government portals and AI assistants will increasingly track deadlines, prepare draft filings and match data automatically. The calendar will run itself technically. Ownership, review and evidence will still need people. Businesses that combine both will spend less time chasing deadlines and more time running the business.

What to do on Monday, by role

• Owner: name one senior person responsible for the compliance calendar.
• CFO: list obligations for the next 90 days with owners and internal deadlines.
• Consultants: share their filing schedules and acknowledgements every month.
• Department heads: report events — new branches, directors, contracts — that trigger filings.

“But…” — the best counterargument

The objection: “Our CA firm handles everything. We pay them to remember the deadlines.”

The answer: A good professional firm is valuable — but legal responsibility remains with the company and its officers. Firms work from the information you give them, and they may not know about every licence, contract or event in your business. An internal calendar with evidence does not replace your advisers; it lets you see whether the work was done. Trust your advisers. Verify the outcomes.

Questions people ask me

“Do we need compliance software?”

Not necessarily. A well-structured spreadsheet or shared calendar works for many small businesses. Software helps as obligations, locations and entities grow.

“How often should the calendar be reviewed?”

Weekly for upcoming items, monthly for completion and quarterly for completeness and changes in law.

“Who should own the calendar overall?”

A senior person — CFO, finance head or company secretary — with authority to escalate.

“What about obligations that are not date-based?”

Event-based obligations — such as filing a change in directors — should be linked to internal processes so that the event automatically triggers a calendar entry.

Where things stand (October 2026): Indian businesses now operate under the Income-tax Act, 2025 (in force from 1 April 2026) and the four labour codes (from 21 November 2025), both of which changed forms, sections and some due dates. Rebuild your calendar from current official sources rather than last year’s list.

Mistakes I see most often

• Working to legal deadlines instead of internal ones.
• Assigning obligations to teams instead of named individuals.
• Treating an email from a consultant as evidence of filing.
• Ignoring state and local obligations.
• Using compliance payments to manage cash flow.

One-page checklist

• Every obligation has a named owner
• Internal deadlines set before legal ones
• Evidence stored for every filing
• Monthly compliance review held

Try this in 30 minutes

Write down every compliance deadline you can remember for next month. Then ask your accountant or adviser for their list.

Compare the two. Every item on their list that was not on yours — and every item on yours that is not on theirs — is a gap your calendar must close.

The short version

• The 1935 Model 299 crash led to the pilot’s checklist: complex tasks need systems, not memory.
• A typical business faces well over a hundred statutory dates a year across tax, payroll, company law and licences.
• Deadlines are missed because of ownership gaps, not knowledge gaps.
• Use the OWNER Calendar: Obligation, When, Named owner, Evidence, Reminder and escalation.
• Review monthly, update for legal changes and ring-fence statutory payments.

Stop relying on memory. Build a calendar that remembers for you — and checks that the work is done.

Before you go

List every obligation, give it an owner and an internal deadline, and require evidence of completion. Once it’s built, your calendar remembers so your people don’t have to.

Further reading

• Atul Gawande, The Checklist Manifesto: How to Get Things Right (Metropolitan Books, 2009).
• US Air Force, National Museum of the US Air Force — history of the Boeing Model 299 and B-17. nationalmuseum.af.mil
• Central Board of Indirect Taxes and Customs; Income Tax Department; EPFO; ESIC; Ministry of Corporate Affairs — official compliance calendars and due dates. cbic.gov.in · incometaxindia.gov.in · epfindia.gov.in · mca.gov.in

◆ ◆ ◆

A version of this article first appeared on ComplianceCalendar.in.

I’m Aashok Kumar Sharma, founder of Aashok F&C Advisory — a finance, accounting and compliance practice working with founders, SMEs and finance teams in India and abroad. I write about the numbers, rules and decisions that quietly decide whether businesses last. Follow me here on Medium for the rest of this 100-part series.

This article is general information, not legal, tax or investment advice. Rules change; check current provisions or speak to a qualified professional before acting. Examples labelled illustrative are composites.