Introduction
Tell us the decision the design needs to support. A short request with a clear decision date helps the design team plan its first look.
Design or UI request: start from the decision, not the look
A design request should say what decision the design has to support, which screens or assets it touches, and when that decision is needed. Ask for the type of work first, because a copy change and a new checkout flow need very different queues. Name the approver before the work starts, so the first mockup is not the first time anyone with authority sees it.
What people search
Design request form: 110 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Words for the respondent
Confirmation
Thanks. Your request is saved, and the design team will review it and reply to you directly.
Request type
Pick the closest option. If the work spans two types, choose the one that needs the most design time.
Decision date
The date a decision needs the design, not the date you would like the work finished.
Screens or pages affected
Names or links, one per line. A list is much easier to estimate than a paragraph that says redesign everything.
Field blueprint
Eleven fields that let a designer estimate the work
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Requester name | Short text | Required | Gives the designer one person to ask about intent, which saves a round of back and forth in a shared thread. |
TeamProductMarketingSalesSupportOperationsOther | Dropdown | Required | Helps the design lead weigh requests from teams with different deadlines. |
Request typeNew screen or flowChange to an existing screenReview of something already liveCopy or text change onlyIcon, illustration or other asset | Single choice | Required | Sets the size and kind of work. A copy change should not wait behind a new flow. |
What problem should this solve? | Long text | Required | The outcome the design must support, in one or two sentences. Without it, the review turns into a debate about colors. |
Who will use it?For example: returning customers on a phone | Short text | Required | Shapes layout and language. A design for new customers is not a design for account administrators. |
Screens or pages affectedNames or links, one per line. | Long text | Required | The scope. Designers estimate from this list, so an unclear list makes every estimate a guess. |
Existing design or referencePaste a link to the file or page. Nothing is uploaded here. https:// | Short text | Optional | Shows the current state or a reference you have in mind. Link to the live page when you cannot link to the source file. |
Decision date | Date | Required | The date the decision needs the design. It drives the schedule, so use the decision date, not a wish. |
Who signs off the design? | Short text | Required | Names the approver before work starts, so the designer does not wait on an approval nobody expected. |
Accessibility or brand requirements | Long text | Optional | Lists constraints that are not visible in the screen, such as a required contrast level or a brand rule for type. |
How will you know it worked? | Long text | Optional | What you will check after launch. Name a measure only if your team already tracks it. |
At a glance
How long the request takes to fill in
11Fields
8Required fields
6Estimated time (minutes)
Estimate based on question types; actual completion time varies.
Try it
Fill in the request as a requester would
After a response arrives
What the design team does with a request
The creator hears after a scheduled run
Processing runs hourly in production. The creator is notified after each run, not when someone submits, so a request needed today should also go straight to the design lead.
Read the grid by decision date
Each request appears in the grid. Read the list by decision date and request type, and move copy-only changes into a short queue that does not wait behind larger work.
Export the queue for planning
Export the responses as CSV when you plan a sprint or a design review, and keep the planning copy with the team that owns the schedule.
Reply to the requester yourself
The form does not reply to requesters. Confirm the reviewer and the start date in your own message, so no request waits in silence after it is saved.
Mistakes to avoid
Requests that a designer has to send back
Describing the look instead of the problem
Make it more modern, or make it pop, does not say what the user should be able to do. Ask for the task first, then let the designer propose how it looks.
Marking everything urgent with no decision attached
Urgent gives the design lead nothing to schedule against. Name the decision that waits on the design and the date it is needed.
Asking for a project in one sentence
Redesign the checkout is a project, not a request. Break it into the screens it touches, or send it as a brief for a scoping conversation first.
Leaving out the approver
A finished design that nobody with authority has seen has to be reworked. Name who signs off before the work begins, not after the first mockup.
Frequently asked questions
Is there a design request form template I can download?
What you get here is the field list and its order, not a Word or PDF file. Requesters open the form on the web through a link, and you can export the responses to CSV for planning.
What should a graphic design request include?
Include the request type, the problem to solve, the audience, the assets affected, the decision date, and the approver. For print or social work, add the exact dimensions and where the asset will appear. Link to the source files rather than describing them from memory.
How do I write a design request a designer can estimate?
List the screens or assets by name, state the request type, and say what is fixed, such as the brand colors, the existing components, or the approved copy. A list of three named screens can be estimated. A sentence that asks for everything to be redone cannot.
Can requesters attach their design files to the form?
No. The form has no file upload field. Paste a link to the design file, the live page or the reference, and make sure the people who need to see it have access.
Browse by category
More requests in Product & Engineering
Requests
API Access Request
Requests
Architecture Review Request
Surveys
Product Feedback
Checklists
Release Sign-off
Surveys
Sprint Retrospective
Surveys
Third-Party Vendor Evaluation
How to build it
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
