A colleague buys a monitor, then asks for the money back. A manager hears about the order after the box arrives. I would rather the ask came first, with the price, the link and the reason, so I can say yes in one reading.
Who it is for
Small companies, school offices and clubs with no purchasing system, where one person approves spending.
What each question is for
- Item, number and cost estimate: the figures I check against the budget.
- Seller and product link: I see exactly what is being bought.
- Needed by: shows what is urgent.
- Reason and repeat: tells me if this is a one-off or a standing order.
- Compared sellers box: a nudge to look around first.
What a requester's AI would ask
"What do you want to buy?" Then "How many?" Then "Why do you need it?" It shows the answers and sends them only after a yes. See agent-fillable forms.
Before you use it
The form takes no payment and no card details. It records the ask and nothing more, and you buy through your usual process. Sort the CSV by the needed-by date to see what is urgent.
A broken item is a repair, not a purchase, so use a work order request for it. Sellers you buy from often can fill in a vendor onboarding form. If you search for a procurement request form, this is the same idea in a smaller size. More tools are in IT and operations forms.
Questions
Can I set a spending limit?
Not as an approval rule. You can set a maximum on the cost field, but most owners sort the CSV by cost and decide for themselves.
How do I handle repeat orders?
Filter `repeat_purchase` for anything not marked one time. Those are candidates for a standing order, so you stop approving the same thing again and again.
Why ask whether sellers were compared?
It is a small prompt, not a check, because the form cannot verify the answer. It reminds people to look around, and you can ask for the comparison when the box is empty.