Keep a founder commitment ledger that shows capacity consequences

Founders make commitments in places that calendars do not capture

Founders make commitments in places that calendars do not capture: at the end of a customer call, in a hiring conversation, during an investor update, or through a quick message to a team lead. The visible event may take thirty minutes, but preparation, review, travel, and follow-up consume additional capacity. A commitment ledger gives founder operations support a way to show that full burden before new promises collide. It is not a second calendar and it is not a ranking of company strategy. It is a compact record of what the founder has agreed to, who relies on it, what work surrounds it, and which leader can change it. The founder still chooses priorities. Support makes the consequences of those choices easier to see.

Record commitments at the point of confirmation

Record commitments at the point of confirmation. Include the promise in the founder's original terms, the stakeholder, the source conversation, the due date and its source, the accountable owner, the founder's required contribution, preparation steps, review time, and follow-up. Distinguish a tentative intention from a confirmed promise. If the date is inferred, label it as an assumption and ask for confirmation. Link to the authoritative project or relationship record rather than copying sensitive context into the ledger. A useful entry might say that the founder owes a decision on a hiring plan after finance and the hiring manager provide evidence. It should not reproduce candidate details in a broad coordination tool.

Convert each promise into capacity blocks without pretending

Convert each promise into capacity blocks without pretending that the estimate is exact. Show the known meeting time and the surrounding work separately. Preparation may belong to an executive assistant, chief of staff, functional owner, or the founder. Name each owner. Include recovery or transition time when the calendar rules already call for it, especially around travel or dense external meetings. The ledger should reveal collisions early: two deliverables need the same review hour, a board item depends on figures arriving late, or an external appearance removes the only preparation window. Support can propose sequencing choices and show what moves. It should not silently cancel, downgrade, or reassign a material commitment.

Review the ledger in a short cadence tied to real planning

Review the ledger in a short cadence tied to real planning. Begin with changes, not a recital of every line. Which new promise entered? Which source date moved? Which preparation owner is blocked? Which decision has reached its responsible deadline? Which tentative item now needs confirmation or release? A founder may decide to decline, delegate, renegotiate, change scope, or protect more time. Record the choice and the person who will communicate it. If the founder defers a decision, state the next review time and the consequence of waiting. "Pending" without a trigger merely hides the collision until a stakeholder asks again.

Keep the ledger honest by closing work precisely

Keep the ledger honest by closing work precisely. A meeting held does not mean the commitment is complete if a promised note or decision remains open. Mark completion when the agreed outcome has been delivered or formally released. Preserve changed terms so the team can distinguish a renegotiated promise from a missed one. Avoid performance theater: a green dashboard can coexist with repeated last-minute preparation if entries omit hidden work. Sample completed and missed commitments to compare estimated surrounding effort with what happened. Use the differences to improve planning rules, not to manufacture a productivity score for the founder.

The ledger becomes especially useful when deciding what kind

The ledger becomes especially useful when deciding what kind of support to hire. If the load consists mainly of scheduling, preparation retrieval, and follow-up, executive assistant support may fit. If commitments regularly collide across functions and require tradeoff briefs, chief of staff support may be closer to the need. If delivery work lacks owners and dependencies, executive project coordination may be the missing capability. The record informs that choice without claiming that one role can solve unclear strategy. The practice is working when the founder sees a proposed commitment beside its capacity cost, the support team knows what it may prepare, and stakeholders receive updates from a named owner. The ledger should reduce surprise, not become another place where promises disappear.

Set retention and visibility deliberately

Set retention and visibility deliberately. The ledger may reference investor, customer, hiring, board, or personal commitments, so broad access can create unnecessary exposure. Keep the operational view limited to what authorized contributors need and store sensitive source material elsewhere. When a commitment closes, retain the outcome and approved historical record under the organization's policy, then remove temporary working detail that no longer serves coordination. A monthly case review can identify promises accepted through channels that bypass the ledger. The response should be a simpler capture habit, not surveillance of every founder conversation. Give close partners an easy way to flag a commitment, and let support confirm it with the founder before treating it as final. During backup coverage, select only the entries whose timing falls inside the window and state what the backup may do. This makes continuity manageable without transferring the founder's whole context. If leaders resist the ledger because it feels burdensome, reduce fields to those used in actual choices. Outcome, stakeholder, timing, founder contribution, surrounding owners, and change authority often reveal enough. A small record that influences the weekly plan is better than a complete register nobody trusts. Its value appears at the moment a new request arrives and the founder can see which existing promise would absorb the cost. Review declined commitments too. They show whether the intake and preparation work was useful even when the answer was no, and they can reveal requests that keep returning through another channel. Record the disposition without turning the ledger into a list of rejected people or speculative opportunities.

Frequently asked questions