Method / Operating knowledge

The knowledge SANDR uses to propose practical work.

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

What the different parts do

The names describe how the knowledge is organised. A team does not need to memorise the library structure to use it.

Domains and Modules
A Domain groups a broad part of the business, such as Team & Talent or Growth & Strategy. A Module brings related work together within that area and makes it easier to browse.
Signals and problem patterns
Signals record situations that need attention. Comparing them with the venue history helps SANDR consider what may be failing. A proposed explanation still needs review.
Blocks
A Block carries a practical response to a recurring problem. It includes conditions for use, prerequisites, a staged route, responsibility, effort, linked Tools, review points and evidence of completion and effect.
Tools
Checklists, SOPs, templates and trackers support specific steps. They help a person carry out the work; a completed form alone does not establish that the business improved.
Articles
Articles explain why a problem happens, what to notice and how to think about it. They provide context alongside a signal or conversation, and connect to practical work where appropriate.
Plans
A Plan applies approved work to a particular venue, with people responsible, tasks, timing and proof. The reusable knowledge and the venue's actual execution remain distinct.

02 / Selecting a response

How SANDR checks the fit

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.

  • Situation: what observations support the interpretation, and what is missing?
  • Conditions: when does the Block apply, and when would it be unsuitable?
  • Readiness: are prerequisites, authority, Tools and a responsible person in place?
  • Capacity: can the team carry the work alongside its current commitments?
  • Connections: should related work happen first, alongside it or later?

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

How the work is staged and checked

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.

L1 · Immediate actions
Address the immediate gap or risk and establish a usable first routine.
L2 · System development
Build the process, documentation and capability needed to make the response repeatable.
L3 · Culture embedding
Keep the routine in use through practice, reviews and adjustments as circumstances change.

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 trail

04 / Published example · B207

Succession Planning

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 source
01The goal and the problem

Why it matters

Independent 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.

Main goals

  • Identify and develop people capable of taking leadership or ownership.
  • Write down critical business knowledge held only in the owner’s head.
  • Compare routes such as internal promotion, management buyout, external sale, or family transfer.
  • Set a realistic transition timeline rather than wait for emergency handover.
  • Build a business that can run without depending on one individual.

Other benefits

  • Reduce reliance on the owner and make the business easier to transfer.
  • Protect continuity for staff and the business.
  • Preserve important culture, supplier, customer, and community relationships.
  • Allow the owner to step back gradually without remaining the permanent bottleneck.
02When this Block applies

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.

Signals that can bring it forward

  • Owner burnout, health concerns, impending retirement, or a stated desire to sell or step back.
  • Critical decisions, relationships, access, or processes exist only in one person’s head.
  • The venue cannot operate confidently without the owner’s daily presence.
  • Related business-planning work with B164 shows that leadership continuity or transferability needs attention.

What must be ready first

  • The linked Tools are available and usable.
  • One named person is available for setup and review.
  • The owner is willing to look honestly at control habits and personal succession preferences.

When not to use it this way

  • Do not call the work complete because documents exist while the same reliance on the owner remains.
  • Do not hand out forms without someone responsible and a regular review.
  • Do not use succession paperwork instead of immediate help if the situation is already critical or unsafe.
03Time and responsibility

L1 · Immediate Actions

4 hours for the dependency audit, Emergency Operations Guide, and initial reflection.

L2 · System Development

12 hours for SOP documentation, successor identification, financial preparation, and professional consultations.

L3 · Culture Embedding

4 hours per quarter for successor development reviews, plan updates, and broker discussions.

Person responsible

The Owner is responsible across L1, L2, and L3.

04L1 · Immediate Actions · 0–2 weeks

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.

  1. Conduct an owner-dependency audit listing every task and relationship that relies on the owner.
  2. Ensure at least one other person has financial access for emergency operations.
  3. Write an Emergency Operations Guide for two-week owner absence scenarios.
  4. Store the guide securely and inform the manager of its location.
  5. Identify the single most critical owner-dependency and begin delegating it.
  6. Start a conversation with the manager about their long-term ambitions and interest in greater responsibility.
  7. Reflect honestly on personal succession preferences: internal promotion, sale, family transfer, or closure.
