Your AIS shouldn't require an investigation

One of the easiest ways to tell how mature an organisation's governance systems are is to watch what happens when the Annual Information Statement is due. For some charities, that means suddenly digging through old board minutes to work out when a director resigned, searching emails for the latest copy of the constitution, asking around to work out how many employees or volunteers the organisation has, and trying to piece together what actually happened over the previous twelve months.

If that sounds familiar, the problem probably isn't the AIS itself. The bigger issue is that the organisation doesn't have a reliable internal process for maintaining the information it needs throughout the year. Ideally, completing the AIS should be relatively straightforward because most of the information being requested is information the organisation already knows, maintains and uses.

Your Responsible People register should be updated when your board changes, rather than reconstructed once a year. Employee and volunteer numbers should come from systems or registers that are maintained as people join and leave. Changes to governing documents should be properly approved, recorded and stored at the time they occur. Financial information should come from accounts that are reconciled regularly and already being reported to the board in a way that directors understand.

The same principle applies to the organisation's activities. If the AIS arrives and the board needs to work backwards to remember what the charity actually did during the year, I think there is a bigger governance question worth asking. A board should already have enough visibility throughout the year to understand what the organisation is doing, who it is serving and whether those activities are actually contributing to its charitable purpose.

For me, this is where ACNC compliance becomes less about preparing information for a regulator and more about building an organisation that knows its own information. There should be clear sources of truth for the important information about the charity, clarity about who is responsible for maintaining it, and processes that make updating that information part of normal operations rather than an annual clean-up exercise.

A compliance register can help, and it doesn't need to be particularly sophisticated. The organisation should know what its key obligations are, who is responsible for each one, where the supporting information is held, when something needs to be reviewed and what events should trigger an action. The important part is recognising that not every compliance activity should be driven by a date on a calendar.

If a director resigns, for example, updating the board register and considering any required ACNC notification should simply be part of the resignation process. If the constitution is amended, storing the approved version and completing any required notifications should be part of implementing the amendment. If a new program or service is being considered, the board should be thinking about whether it fits within the charity's purposes while the program is being developed, rather than discovering a potential problem when somebody completes the AIS the following year.

The same thinking can be applied beyond the ACNC. When a new grant is accepted, its reporting requirements, restrictions and acquittal dates should be recorded when the agreement is signed. When somebody joins the board, eligibility checks, declarations, conflicts and onboarding should happen as part of their appointment. When something changes in the organisation, the question “does this trigger any governance or compliance action?” should be part of the process.

This is the difference between managing compliance throughout the year and responding to compliance deadlines when they appear. One creates an annual scramble where people are trying to reconstruct the organisation's history. The other means that when the AIS is due, most of the work has already been done simply because the organisation has been well governed throughout the year.

I don't think the goal should be to develop an enormous compliance bureaucracy, particularly for smaller charities. The process should be proportionate to the organisation. A spreadsheet, SharePoint list or simple governance register might be perfectly adequate if it is maintained properly and people know who owns it. The technology matters far less than having a process that actually works.

For a well-governed charity, completing the AIS should almost be boring. You aren't trying to work out what happened during the year or whether the information is still correct. You're taking information the organisation already knows, checking it and reporting it.

Good compliance should be the by-product of good internal systems, not an annual exercise in finding information.