Governance for Families
How a Lean Family Office Runs a Capital Call
The workflow behind a capital call: intake, validation, liquidity, authority, payment, evidence, record update and close.
Overview
A capital call is a good test of an operating system because it is urgent, involves money leaving the family, and touches several people at once. Handled well it is a workflow. Handled badly it is a scramble that reaches the Principal for reasons that have nothing to do with judgement.
The difference is not effort. It is whether the steps were defined before the notice arrived.
What usually happens
The notice arrives, often by email, often to whoever the fund has on file.
Then the reconstruction begins. Which fund is this? Which entity holds the commitment? How much is left to draw? Is the cash where it needs to be, or does something need to be sold or moved? Who can authorise the payment? Who tells the accountant afterwards?
None of these questions is difficult. All of them require someone who holds context, and in most offices that person is the Principal or the one person who remembers.
The work gets done. It gets done under time pressure, by the busiest person, with the answers reconstructed each time.
The workflow
Defined once, a capital call runs as a sequence.
Notice received. It arrives at a monitored destination rather than an individual's inbox.
Identify investment and entity. The register already records which entity holds which commitment, so this is a lookup rather than a question.
Validate amount and remaining commitment. The called amount is checked against the recorded commitment and drawdown history. A discrepancy stops the workflow rather than being absorbed.
Check liquidity. Available cash in the paying entity is confirmed. If it is short, the funding decision becomes its own escalation rather than a surprise at payment time.
Apply the decision rule. Written authority determines whether this proceeds under delegated authority or requires approval. Most calls within an existing commitment fall under a rule.
Principal approval only if required. The Principal is asked when the rule says so, not by default.
Execute funding. Payment is made through the agreed channel with the agreed controls.
Store evidence. The notice, the authorisation and the payment confirmation are filed against the investment.
Update the commitment register. Remaining commitment is adjusted. This is the step that most often gets missed, and missing it is what makes the next call harder.
Notify relevant advisers. The accountant and anyone whose work depends on it are told, once, through a defined route.
Close. The workflow has a stated end.
Where each step actually fails
The failures are predictable, which is what makes them designable.
Intake fails when notices arrive at individuals. Someone travels, and a deadline moves.
Validation fails when the register is stale, so the discrepancy between called and recorded is discovered late or not at all.
Liquidity fails when it is checked at payment rather than at intake, turning a fundable call into an urgent one.
Authority fails when the rule is unwritten, so every call escalates regardless of size.
Record update fails most often of all, because the money has moved and the pressure is gone. The consequence appears months later when the remaining commitment is wrong.
What the Principal should see
Under a defined workflow, most capital calls should reach the Principal as No Action, or as Know once complete.
They should reach Decide when the call is outside the delegated limit, when funding requires selling something, or when the validation step found a discrepancy.
That is the whole point. The Principal makes the decision that requires judgement. They do not provide the orchestration around it.
The starter pack
The artefact worth building is small.
A one-page workflow with the eleven steps, each with a named owner. The decision rule for capital calls, with the threshold above which the Principal is asked. The commitment register fields that must be updated at close. The list of who is notified.
Written once, it covers every subsequent call. The second one is faster than the first, and the tenth requires nobody to remember anything.
Frequently asked questions
Why use a capital call as the example?
Because it is time-bound, involves money leaving the family, and touches the investment, entity, liquidity and record-keeping layers at once. An office that runs a capital call cleanly usually has the underlying pieces in place.
What is the most commonly missed step?
Updating the commitment register after payment. The pressure ends when the money moves, so the record update is deferred and then forgotten. The cost appears at the next call, when the remaining commitment is wrong.
Does this require software?
No. It requires the steps, the owners, the decision rule and a place to record the outcome. Software can hold that well, but the discipline is what makes it work.