05L2 · System Development · 2–8 weeks

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.

  1. Create written SOPs for every process currently managed solely by the owner.
  2. Train the manager or successor candidate on each process with a supervised trial period.
  3. Identify and begin developing the potential successor through management training and mentorship.
  4. Clean up financial records and ensure the business structure supports eventual transition.
  5. Review the lease for transferability and address any personal asset entanglements.
  6. Consult an accountant on the optimal business structure for succession or sale.
  7. Create a formal Succession Planning Document with timeline and milestones.
06L3 · Culture Embedding · 8+ weeks

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.

  1. Implement a formal successor development programme with 6, 12, and 18-month milestones.
  2. Test successor readiness through extended owner absences with performance review.
  3. Engage a hospitality business broker for valuation if external sale is the preferred route.
  4. Ensure the business demonstrates clean financials, capable management, and documented systems.
  5. Build the owner’s personal identity and interests beyond the cafe to ease emotional transition.
  6. Review and update the succession plan annually.
07The five practical Tools

All five Tools belong to B207 and are owned by the Owner role. Their complete working records remain inspectable.

T207-01 · L1 · checklist · Owner

Owner-Dependency Audit

Lists every task, decision, relationship, and knowledge area that currently depends on the owner, scored by criticality and ease of delegation.

Inspect Tool source →
T207-02 · L1 · SOP · Owner

Emergency Operations Guide

Provides instructions for running the cafe during unplanned owner absence, including financial access, suppliers, decision authority, staff management, and escalation contacts.

Inspect Tool source →
T207-03 · L2 · template · Owner

Succession Planning Document

Covers the preferred transition route, successor identification, development milestones, financial preparation, timeline, and annual review schedule.

Inspect Tool source →
T207-04 · L3 · tracker · Owner

Successor Development Tracker

Tracks skills, delegated responsibilities, completed periods of working independently, and readiness at 6, 12, and 18 months.

Inspect Tool source →
T207-05 · L3 · checklist · Owner

Business Sale Readiness Checklist

Covers financial record clean-up, lease review, asset inventory, business structure, valuation preparation, and broker engagement.

Inspect Tool source →
08Proof it was done vs proof it helped

The record defines completion evidence and intended outcome checks separately. The targets below belong to this example Block; they are not reported customer outcomes.

Proof it was done

  • The Owner-Dependency Audit is in place and being used.
  • The Emergency Operations Guide is in place and being used.
  • The Succession Planning Document with timeline is in place and being used.
  • The Successor Development Programme outline is in place and being used.
  • The Business Valuation preparation checklist is in place and being used.

Proof it helped

  • The Emergency Operations Guide is completed and stored securely within 30 days.
  • At least 80% of owner-dependent processes are documented and delegated within 12 months.
  • A successor candidate is identified and in a formal development programme within 6 months of starting the Block.
  • The business is capable of operating independently for at least four consecutive weeks without owner involvement.
A document sitting in Drive is not proof of change.
09How the Block can fail

Agreement without action

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.”

Successor in name only

A successor is named but does not receive genuine authority, access, development investment, or meaningful decisions. The title changes; the reliance does not.

Sale readiness arrives too late

Years of weak records or owner-dependency suppress the valuation when the owner finally wants to sell.

Family succession is assumed

A family member is treated as the successor without an honest discussion about desire, capability, or fit.

What to watch and how to recover

  • The owner can describe the Block but cannot show current evidence.
  • The linked Tools exist but are incomplete, late, or not reviewed.
  • The same operating issue keeps recurring despite the Block being described as in place.

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.

10Constraints, review rhythm, and fit

Real constraints

  • Succession planning requires honest self-reflection from the owner and may be emotionally difficult.
  • Developing a genuine internal successor takes at least 12–24 months; there is no shortcut to readiness.
  • An external sale still depends on market conditions, location, and lease terms outside the owner’s control.

Review rhythm

  • Monthly: owner and successor check development progress.
  • Quarterly: review the Succession Planning Document.
  • Annually: review the full plan, financial preparation, and transition timeline.

Where it can fit

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.

11How this Block connects to the wider knowledge

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.

12Source record and provenance

Block

B207 · Succession Planning · version v3.0

Schema and state

Schema 3.0 · state: enriched · enrichment level: gold

Source status

The source identifies this record as AI-generated. It is open to review and should not be read as independently validated guidance.

Recorded enrichment

4 March 2026 · claude_direct_v2

Recorded classification

D11_growth_strategy · M11: Expansion & Market Positioning

Engine tags

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

The explanation beside the work

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.