L1 · Immediate Actions
4 hours for the dependency audit, Emergency Operations Guide, and initial reflection.
Method / Operating knowledge
Under the conversation is a library organised around recurring hospitality problems. It connects the situation a team is facing with explanations, practical interventions and the Tools needed to carry them out.
This guide explains how the parts fit together and opens one published Block, Succession Planning, in detail. You can inspect its route, responsibilities, Tools and source without creating an account or changing an operating record.
01 / Library structure
The names describe how the knowledge is organised. A team does not need to memorise the library structure to use it.
02 / Selecting a response
A late opening, repeated shortage or a decision that always waits for the owner can all raise a question. SANDR considers the available accounts and permitted venue history before suggesting an underlying problem and a response.
The library connects problem patterns with relevant Blocks. That relationship gives the suggestion a reason that can be inspected. It does not establish the cause by itself: the same symptom can have different explanations in different venues.
The manager can study the Guide, question the interpretation and decide whether to move forward. Opening a Block is a read-only step; it does not activate a Plan.
03 / From a Block to a Plan
Blocks organise their route into three levels. The timing and effort depend on the individual Block and the venue; they are not three tasks to complete in one sitting.
After approval, the Plan gives the relevant actions an owner and timing. Linked Tools support execution. Reviews ask both whether the work happened and whether the original situation changed.
For a handover routine, completed handovers show use; fewer missing-information incidents show a possible effect. If the paperwork is current but the problem remains, the response or its explanation needs another look.
Explore one illustrated decision trail04 / Published example · B207
This Block addresses dependence on the owner: decisions, supplier relationships, access and operating knowledge that are difficult to transfer. It covers emergency continuity, delegation, successor development and preparation for a possible ownership transition.
In the library it sits within Growth & Strategy, in Expansion & Market Positioning. The Owner role is responsible. The record describes early changes within 1–2 weeks and a settling window of 1–2 quarters; developing a successor can take much longer. These are planning estimates from the source, not guarantees.
This is the published B207 v3.0 record, identified in its source as AI-generated. Its targets and time estimates are intended checks, not evidence of achieved results. The example explains the structure; applying it requires review against the actual business.
Inspect the complete Block sourceIndependent venues often keep supplier relationships, customer knowledge, staff authority, financial oversight, access, and operating judgement with the owner. An unexpected absence can therefore become a business-continuity problem very quickly. Succession planning is not a promise that the owner is leaving tomorrow. It is the work of making the business capable of surviving their absence and preparing a deliberate transition if one is needed.
Use it when too much of the venue depends on the owner, or when the business wants to prevent that problem before it becomes serious.
4 hours for the dependency audit, Emergency Operations Guide, and initial reflection.
12 hours for SOP documentation, successor identification, financial preparation, and professional consultations.
4 hours per quarter for successor development reviews, plan updates, and broker discussions.
The Owner is responsible across L1, L2, and L3.
The first question is not “who takes over in five years?” It is: what breaks if the owner disappears tomorrow? L1 exposes the immediate dependencies, secures essential financial and supplier continuity, and leaves another authorised person with a usable two-week emergency route.
L2 systematically reduces owner-dependency throughout the business. The owner documents the processes they still carry alone, gives another person supervised practice, chooses a realistic succession route, and begins the financial and legal preparation needed to make that route viable.
L3 turns the plan into a living strategy. Readiness is tested through real delegated decisions and extended owner absences; internal succession, external sale, and family transfer are treated as different routes with different evidence rather than assumed outcomes.
All five Tools belong to B207 and are owned by the Owner role. Their complete working records remain inspectable.
Lists every task, decision, relationship, and knowledge area that currently depends on the owner, scored by criticality and ease of delegation.
Inspect Tool source →Provides instructions for running the cafe during unplanned owner absence, including financial access, suppliers, decision authority, staff management, and escalation contacts.
Inspect Tool source →Covers the preferred transition route, successor identification, development milestones, financial preparation, timeline, and annual review schedule.
Inspect Tool source →Tracks skills, delegated responsibilities, completed periods of working independently, and readiness at 6, 12, and 18 months.
Inspect Tool source →Covers financial record clean-up, lease review, asset inventory, business structure, valuation preparation, and broker engagement.
Inspect Tool source →The record defines completion evidence and intended outcome checks separately. The targets below belong to this example Block; they are not reported customer outcomes.
The owner accepts the need but continually postpones the real work, leaving the business vulnerable to sudden incapacity. Early signs include stale Tools, missing evidence, missed reviews, and the same reliance on the owner returning while the Plan is described as “in place.”
A successor is named but does not receive genuine authority, access, development investment, or meaningful decisions. The title changes; the reliance does not.
Years of weak records or owner-dependency suppress the valuation when the owner finally wants to sell.
A family member is treated as the successor without an honest discussion about desire, capability, or fit.
Prevention: tie the Block to a named owner, timings, follow-up, live Tool use, and a regular management review.
If it slips: return to the smallest live routine the team can keep, re-brief what good execution looks like, and move to related work such as B164 if the problem has moved beyond this Block’s scope.
The record applies across independent cafes, specialty-coffee venues, chains, franchises, drive-throughs, kiosks, coffee vans, and bakery cafes, with a recorded team-size range of 1–99 people.
B207 belongs to D11 · Growth & Strategy and uses M11 · Expansion & Market Positioning as its primary execution Module.
The diagnostic record connects four Failure Modes – FM086, FM089, FM090, and FM115 – to Response Pattern RP049, which can point SANDR towards this Block. B207 then carries five linked Tools through its L1, L2, and L3 route.
The source connects B207 with B164 · Business Plan & Strategy as a dependency and possible next Block. It is related work whose timing depends on the actual business, not a blanket rule that one Block must always precede the other.
This Guide explains how the Block works. It is not financial, legal, employment, or succession advice for a specific company.
B207 · Succession Planning · version v3.0
Schema 3.0 · state: enriched · enrichment level: gold
The source identifies this record as AI-generated. It is open to review and should not be read as independently validated guidance.
4 March 2026 · claude_direct_v2
D11_growth_strategy · M11: Expansion & Market Positioning
Succession, exit planning, leadership, business sale, delegation, owner dependency, growth strategy, and resilience.
The complete JSON source remains public so every field and relationship can be inspected rather than hidden behind the Guide.
05 / Articles and learning
Articles provide context around a situation: why it can happen, which details deserve attention and how to reason about it. They can be browsed or brought into a relevant conversation alongside signals and practical knowledge.
An Article can connect to Domains, Signals, Blocks, Tools and related reading. SANDR can use its text as source material and relate it to the venue's question. People can save Articles and return to their reading progress.
The distinction matters during onboarding and management conversations. An explanation can build understanding without becoming another task. When action is needed, a Block describes the intervention and a Plan carries the approved work.
Later results help the team review its decisions. A successful routine can be retained; an ineffective response needs adjustment or a new explanation. The record of what was tried and why remains useful either way.