Example result illustrating this prompt's visual direction. Actual results may vary by model, reference image and settings.
Parallel Vendor Reviews from Onboarding Approval Notes
Convert vendor onboarding notes into parallel review lanes with a clearly defined join before activation.
Prompt
Transform the uploaded reference photo into a clean, readable approval-routing visual. The intended source is a legible photo of vendor onboarding notes showing required review teams, review dependencies, and activation conditions. 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 genuinely independent reviews into parallel lanes while keeping source-defined prerequisites sequential. Preserve the documented review teams and their evidence requirements. Show whether activation requires all reviews, any review, or another explicitly stated join condition. If the join rule is missing, mark it Needs clarification and leave activation blocked in the proposed map. Show how a rejected, pending, or returned review affects the join only when documented. Do not silently omit an uncompleted review or interpret parallel review as permission to activate early. Compose a landscape onboarding board with compact vertical review lanes, a shared join area, and a visually distinct activation card. 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.
How to use it
- Upload a legible photo of vendor onboarding notes showing required review teams, review dependencies, and activation conditions.
- Paste the prompt and provide any confirmed rule clarifications alongside the photo.
- Check the finished visual against the source and resolve all Needs clarification cards before using it to configure an automation.
Common failure fixes
- If a prerequisite becomes parallel, restore the source dependency before the affected review.
- If activation appears before the join condition is satisfied, separate the activation card and restore the documented gate.
- If the join rule is absent, label it Needs clarification rather than assuming all or any approval.