Philippines staffing guide · Published
On this page
Build an intake triage form for client requests
A triage form that separates urgency from importance, captures who can approve the work, and routes each request to the right assistant lane.
Most client requests arrive as a sentence in an email or a message in a shared channel. The details that decide the work are often spread across three replies. The assistant has to work out what is needed, who can approve it, and when it is due before any work starts. A triage form moves those questions to the front and gives every request the same first pass. The form is short, but it prevents the quiet rework that comes from guessing at scope.
The form should be owned by the assistant team rather than by each client contact. One format makes requests comparable across lanes and lets a supervisor spot patterns in volume or delay. Keep the fields stable for a quarter before changing them, because a form that shifts every week teaches requesters to skip it. Test it on live requests for two weeks and record where people hesitate.
Separate urgency from importance
Urgency describes when someone wants an answer, while importance describes what happens if the work is late or wrong. Ask for both and keep them in separate fields so a loud requester cannot set the priority alone. Give examples of urgent work, such as a client call in two hours or a filing deadline that day. Give separate examples of important work, such as a contract renewal that closes next month.
The assistant should record the stated urgency without negotiating it on the first pass. If the requester marks everything urgent, the triage owner reviews the pattern at the end of the week. A short note in the form can capture who set the priority and why. That note protects the assistant when a later review asks why routine work waited.
Capture the requester and the approver
A request can come from someone who cannot approve the work or the cost behind it. Add fields for the requester, the person who owns the outcome, and the person who can approve an exception. When all three are the same, the form takes seconds to complete. When they differ, the assistant knows where to send a question before starting.
Record the channel where the request arrived and the time it was received. Those details settle later disputes about when the clock started and what was actually asked. Do not rely on the message thread as the only record, because threads fork and get edited. The form becomes the single entry point that the team can count and review.
Ask for the outcome, not the task
Requesters often describe a task they have in mind, such as send the file or update the sheet. Ask what the output must achieve, such as a client receiving a complete packet before a review meeting. The outcome lets the assistant choose a better method or flag a missing step. It also exposes requests that cannot be completed with the information provided.
Add a field for the required-by date and the reason for that date. A date with no reason is a preference, while a date tied to a meeting or a filing is a constraint. Ask what happens if the date slips so the team can judge the real consequence. These three fields, outcome, date, and consequence, do most of the triage work.
Route by lane and skill
Give each request a lane name that matches the team structure, such as inbox, documents, scheduling, or reporting. Route within the lane by the skill the work needs rather than by who is free at that moment. A form that routes only by availability moves complex work to whoever answers first. Add a required skill field with a short list the team agrees on.
Some requests should stop at triage and go back to the client for clarification. Define the two or three conditions that trigger a return, such as a missing approval or an unclear deliverable. The assistant then sends a standard clarification note instead of starting speculative work. Record the return reason in the form so the team can see which clients need a better brief.
Review the triage data monthly
Count requests by lane, priority, return reason, and time to first response. Look for lanes that receive work they should not, and for requesters whose items are always marked urgent. A monthly review of twenty minutes is enough to spot a form field nobody uses. Remove that field or explain it better rather than letting the form grow.
Compare the triage record with the completed work to find requests that changed scope after intake. When scope changes often, the outcome field needs a sharper prompt. Share the findings with the client contact in plain language and ask for one change at a time. The form improves when the review produces a specific edit, not a general reminder.
Keep the form fast enough to use
A triage form with thirty fields will be bypassed during a busy morning. Aim for eight to ten fields and make the rest optional or filled by the assistant. Use drop-down lists for lane, priority, and approval status so entries stay consistent. Leave one free-text box for context and tell requesters what belongs there. Test the form on a phone, because many client contacts will use one while travelling between meetings.
Place the form where requests already arrive instead of asking people to visit a new tool. A short link in the shared inbox signature and the client channel is usually enough. Review completion rates after the first month and interview the two heaviest requesters. A form that saves them a follow-up email will survive without enforcement.
Questions and operating boundary
Should clients fill in the triage form themselves?
Yes for new requests, with the assistant completing any field the client cannot answer. The assistant should confirm the priority and approver before work starts.
How many priority levels are useful?
Three is usually enough: same day, this week, and scheduled. More levels invite debate without changing the order of work.
What if a request arrives by phone?
The assistant logs it in the form during or immediately after the call and reads the key fields back to the requester.
Source
sba.gov provides authoritative background and does not endorse this service.