Changed Request Reapproval from Revision Policy Notes

Conceptual expedited approval board with a navy review column, amber exception lane, shield tile, and teal follow-up folder.

ChatGPT

Urgent Exception Approval from Expedited Routing Notes

Transform expedited approval notes into a controlled exception route with eligibility, authority, and follow-up review.

Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of expedited approval notes defining urgency criteria, exception authority, required evidence, and any retrospective review. 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. Keep the normal approval path visible and add a separate expedited path only for source-defined eligibility criteria. Preserve who can authorize the exception, the evidence required, any scope or expiry limits, and any required later review. Urgency alone must not imply approval or authorize bypassing a required reviewer. If eligibility, exception authority, or follow-up timing is missing, mark it Needs clarification instead of inventing a shortcut. Distinguish temporary authorization from final sign-off and show how the documented exception closes. Compose a split normal-and-expedited approval board with a guarded exception entry and a separate follow-up review card at the bottom. 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.

View Details

Conceptual reapproval board showing overlapping request sheets, highlighted changed fields, and a new teal review card.

ChatGPT

Changed Request Reapproval from Revision Policy Notes

Turn revision policy notes into a change-sensitive reapproval map with explicit invalidation and version boundaries.

Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of revision policy notes showing which request changes invalidate approvals and which review stages must restart. 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. Identify each documented material-change trigger and the exact affected approvals. Keep unchanged approvals valid only where the source explicitly permits it. Distinguish correction before approval from a material change after sign-off. Associate each approval with the request version it covers and show the source-defined reapproval destination. Route undefined change types or missing version rules to Needs clarification. Do not allow an approval of an earlier version to appear as approval of the revised request, and do not invent numeric tolerances or materiality thresholds. Compose a side-by-side original-and-revised request board with changed fields visually accented and an adjacent reapproval lane. 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.

View Details

Conceptual committee approval board with indigo reviewer tiles, amber and emerald gates, and a separate plum exception tile.

ChatGPT

Committee Quorum Routing from Decision Notes

Convert committee approval notes into a voting gate that distinguishes participation, approval thresholds, and veto rules.

Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of committee decision notes defining eligible reviewers, quorum, voting thresholds, abstentions, and veto rights. 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. Separate attendance or participation quorum from the number or proportion of affirmative approvals. Preserve the denominator used by each source rule and show how abstentions, recusals, missing responses, ties, and vetoes are handled only when documented. Do not treat a simple majority as unanimity or a participation quorum as approval. Keep any rule conflict unresolved in a Needs clarification card before the final decision. Represent committee roles rather than inventing members and distinguish a failed vote from a pending vote. Compose a committee board with reviewer tiles grouped above separate participation and decision gates, plus an isolated exception area. 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.

View Details

Conceptual correction board with request and revision sheets in a circular arrangement and a separate closed folder.

ChatGPT

Returned Request Rework from Correction Notes

Transform correction notes into an approval rework loop that separates rejection, revision, and resubmission.

Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of approval correction notes showing return reasons, requester responsibilities, and resubmission rules. 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. Map return-for-correction as a distinct state from final rejection. Show the documented reason or missing evidence, the requester action, and the condition for resubmission. Preserve whether the corrected request returns to the original reviewer or restarts an earlier stage. Display which prior approvals remain valid only if the source specifies it. Keep the original request and revision identities distinct where described. Flag undefined resubmission destinations or approval retention rules as Needs clarification; do not invent retry limits or assume a corrected request is approved. Compose a compact loop-shaped correction board with reviewer, returned request, revision evidence, and resubmission cards; rejection sits outside the loop. 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.

View Details

Conceptual overdue approval board with a navy card, amber clock disc, coral notifications, and a mint stop marker.

ChatGPT

Overdue Approval Reminders from Escalation Notes

Convert reminder and escalation notes into a timer-aware approval map with stop conditions and explicit clock rules.

Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of approval reminder notes specifying deadlines, timer start events, reminder recipients, and escalation rules. 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. Show the event that starts the approval clock and preserve the stated duration, time zone, working-day calendar, pause rules, reminder intervals, and recipients when present. Distinguish a reminder from escalation and from reassignment. Mark unspecified clock assumptions as Needs clarification rather than choosing business or calendar hours. Show documented timer cancellation when the request is approved, rejected, withdrawn, or otherwise completed. A timeout must not become automatic approval unless the supplied rule explicitly says so; display any such rule verbatim and prominently for review, never execute it. Compose a portrait pending-approval board with a narrow timer rail, separate reminder and escalation cards, and visible terminal stop markers. 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.

View Details

Conceptual approval coverage scene with two role cards, a calendar tile, and an amber authority badge.

ChatGPT

Absent Approver Delegation from Coverage Notes

Transform approval coverage notes into a primary-and-delegate routing map that preserves authority limits.

Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of approval coverage notes naming primary roles, delegates, absence triggers, and delegated authority limits. 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. Map the primary approver first and expose delegation only under the documented absence or unavailability trigger. Preserve the delegate scope, effective dates, authority limits, and any required delegation record. Distinguish substitution from adding another required reviewer. Route undocumented coverage gaps to Needs clarification; do not silently send requests to a manager or grant broader authority. If no eligible delegate exists, show a pending or escalation state only as the source permits. Keep the return-to-primary condition visible if supplied. Compose a two-column coverage board with the primary approver on the left, the authorized delegate on the right, and a compact scope card between them. 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.

View Details

Changed Request Reapproval from Revision Policy Notes

Prompt

How to use it

Common failure fixes

Changed Request Reapproval from Revision Policy Notes

Prompt

How to use it

Common failure fixes

More from Approval Notes to Automated Routing Prompts

Urgent Exception Approval from Expedited Routing Notes

Changed Request Reapproval from Revision Policy Notes

Committee Quorum Routing from Decision Notes

Returned Request Rework from Correction Notes

Overdue Approval Reminders from Escalation Notes

Absent Approver Delegation from Coverage Notes