Project Request Intake & Triage Desk
Capture every internal project request through one guided form that asks the right follow-ups per request type, runs a completeness check, and drafts a triage-ready request — then a PMO lead reviews, dispositions accept/defer/decline, and approves before anything hits the backlog or your PM tool.
A web tool where anyone on your team submits a project request through a guided intake form that adapts its questions to the request type, validates the requester and department against your list, and runs a completeness check. AI assembles a clean, structured, triage-ready draft. A PMO lead reviews it on one screen, fixes any field, sets accept/defer/decline, and approves — and only then does the item enter the backlog and export to your PM tool in its exact import columns.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- A requester/department list, a list of request types with their required fields, and your triage rules (CSV or Google Sheet is fine)
- Claude Code or any AI coding agent
The problem this kills
Project requests reach you everywhere except the one place you can act on them: a hallway ask, a Slack message, a forwarded email, a "quick favor" in a meeting. By the time you sit down to triage, half of them are missing the things you need to make a call — who the sponsor is, what problem we're actually solving, the deadline, whether there's any budget, and which team benefits. So you spend your week chasing people for the basics instead of deciding what's worth doing.
And because there's no front door, the same request shows up twice under two names, vague "make it better" asks sit in the backlog forever, and pet projects with a loud sponsor jump the line ahead of work that matters more. Your backlog stops being a plan and becomes an inbox.
This is exactly the kind of structured, rules-driven intake that a small internal tool does far better than a shared inbox or a free-form form — and you do not need to be a developer to build it.
What you'll build
A single, guided front door for every internal project request. The requester picks a request type, and the form adapts — a new-tool request asks different follow-ups than a report change or a process fix. It validates their email and department against your list, captures the sponsor, the business problem, the desired outcome, the deadline, and a rough budget band, and runs a completeness check so nothing half-baked gets submitted.
AI takes those answers and assembles a clean, triage-ready draft: a tight title, a one-paragraph problem statement, the outcome, the benefiting team, and the fields your PMO actually triages on. The PMO lead opens the draft on one screen, fixes anything, sets the disposition — accept, defer, or decline — and clicks Approve. Only then does the request enter the backlog and export to your PM tool (Jira, Asana, Monday, ClickUp, a smartsheet — whatever you run) in its exact import columns.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your business — how requests reach you today, your real request types and the fields each one needs, how you name and code things, your typical and peak request volumes, your accept/defer/decline rules, your sponsor sign-off and budget bands, and your nastiest edge cases — and then tailors the data model, the per-type questions, the validations, and every later step to your answers. This is an intake desk shaped around how your PMO actually triages, not a generic form template.
From there it walks the agent through the database schema, the requester/department import with validation, the request-type-driven dynamic form, the completeness check, the AI draft assembler, the duplicate guards, the PMO review-and-disposition screen, and the export to your PM tool's import columns. Every step ends with a ready-to-copy prompt. Because the whole thing runs on a sheet in and a clean CSV out, you can build and use it this weekend even with no live connection to your PM tool.
The governance it includes (this is the point)
This decides what your team works on, so it's built like it matters: login so only your people can submit and triage, row-level security so you only ever see your own organization's requests, and a complete audit trail of every submission, edit, disposition, and export — who did what, and when. Nothing reaches the backlog automatically: each request is a draft until a PMO lead reviews it, sets a disposition, and approves — the hard human-in-the-loop gate. Duplicate guards on a normalized title, and on the same requester asking for the same outcome within 14 days, mean the same ask can't be triaged twice.
Who it's for
PMO leads, intake coordinators, team leads, and ops managers who field internal project requests and want a real front door instead of a shared inbox. If you can describe how you decide to accept, defer, or decline a request, you can build this.
You've got this — open the plan, paste the first prompt, and let it interview you about your intake.