Form · Request
Software development request form template
Asks the questions a developer would ask before estimating: what problem this solves, for whom, how it is handled today and what the finished thing must do. Changes to existing systems name the system, and only requests with a real deadline are asked for the date and what it depends on.
Try it live
Try it as a respondent
Every question, and where it leads
The conversation
What a respondent is asked, in order.
Have something you'd like built or changed? Start with the problem and we'll work out the solution together.
Who is making the request?
Which team or department are you in?
What kind of request is this?
Which existing system or systems does it involve?
What problem are you trying to solve?
How is it handled today?
Who will use it?
Roughly how many people will use it?
What must it do for you to call it done?
Anything that would be nice but isn't essential?
Do any of these apply?
How much difference would this make to your team's work?
Is there a date it has to be live by?
What is the date?
What depends on that date?
Sketches, screenshots or example files
Ends with
Request received
The flow
Where each answer leads. Every route here is editable once the form is yours.
Contact info
Short text
Single select
Short text
Long text
Long text
Multi select
Dropdown
Long text
Long text
Multi select
Opinion scale
Yes / No
Date
Short text
File upload
What this template uses
- Contact info
- Short text
- Single select
- Long text
- Multi select
- Dropdown
- Opinion scale
- Yes / No
- Date
- File upload
- 7 branches
Questions to consider
- What size of request should go through this form, and what is small enough to just ask for?
- Which constraints matter most in your organisation, such as data protection or accessibility?
- Who decides which requests are built, and how often do they meet?
- Should the form ask for a budget holder or sponsor?
How to use the responses
Read the problem and the current workaround before the proposed solution, because the right fix is often smaller than the request. Follow up with the requester to turn the must-have list into acceptance criteria before estimating. Score requests by the difference they would make against the number of users and any fixed deadline, and export the list to CSV to review it with whoever sets priorities.
How to customize and share it
- 1Replace the constraints list with the checks your team has to make, such as security review or accessibility.
- 2Name your internal systems in a dropdown if requests always touch the same few.
- 3Share the link where requests currently arrive, and add your review cadence to the ending so requesters know when to expect an answer.
Frequently asked questions
What should a software development request include?
The problem, who has it, how it is handled today, what the solution must do and any constraints or deadlines. That is enough for a developer to ask sensible questions and give a rough estimate.
Why ask for the problem instead of the solution?
People often ask for the first fix they thought of. Knowing the underlying problem lets the team suggest something simpler, or something that already exists.
Is this the same as a feature request form?
It overlaps. A feature request usually comes from customers about a product; this form is for internal teams asking for tools, changes or integrations, and gathers more detail for estimating.
Can I add technical questions?
Yes. Copy it with Use this template and add questions about platforms, data sources or hosting. You can also branch so only technical requesters see them.