Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Expense Approval Interface.
Required content and structure
Review amount, receipt, policy exceptions and approve/request-change actions.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Supply expense amounts, currencies, receipts, policy rules and the reviewer actions. Identify which policy checks are confirmed and which need human review.
Layout and behavior
Place the receipt and claimed amount in a common reading area. Keep exceptions visible beside approve or request-change actions and require an explanation where the workflow calls for one.
Task-specific acceptance check
- Preserve currencies and provide a reason for requests to change.
- Test a missing receipt, mixed currency and a request for correction.
- Do not treat a missing policy match as proof of a violation or lose the reviewer's written reason.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Expense Approval Interface. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Review amount, receipt, policy exceptions and approve/request-change actions. Use the following task-specific layout guidance when translating the image into editable elements: Place the receipt and claimed amount in a common reading area. Keep exceptions visible beside approve or request-change actions and require an explanation where the workflow calls for one.
Visual direction from the example brief
light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy.
Interaction specification
The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Review amount, receipt, policy exceptions and approve/request-change actions. Preserve currencies and provide a reason for requests to change. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write an Expense Approval Interface Design Prompt
Use this expense approval interface design prompt to review amount, receipt, policy exceptions and approve/request-change actions.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Keep the Receipt and Exception Together
An expense approval view should make the amount, receipt and policy question easy to compare.
A prominent approval button cannot replace the information needed to justify a decision. Place the receipt and claimed amount in a common reading area. Keep exceptions visible beside approve or request-change actions and require an explanation where the workflow calls for one.
From the Prompt
Place the receipt and claimed amount in a common reading area.
Make It Your Own
Display [AMOUNT] with its original currency beside [RECEIPT]. Show the supplied [POLICY_EXCEPTION] and provide a reason field when requesting a correction.
Prepare the Expense Approval Interface Content
The expense details sit above a large receipt viewer with attachment thumbnails. Prepare the submitted amount, currency, dates and source receipt as a consistent record.
Supply expense amounts, currencies, receipts, policy rules and the reviewer actions. Identify which policy checks are confirmed and which need human review.
From the Prompt
Review amount, receipt, policy exceptions and approve/request-change actions.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this expense approval interface. Supply expense amounts, currencies, receipts, policy rules and the reviewer actions. Identify which policy checks are confirmed and which need human review. Identify missing inputs before replacing them with demonstration content.
Review an Unclear Receipt
The right rail places a policy exception above approval, change-request and rejection controls. Test required reasons, permissions and audit history before applying a decision.
Try an unreadable receipt and an amount in a second currency. The reviewer should be able to request clarification without silently converting or approving the expense. Test a missing receipt, mixed currency and a request for correction. Do not treat a missing policy match as proof of a violation or lose the reviewer's written reason.
From the Prompt
Preserve currencies and provide a reason for requests to change.
Make It Your Own
Review the expense approval interface against this requirement: Preserve currencies and provide a reason for requests to change. Test a missing receipt, mixed currency and a request for correction. Do not treat a missing policy match as proof of a violation or lose the reviewer's written reason. Preserve approved content and revise only the parts that fail this check.
Review Your Expense Approval Interface Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Test a missing receipt, mixed currency and a request for correction. Do not treat a missing policy match as proof of a violation or lose the reviewer's written reason.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current expense approval interface. Test a missing receipt, mixed currency and a request for correction. Do not treat a missing policy match as proof of a violation or lose the reviewer's written reason. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
