Tithi MondalBlog

Guide6 min readUpdated

Training Manual Design: SOP, Handbook and Step Layouts

Training manual design for SOPs, user manuals and staff handbooks: step layouts, screenshots with callouts, page templates and version control.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Training Manual Design: SOP, Handbook and Step Layouts: cover illustration

Suppose a cloud kitchen in Kolkata hires four new staff members before a festival rush. The owner explains the opening routine once, aloud. By the second day, two people clean the fryer in the wrong order and one forgets to check the gas valve. A one-page printed checklist on the wall would have prevented all three mistakes.

Training manual design is the layout of instructions so that a new person can follow them correctly without asking for help. It covers step layout, screenshots, warnings, page templates and updates. An SOP is a standard operating procedure: a written set of steps that makes everyone do a task the same way. This guide shows how to design both so staff actually use them.

How should an SOP document be laid out?

An SOP document should state its purpose, who does the task, the numbered steps and what to do if something goes wrong. Place these parts in a fixed order on every SOP, so staff learn where to look.

Use this page structure:

  1. Title. The task as an action: "Open the shop counter", not "Opening procedure".
  2. Header strip. Owner of the task, time needed, tools needed, version and date.
  3. Purpose. One sentence on why the task matters.
  4. Steps. Numbered, one action each.
  5. Warnings. Safety and quality notes, in a separate coloured box.
  6. If something goes wrong. Who to call, with a phone number.
  7. Footer. Version number, date, page number.

Keep one task on one page where possible. A person with wet hands in a kitchen or a tired person at a counter will not read two pages.

How do you write step by step instructions with screenshots?

Step by step instructions with screenshots work when each step has one action, one image and one sentence. The reader should look at the image, read the sentence and do the action.

Layout rules:

  • Put a large step number on the left, then the sentence, then the screenshot on the right or below.
  • Begin each sentence with a verb: "Click Save", "Press the green button", "Pour water to the red line".
  • Use bold only for the name of a button or field, exactly as the name appears on screen.
  • Keep one action per step. If you write "and then", split the step into two steps.
  • Add the expected result when it helps: "The screen shows Order saved".

On admin panels I have designed, help text and numbered steps sit beside each form, and the same pattern works in a printed manual. For a deeper look at screens that staff use every day, see the admin dashboard UI and UX design post.

How should screenshots and photos be prepared?

Screenshots should be cropped to the part that matters, taken at the same size and marked with numbered callouts. A full screen with ten menus confuses the learner.

Use the same device and browser window size for every screenshot, so the manual looks consistent. Crop out the address bar and any private data. Replace real customer names, phone numbers and amounts with sample data. Add a red or brand-coloured circle or arrow around the item to click, and a small number that matches the step number. Keep the callout style the same everywhere.

Screenshots go out of date when the software changes. Give each screenshot a clear file name, such as "step-03-save-order.png", and list the manual version beside the software version that the manual matches. For photographs of a physical task, shoot at the worker's eye level with good light and show the hands and the tool. The image formats guide explains which format to use so images stay sharp but the file stays small.

How should a user manual layout organise many tasks?

A user manual layout organises tasks by what the reader wants to do, not by the menu names in the software. A reader searching for "refund an order" will not know which menu holds the refund.

Use a structure of 4 parts:

  1. Quick start. One or two pages that take a new person from login to the first success.
  2. Task guides. One page per task, named as an action.
  3. Troubleshooting. A table of problems, causes and fixes.
  4. Reference. Terms, roles, contact numbers and shortcuts.

Add a contents page with page numbers and clickable links. Add a short glossary, so that every technical word has a plain meaning. The design terms glossary shows the style: a term, then a one-line meaning. For a troubleshooting table, use three columns: "What you see", "Likely cause", "What to do". Keep every cell to a short sentence.

How do you design a staff handbook that people read?

A staff handbook is read when the handbook is short, grouped by questions staff ask and written in the language staff speak at work. A handbook of 15 pages that is read beats a handbook of 60 pages that sits in a drawer.

Group content under questions: "When do I get paid?", "What do I do if I am sick?", "How do I report a problem?". Put the policies that staff need every week first, and detailed rules in the appendix. Policy wording on leave, pay and conduct should be written or checked by someone qualified in these matters. The designer's work is to make the wording clear, with headings, short paragraphs and one summary box per topic.

Many teams in West Bengal work in Bengali and English. Offer both versions, with the same layout, and test that the Bengali text is large enough and has enough line spacing. The bilingual Bengali and English website design guide covers how to pair the two scripts, and the Bengali typography post covers type choices. Use simple words. A manual for floor staff should read at a school level, not a legal level.

What page template and type sizes suit a manual?

A manual needs one page template, with the same margins, header and footer on every page. A consistent template helps staff find things by position.

Use A4 for the full manual and A5 or a single A4 sheet for work-area cards. Choose body text of 11 points for a manual used on a desk and 14 points or larger for a card read from a distance. Use a sans-serif font with clear numbers. Set headings in a heavier weight and a single brand colour. Use colour with meaning: red for danger, amber for caution, green for done. Do not rely on colour alone, and add words such as "Warning". The colour contrast guide shows how to keep text readable on coloured boxes.

For more on fonts and sizes, see typography basics for non-designers. For a food business, the bakery and cloud kitchen design post covers the website side, but the same clear checklists help a kitchen floor too.

How do you keep a manual up to date?

Keep a manual up to date by giving the manual one owner, a version number, a date and a short change log. Without these, staff will use whichever old copy they find.

  • Put "Version 2.1, updated 12 November 2026" in the footer of every page.
  • Add a "What changed" box on the first page.
  • Replace old copies in print and in shared folders on the same day.
  • Store the source file and all screenshots in one folder with clear names.
  • Review the manual when the process or software changes, and at least once a year.

If you want the template, step layout and callout style designed once, so your team only adds the steps, you can describe your manual through the contact page or read about the presentation design service, which covers document layouts.

Frequently asked questions

What is an SOP document?

+

An SOP is a standard operating procedure. It is a written set of steps that tells staff how to do a task the same way every time.

How many steps should one SOP page have?

+

Use 5 to 8 steps per page. If a task needs more, split it into two tasks with their own titles.

Should a manual be printed or on screen?

+

Both can work. Print short instructions for the work area, such as a kitchen or counter, and keep the full manual as a PDF that staff can open on a phone.

How often should a manual be updated?

+

Update the manual whenever the process or the software changes, and show the version and date in the footer. Remove old copies so no one follows outdated steps.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.