Philippines staffing guide · Published
Prepare a purchase request packet an outsourced assistant can route
A routed purchase request fails when the packet is incomplete. Define the fields, evidence, and authority path before an assistant sends it to procurement.
The short answer
Give the assistant a fixed packet: requester, item, amount, budget line, quote, and needed date. Route by written authority, return incomplete requests with a named missing field, and review the routing log monthly.
What the packet is for
A purchase request packet is not the purchase itself. It is the evidence a buyer needs to decide whether the purchase should happen, who should approve it, and what record proves it.
An assistant can assemble and route that packet without choosing the vendor or committing money. Keep that distinction visible in the role brief, because it defines the boundary of the work.
Without a standard packet, every request arrives in a different shape. One contains a screenshot, another a forwarded email, and a third only a message that says we need this by Friday.
The buyer then spends the first hour reconstructing the request. A fixed packet moves that effort to the requester and lets the assistant do the useful part: checking completeness and routing.
Require the fields a buyer needs
Start with six fields: requester, item or service, quantity, total amount, budget line, and needed date. Add the vendor and quote when they exist, and a short business reason for every request.
These fields answer the questions a buyer asks first, so the packet does not stall on a basic clarification. Keep the labels identical to the fields in the procurement system.
Make the amount field numeric and require the currency. A request that says around two thousand is not routable because the approval path depends on the exact figure.
Require the budget line even when the requester does not know the remaining balance, because the owner of that line must confirm it. When a field is unknown, the packet should say unknown with a named person who will supply it, not leave a blank.
Attach the evidence, not the conversation
Attach the quote, the specification, and the approval that already exists. Do not attach a long email thread and expect the buyer to find the decision inside it.
If the decision is buried in a thread, the assistant should summarize the decision and link the message. The packet should let a reviewer verify the claim in one or two clicks.
Label each attachment with what it proves. A quote proves price and scope, a specification proves what is being bought, and a prior approval proves authority. An unlabeled file forces the buyer to guess and often gets ignored.
Remove duplicate files and rename generic downloads before attaching them. A clean packet is a sign that the assistant understands the purpose, not just the form.
Route by authority and amount
Write the routing table as a set of conditions: amount range, category, budget line owner, and any special approval such as data security or legal review. The assistant should be able to follow the table without interpreting seniority.
If two conditions conflict, the higher control wins and the packet goes to the person named in the exception rule. Store the table where the assistant works, not in a policy archive nobody opens.
Give every route a service level and a fallback. A request that sits with an approver who is traveling should move to a named delegate after a stated time. The assistant should record the handoff and tell the requester what changed.
Without a fallback, the packet waits silently and the requester escalates through a side channel. That side channel is where the audit trail usually breaks.
Handle missing or conflicting information
Return an incomplete packet with a short list of missing fields and the person who can supply each one. Do not reject the request with a general message, because the requester will resend the same incomplete packet.
Use a standard return note that names the field, the reason it matters, and the next step. Track how often each field is missing so the form or the training can improve.
When two attachments disagree, keep both and flag the conflict for the buyer. The assistant should not choose the lower price or the newer date without a rule.
Record which value came from which source and what remains unverified. A conflict that is resolved by guessing is worse than a conflict that is visibly held for a decision.
Review routing after the first month
Count packets by route, returned packets, time in each approval step, and requests that arrived outside the form. Read a sample of returned packets to see whether the return note was clear.
Ask the buyers which fields they still have to chase. These numbers show whether the assistant is reducing work or merely moving it.
Choose one change for the next month: simplify a field, add a delegate, or update the routing table. Keep the change small enough to test.
If the same request type keeps failing, the form may be asking for information the business does not have at that stage. Fix the process before adding another approval layer.
Set a handoff for urgent requests
Some requests cannot wait for the normal routing cycle, such as a service outage, a safety issue, or a payment that blocks a customer. Write a short urgent path that names the trigger, the channel, and the person who responds.
The assistant should use it only when the trigger is present, not whenever a requester is loud. A clear urgent path protects the normal queue from constant interruption.
Record every urgent request and review the list weekly. If the same category arrives as urgent every time, the normal route is too slow or the threshold is wrong.
Move that category into a faster standard path rather than accepting permanent exceptions. The goal is a queue where urgency is rare enough to mean something.
Questions to copy for the sales call
- "Which six fields must every purchase packet contain?"
- "Who approves each amount range, and who is the named delegate?"
- "Which evidence proves price, scope, and prior authority?"
- "How will we return an incomplete packet without losing the request?"
Sources
- SBA: Manage your business: Guidance on small-business operations, including planning and financial controls.
- NIST Cybersecurity Framework 2.0: A structure for assigning responsibilities and protecting information across shared processes.
- GAO: Assessing Data Reliability: Methods for testing whether records are complete and support the decision being made.
Common questions
Can the assistant contact vendors for quotes?
Yes, if the brief permits it and the assistant uses approved vendors and a standard quote request. The assistant should not negotiate final terms or commit to a purchase.
What if the requester is senior to the approver?
Follow the written authority table. Seniority does not replace the control, and an exception should be documented with the name of the person who accepted it.
Should small purchases skip the packet?
Use a short form for small amounts rather than no form. The fields can shrink, but the record of requester, amount, and budget line should remain.
How long should routing take?
Set a target for each step and measure it. A reasonable first target is one business day for completeness review and one for the first approver.