Register of Interests: Keeping Board Conflicts on Record

What a register of interests is, in plain terms

Say you sit on a 9-person nonprofit board, and the organization is about to vote on a vendor contract with a company your spouse partly owns. Before that vote happens, someone needs a record that you disclosed the connection — not a vague memory of "I think she mentioned something," but a dated entry anyone can pull up later.

That's the job of a register of interests: a board document that logs each director's outside financial, familial, or organizational ties that could reasonably affect their votes. A board register of interests is a standing log — usually a spreadsheet or table inside the board's minute book — where each director records relevant outside interests, and it's updated whenever a new conflict arises, not just once a year. It's the paper trail that lets a board (or an auditor, regulator, or journalist) answer the question "did anyone know about this conflict before the vote?" without relying on anyone's recollection.

It sits next to, but isn't the same as, your conflict-of-interest policy. The policy sets the rules — what counts as a conflict, what directors are supposed to do about it. The register is the evidence that the policy was actually followed.

Why a loose policy isn't enough

A lot of boards have a conflict-of-interest policy buried in their bylaws and assume that's sufficient. It isn't, for one simple reason: a policy describes intent, not fact. If a funder, auditor, or state attorney general ever asks whether a specific director disclosed a specific interest before a specific vote, "our policy requires disclosure" doesn't answer that. A dated register entry does.

This matters more for some organizations than others. Nonprofits, government contractors subject to procurement rules, and healthcare boards overseeing physician relationships all tend to have an external party who may eventually ask for this record. Even if your board never gets asked, keeping the register is cheap insurance against a dispute between directors months or years later about who knew what.

None of this is legal advice — your bylaws, your state's nonprofit or corporate statutes, and your own counsel should set the specifics of what your register needs to capture and how long you keep it. What follows is the operational pattern most boards land on.

When declarations actually happen

Declarations aren't a once-a-year chore you knock out during annual filings. They happen at three different points, and boards that only do one of them end up with gaps.

| Trigger | What gets captured | Who's responsible | |---|---|---| | On appointment | A new director's baseline interests — employers, significant shareholdings, family ties to vendors or competitors | The incoming director, usually with the board secretary confirming receipt | | Annually | A refresh confirming nothing has changed, or an update if it has | Every sitting director, prompted by the secretary or chair | | Per meeting, as items arise | A specific declaration tied to a specific agenda item, made before discussion starts | Any director with a relevant interest, noted live in the meeting |

The third row is where most registers actually earn their keep. Annual declarations catch the obvious, ongoing stuff — a board seat elsewhere, a spouse's employer. But a one-off conflict, like the vendor contract example above, only surfaces when the agenda item comes up. That means your agenda-setting process needs a built-in moment for "does anyone need to declare an interest before we discuss this?" If you're planning agendas with something like a timed agenda planner, that prompt is easy to bake in as a standing line item rather than something the chair has to remember to ask.

How recusals get minuted

Declaring the interest is step one. Recusal — the director actually leaving the discussion and the vote — is step two, and it needs its own paper trail inside the minutes, separate from the register itself.

A clean recusal minute usually records:

• The name of the director recusing and the agenda item in question
• The nature of the interest, in enough detail that someone reading it cold understands why recusal was necessary
• The time the director left the room (or the call) and the time they returned, if they rejoined for unrelated business
• Confirmation of whether the remaining directors still had quorum to vote

That level of detail is tedious to capture by hand mid-meeting, which is exactly why a lot of boards lose it — someone remembers to note "Director X recused" and forgets the timestamp or the reason, and six months later nobody can reconstruct it. If your board is taking structured meeting minutes already, recusal entries should follow the same template every time, not get freelanced meeting to meeting. For formal board sessions specifically — agendas, minutes, votes, and the interests register together — a dedicated board meeting workflow keeps the recusal note attached to the same record as the vote tally, so you're not cross-referencing two documents later.

Keeping the register somewhere people can actually find it

A register of interests that lives in one director's personal folder isn't really a register — it's a rumor with a filename. It needs a fixed home, version history, and a way to show who updated what and when.

A few practical habits help:

• Store it alongside your bylaws and minute book, not in a separate inbox or personal drive — a shared document library works better than email attachments that go stale
• Assign one person (usually the board secretary) as the only one who edits the master copy, even though every director contributes updates
• Review it at the start of every meeting cycle, not just when someone remembers
• If a recusal generates a follow-up action — say, getting outside counsel to review a contract — track it the same way you'd track any other board commitment, through action tracking rather than a note in someone's inbox

Many boards also keep a running, timestamped history of governance decisions — declarations, recusals, votes, and the context around each — alongside the register itself, so they're not reconstructing the sequence of events from memory months later.

Frequently Asked Questions

What's the difference between a register of interests and a conflict-of-interest policy?

The policy is the rulebook — it defines what counts as a conflict and what a director is supposed to do when one comes up. The register is the record that shows the policy was actually followed: who declared what, and when. Your bylaws or counsel should define the specifics of your policy; the register is the operational log that proves compliance with it.

Who should be able to see the register?

Typically the full board, the board secretary, and whoever is responsible for governance or compliance oversight. Some organizations also make a summarized version available to auditors, major funders, or regulators on request. Check your own bylaws or jurisdiction's disclosure rules for whether any part of it needs to be public.

Does declaring an interest always mean a director has to recuse?

Not necessarily — some boards allow a director to disclose an interest and still participate in discussion (but not the vote), while others require full recusal from both. That threshold should be set in your conflict-of-interest policy, not improvised meeting by meeting, since inconsistent handling is exactly what creates disputes later.

How long should register entries be kept?

Retention periods vary by jurisdiction and organization type, so this is a question for your bylaws or legal counsel rather than a one-size-fits-all rule. As a general practice, most boards keep register entries for as long as they keep board minutes, since the two documents are often read together.

Can a small board skip the register and just rely on verbal disclosures?

You can, but it's a fragile approach — verbal disclosures aren't searchable, don't survive turnover, and don't hold up well if a conflict is ever disputed after the fact. Even a lightweight spreadsheet beats relying on collective memory, and it takes very little setup to start one.

If your board is still tracking interests, votes, and minutes across separate documents, it might be worth seeing how a connected meetings and governance platform handles all three in one place. Check pricing or get in touch to talk through your board's specific setup, or start a trial and bring your next board pack into it directly.