Philippines staffing guide
An Intake Form That Stops Vague Assistant Requests
A good request names the outcome, the source, the deadline, and the owner. Build the form before the queue fills with guesswork.
Published · 9 minute read
On this page
An assistant queue is only as good as the requests that enter it. A message that says please handle this gives the assistant no outcome, no source, and no way to know when the work is done. The result is a round of clarifying questions, a missed deadline, or a polished deliverable that answers the wrong question.
The operating problem
An assistant queue is only as good as the requests that enter it. A message that says please handle this gives the assistant no outcome, no source, and no way to know when the work is done. The result is a round of clarifying questions, a missed deadline, or a polished deliverable that answers the wrong question.
Start with a short intake form that every requester can complete. Ask for the outcome, the audience, the source material, the deadline, the owner of the final decision, and the format. Add a field for what not to do. That last field is often the most useful because it surfaces a boundary before the work begins.
The outcome should be a deliverable, not an activity. Review the deck is vague. Produce a three-slide summary of the attached report for the Monday leadership meeting, with the decision and the open risks, is a request that can be accepted or declined. The assistant can then check whether the source is present and whether the deadline is realistic.
What to control
The source field should point to the authoritative document, not to a folder with twenty versions. Ask the requester to name the version or the date. If the source is a conversation, record who said what and when. The assistant should not have to reconstruct the source from memory or from a chat thread.
The deadline needs a date, a time, and a time zone. ASAP is not a deadline. If the request is urgent, ask what will happen if it arrives an hour later. That question usually reveals whether the urgency is real. The assistant can then prioritize without guessing.
The owner field is not the assistant. It is the person who accepts the final work and makes the consequential decision. The assistant may prepare, draft, and check, but the owner approves the message, the number, the recommendation, or the external commitment. Write that line on the form so it is visible before the work starts.
A workable routine
The what not to do field captures the boundaries that are easy to forget: do not contact the client directly, do not change the pricing, do not include the confidential appendix, do not promise a date. These are not restrictions on the assistant's competence. They are the guardrails that let the assistant move faster without creating risk.
Review the form after the first month. Which fields are always blank? Which requests arrive through chat instead of the form? Which questions does the assistant still have to ask? A form that is too long will be ignored. A form that is too short will produce the same vague requests in a different format.Use a required field only when the work cannot start without it. Too many required fields make requesters abandon the form or paste a vague note into the first box. Mark the source, outcome, owner, and deadline as required, and make the rest optional with a prompt. Review which optional fields are consistently filled and which are ignored.
A form is not a substitute for a conversation about a complex request. For a large or sensitive task, the assistant should schedule a short scoping call and record the answers in the form. That keeps the written record while allowing the requester to explain the context.
Review and evidence
The assistant should be able to decline a request that is outside the lane or missing a material field. The decline should name the missing piece and the route to fix it. A queue that accepts everything creates the illusion of service while pushing the real decision back to the owner.
Review the form with the people who use it. A field that makes sense to the owner may be confusing to a sales manager. The label, the example, and the help text should use the requester's language. A form that is designed only from the assistant's perspective will produce incomplete requests.