The Bottom Line
- Wording is not decoration: NICE recommendation language is designed to express strength/certainty and avoid ambiguity.
- Reading “offer/advise” vs “consider” properly helps with shared decision making and defensible documentation.
- You don’t need to memorise the manual—just adopt a consistent interpretation rule and reflect it in how you explain options.
Why this matters (especially for high-intent NICE/CKS searches)
A lot of “no click” behaviour in NICE/CKS-related search comes from users wanting a plain-English explanation of what the wording actually means in practice. If you make the semantics legible, you increase trust and reduce bounce.
A practical interpretation rule (clinician-friendly)
1
1) Treat strong wording as “default action unless contraindicated”
When guidance uses directive language, interpret it as the standard course—then document your reason if you deviate.
2
2) Treat “consider” as “context-dependent: discuss + personalise”
This is where patient factors, comorbidity, preferences, and local constraints legitimately shift the decision.
3
3) Mirror the uncertainty in your documentation
If the wording is weaker, your note should reflect that the decision was weighed and individualised.
Documentation micro-template
“Reviewed NICE-aligned guidance; discussed options and rationale; decision made with patient context and preferences considered.”
This keeps you aligned to the intent of “consider” language without writing an essay.
SourceNICE — Developing and wording guideline recommendations (official)
Open Link