Business Protocols

What business protocols are

A business protocol is a repeatable pattern of behaviour for a recurring business situation — a negotiation, a hiring conversation, a client escalation, a board report, a vendor review, a crisis communication. Unlike an SOP, which governs a technical or operational procedure, a business protocol governs a human interaction: what to say, in what order, to whom, and what constitutes a successful outcome.

Every high-performing organisation has business protocols. Most of them exist only as tribal knowledge — in the heads of senior people, transmitted by observation and informal coaching, lost when those people leave. A founder knows intuitively how to handle a customer complaint that threatens to go public. A veteran sales director knows exactly when to bring in the CEO and when to hold the line alone. A CFO knows what level of detail the board actually wants in a financial report versus what they say they want.

This knowledge is enormously valuable and almost never written down. CLN is the format that makes it writable — without killing the nuance, the branching logic, and the embedded risk awareness that make it useful.

Why protocols stay tribal — the documentation trap

The reason business protocols are rarely documented is that the formats available for documentation are all wrong for the content.

Prose buries the decision logic in narrative. You can read a two-page description of "how we handle escalated client complaints" and still not know whether to involve legal counsel before or after the first call with the client. The decision point is in there somewhere — but it is dressed as context, not flagged as a branch.

Bullet lists flatten conditional logic. "Step 4: assess severity" tells you nothing about what to do with the assessment. The branch — "if critical, escalate to CEO; if moderate, handle at account manager level; if cosmetic, log and schedule" — is implicit at best, absent at worst.

Flowcharts capture branching but obscure risk, ownership, and rationale. A diamond box that says "LEGAL REVIEW NEEDED?" contains none of the information needed to answer the question.

What CLN adds to business protocols

CLN's operator set was designed for exactly this kind of content. Every element that makes a business protocol useful — and currently undocumentable — has a direct operator mapping:

Protocol types and where CLN fits each

Negotiation protocol — full example

Negotiation is the business protocol where tribal knowledge is most expensive to lose and hardest to transmit. A junior account executive watching a senior deal with a procurement team learns by osmosis — which concessions came first, which were held back, when the tone shifted, when silence was used as a tool. CLN can encode this.

Client escalation — the hardest protocol to get right

Client escalations are the protocol most organisations handle the worst — and the one where getting it wrong is most visible. The failure modes are symmetric: under-escalate and the client feels unheard; over-escalate and you signal the account is unstable, burning senior resources on manageable problems.

Hiring protocol — making the invisible scorecard explicit

Most hiring decisions are made by pattern-matching against an unspoken mental model. The experienced interviewer "knows" when a candidate is right — but cannot articulate the criteria precisely enough to train the next interviewer. CLN encodes the model.

Board reporting protocol — what boards actually want

Board reports are among the most consequential recurring business communications and among the most poorly designed. Most boards receive decks that are too long, lead with metrics the board already knows, bury the decisions that require their input, and present problems without proposed resolutions.

Crisis communication — when the protocol matters most

Crisis communication protocols fail most often because the people executing them are under maximum stress, minimum time, and conflicting pressures from multiple stakeholders. CLN's design — cognitive load at write time, near-zero load at execution time — is precisely optimised for this condition.

Building a protocol library

Individual protocols are useful. A protocol library — a versioned, linked collection of CLN protocols covering all major recurring interactions — is transformative. It is the institutional knowledge system that most organisations try and fail to build with wikis, Notion databases, and policy handbooks.

From tribal to institutional: the transfer protocol

The practical question is how to extract the tacit knowledge from senior people and encode it in CLN without requiring them to write documentation — an activity most senior people actively resist.

The most effective method is the observation-annotation loop: a junior team member observes a senior executing a protocol, then writes a CLN draft of what they saw. The senior reviews the draft — not to write, but to react. Reactions are fast: "that's wrong," "add a risk here," "this step only applies if X." The CLN draft becomes the anchor for a 30-minute conversation that captures years of tacit knowledge.

This works because CLN's structure makes the gaps in documentation immediately visible. If a senior person looks at a CLN protocol and sees a ? branch with no targets, or a ! with no consequence, they immediately know something is missing — without having to read the document as prose first.

Related articles