A conflict of interest that has been disclosed and managed is a managed risk. One that has not been disclosed is an unmanaged risk waiting to become a problem.

The logic of conflict of interest management rests on a simple foundation: the organisation cannot manage what it does not know about. The individual who holds an interest that creates a conflict, but who has not disclosed it, deprives the organisation of the ability to assess the situation, to put in place appropriate safeguards, and to make an informed decision about how the individual's role should be structured while the conflict exists.

Disclosure is therefore not merely an administrative requirement — it is the precondition for everything else in the conflict of interest framework. Without it, no assessment is possible, no management measures can be taken, and no record exists that the organisation exercised the judgment it was required to exercise. The compliance programme that has a thoughtful conflict management procedure but a weak disclosure system has built the response mechanism without the trigger.

Building a disclosure architecture that works requires attention to three distinct challenges: making disclosure easy enough that people actually do it, making the obligation clear enough that people understand when they are required to do it, and making the process safe enough that people are not deterred from disclosing by fear of the consequences. Each challenge requires a different design response, and each is frequently underweighted in programmes that have focused primarily on the documentation and management side of the framework.

"A disclosure system that employees find confusing, burdensome, or risky will produce systematic under-disclosure — not because employees are trying to conceal conflicts, but because the system has not been designed from the perspective of the person who is trying to decide whether and how to use it. The design of the disclosure process is as important as the design of the management framework that follows it."

Periodic declaration, event-triggered disclosure, and an accessible standing mechanism.

Periodic declaration is the foundation: a structured process, typically annual, through which all employees at relevant levels complete a formal declaration covering the categories of interest the organisation has defined as requiring disclosure. Periodic declaration creates a baseline — a documented record, updated regularly, of the interests that employees have declared — and creates the compliance obligation that makes non-disclosure a disciplinary matter rather than an oversight.

The design of the periodic declaration form is more consequential than it appears. A form that lists specific categories of interest — shares in suppliers or competitors, family members employed by counterparties, external board positions, business interests outside the organisation — and asks binary yes or no questions produces a narrower range of disclosures than one that uses open-ended questions alongside categorical ones. The best forms combine both: structured questions that capture the obvious categories, and open-ended questions that invite employees to identify situations they are uncertain about or that do not fit neatly into the defined categories.

Event-triggered disclosure is the requirement to disclose when a relevant situation arises, regardless of whether the next periodic declaration cycle is imminent. An employee who acquires shares in a supplier in March should not wait until the January declaration to disclose that interest. A manager who begins a romantic relationship with a direct report should disclose immediately, not at the next annual cycle. The event-triggered obligation requires that employees understand the disclosure requirement well enough to recognise when a triggering event has occurred — which depends entirely on the quality of the training and communication that supports the framework.

The standing mechanism is the always-available channel through which employees can disclose a situation, ask a question about whether a situation requires disclosure, or seek guidance on how a disclosed situation will be managed. This mechanism is particularly important for apparent and potential conflicts — situations where the employee is uncertain whether disclosure is required and where the answer depends on a judgment about perception and proportionality that a compliance professional is better placed to make than the individual employee.

The most revealing question about a disclosure architecture's adequacy is not how many disclosures it receives but what proportion of the disclosures it receives are event-triggered versus periodic. An architecture that receives disclosures almost exclusively through the annual declaration process and very few through the event-triggered mechanism is an architecture where employees are not recognising triggering events in real time — which means they are either not applying the framework to their day-to-day decisions, or they are not confident enough in the guidance to use the standing mechanism when uncertainty arises.

Fear of consequences is the most common reason adequate conflicts go undisclosed.

Employees who hold interests that require disclosure frequently delay or avoid disclosing them because they fear the consequences: that the disclosure will result in the removal of a valued responsibility, that it will attract scrutiny to their personal financial arrangements, that it will damage their relationship with a manager, or that it will be interpreted as an admission that they have already acted improperly.

These fears are understandable and, in some cases, rational — in organisations where previous disclosures have been handled with insufficient sensitivity or where the response to disclosure has felt disproportionate to the situation disclosed. Addressing them requires that the compliance function communicate clearly and consistently about what disclosure leads to: not automatic disqualification from a role, not disciplinary action, but an assessment and a conversation about how the situation can be managed in a way that protects both the individual and the organisation.

The principle that early disclosure is always better than late disclosure — better for the individual, better for the organisation, and better for the relationship between them — needs to be demonstrated through the organisation's handling of actual disclosures, not just communicated through policy. Every time a disclosure is received and handled proportionately, transparently, and with respect for the individual's position, the disclosure system gains credibility. Every time it is handled badly, it loses credibility that is very difficult to rebuild.

"The disclosure architecture that works is the one where making a disclosure feels like the beginning of a manageable conversation — not the beginning of a disciplinary process. Building that feeling requires consistent, proportionate, respectful handling of every disclosure the system receives. It is built one disclosure at a time."

Download this article

Save a PDF copy for offline reading, or share it with a colleague who might find it useful.

Download PDF