Knowledge base & SOPs
SOP vs Checklist vs Training Document
These tools solve different problems. An SOP is the authoritative procedure. It explains context, standards, and the correct sequence for someone who already belongs in the role. It answers why this matters and what good looks like.
A checklist is the verification layer for busy shifts. It is shorter, time bound, and tied to completion proof. It does not reteach knife skills from scratch. It confirms that critical steps happened: temps, sanitizer, cooling, lockup, cash policy.
A training document or module is for people who are not yet competent. It includes explanation, demonstration, practice, and assessment. Quizzes and sign offs exist because hospitality hires fast and schedules irregularly.
Teams get into trouble when a forty page PDF pretends to be all three. New hires drown. Veterans ignore it. Managers skip audits because the doc is unreadable.
The fix is linking artifacts. SOP in the Knowledge Base, checklist in Operations, skill path in the LMS. One change event updates all three intentionally.
Restaurant Codex is built around that trilogy exactly as the Help Center describes: Operations for execution rhythm, Knowledge Base for the source of truth, Learning Management for building and proving skill.
Related question
How do you create restaurant SOPs?One outcome per SOP, plain language, numbered steps, photos on risk, failure paths, an owner, and versions you can retire without ghost files.