A regulator reporting calendar that chases owners
Last checked 2026-11-13
Missing a reporting date is rarely about not knowing it exists. It is usually about the inputs arriving late, or the person who knew being away.
Examples of fixed and event-driven deadlines
Reporting obligations come in two kinds. Fixed deadlines fall on the same date every year. Event-driven deadlines start running when something happens, such as a serious injury. A useful calendar holds both. Some examples, with the jurisdiction named:
| Obligation | Deadline | Jurisdiction | Source |
|---|---|---|---|
| NGER emissions and energy report (registered corporations) | By 31 October each year, or the next business day if that falls on a weekend or holiday | Australia | Clean Energy Regulator |
| OSHA injury and illness records, electronic submission (where an establishment is required to submit) | January 2 to March 2 | United States | OSHA recordkeeping |
| Work-related death | Report to OSHA within 8 hours | United States | OSHA recordkeeping |
| Inpatient hospitalisation, amputation or loss of an eye | Report to OSHA within 24 hours | United States | OSHA recordkeeping |
| WHS notifiable incident | Immediately after becoming aware, by the fastest possible means | Australia | Safe Work Australia |
| WHS notifiable extended absence (December 2025 model WHS update) | Within 14 days, only where your jurisdiction has adopted it | Australia | Safe Work Australia |
These are examples, not a full list, and the details have conditions and exemptions. In the US, for instance, OSHA's recordkeeping rule applies to employers with more than 10 employees and some industries are exempt. Check the source for each obligation that applies to you.
Building the calendar
A reporting calendar works when each entry answers five questions:
- What is due? The report or notification, and the regulator.
- When? The date, or the trigger for event-driven obligations.
- Who owns it? One named person, plus a backup.
- What inputs are needed? Meter readings, fuel invoices, injury logs, production figures, and who holds each one.
- How is it lodged? The portal or channel, and who has the login.
A SharePoint List or an Excel table in your tenant is enough. The AI can help you build it from your licence conditions, past lodgement emails and existing spreadsheets, then propose the entries for you to confirm. It does not decide which obligations apply to you.
How reminders and owner chasing work
Once the calendar exists, The Everything can run it:
- Lead-time reminders. You choose the lead times, for example 60, 30, 14 and 7 days before a fixed date. Reminders go to the owner in Teams or by email, and to the backup if the owner is away.
- Input requests. Ahead of a report, it asks each input holder for their figures, attaches last year's version for reference, and follows up.
- Collation. It gathers the replies into one folder and drafts a summary or a figures pack in Excel or Word, noting anything missing or different from last year.
- Status. You can ask in Teams "what's due in the next 90 days and what are we waiting on?" and get a straight list.
- Close-out. After lodgement, it files the submission receipt and moves the date forward a year.
Event-driven obligations work differently: the calendar cannot remind you of an incident before it happens. For those, see incident reporting, where the point is to get a person to the regulator fast, not to wait on a draft.
What stays with a person
- Which obligations apply. The calendar is only as good as the list behind it, and that list needs someone who knows your licences and operations.
- The numbers. The AI can collate and compare; the responsible person checks the figures and the method.
- Signing and lodging. Declarations and submissions are made by a person, in the regulator's own portal or channel.
- Late or missed dates. If a deadline cannot be met, talking to the regulator is a decision for you.
Before you start
The Everything runs inside your Microsoft 365 tenant with tightly scoped permissions, but your data does leave the tenant for AI processing. Its privacy policy names Microsoft (Azure OpenAI) and OpenAI as AI providers and says providers may process information outside your country. The public site does not claim any certification such as SOC 2 or ISO 27001, and it does not name a hosting country.
Reporting inputs can be commercially sensitive (energy and production data) or personal (injury logs). Check your privacy and record-keeping obligations before you connect them. Keep regulator portal logins with the people who lodge; the AI does not need them to send reminders or draft reports.
Questions people ask
When is the NGER reporting deadline?
The Clean Energy Regulator says registered corporations report their emissions, energy production and energy consumption by 31 October each year, or the next business day if that falls on a weekend or public holiday (Australia).
When is OSHA's electronic submission window?
OSHA's recordkeeping page gives January 2 to March 2 for electronic submission (United States). Check whether your establishment is required to submit.
Will the AI lodge reports in the regulator's portal?
No. It reminds, gathers inputs and drafts. A responsible person checks the figures and lodges the report.
Can it work out every reporting date that applies to us?
No. It can help you build the calendar from your licences and past lodgements, but deciding which obligations apply needs someone who knows your operations, and sometimes an adviser.
What if the owner of a deadline leaves the business?
Each entry should have a backup owner. The AI can flag entries whose owner no longer has an active account, so you can reassign them.
Try it on your own compliance year
The Everything is an AI worker that lives in Microsoft Teams and works with the registers, documents and mailboxes you already have in Microsoft 365. It asks before anything important goes out. $400 AUD/month + GST per company, unlimited team members, with a 14-day free trial and no credit card.
See how The Everything works