Want to find out more or book a demo? Contact Us

How to Set Up a Conflict of Interest Register

Why a Conflict of Interest Register Matters

Conflicts of interest are a normal part of organisational life. Directors sit on other boards, staff have family members who run businesses, and committee members hold shares. Having a conflict is rarely the problem. Failing to declare it, record it and manage it is.

A conflict of interest register is the central record of those declarations and what was done about them. When a decision is later questioned by an auditor, a regulator, a journalist or an unsuccessful tenderer, the register is your evidence that the organisation knew about the interest and handled it properly.

For many Australian organisations it is also an expectation. Company directors have to give notice of material personal interests under the Corporations Act 2001. Officials of Commonwealth entities have a duty to disclose interests under the PGPA Act. Registered charities must meet ACNC Governance Standard 5, which includes disclosing actual or perceived material conflicts. State and territory local government legislation sets out disclosure obligations for councillors and council staff.

Actual, Perceived and Potential Conflicts

A good register captures more than the obvious cases. It helps to be clear about the three types:

  • Actual - a real conflict exists now between a person's private interests and their duties. For example, a procurement panel member whose partner owns one of the tendering companies.
  • Perceived - a reasonable person could think a conflict exists, even if it doesn't. Perceived conflicts can damage trust just as much as actual ones.
  • Potential - no conflict exists yet, but one could arise if circumstances change. For example, a board member who is a shareholder in a supplier the organisation may use in future.

If in doubt, declare. A declaration that turns out to be unnecessary costs almost nothing. An undeclared conflict that surfaces later can cost a great deal.

What to Record in Your Register

Whether you use a spreadsheet or a dedicated system, each entry should capture enough detail to show what the interest was and how it was managed. At a minimum, record:

  • Who is declaring - name, role, and the board, committee or business unit they belong to.
  • Date of declaration - and the meeting or process where it was raised, if applicable.
  • Nature of the interest - financial, personal, family, professional or other, with a clear description.
  • Type of conflict - actual, perceived or potential.
  • Related matter - the decision, contract, tender, grant or agenda item it affects.
  • Management action - what was agreed: for example, withdrawing from discussion, not voting, removal from a panel, divesting, or no action needed with reasons.
  • Who approved the action - usually the chair, a manager, or a probity adviser.
  • Status and review date - whether the conflict is ongoing or closed, and when it will next be checked.

The management action is the field most often left blank, and it is the one auditors care about most. A register that lists interests without showing how they were handled is only half a record.

Who Should Declare

The short answer is anyone who makes or influences decisions on behalf of the organisation. In practice that usually includes:

  • Board members and directors, including independent and co-opted members.
  • Committee members, such as audit and risk committees.
  • Executives and senior managers.
  • Staff involved in procurement, grants, recruitment, licensing or regulatory decisions.
  • Contractors, consultants and evaluation panel members working on specific processes.
  • Volunteers in decision-making roles, which is common in not-for-profits.

Your conflict of interest policy should state who is covered so that nobody has to guess.

When Declarations Should Happen

Most organisations need declarations at several points, not just once a year:

  • On appointment - a standing declaration of interests when someone joins the board, a committee or a sensitive role.
  • At every meeting - a standing agenda item asking for declarations relating to the business of that meeting, recorded in the minutes and the register.
  • At the start of specific processes - tender evaluations, grant assessments and recruitment panels should each require a fresh declaration from participants.
  • When circumstances change - a new job, shareholding or relationship should be declared as soon as it arises, not at the next scheduled review.

How Often to Review the Register

An annual review is the common baseline. Once a year, ask everyone covered by the policy to confirm or update their standing declarations, and have the board or audit and risk committee review the register as a whole.

Beyond that, review individual entries whenever the related matter progresses - when a contract is awarded, a project closes or a person changes roles. Ongoing conflicts should carry a review date so they don't sit in the register unchecked for years.

The annual review is also a good time to check the register itself. Look for entries with no management action recorded, conflicts marked ongoing that should have closed, and people who should be declaring but haven't.

Common Mistakes to Avoid

  • Treating declaration as the end of the process - declaring a conflict doesn't manage it. The register needs to show what happened next.
  • Keeping declarations in too many places - meeting minutes, HR files, procurement folders and email. If nobody can see all of a person's declared interests in one place, conflicts get missed.
  • Relying on memory for annual reviews - without reminders, annual declarations slip, and they tend to slip without anyone noticing.
  • No link to decisions - an interest recorded without the related contract, tender or agenda item is hard to verify later.
  • Ignoring perceived conflicts - these are often where reputational damage comes from.

Moving Beyond the Spreadsheet

A spreadsheet can work for a small board. As the number of people, meetings and procurement processes grows, it gets harder to keep current, harder to control who can edit it, and harder to prove that nothing was changed after the fact.

GovMan supports conflict of interest declarations as part of its probity and procurement tools, with a full audit trail of every change. Because declarations sit alongside GovMan's obligations register, risk register and governance tools, conflicts can be linked to the decisions and contracts they relate to. For more on why this matters, see our article on probity and compliance.

If you'd like to see how it works, we'd be glad to show you.

Request a Demo

Share this article:
Recent Articles