What Is a Quick Reference Guide?

Before we knew the proper terms, we made these constantly. Someone finished training, went back to their desk, and needed one small reminder about the thing they had done twice that morning. So we wrote the essentials on a single page and handed it over.

Cheat sheet is what we called it. The industry calls it a job aid, or a quick reference guide. Same object, and the plain name is the one people understand fastest.

In plain terms

A quick reference guide is a single page that reminds someone how to do something they have already been shown, at the moment they are doing it.

It is for the second time, not the first

This is the distinction that makes them work. A quick reference guide is not for learning a task. It is for remembering one. It assumes the training happened and the person mostly knows what they are doing, and it fills the small gap where confidence runs out.

That is why brevity is not a nice-to-have. Somebody is holding this while a customer waits. If they have to read a paragraph to find one field name, it has failed at the only job it had.

How it differs from an SOP

Both are documentation, and they are often written from the same source material, but they serve different moments.

SOP

Quick reference guide

Purpose

The complete, agreed procedure

A reminder of the key moves

Read when

Learning it, or checking the correct way

Mid-task, at the desk or counter

Length

As long as the process needs

One page, ideally one side

Detail

Every step, plus exceptions

Only what is easy to forget

Lives

In your knowledge base

Pinned up, taped down, in a drawer

The two work best as a pair. The SOP is the authority. The quick reference guide is the shortcut, and it points back to the SOP for anything it deliberately leaves out.

What makes a good one

The best ones are almost aggressively short. A few habits get you there:

One task per page. If it covers three unrelated things, it becomes something people have to search, which defeats the point.
Name what they will see. Use the actual button, field, and menu names from the screen in front of them.
Show, do not describe. A small screenshot of the right button beats a sentence explaining where it is.
Order it the way the task happens, not the way the software is organized.
Include the one thing that goes wrong. Every task has a common stumble. Answering it here prevents most of the questions.
Make it survive a printer. Many people want it on paper. If it only works in colour on a screen, it will not get used.

A quiet benefit: quick reference guides cut support questions faster than almost anything else you can produce, because they answer the small, embarrassing questions people would rather not ask twice.

Call it whatever your team calls it

The formal names are useful when you are organizing a library. Inside a team, use the words people already say.

Quick reference guideThe standard term. Good for filing and for client-facing documents.

Job aidThe instructional design term. Precise, if slightly clinical.

Cheat sheetWhat most people actually call it. Nobody needs it explained.

None of them is wrong. What matters is that the page exists, that it is short, and that it is within arm's reach when someone needs it.

What is a quick reference guide?

It is for the second time, not the first

How it differs from an SOP

What makes a good one

Call it whatever your team calls it

Keep exploring

What is an SOP?

How to explain software clearly

Documentation Services

We build the guides people keep at their desks.