How to get staff to use SOPs instead of asking a manager
Liam Jones
Founder of Pilla
Date Modified
27 August 2026
I'm Liam Jones, founder of Pilla and a qualified management consultant. I've helped hundreds of businesses set up workflows, and in this article I'm going to show you four practical ways to help staff use SOPs without turning a manager into the search bar.
I'll cover guidance at the point of work, training people to find it, a route for genuine exceptions and a review for repeated questions. Together they make routine work easier to complete without interrupting someone.
If you're looking to automate this part of your operation, talk to us and we'll show you what it would take to set up.
The problem we're solving
In deskless teams, the person acting as the search bar is usually a manager. The job is not to write more SOPs. It is to make the right instruction easier to use than interrupting them.
She had 35 documented SOPs. Her team still asked her everything.
Walked into a 15-person consulting firm a couple weeks ago. Founder hadn't slept more than 5 hours in a year. First thing I asked: "Do you have SOPs?" She pulled up a folder with 35 of them. Real ones. Detailed. Written by her, painfully, at night. I asked her team how often they use them. Blank stares. One person said "I didn't know those existed." Another said "It's faster to just ask her." There it was. The SOPs weren't the problem. The SOPs were great. The team had been trained, over years, that the founder was the search bar. Asking her was a 30-second loop. Reading an SOP was a 10-minute loop with risk of being wrong. Of course they asked her. I used to think SOPs alone solved founder-dependency. They don't. SOPs are necessary, not sufficient. What actually breaks the loop is making the SOP faster to find than the founder is to interrupt. That's it. That's the whole game. If you've got SOPs sitting in a Google Drive somewhere and your team isn't using them, the problem isn't your team. The problem is the SOP is harder to access than you are.
Understand the problem
Deskless staff rarely ignore a procedure because they dislike procedures. They ask a manager because the manager is easier to reach than the right instruction. The fix is to put guidance where the work happens, train people to find it, give genuine exceptions a clear route and use repeated questions to improve the process, so routine questions stop landing on one person.
Workflow solutions at a glance
- #1 - Put the procedure inside the work. Use a dedicated point-of-work SOP workflow that staff open on the device they use to do the job. The procedure sits in the work itself, then the worker records whether it covered the real situation, any unclear step and whether the task was completed, paused or stopped, so the answer stays with the task instead of the manager.
- #2 - Train staff to find and follow the right process. Use a dedicated SOP find-and-follow training workflow to test the habit, not just explain one procedure. The manager names the procedure, records where the worker found the current version, watches them complete the task and signs off whether they can do it independently.
- #3 - Route genuine exceptions without interrupting a manager. Give staff a short exception request for the cases the procedure does not cover. It asks which task and procedure they checked, what did not fit, what they safely tried and whether work can continue. On completion, Pilla posts the structured request in team chat, so the team gets the context without an unstructured interruption.
- #4 - Review repeated questions and repair the process. Run a short weekly review of exception requests and team-chat questions. The manager groups repeated issues, records the root cause, agrees the smallest change and assigns an owner and review date. Pilla then posts the agreed update to the team, turning interruptions into a queue of process improvements.
#1 - Put the procedure inside the work
Best for: Deskless teams where the right SOP exists, but staff have to leave the task and search a folder to find it.
Use a dedicated point-of-work SOP workflow that staff open on the device they use to do the job. The procedure sits in the work itself, then the worker records whether it covered the real situation, any unclear step and whether the task was completed, paused or stopped, so the answer stays with the task instead of the manager.
What the workflow includes
- Open the current SOP workflow at the point of work
- Read and complete each instruction in order
- Record whether the procedure covered the job and what happened next
#2 - Train staff to find and follow the right process
Best for: Teams that have documented procedures but have not made finding and using them part of training.
Use a dedicated SOP find-and-follow training workflow to test the habit, not just explain one procedure. The manager names the procedure, records where the worker found the current version, watches them complete the task and signs off whether they can do it independently.
What the workflow includes
- Ask the worker to find the current procedure without being shown
- Watch them complete the task and explain the exception route
- Record the result, then collect worker and manager sign-off
#3 - Route genuine exceptions without interrupting a manager
Best for: Deskless teams where the SOP covers normal work but staff still meet unusual or unsafe situations.
Give staff a short exception request for the cases the procedure does not cover. It asks which task and procedure they checked, what did not fit, what they safely tried and whether work can continue. On completion, Pilla posts the structured request in team chat, so the team gets the context without an unstructured interruption.
What the workflow includes
- Check the latest procedure and identify the exact step that does not fit
- Record the blocker, safe actions already tried and whether work can continue
- Post one structured exception request in team chat
#4 - Review repeated questions and repair the process
Best for: Managers who keep answering the same questions and need to fix the cause rather than repeat the answer.
Run a short weekly review of exception requests and team-chat questions. The manager groups repeated issues, records the root cause, agrees the smallest change and assigns an owner and review date. Pilla then posts the agreed update to the team, turning interruptions into a queue of process improvements.
What the workflow includes
- Group repeated questions by task or procedure
- Choose whether the problem is access, clarity, training, ownership or a missing exception
- Assign the change, owner and review date, then share it with the team
Further guidance
How to choose the right workflow
Start with the point where staff leave the process and ask a manager.
- Choose guidance inside the work when the SOP exists but staff cannot reach the right instruction quickly on the device they use at work.
- Choose guided training sign-off when staff know a procedure exists but have not learned how to find and use it for themselves.
- Add a structured exception route when normal work is documented but unusual cases still need a safe decision from the team.
- Run a weekly friction review when the same questions keep returning and the process itself needs to change.
The four workflows work best as a loop. Put the guidance at the point of work, train staff to use it, capture the exceptions it cannot answer and let managers fix the repeated friction. The goal is not to stop staff asking for help. It is to make routine work independent and save manager attention for the cases that genuinely need it.