How Courts Evaluate the Way Organizations Actually Operate
Most commercial disputes begin with a disagreement about facts, contracts, duties, money, or responsibility, but many eventually turn on a more difficult question: what would a reasonable organization, executive, manager, lender, board, employer, or commercial actor ordinarily have done in the circumstances?
That question sits at the boundary between law and management.
Judges and lawyers are skilled at determining legal obligations, interpreting contracts, assessing testimony, and applying precedent. What can be much harder is understanding the practical reality of how organizations actually function: how authority is delegated, how decisions are escalated, how records are created, how exceptions are handled, how managers exercise discretion, what constitutes ordinary commercial practice, and whether conduct that appears unusual in hindsight was in fact reasonable at the time.
These issues increasingly matter because modern organizations are complex systems. Decisions are rarely made by one person acting in isolation. They emerge through policies, systems, committees, approvals, informal practices, professional judgment, and organizational routines that may never be fully captured in a single document.
When litigation eventually arrives, those invisible systems can become central evidence.
This ten-part Arcus series examines that intersection between organizational practice and legal dispute: how business judgment can be examined systematically, why hindsight creates serious analytical risks, and how courts, counsel, and organizations can better understand what actually happened inside a business before concluding whether the conduct was reasonable.
Get in touch for a discovery session.
Project Discovery Session
In our brief Discovery Session, we will explore your definition of success for your project and map project milestones.
When Business Judgment Becomes Evidence is an Arcus Consulting Group executive and legal series examining how organizational practice, decision-making, management systems, commercial judgment, and institutional behaviour can become relevant in litigation and regulatory disputes.
It is intended for litigators, general counsel, corporate executives, boards, insurers, financial institutions, professional firms, and organizations involved in complex commercial matters where the reasonableness of business conduct is at issue.
The central proposition is straightforward: when a dispute involves what an organization knew, who should have acted, whether a matter should have been escalated, whether a process was ordinary, or whether management behaved reasonably, legal analysis may benefit from a deeper understanding of how organizations actually operate.
A useful starting question for counsel is therefore not simply:
“What documents do we have?”
It is:
“What organizational system produced these documents, decisions, and actions?”
That question can reveal different witnesses, different records, different explanations, and occasionally a different theory of the case.
The Arcus Business Evidence and Expert Advisory offering can support counsel through early organizational analysis, business-process reconstruction, commercial-reasonableness assessment, expert consulting, and, where appropriate, independent expert evidence.
The strongest expert contribution is rarely to tell the court what conclusion it should reach.
It is to make the business sufficiently understandable that the court can evaluate the evidence in its proper organizational context.
A commercial dispute can generate thousands of pages of records, months of examinations, multiple expert reports, and competing legal theories, yet the real issue may eventually narrow to something surprisingly practical. Was the conduct at issue consistent with how a reasonable organization would ordinarily operate under similar circumstances?
That question sounds straightforward until one tries to answer it.
There is rarely a single manual describing how every important business decision should be made. Organizations operate through combinations of written policy, professional discretion, informal norms, delegated authority, commercial pressures, established practice, and judgment exercised under imperfect information.
The challenge is therefore not merely to locate a policy and ask whether it was followed. The more useful inquiry is often whether the organization’s actual decision-making system was reasonable.
Policies are only part of the story
Suppose a lender’s written policy requires periodic account review.
A dispute later arises over whether a particular account received appropriate attention.
The policy may establish an expectation, but it does not by itself reveal:
how exceptions were identified;
which systems generated alerts;
who reviewed those alerts;
what information was available;
when escalation normally occurred;
who had discretion;
how competing risks were prioritized;
whether the matter was unusual.
Those facts may determine whether the organization’s conduct was commercially reasonable.
The same problem appears in almost every industry. A hospital may have a clinical protocol, but professional judgment still matters. A corporation may have an acquisition policy, but boards retain discretion. An employer may have a disciplinary framework, but managers must interpret circumstances. A financial institution may have risk procedures, yet decisions still require judgment.
Reasonableness must be reconstructed
A useful examination therefore often begins by reconstructing the decision environment as it existed at the time.
What did management know?
What could it reasonably have known?
What systems were operating?
What alternatives were available?
What authority did the relevant individuals possess?
What pressures or constraints existed?
What would comparable organizations typically have done?
Once those questions are answered, the analysis becomes much more grounded.
The Arcus perspective
This is where organizational and management expertise can add value in litigation. Arcus can examine the conduct not by substituting legal conclusions for those of the court, but by helping explain the organizational context within which the conduct occurred.
The distinction is important.
The expert should not tell the court who should win.
The expert can help the court understand how organizations of this type ordinarily make decisions, allocate responsibility, manage risk, and exercise commercial judgment.
That may provide the context required to evaluate whether the conduct was unusual, deficient, ordinary, or reasonable.
Once something has gone wrong, the chain of events often looks obvious.
The warning signs seem clearer.
The missed opportunity appears undeniable.
The alternative course appears rational.
The eventual loss seems predictable.
But none of that means the outcome was predictable when the original decision was made.
This is one of the central dangers in evaluating organizational conduct.
Organizations make decisions forward
Courts necessarily examine disputes backward.
That difference creates a powerful cognitive distortion.
A board that rejects an acquisition before the target triples in value can later appear shortsighted.
A lender that extends credit before a market collapse can appear reckless.
A manufacturer that maintains a supplier relationship before a major disruption can appear complacent.
An employer that does not immediately dismiss a struggling executive can appear indecisive once subsequent problems emerge.
Yet management did not possess the future when the decision was made.
The relevant question is not whether the decision looks good after the outcome is known.
It is whether the decision process was reasonable given the information available at the time.
Separate outcome from process
This distinction is fundamental.
A poor outcome can follow a good decision.
A good outcome can follow a terrible decision.
Consider two executives making identical investments. One happens to benefit from an unexpected regulatory change while the other is harmed by an unforeseen geopolitical event. The eventual financial result tells us little about the quality of the original decision unless we examine what each executive knew and how the decision was reached.
The same principle should apply in commercial disputes.
Reconstruct the information set
A disciplined analysis asks:
What information existed on the relevant date?
Which information had actually reached the decision-maker?
What signals would ordinarily have been regarded as significant?
Which uncertainties remained unresolved?
What alternatives were realistically available?
How much time was available to act?
What would a reasonably experienced decision-maker have understood from those facts?
This is very different from assembling every document produced during litigation and treating all of it as though it had been known simultaneously.
Why expert analysis can help
Management experts can assist by reconstructing the organizational decision context rather than simply recounting the chronology.
That may involve distinguishing between:
information stored somewhere in the organization;
information ordinarily accessible to a particular role;
information that had actually been escalated;
information that would normally have triggered action.
These distinctions can become decisive because organizations are not omniscient entities. Information can exist inside a company without being practically available to every individual responsible for making a decision.
The broader lesson
Executives should understand this even before litigation arises.
Good records should document not only what was decided but the principal assumptions, information, and rationale supporting the decision.
Years later, that contemporaneous record may provide a far more accurate account of the organization’s judgment than any reconstruction performed after the dispute has begun.
When lawyers begin examining responsibility inside an organization, the organizational chart is an obvious starting point.
It identifies titles.
Reporting relationships.
Hierarchy.
Sometimes formal authority.
But it can also be misleading.
Organizations frequently operate through informal influence, delegated authority, committees, functional expertise, dotted-line relationships, and exception processes that do not appear on any chart.
Formal authority and practical authority can differ
Imagine a major customer account experiencing difficulty.
The account manager owns the relationship.
Risk management controls exposure.
Finance monitors performance.
Legal advises on contractual rights.
A credit committee possesses formal approval authority.
A senior executive can intervene.
Who made the decision?
Depending on the issue, the answer could be all of them or none of them individually.
This matters because litigation often seeks to identify a single person who was “responsible.”
The organization may not have functioned that way.
Decisions move through systems
A more useful approach maps the actual decision process.
Who identified the issue?
Who gathered information?
Who interpreted the information?
Who recommended action?
Who had authority to approve?
Who could prevent action?
Who implemented the decision?
Who monitored the outcome?
These questions reveal something an org chart cannot: decision architecture.
Why this matters in examinations
A witness may truthfully say, “I did not make that decision,” even though the person’s role materially influenced the outcome.
Another witness may possess formal authority but rely almost entirely on recommendations prepared elsewhere.
Understanding these distinctions can transform the quality of questioning.
Instead of repeatedly asking “Who was responsible?” counsel can examine the workflow through which responsibility was exercised.
The invisible organization
Every organization contains an invisible structure alongside the formal one.
It includes:
trusted advisers;
experienced employees;
committee dynamics;
escalation customs;
informal approval expectations;
relationships between head office and operating units.
These patterns can be highly relevant when assessing whether a decision process was normal.
The Arcus approach
An organizational-practice analysis can reconstruct this architecture from documents, testimony, policies, systems, and role descriptions.
The result is not simply an organization chart.
It is a map of how the organization actually acted.
That can help counsel identify missing witnesses, misunderstood roles, unexplored systems, and inconsistencies between formal policy and actual practice.
Written policies carry enormous evidentiary weight because they appear objective.
The policy said X.
The employee did Y.
Therefore the conduct was wrong.
Sometimes that conclusion is appropriate.
But organizations do not operate entirely through mechanical compliance.
Policies establish frameworks. Judgment operates inside them.
Policies can be mandatory, advisory, or contextual
Some rules permit no discretion.
Others establish general expectations.
Still others describe preferred practice while allowing management to respond differently when circumstances justify it.
The distinction matters.
A policy requiring two signatures on a transaction may be fundamentally different from a policy stating that certain circumstances “should ordinarily” be escalated.
Both are policies.
Their operational meaning is not the same.
Compliance can also conceal poor judgment
Suppose management technically satisfies every step in a risk-review policy but ignores obviously deteriorating conditions.
Formal compliance may exist.
Commercial reasonableness may not.
The reverse can also occur.
Management may depart from a standard procedure because an unusual situation requires immediate action, yet the decision may still be entirely reasonable.
Ask what the policy was designed to accomplish
A strong analysis therefore examines purpose.
Why did the rule exist?
What risk was it designed to address?
How much discretion was contemplated?
How was the policy normally interpreted?
Were exceptions common?
Who possessed authority to approve them?
Was the underlying objective still achieved?
This turns a binary compliance question into a more realistic examination of organizational practice.
Context matters
Policies should also be understood inside the wider operating environment.
A policy written for ordinary conditions may function differently during a crisis.
A decentralized organization may rely more heavily on local management discretion.
A regulated institution may maintain highly formal controls.
An entrepreneurial company may operate through faster, less documented decision processes.
Commercial reasonableness is therefore rarely determined by policy text alone.
The practical lesson for organizations
Companies should periodically examine whether policies match actual practice.
A policy that everyone routinely ignores is not a strong governance tool.
Neither is a policy so ambiguous that nobody understands when escalation is required.
Those weaknesses may remain invisible during normal operations.
Litigation has a way of exposing them.
Document production is central to commercial litigation.
Emails.
Minutes.
Reports.
Spreadsheets.
Policies.
Contracts.
Correspondence.
Yet a surprising amount of organizational activity occurs inside systems that may not initially be obvious from traditional document categories.
This creates an important question:
What systems did the organization actually use to perform the work at issue?
Modern organizations leave many kinds of records
A financial institution may use:
customer relationship systems;
credit systems;
exception reports;
risk dashboards;
workflow software;
transaction-monitoring tools;
approval systems;
internal messaging;
portfolio-monitoring applications.
A manufacturer may rely on:
maintenance systems;
quality-control records;
inventory platforms;
production logs;
supplier databases.
A professional-services firm may use:
document systems;
time records;
matter-management software;
client relationship platforms.
If litigation examines organizational conduct without understanding the underlying systems, important evidence can be missed.
Search scope depends on operational understanding
Imagine a dispute about whether a risk was monitored.
Searching email may reveal discussions.
But what if monitoring principally occurred through an internal dashboard?
What if exceptions appeared in a weekly report?
What if an automated alert existed?
What if the relevant workflow was recorded in a proprietary system rather than correspondence?
The absence of an email would tell us very little.
Start with the process
A better sequence is:
How was this activity performed?
Which systems supported it?
What records did those systems create?
Who used them?
How long were records retained?
What fields were searchable?
Only then can document discovery be meaningfully assessed.
This can materially change litigation strategy
A process-focused examination may reveal that apparent documentary gaps have innocent explanations.
It can also reveal the opposite: categories of potentially relevant information that were never searched because nobody first mapped the operating system.
The Arcus perspective
Organizational experts can help bridge the gap between legal discovery and business operations.
The role is not to conduct forensic technology work unless specifically qualified to do so.
It is to help identify the operational architecture that determines where relevant records would normally be created and maintained.
In complex institutional litigation, that distinction can be extremely valuable.
Organizations accumulate practices that are never formally written down.
Experienced employees know them.
Managers understand them.
New hires learn them through observation.
These practices can influence decisions as powerfully as written policy.
In litigation, however, informal practice is difficult to prove because it exists partly in organizational memory.
Established practice matters
Suppose company policy allows customer exceptions with senior approval.
The written policy says little more.
But perhaps the company has followed the same informal approach for years:
the account manager prepares the case;
finance reviews the economics;
legal assesses risk;
a particular committee discusses unusual cases;
the senior executive rarely intervenes unless the exposure exceeds a threshold.
That pattern can become relevant when determining whether a disputed transaction was extraordinary or entirely routine.
But anecdotes are not enough
One employee saying, “We always did it this way,” does not automatically establish organizational practice.
A reliable analysis looks for corroboration.
Repeated examples.
Consistent testimony.
Templates.
Committee records.
System workflows.
Historical decisions.
Training materials.
Internal correspondence.
Patterns across time.
The objective is to distinguish genuine organizational practice from individual recollection.
Practice can also contradict policy
This creates a more difficult issue.
If written policy says one thing but the organization systematically operates another way, which better describes the actual standard of conduct?
The answer depends heavily on context.
The inconsistency itself may be significant.
It can suggest weak governance, informal modification of practice, or a gap between head-office policy and frontline reality.
Why this matters to counsel
Evidence of established practice can help explain actions that otherwise look irregular when viewed in isolation.
Conversely, proving that the disputed conduct departed materially from years of ordinary practice can strengthen an argument that something unusual occurred.
The executive lesson
Leaders should not assume that only written policies define organizational behaviour.
Culture, habit, precedent, and informal norms often form a parallel operating system.
If those norms matter, management should understand them before litigation forces everyone else to reconstruct them.
One of the easiest analytical mistakes in a business dispute is to evaluate conduct against an idealized standard.
Could management have asked another question?
Yes.
Could another review have been performed?
Probably.
Could documentation have been better?
Almost always.
Could another control have existed?
Certainly.
If perfection becomes the standard, virtually every organization will fail.
Real businesses operate under constraints
Managers work with incomplete information.
They face deadlines.
They allocate attention among competing priorities.
They rely on employees.
They make judgments.
They incur costs to obtain additional information.
They sometimes choose speed over certainty.
They may choose commercial flexibility over control.
Reasonableness has to account for these realities.
Every control has a cost
Consider a business attempting to eliminate fraud.
It could theoretically require multiple approvals, extensive verification, manual review, and senior oversight for every transaction.
Fraud risk might decline.
The business might also become unusable.
Management therefore balances:
risk;
cost;
speed;
customer experience;
operational capacity.
This balancing process occurs everywhere.
A reasonable organization is not one that eliminates every risk.
It is one that manages risk in a manner proportionate to the circumstances.
The proportionality question
A useful analytical framework examines:
the magnitude of potential harm;
the probability of harm;
the cost of additional control;
the information available;
industry practice;
the reversibility of the decision.
The expected level of diligence should generally rise as consequences become more significant.
Avoid the “could have” trap
Litigation frequently identifies actions management could have taken.
That does not establish that a reasonable organization would have taken them.
The distinction is critical.
There are almost always additional precautions available.
The relevant question is whether the precautions actually taken were commercially reasonable in context.
Why this matters
Expert evidence is most useful when it helps the court understand the real operating trade-offs organizations face rather than constructing an imaginary world in which every foreseeable risk receives unlimited resources and attention.
Business judgment is necessarily imperfect.
Reasonableness should be assessed accordingly.
Many organizational disputes ultimately turn on escalation.
Someone knew something.
When should it have been reported upward?
To whom?
At what point did an ordinary operational issue become sufficiently serious to require senior attention?
These questions appear simple only after the event.
Organizations cannot escalate everything
If every operational anomaly reached the CEO, the organization would collapse under its own information.
Management therefore establishes explicit or implicit thresholds.
Frontline employees handle routine matters.
Managers handle exceptions.
Senior executives handle material issues.
Boards oversee the most consequential risks and strategic choices.
The challenge is determining when a matter crosses one of these boundaries.
Escalation depends on signals
A single missed payment may not matter.
Repeated missed payments may.
A small cost overrun may be ordinary.
A pattern of overruns may indicate a larger problem.
One customer complaint may be noise.
Twenty similar complaints may be evidence of systemic failure.
Escalation is therefore partly a pattern-recognition exercise.
Look for thresholds
A strong organizational analysis asks:
Were there formal escalation rules?
Were there financial thresholds?
Did software generate flags?
Were certain categories automatically referred upward?
How had similar cases been handled historically?
Did management possess discretion?
When did the information become qualitatively different?
These questions can clarify whether an individual reasonably treated the matter as routine or should have recognized it as exceptional.
Senior management should care about this now
Organizations should examine whether their escalation architecture is actually understood.
Ask a manager:
What would cause you to bring this issue to your boss?
Then ask the boss:
What do you expect that manager to escalate?
If the answers are materially different, the organization has discovered a governance gap.
Litigation merely reveals the gap
When escalation fails, responsibility is often assigned to the individual who did not act.
Sometimes that is appropriate.
Sometimes the deeper problem is that the organization never created a clear escalation system.
That distinction can matter enormously.
Expert reports can become highly technical.
Definitions.
Assumptions.
Standards.
Authorities.
Opinions.
Conclusions.
All are important.
But in complex organizational disputes, the reader may first need something more fundamental:
an understandable explanation of how the business actually works.
Context makes evidence intelligible
Imagine a dispute involving commercial banking.
Before evaluating whether a decision was reasonable, the reader may need to understand:
relationship management;
credit approval;
risk monitoring;
account review;
exception management;
collateral;
escalation;
portfolio oversight.
Without that context, individual documents can be misinterpreted.
A report or email may look decisive when it was merely preliminary.
A committee may appear responsible when it was advisory.
A system flag may seem important without understanding what the flag actually signified operationally.
The expert as translator
One valuable role of an organizational expert is translating institutional complexity into language a judge can readily understand.
That does not require oversimplification.
It requires structure.
What was the organization trying to accomplish?
How was work divided?
How were decisions made?
What controls existed?
Where did discretion reside?
What would ordinarily happen next?
Once the operating model is clear, opinions become easier to evaluate.
Avoid the advocacy trap
The strongest expert evidence should not read like counsel’s factum written by another author.
An expert who overstates the case can undermine credibility.
A more persuasive report identifies:
what is supported;
what is uncertain;
what is unusual;
what is consistent with ordinary practice;
where reasonable professionals might disagree.
That analytical discipline often carries more weight than absolute language.
The implication for counsel
Engaging an expert early enough to understand the business can improve more than the report.
It can influence discovery strategy, witness identification, document requests, examination topics, and theory of the case.
By the time the report is drafted, some of the most valuable expert work may already have occurred.
Commercial litigation is often organized around legal claims.
That is necessary.
But complex organizational disputes can benefit from a parallel question:
What would we need to understand about the business in order to know whether the conduct makes sense?
That question can lead to a different kind of early case analysis.
Start with the operating model
Before drawing conclusions, reconstruct:
the organization;
the roles;
the systems;
the policies;
the decision rights;
the escalation processes;
the relevant chronology;
the information available;
the ordinary practices.
This creates the factual architecture of the organization.
Then isolate the disputed decision
What exactly is being criticized?
Who participated?
What alternatives existed?
What constraints applied?
What was known at the time?
What would comparable organizations ordinarily have done?
Which parts of the conduct were routine?
Which were unusual?
Test competing explanations
A good review should not begin by assuming one side’s interpretation.
Instead consider several possibilities.
Perhaps the process was deficient.
Perhaps the outcome was unfortunate but the process reasonable.
Perhaps a policy existed but did not apply as asserted.
Perhaps the wrong organizational actor has been identified.
Perhaps the relevant records reside in a system nobody has yet examined.
Perhaps hindsight is distorting the analysis.
The value lies in testing these explanations against evidence.
A potential Arcus Business Evidence Review
Arcus can develop an early-stage service for counsel, general counsel, insurers, boards, and organizations facing complex commercial disputes.
The review could examine:
- organizational structure;
- decision architecture;
- policies and practices;
- role accountability;
- escalation processes;
- information flows;
- relevant systems;
- commercial norms;
- management judgment;
- chronology;
- evidentiary gaps;
- potential expert issues.
The engagement can be structured initially as consulting support rather than testimony, allowing counsel to understand the organizational issues before deciding whether expert evidence is ultimately required.
Why early involvement matters
A complex case can become much harder once discovery has substantially progressed.
Witnesses may already have been examined.
Document categories may have been defined.
The theory of the case may have hardened.
Important operational questions may never have been asked.
Bringing organizational analysis into the case earlier can expose those gaps while they can still be addressed.
The broader opportunity
The most significant evolution in expert evidence may not involve producing more expert reports.
It may involve using expertise earlier to understand the system behind the dispute.
That is particularly important when the litigation involves institutions whose internal operations are unfamiliar to the court.
Banks.
Insurers.
Healthcare organizations.
Governments.
Manufacturers.
Professional firms.
Large employers.
Complex family enterprises.
In these disputes, facts do not exist independently of organizational context.
The same email can mean something very different depending on who sent it, what authority that person possessed, which process it formed part of, and how similar matters were normally handled.
Understanding that context can materially change the interpretation of the evidence.