Philippines staffing guide
An Escalation Ladder for Assistant Questions
Not every question needs the owner. Give the assistant a ladder from source check to escalation.
Published · 8 minute read
On this page
An assistant who asks too many questions becomes a bottleneck. An assistant who guesses becomes a risk. The middle path is an escalation ladder: a short sequence of checks the assistant can perform before bringing the question to the owner.
The operating problem
An assistant who asks too many questions becomes a bottleneck. An assistant who guesses becomes a risk. The middle path is an escalation ladder: a short sequence of checks the assistant can perform before bringing the question to the owner.
The first step is the written source. The assistant checks the approved procedure, the policy page, or the current template. If the answer is there, the assistant applies it and records the reference. This step prevents questions that the documentation already answers.
The second step is the exception log or the frequently asked questions. If a similar case was resolved last month, the assistant can use the recorded decision, provided the facts match. The assistant should not generalize from a case with different circumstances. A note that says we decided this before is not enough without the context.
What to control
The third step is a peer or a backup. A second assistant may know the answer or know who does. This step is especially useful for tooling questions and routine exceptions. It also reduces the owner's interruption load without hiding the issue.
The fourth step is the owner. The assistant should bring the question with the facts, the options, the recommendation, and the consequence of waiting. A question that says what should I do? is harder to answer than one that says the source conflicts on the deadline; option A meets the customer promise, option B protects the budget; I recommend A and need your decision by 3 p.m.
Define which questions skip the ladder. A security concern, a legal threat, a safety issue, or a request that exceeds the assistant's authority should go directly to the named owner. The assistant should not spend an hour researching a matter that needs an immediate stop.
A workable routine
Track the questions each week. Which ones were answered by the source? Which required an owner decision? Which revealed a missing procedure? The pattern tells you where to improve the documentation and where the assistant needs coaching. A high volume of owner questions may mean the brief is incomplete, not that the assistant is weak.
Review the ladder after a month. If the assistant is still asking the same question, the source or the training is not working. If the owner is answering questions that the source already covers, the assistant may not trust the documentation. Fix the trust by showing examples and confirming the source is current.Write the ladder down and give it to the assistant on day one. A new person should not have to discover the escalation path by asking. Include the names, the channels, the response expectations, and the conditions that skip the ladder.
Some questions are really requests for permission. The assistant should know which decisions are delegated and which are not. If the answer is in the delegation log, the assistant can act. If the log is silent, the question goes to the owner. That is faster than a debate about whether to ask.
Review and evidence
Track the source of each question. If most questions come from a missing procedure, fix the procedure. If they come from a specific requester who gives incomplete briefs, address the intake. If they come from the assistant's uncertainty about authority, update the log and the training.
Review the ladder after a month and remove steps that do not help. A peer step that adds a day of waiting is worse than a direct question. A source step that points to an outdated page creates frustration. The ladder should reduce delays, not add ceremony.