Request Intake and Triage Template
Three documents and three sheets that turn your team's most common follow-up questions into required form fields, and stop requests that skip the form.
Free download · No account needed
Request Form Fields, derived
Bramwell Foods, Data & Reporting team, one quarter
| Generic template | Universal fields: requester, type, urgency, attachments |
| What it misses | 29% of real requests never reached the form: 73 of 248 |
| This pack | One derived field per type, ask-back rate stated |
Highest ask-back field per request type
| Request type | Derived field | Ask-back rate |
|---|---|---|
| New report build | Metric owner / sign-off | 89.5% |
| Access request | System + restricted flag | 81.8% |
| Bug fix | Since-when date | 75.0% |
| Ad hoc data pull | Exact date range | 67.2% |
| Dashboard change | One-time or ongoing | 61.0% |
None of these five fields appears on a generic intake template. Each earned its place by being the question analysts actually asked back, at the rate shown.
Every internal request form template on page one ships the same universal field list. The ClickUp Request Form Template leads with must-have fields like requester info, request type, urgency, supporting details and attachments, standardized across every request type at once. That list isn't wrong, exactly, it's generic: none of it comes from what a specific team's specific requests have actually needed clarified before work could start. A twenty-minute access grant and a four-day report build get the same five boxes.
A harder problem is invisible to any form template, because it is the volume that never reaches the form at all. A request handled by direct message never enters a ticketing tool's count, a shared inbox's log, or any dashboard built on either one, so intake advice gets written as if all demand already lands somewhere countable. Nothing in a generic template's setup instructions asks a team to check whether that assumption holds for its own queue before publishing a process built on top of it.
Bramwell Foods' Data & Reporting team tested both gaps directly. A one-week audit of the team's own Slack history against its shared-inbox log found 5 requests fulfilled entirely by direct message against 12 logged that same week. Extrapolated across the quarter, that ratio implies roughly 73 invisible requests, 29% of a true 248-request workload. Deriving each request type's required field from its own historic ask-back rate, then enforcing the form with a fixed rejection note, dropped DM-only volume to 8.5% within a month.
What's in the pack
Request Form Fields
Three core fields plus one derived field per request type, each stated next to the historic rate at which that exact question got asked back before work could start.
Why ask-back beats a generic field list
A field earns its place by being counted, not by sounding thorough. A universal list borrowed from another team's template is exactly what this pack replaces.
Triage Queue
The live operational sheet: one row per open request, its priority tier, its assigned analyst, and its status, so a reassignment shows up here before it shows up as a missed target.
Aging Report
Flags anything past the one-hour acknowledgement or four-hour triage window automatically, off the submission timestamp, rather than waiting for someone to notice.
Intake Policy
States the measured DM-bypass rate plainly and sets the rule: every request enters through the form, with a named exception for true emergencies only.
Triage Rules
Acknowledgement and triage timing, the three priority tiers tied to an observable condition instead of a requester's own urgency rating, and routing by request type.
Rejection Note
Two fixed replies, one for a request that arrived by direct message and one for a request outside this queue's scope, so enforcement doesn't drift by whoever answers.
How to use it
- 1
Open in River, or download it
Install the pack and hand River your request history, or download all three documents and three sheets blank and derive the fields yourself.
- 2
Send what's logged, and what isn't
A shared inbox or ticketing export for the visible requests, plus whatever you can find of direct messages or hallway asks that were fulfilled without being logged.
- 3
Let the ask-back count set the fields
Every request type gets one required field, the question that got asked back most often for that type, with the rate stated next to it.
- 4
Publish the form, enforce it with the note
The Rejection Note redirects anything sent around the form, and the Aging Report catches anything the acknowledgement or triage automation misses.
Frequently asked questions
Is this free, and what do I get?
Free, no signup needed for the download: three documents and three spreadsheets. The AI half is optional. Send River your request history, including what bypasses it, and it derives the fields and drafts the policy for you. More in the template library.
Why not just use the fields every intake template already ships?
Because a universal list isn't derived from anything; it's what a form obviously should ask. In the worked example, the field that mattered most, a metric owner for a new report build, doesn't appear on a single generic template, because no generic template counts a specific team's follow-up questions.
What counts as a request "bypassing the queue"?
Any request fulfilled without ever entering the team's shared record: a direct message answered directly, a hallway ask completed on the spot. It's invisible precisely because no count of the visible queue includes it, which is why measuring it needs a separate spot-check audit.
What happens when someone still sends a direct message?
They get the Rejection Note, not an answer. It redirects to the form and states the acknowledgement and triage timing they'll get once it's submitted, with one named exception for a live incident or a deadline inside four hours.
Isn't every request urgent to the person asking?
That's exactly why priority is assigned at triage against an observable condition, not chosen by the requester on the form. A live incident gets a faster ladder entirely; this queue's Blocking tier is reserved for work that stops without it.
What does Edit with AI actually do?
Creates a free account, installs this exact pack as a private space, and primes the agent to ask for your request history and your bypass volume both. Nothing gets derived until you send something, and the blank pack is always there to download instead.
Build the form from what people actually ask
Take the documents and sheets blank, or install this pack in River and send it a quarter of your own request history, DMs included.
Edit with AI