Multi-stepOperations
Make every request easy to review.
Collect internal purchase requests, track decisions in a restricted table, and chart requested spending by category.
A complete worked example
Collect purchase details without burying the decision.
The operations lead needs a consistent request for a new studio monitor, with the justification and quote kept together.
Fictional project and sample data. This preview does not submit, publish, or change access.
Staff form; reviewer table · illustrative result
Purchases awaiting a decision
The reviewer can see the need and the amount before opening the supporting detail.
- Review owner
- Operations team
- Decision process
- Human review recorded in the table
| Request | Estimate | State |
|---|---|---|
| Studio monitor | $480 | Needs review |
| Travel case | $160 | Need quote |
| Desk lamp | $65 | Approved by reviewer |
Studio monitor request
The design team needs a second display for proof review by October 8. A supplier quote is attached. The requester supplies the need; the reviewer records the decision.
What the recipient can access
A staff request form with the relevant purchase questions.
Kept out of this handoff
Decision notes, other requests, and reviewer-only fields.
How it runs
- Ask for the essentialsCollect the item, amount, category, and business reason through a form restricted to your team.
- Keep decisions with reviewersPlace the response database in Finance and keep approval status and decision notes off the submission form.
- Review the queueFilter pending requests and sum amounts by category to understand the requests in front of the team.
- You getA consistent request form, a finance-owned review table, and a saved view of the decisions waiting for attention.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Create a purchase-request database in our Finance folder and an internal form for requester, item, amount, category, and reason. Ask which company access setting to use. Add internal status and decision-date fields that only database editors can change. Create a pending-requests view and a chart summing requested amounts by category. Use our existing Finance permissions. Keep approval decisions manual unless I ask for an automation.
What this workflow needs
Company-only forms require the relevant workspace plan and sign-in configuration. Approval status is a field your authorized reviewers update; automatic approval rules require a separate workflow.
Can employees submit requests without seeing everyone else's spending?
Yes. The form and database have separate access settings. Give employees access to the form and restrict the response database to the review team.