A task-intake form is the front door for work sent to a virtual assistant. A good form captures enough context for triage without asking the requester to write a brief. It should make the outcome, the source, the deadline, and the approver visible in a few fields. The form is also a control because it creates a record of what was requested and when.
Ask for the outcome before the task
Make the first field a short description of the finished result rather than the activity. A request to update the tracker is less useful than a request for a tracker where every open item has an owner and a date. The outcome tells the assistant when the work is done. It also gives the reviewer a standard for the check.
Ask the requester to name the decision or action the output will support. A report prepared for a client meeting has a different standard from a report prepared for an internal archive. The context helps the assistant choose the right level of detail. It also shows whether the request is ready to start.
Include a field for what is explicitly out of scope. A requester may assume the assistant will also send the document or update the client, while the role may not include those steps. Writing the exclusion prevents a completed task from being treated as incomplete. It also protects the assistant from an unplanned expansion.
Keep the outcome field short and require plain language. A form that invites a long narrative slows triage and pushes the real context into an attachment. A few specific sentences are usually enough to decide the route. The assistant can ask a follow-up question when the outcome is still unclear.
Capture the source and its location
Ask for the source record that supports the task, not only a description of it. A payroll change needs the approved letter, and a client update needs the matter record. The source field should accept a link or a file reference rather than a general instruction to check email. A request without a source is a candidate for an exception.
Record the version or date of the source when the file can change. A rate letter and a policy document may both be current in name and different in content. The form should ask which version the requester intends. The assistant can then compare the source with the work instead of assuming.
Ask where the completed work should be stored. A task that is finished but saved in the wrong folder creates another round of work. The destination should be a specific location, not a general system name. If the destination is unclear, the form should route the request to the owner before work begins.
Include a field for related items that the assistant should not change. A request to correct one employee record may sit beside similar records that are already approved. Naming the boundary prevents an unrelated edit. It also helps the reviewer see the scope of the change.
Make the deadline and the priority explicit
Ask for the date the work is needed and the reason for that date. A deadline without a reason is difficult to prioritize when two requests arrive together. The reason may be a meeting, a filing, or a pay run. The assistant can then judge whether a short delay matters.
Separate the requested date from the latest acceptable date. A requester may prefer Friday but can accept Monday, and that difference changes the queue. The form should capture both when they differ. The assistant can plan the work without treating every preference as a hard deadline.
Ask who will use the output and whether the use is internal or client-facing. Client-facing work usually needs a named reviewer before release. Internal work may follow a lighter check. The form should make the review requirement visible at intake rather than at the end.
Record the priority rule that applies rather than a free-form priority label. A label such as high means different things to different requesters. A rule based on the date, the client, or the consequence is easier to apply consistently. The assistant should not have to infer priority from the tone of the message.
Name the approver and the reviewer
Ask for the person who can approve a change in scope or a client-facing release. The requester and the approver are often different people, and the form should show both. An approval route that is discovered late causes the work to wait. The names should be roles or people who are actually available.
Ask who will review the completed work and what the review should focus on. A reviewer who is asked to check everything will check nothing well. A specific focus, such as the dates or the client-facing language, makes the review useful. The form can offer a short list of common review types.
Record the backup approver for the period when the primary is unavailable. A route with no backup stops at the worst possible time. The backup should be named before the work starts. The form can show the current backup rather than asking the requester to know it.
Check that the named approver has the authority the task requires. A manager who can approve a schedule change may not be able to approve a payment adjustment. The form should route the request to the correct owner. An approval from the wrong role is not a control.
Triage with a small set of routes
Use a small number of routes, such as ready to start, needs information, needs approval, and out of scope. A short list makes triage fast and consistent. The assistant should be able to choose a route without a long discussion. The route should also determine the next action and the owner.
Write the triage rule for each route in the role guide. For example, a missing source may route to needs information, while a request for a new type of work may route to out of scope. The rule should say who is contacted and what is recorded. A route without a next step is only a label.
Ask the assistant to record the route and the reason at intake. The record shows whether the form is collecting enough information and where requests most often stall. A pattern of needs information may mean a field is unclear or missing. The review can then improve the form rather than blame the requester.
Test the form with real requests
Test the form with five recent requests before making it mandatory. Ask the assistant to triage them using only the form and the role guide. Note every question the assistant had to ask outside the form. Those questions identify missing fields or unclear wording.
Ask a requester to complete the form without help and time how long it takes. A form that requires training will be bypassed during a busy week. The fields should be understandable from the labels alone. A short guide can help, but the form should not depend on it.
Compare the triage result with the route the work actually needed. A mismatch may mean the rule is wrong or the form is collecting ambiguous information. Revise one field at a time so the effect is visible. A wholesale rewrite makes it hard to know what improved.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Department of Labor — Fair Labor Standards Act context on hours, work time, and recordkeeping.
Related reading
Build a role-scope card before a virtual assistant starts
A one-page role-scope card that names the tasks, the decisions, the tools, and the stop rule before a virtual assistant's first morning.
Write a first-month check-in script for a virtual assistant
A repeatable check-in script that surfaces blockers, review load, and role drift without turning the meeting into a status recital.
Set a working-hours and availability agreement with a virtual assistant
A working-hours agreement that covers time zones, response windows, peak coverage, and the difference between urgent and ordinary requests.
