Requests land in chat, in email and in the hallway. Half of them skip the deadline, and most skip the reason. I would rather give people one link, and let the team work from one list.
How it works
- The requester names the request and picks the kind of work.
- They explain why it is needed now and what done looks like.
- They set a due date, a priority and a rough size.
- They add links, name an approver and say if a review is needed.
What a requester's AI would ask
"What do you need, in a few words?" Then "When is it due?" Then "Who approves the final result?" It lists every answer and sends only after a yes. Read about agent-fillable forms.
Good to know
Sort by due date, then by priority. The size answer is a guess, so treat it as a hint. Ask for links, not attachments, because the form has no uploads. Nobody gets an automatic reply, so say in the form description how you will respond.
Find more in forms for agencies, forms for IT and operations and forms for creators. Accepted work can move on to a creative brief, and scope shifts belong in a change request form.
Questions
Is this the same as a creative brief?
No. This is a short intake for the team to triage. A creative brief goes deeper once the request is accepted, so use this first and the brief second.
How do I stop everything being marked urgent?
Ask for the reason behind the date in the why-now question, and review the urgent rows each morning. Requests with no reason can go back to the sender.
Can I send accepted requests to our task tool?
A signed webhook can fire for every response, so your task tool or a small script can receive it and create a card. You can also export a CSV.