Governance Is a Record, Not a Judge

I have been on both sides of acting without authority.

In one case, I sat on a board considering an investment. Another member used funds for travel without first seeking the board's approval. I asked for an explanation while it was happening and received none until much later, when a formal inquiry made silence impossible.

The expense might have been defensible on business grounds. What changed the case was an unsolicited remark: “just do it and beg for forgiveness later.” The member knew the limits of his authority and treated procedure as an obstacle. The remaining board members agreed that discipline was warranted.

In another case, an organization's network went down. I was the senior person immediately available, but not the person formally authorized to terminate anyone. The record showed that a newly arrived contractor had committed the settings that caused the outage, then denied doing so. Someone else alleged that his credentials must have been false. I could not verify that accusation, so I refused to rely on it. I acted only on what the logs established: the change had been made, and the denial contradicted the record. I ordered him to leave and had the contract ended.

I had acted without authority too.

The same formal defect appeared in both cases. Yet I still believe the two acts deserve different treatment. The reason cannot simply be that mine worked out and the other did not. That would make governance nothing more than outcome bias wearing a suit.

The difference was answerability.

Procedure makes a body

Legitimacy is procedure: a decision becomes binding because it was reached in the agreed way, not merely because someone considers it reasonable. Governance is that principle applied to an organization.

A board is not a collection of people who each possess the whole authority of the body. The office of director may carry power and responsibility, but the board ordinarily acts through whatever procedure gives the body a single voice: a meeting, a motion, a vote, a written consent, or another valid form under its governing rules.

Formalities vary by jurisdiction and constitution. Singapore's Companies Act, for example, requires minute books for specified resolutions and declarations, including those of a sole director. Delaware law places corporate management under the board and, where permitted, allows unanimous written or electronic consent filed with the minutes. These are jurisdiction-specific illustrations, not universal rules or legal advice. Collective authority needs a form, and the form needs a record.

Without that record, there is no reliable distinction between what the organization decided and what one influential person wanted.

A resolution binds the dissenters

Board members will disagree. Each may believe the others are wrong. Procedure does not eliminate that adversity; it converts it into a decision.

The resolution is the organization's finality. It commits the body to a rule, a transaction, or an enforcement choice. A member who voted against it may continue to believe it was unwise, but if the procedure was legitimate, the member has a duty to respect the result.

You may not like it, but if you respect the procedure, you respect the resolution.

The result's authority comes from rules accepted before participants knew who would prevail. Those rules should state who may decide, the required quorum, what must be recorded, and what review is available. Authority remains balanced by the duty to answer for its exercise—the same balance between power, responsibility, and accountability that applies throughout an institution.

The record preserves how the answer became the organization's answer.

The dangerous exception

Legitimacy cannot be the only good, at least not in the short term.

Organizations face emergencies. Sometimes the person closest to the event must act before the authorized body can assemble. A sharp operator may need the courage to do the right thing without proper backing, knowing that the decision may later be rejected and that the consequences will be personal.

Pretending this can never happen is a defect in governance.

But if unauthorized action is sometimes necessary, “beg forgiveness later” cannot become a standing operating model. The exception must preserve the very thing the ordinary procedure protects: answerability.

This is where the two cases diverged.

The board member was asked to explain the expense while it was happening and went quiet. The explanation arrived only after the system forced it. The expense also benefited the person who made it.

I acted at personal risk to address an operational failure, remained reachable, and was prepared to explain the decision as soon as the proper authority returned. I also refused to rely on the most inflammatory allegation because the record did not establish it. I acted on the narrower fact the logs could prove.

The resemblance still matters. I believed my decision would withstand scrutiny; the board member may have believed the same. My act was never formally ratified; it simply stood. His might have been accepted had he answered promptly. If I could know in advance that my act would be accepted, procedure would be decorative. The risk was real.

Same rule broken. What diverged was the answering.

Ratification is not forgiveness

Ratification is after-the-fact legitimization. The authorized body examines an act taken without proper authority and decides whether to adopt it as its own.

That idea has formal legal expressions. Delaware's corporate statute, for example, provides a procedure for ratifying certain defective corporate acts caused by a failure of authorization. The board's resolutions must identify the act, when it occurred, the nature of the authorization failure, and the approval of ratification. The exact legal effect and required approvals are jurisdiction-specific, but the architecture is instructive.

Ratification does not mean that every unauthorized act becomes acceptable if it produced a good result. It means the proper body develops the record and makes a new, authorized decision about the earlier act.

The person who acted remains answerable for taking the risk. The board remains answerable for ratifying or rejecting it. Neither can hide behind the other.

A healthy system can therefore tolerate some illegitimacy without celebrating it. It leaves room for courage while refusing to turn courage into self-issued authority.

The system should flag, not judge

This leads to a specific design principle: a governance system should keep the record and flag discrepancies. It should not judge.

It should be able to show:

• what rules and authorities applied;
• what the organization formally decided;
• who acted and under what claimed authority;
• where conduct diverged from the recorded procedure;
• what explanation was offered, and when;
• whether the proper body later ratified, rejected, or disciplined the act; and
• what the organization learned from the outcome.

That record supports the person or body occupying the judge's seat. It does not occupy the seat itself.

A system can detect that approval is missing. It can surface that a decision conflicts with a prior resolution. It can preserve the contemporaneous explanation so hindsight cannot rewrite it. It can prompt a review when the procedure too often, or too severely, produces the wrong result.

But it cannot decide whether an emergency justified the breach, whether an explanation is credible, whether ratification serves the organization, or whether the rule itself should change. Those are judgments. They must terminate in named humans who can be questioned and held accountable.

A governance system that never judges can still support a board that judges badly. The record constrains through exposure, not veto. Like a useful standard, it makes defects visible and gives the proper judge an opportunity to cure them. It cannot guarantee a wise cure.

Always in court does not mean always public

A durable record can make an organization feel as though it is always in court. Decisions remain visible, explanations can be compared with evidence, and governance acts cannot comfortably disappear.

That can chill candor if implemented carelessly. Not everything belongs in public. Trade secrets, personal information, privileged advice, and sensitive operational details may require strict access controls.

But privacy and disappearance are not the same thing.

The people legitimately entitled to review a governance decision must be able to inspect what happened. Matters of governance have to be able to survive public scrutiny—even when lawful confidentiality means the underlying record is not literally public. The test is whether the decision could be exposed and defended, not whether every document should be posted online.

Keep the judgment human

Governance is not the automation of obedience. It is the preservation of legitimate human authority.

Write down the rules. Record the resolutions. Flag the discrepancies. Allow real emergencies to remain possible, but require the person who acts outside the rules to answer quickly and completely. Let the proper body ratify, reject, discipline, or revise. Then preserve that decision too.

The system should make evasion difficult and judgment inspectable.

It should never pretend to be the judge.