6.2 · Recurring issues (playbook)

Level 6 · In Practice

6.2Recurring issues (playbook)

Goal: have a “symptom → causes → actions” playbook for common legal difficulties.
Estimated time: 12 min · If you only have 5 min: read “The essentials in 30s” + the diagram.

The essentials in 30 seconds

  • Reflex: one symptom = likely causes = a sequence of actions — diagnose before acting, consult as soon as the stakes are serious.
  • Root: a recurring trouble almost always comes from the same fundamentals (write and keep records, read before signing, protect your assets, prevent).
  • Order: start from the table's most frequent cause, then check against facts and your documents before applying the rest.

Yacine thread — 1 year on: the playbook posted in the office

One year on, Yacine keeps this playbook near his contract templates. Verdict: three lines served him most — disagreement with no evidence avoided through systematic writing, the clause re-read before signing, and the unpaid invoice handled early via the amicable ladder. For each, he ended up fixing the reflex (write, read, prevent) instead of repeating the incident.

Observed symptom, checked causes, actions in order: the reflex holds in three beats.

One reflex per symptom

Most legal troubles recur for classic reasons. Linking each symptom to its likely causes and a sequence of actions saves precious time — and reminds you when to seek advice. ⚠️ General guidance, not advice: check the law of your country.

SymptomLikely causesActions
A disagreement with a customer/supplier and no evidenceverbal agreement, nothing in writing, documents not keptconfirm in writing, keep contracts/quotes/delivery notes/invoices; “prove or perish” (L0.4, L5.2)
Discovering that a signed clause traps uscontract signed without full reading or negotiationread everything BEFORE signing, negotiate upstream, have high-stakes contracts reviewed (L1.2, L1.5)
A third party has filed “our” name / copies our productstrademark never filed, use without protectionfile your trademark, take action for infringement (if you hold rights) or unfair competition; check availability upstream (L4.1, L2.4)
We paid for a creation but do not control the rightsno written assignment of copyrightrequire/regularise a written, precise assignment (rights, media, territory, duration) (L4.2)
Doubt about “data” compliance (customers, employees)no register, unclear lawful basis/purpose, excessive collectionmap processing activities, lawful basis, minimise, inform, secure (L3.1, L3.2)
An unpaid invoice dragging onlate follow-up, no formal notice, limitation period approachingearly amicable escalation → formal notice → simplified procedure; watch the limitation period (L2.3)
General terms that do not protect youunenforceable (communicated late, hidden) or unfair termspresent and have accepted BEFORE the contract, keep proof, balanced clauses (L2.1)
Rushing to court driven by outragelitigation seen as the first responsefavour amicable resolution, mediation, settlement; weigh cost/benefit/chances (L5.2, L5.3)
Exposed to a serious risk with no protectionno mapping, no suitable insurancemap risks, prevent, transfer (insurance) serious risks (L5.1, L5.4)
Common misinterpretation: “the playbook replaces diagnosis and the lawyer”. No. The table gives likely causes, not a verdict: check facts and your documents before applying the action sequence, and consult a professional as soon as the stakes are serious.

Ready-to-say script — name the symptom before acting (1 min)

“My symptom: [disagreement with no evidence / trapping clause / dragging unpaid invoice]. My hypothesis no. 1: [the playbook's most frequent cause]. I check against facts and my documents, I apply the sequence, and I consult if the stakes are serious. I review in two weeks.”

Copy-paste template — express diagnosis sheet

Observed SYMPTOM (facts and documents): ...
Since when / frequency: ...
Likely CAUSES (playbook 6.2): ...
Check (facts, kept records, re-read clauses): ...
ACTIONS (in order): 1) ... 2) ... 3) ...
CONSULTATION needed? (stakes, who, when): ...
REVIEW in 2 weeks: improved? stable? worse?...

Small business / tight budget

No formal table: one symptom, one cause checked against facts, one noted correction.

Algeria SME

Include local practices in the causes before concluding: evidence circuits, real payment delays, access to legal professionals.

Remote / hybrid

Add the records circuit to likely causes: at a distance, an agreement not confirmed in writing looks like no agreement.

Cross-cultural

Check the local applicable law before acting: a clause valid here may have no effect elsewhere.

Caution: Several symptoms touch on evidence, trademarks, data, unpaid invoices and insurance: effects, conditions and procedures depend on the country and evolve. Always check the law of your jurisdiction and consult a professional as soon as the stakes are serious — this playbook gives pointers, not an opinion on your case.

48h challenge — apply tomorrow

Spot 1 current symptom in your business, fill the express diagnosis sheet and test the 1st action.

Section exit checklist
  • I can link a symptom to its likely causes.
  • I have filled (or scheduled) an express diagnosis sheet.
  • I know the referral to the level to dig into for my case.
Self-rating 1-5: diagnosis before action?fixing at the root?
Check your understanding

Yacine discovers a signed clause traps him. Which reflex does the playbook apply?

💡

A recurring problem is not ten incidents: it is one missing reflex to fix at the root (write and keep records, read before signing, protect your assets, prevent). ⚠️ Law varies by country: consult a professional in your jurisdiction for a real case.