How to build a related-party register and recusal process
The clearest public rulebook we found governs English academy trusts. Its tests translate well to a family group, with our own judgement added where they fall short.
A related-party register rarely fails because someone set out to hide a deal. It fails because a contract with a relative's firm arrives on a busy afternoon, looks ordinary, and is signed before anyone asks who sits on the other side. The clearest public rulebook we could find on this problem governs English academy trusts, which report related-party dealings to the Department for Education (DfE). Its central test is a number. According to gov.uk, a supply of goods or services by a related party needs prior DfE approval above £40,000 in a financial year ending 31 August. Nothing in our sources covers family holding companies, so the steps below borrow the academy tests and mark where our own judgement takes over.
Before you start
Four things must be true before anyone fills in a form. Skip one of them and the register will look tidy while working badly.
- One named owner for the register, who is not a person the register covers.
- A written definition of related party that names family members, directors, shareholders and the companies they control, settled with a lawyer who has read your constitutional documents.
- A board list of decisions that need approval, with the level of approval each one needs.
- An agreed rule that no one approves a transaction in which they, or a close family member, hold an interest.
If you cannot answer the first two points in a sentence each, do not start the steps yet. A register built on a vague definition leaves out the difficult cases, and those are the ones it exists to catch.
- Step 1
Define the parties
Write down every category of related party and the people in each: directors, shareholders, family members in the group, and entities those people control. The academy rules set one boundary clearly. According to gov.uk, an approval concession does not extend to subsidiaries of the related party. Test your own definition against that boundary, because a deal with a subsidiary is the one most likely to slip past a list of names.
- Step 2
Fix the fields
Give every transaction the same record: date, parties, what is being bought or sold, value, whether it is new or a renewal, approval status, who declared it, and where the evidence sits. Renewals belong in the register, so a rolled-over contract cannot pass as old news. The academy guidance includes an evidence checklist for approval requests; adapt the idea into a list of your own. Missing evidence is usually the first thing a later reviewer finds.
- Step 3
Declare before you commit
Record the transaction and the related party before you confirm it with them. That is the order the academy rules require for new transactions and renewals, and in our judgement it is the right order for a family group. Once a purchase order has gone out, the register records a decision already made. In our experience, most of the awkward conversations start with someone saying they assumed it was fine.
- Step 4
Set thresholds and do not split
According to gov.uk, the £40,000 threshold applies to single transactions and values are not aggregated by supplier. We would not copy that gap. Our judgement is that a family group should add up what it spends with each related party across the year and apply the threshold to the total. Splitting one contract into several smaller ones is the usual route around a limit, and a register that counts invoices one at a time will not see it.
- Step 5
Approve and recuse
Approval should come from people with no interest in the transaction. The conflicted person declares the interest, leaves the room for the discussion and the vote, and the minute says so. Where the chair or a senior executive is involved, the academy guidance asks trusts to weigh the impact carefully. A sensible test is whether the chair could reasonably be seen to approve a contract with their own relative. If the answer is yes, an independent director decides.
- Step 6
Send the unusual cases up
Some transactions go to the top whatever their value. According to gov.uk, the academy rules require prior DfE approval for novel or contentious transactions, and for those with wider repercussions, regardless of value. We would apply the same idea: any deal that is unusual or contested goes to the full board, however small. A series of deals with one supplier can share a single approval if each is described in enough detail, so write the description so that a reviewer can see exactly what is co
- Step 7
Plan for the emergency
Emergencies happen, and the academy rules treat emergency procurement separately. The source we reviewed says the trust must act and report under separate conditions, but the extract does not set those conditions out, so we have not reproduced them. Read the full guidance before you write your own emergency rule. As a working default, we would require an emergency deal to be declared within the same week and put to the board at its next meeting.
- Prior DfE approval threshold for related-party goods or services, per gov.uk
- £40,000
- Related-party transactions declared in annual financial statements, per gov.uk
- any value
Where registers go wrong
The first mistake is treating the register as a filing exercise. The academy rules show what happens after a breach. According to gov.uk, a retrospective related-party transaction is a breach of the academy trust handbook, the DfE may take further action, and the accounting officer reports the breach in the statement on regularity, propriety and compliance. A family group may have no regulator reading its register, but the logic holds. A breach kept out of the register is still a breach. It is simply harder to find, and it tends to surface later and at a worse moment.
The second mistake is keeping records only for transactions that need approval. The academy guidance requires accurate records of all related-party transactions, even where approval is not needed, and says the DfE may request them in an audit or review. It also says the department still monitors reported transactions that require no approval. Small deals are where patterns show up. A register that holds only the large contracts gives a false picture of who the family actually does business with.
The third mistake is letting the person being declared keep the pen. The register belongs to the board and should be kept by someone with no interest in its entries. The fourth is quiet repair. When a deal turns out to have gone ahead without approval, log it, report it at the next meeting, and say plainly what was not approved. Do not re-date the paperwork to make the sequence look cleaner. Take legal advice on any exposure before anyone contacts the other party.
Trusts should carefully consider the impact of this requirement and its relevance to transactions involving the board chair or the accounting officer
- Does this rulebook apply to a family holding company?
No. The sources we reviewed cover English academy trusts reporting to the Department for Education. They say nothing about family holding companies, shareholders or directors. The steps above borrow the academy tests and add our own judgement where those tests fall short, and we have said where that happens. Your lawyer should decide what your own constitutional documents require.
- Did we check the OECD texts on this subject?
We tried. The sources we reviewed did not include the OECD Guidelines on Corporate Governance of State-Owned Enterprises or the OECD Principles of Corporate Governance, so this article does not rely on them. Read the texts directly before you adopt any wording from them, and check that you have the edition you need.
- Do small transactions belong in the register?
Yes. The academy guidance requires accurate records of all related-party transactions, even where no approval is needed, and says the DfE monitors reported transactions that need no approval. A family group gains the same benefit. Small transactions show patterns, and a register that holds only large deals gives a misleading picture.
- Who approves a deal that involves the chair?
Not the chair. The academy guidance asks trusts to consider the impact of the related-party rules on transactions involving the board chair or the accounting officer. In our judgement, the chair declares the interest and withdraws, and an independent director or a committee decides. Record the reason for that choice in the minutes.
- What do we do if we find a deal we never declared?
Log it, report it to the board at its next meeting, and say plainly what was not approved. The academy rules treat a retrospective related-party transaction as a breach, allow the DfE to take further action, and require the accounting officer to report it. Take legal advice on any company or personal exposure before anyone contacts the other party.
This week, name the register's owner and ask counsel for a draft definition of related party. Then list every transaction from the last twelve months with a family member, director, shareholder or entity any of them controls, and run each one through the fields in step two. The first pass will be untidy, and that is useful. It shows where the definition is too narrow and where approvals were never recorded at all.

