Conceptual budget sign-off board with descending green and cream approval cards and adjacent document tabs.

Example result illustrating this prompt's visual direction. Actual results may vary by model, reference image and settings.

Sequential Budget Sign-Off from Department Notes

Turn departmental budget sign-off notes into ordered approval stages with visible ownership and handoff conditions.

Prompt

Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of budget sign-off notes listing the review order, responsible roles, required evidence, and allowed outcomes. Use only legible information present in the photo or explicitly supplied alongside it. Preserve the source process meaning, role names, rule values, conditions, and relationships; replace the photographed paper or whiteboard presentation with a polished digital board. Do not reproduce desk clutter, handwriting defects, glare, or perspective distortion. Preserve the exact sign-off sequence and distinguish review, recommendation, and final approval roles. For each documented handoff, show the evidence required and the condition that permits progression. Keep rejection and return-for-correction separate. Only include a stage-skipping condition when it is explicitly present in the source. Flag contradictory role order or undefined final authority as Needs clarification. Do not invent budget values, approval authority, or permission to commit funds. Compose a compact top-to-bottom staircase of sign-off cards with an adjacent evidence column and short connectors. Use short English labels, high-contrast typography, orthogonal connectors, action cards for steps, and decision diamonds only for actual decisions. Use labels as well as color to distinguish states. Keep arrow direction unambiguous, avoid connector crossings, and fit the complete map inside the canvas without clipping. Include only labels needed to understand the workflow; do not add slogans, decorative captions, logos, or explanatory filler. For an unreadable or conflicting rule, preserve a visibly unresolved Needs clarification card at the affected point; never draw a falsely complete route beyond it. If the photo lacks enough legible content to identify the process, request a clearer source photo before creating the visual. Redact personal contact details, signatures, and account identifiers unless essential and explicitly requested; retain approver roles. Deliver one finished visual derived from the reference photo. This is a visual design for review: do not send notifications, grant approvals, change records, connect accounts, or claim an automation has been deployed.
Recommended: ChatGPT
Upload your photo to the AI tool first, then use this prompt. The prompt asks the model to preserve identity and key visual features.

How to use it

  1. Upload a legible photo of budget sign-off notes listing the review order, responsible roles, required evidence, and allowed outcomes.
  2. Paste the prompt and provide any confirmed rule clarifications alongside the photo.
  3. Check the finished visual against the source and resolve all Needs clarification cards before using it to configure an automation.

Common failure fixes

  • If recommendation is shown as final approval, restore the distinct authority labels from the source.
  • If a stage is skipped, remove the shortcut unless the source explicitly allows it.
  • If evidence requirements crowd the stage cards, place them in an aligned side column without changing their associations.