Manuals to Answers

Two things, in about forty-five minutes. A one-page sheet answering the twenty questions your crew actually asks, in the words they ask them. And a short list of the questions your handbook cannot answer at all.

The second list is the more valuable half. Every question on it is something your crew has been guessing at, or asking you personally, for as long as the gap has existed.

Your manual as a file. A PDF or a Word document is ideal, and a Google Doc works. If it only exists on paper, photograph each page with your phone in decent light and save it as one PDF. It does not need to be pretty. It needs to be legible.

A free Google account, for NotebookLM. There is nothing to install and nothing to pay, and the free tier allows far more questions a day than this uses.

Twenty minutes of quiet. Reading the answers properly is the part that matters, and it is the part people skip.

You are putting an internal document on a third-party service. For a standard handbook that is usually unremarkable, but it should be your decision made knowingly rather than by accident.

If your manual contains individual pay figures, medical arrangements, or anything naming a specific employee, take those pages out first.

It answers from the document you uploaded and cites where in the manual each answer came from. That is the whole point here: you want to know what your handbook says, not what a handbook generally says.

Because it is tied to your document and shows its sources, it is far less likely to invent an answer, and when the manual does not cover something it will usually say so.

Check the citation on anything you are going to put in front of your crew. Click through and read the sentence it pulled from. Being grounded in your document is not the same as being right every time.

Sort every answer into one of three piles. This is where the value is.

Right and usable. The manual answers it clearly and the answer is still true. These go straight onto your one-page sheet.

The manual cannot answer it. The tool says the document does not cover it. Write every one of these down. This is your gap list.

Right on paper, wrong in real life. The answer is faithfully quoted and it describes a policy you stopped following years ago. The tool has no way to know that. Each of these is a live risk: a new hire following the handbook to the letter would be doing the wrong thing, and in a dispute the written version is the one that counts.

Take the first pile and compress it onto a single page. One page, not two. Someone should be able to find an answer without deciding whether it is worth the bother.

Use the question as the heading, in the employee's words rather than the policy's. One or two sentences of answer. If it needs a paragraph it belongs in the manual, and the sheet should say which page. Put a name and a phone number on anything the sheet cannot answer, and the date you made it in the corner, because in a year that date is what tells someone to check.

Then put it where it will be seen: the back of the shop door, the truck binder, or a photo sent to the crew's phones. A quick reference filed in a shared drive is a quick reference nobody reads.

It does not update your manual. It shows you what the manual says. The second and third piles are a to-do list for a person.

It is not legal advice, and neither is the guide. If the review turns up something that looks like a compliance problem, that is a conversation with someone qualified.

It only knows what you gave it. If half your real policy lives in your head or in a supervisor's memory, it cannot see that half.

It does not keep itself current. Change the policy and the sheet you printed is wrong until somebody redoes it. If you would rather the procedures stayed current on their own, that is what SOP Procedures is for.