Knowledge and AI

Create and organize internal guides

Write short guides that are easy to search, keep the title and structure clear, and use the knowledge library as the home for internal SOPs.

5 min read · Updated Mar 18, 2026 · Managers and content owners maintaining internal guides

Use the knowledge area for short SOPs, internal how-to guides, and reference pages the team should be able to search later.

Open Knowledge Library, start a page from New Guide, then keep editing from the page view or the edit route later.

Quick facts

Start here

  • A guide is best for a repeatable process or reference topic that people will search for later.
  • Keep one page focused on one job to be done.
  • Short sections and direct titles are easier to search than long narrative documents.
  • Review and update guides on a rhythm so stale SOPs do not become hidden risk.

What belongs in a guide

  • Use a guide for an SOP, a setup flow, or a stable internal reference.
  • Use a checklist for repeated completion tracking, not for long instructions.
  • Use a course or training flow when the content needs sequencing or formal learning steps.

Step 1: Start from the knowledge library

Browse existing pages before writing a new one

Open Knowledge Library.

Search first so you do not create a second page for the same topic.

The library view helps you check whether the topic already exists before you create a new guide.

Step 2: Write a short, searchable page

Use a simple structure in the editor

Open New Guide or edit an existing page from its edit route.

Use a clear title, a short intro, step headings, and direct language.

  • Good title: Close the pastry station at end of day
  • Weak title: Pastry notes
The editor works best when the page is structured around one clear task with short sections and a direct title.

Keep guides current

Use a light review rhythm

Pick a review owner and revisit important guides on a schedule.

Small updates on a regular rhythm are better than large stale pages that no one trusts.