Counts show all available guides. Filters combine to narrow your results.
Build a workflowGuide
Show who hands work to whom in a small process
Show each role’s handoff, required contents and the point where a return path is undefined.
Illustrative resourceNot tool-testedAdults working with non-sensitive process handoffs information
What you’re working towards
A role-lane process map in text, with explicit handoff contents, return loops and unowned transitions held. This is an authored practice example; no consumer AI run has been recorded.
Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides
Saving needs JavaScript. Reading and downloading this guide does not save it.
Make a start
One step at a time.
4 steps
Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.
Start with the synthetic example, then adapt each prompt to your task.
01
Try the complete example
Open a new chat in a text AI assistant you already have permission to use. Paste all of Input from this guide, then the prompt below, in one message. Do not paste Output: that is the illustrative answer for comparison. Expect a written result that will show each role’s handoff, required contents and the point where a return path is undefined. Different wording is fine; the source facts and rules must agree.
Your starting prompt
Map the supplied process as text role lanes and a numbered handoff ledger. State who passes what to whom and under which condition, retaining each source ID. Walk the normal path, draft-return loop and failed-proof path. Keep the missing corrected-proof gate visibly held; do not invent an owner, approval or production step.
Use only the complete synthetic input pasted above. Return the finished written result. Keep missing facts unknown. Do not send, publish, order or change another service.
02
Walk a returned item through the map
Use a scrap of paper to stand for the draft. Move it through the role names for a rejected draft, then a mismatching proof. Stop where the source stops. If the map lets either route skip an approval or invents a receiver after the failed proof, ask for the whole map to be corrected from S3 and S5. This is a human dry run of the text, not an actual proof inspection.
Your starting prompt
Trace one draft rejection and one proof mismatch through the synthetic map. For each transition name the source rule, receiving role and payload. Stop at the first undefined transition. Do not repair the gap by assumption or claim a real process trial.
03
Trace the answer back to the source
Compare the answer with Input yourself. All four roles and S1–S5 are represented. A rejected draft returns to Editor and then Owner; it never bypasses review to the coordinator. A mismatching proof returns to Editor with differences and then holds; no corrected-proof approver is invented. Only a matching proof ends the defined checking route, with no production or publication permission. If a check fails, paste: “This part is wrong: [quote it]. My source says: [quote the exact line]. Return the complete corrected result and explain the change.” Recheck before saving; if the source itself is incomplete, keep that part unresolved.
Your starting prompt
Audit the result against the source pasted in this chat. Check these specific points:
- All four roles and S1–S5 are represented.
- A rejected draft returns to Editor and then Owner; it never bypasses review to the coordinator.
- A mismatching proof returns to Editor with differences and then holds; no corrected-proof approver is invented.
- Only a matching proof ends the defined checking route, with no production or publication permission.
Show each mismatch and return a complete corrected replacement. Distinguish your text audit from checks that only a person or the actual application can perform.
04
Use your own input
For your own version, open a new chat. Paste the prompt below after replacing every bracketed field. Replace related IDs, quantities, dates, rules and limits together; none of the practice facts carries over. Expect the same named deliverable using your source. Review it yourself: walk each return path supplied in MY INPUT through the map with paper tokens. Check that no required approval is skipped and any missing next handoff stays unresolved. Do not invent a return path if none is supplied. If a check fails, paste: “This part is wrong: [quote it]. My source says: [quote the exact line]. Return the complete corrected result and explain the change.” Recheck before saving; if the source itself is incomplete, keep that part unresolved.
Your starting prompt
Map my complete low-stakes process into role lanes and numbered handoffs. For each transfer state sender, receiver, contents, condition and source. Preserve return loops and approval scopes. Walk a normal route and each supplied rejection route. Stop undefined or unowned transitions and ask the process owner; do not invent responsibility or claim the process was executed.
MY INPUT
Complete low-stakes process description: [replace with your own complete non-sensitive details, or state unknown]
Named roles and responsibilities: [replace with your own complete non-sensitive details, or state unknown]
Inputs/outputs per step: [replace with your own complete non-sensitive details, or state unknown]
Return/rejection paths: [replace with your own complete non-sensitive details, or state unknown]
Known completion condition: [replace with your own complete non-sensitive details, or state unknown]
Use only MY INPUT for facts and constraints. Ask for an essential missing fact or conflicting rule before deciding; do not import practice-example names or numbers. Return the complete result plus unresolved questions and a source-based check list. Do not send, publish, buy, schedule or change another service.
Optional: improve the result
Fill a gate only with an explicit new rule
Show an owner-supplied addition separately from the original process. This optional extension uses only the synthetic example. Return to the sample chat, or paste its full Input into a new chat first. Do not transfer the changed sample values to your own input.
Advanced prompt
For this sample only, add new rule S6: after H5, Editor sends corrected draft to Owner; Owner must approve it before Print Coordinator creates a new proof, which repeats S4. Produce a revised map and change log. Keep matching proof as the checking end only; do not add production authorization.
Show, then try
See the shape of the result.
This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.
01 / The starting point
Synthetic input
Synthetic practice input. All names, products, records and policies below are invented.
Complete fictional poster-proof process. Roles are Requester, Editor, Owner and Print Coordinator.
S1: Requester sends approved text to Editor.
S2: Editor checks spelling and sends the draft to Owner.
S3: Owner either approves that draft or returns specific corrections to Editor. A returned draft goes through Editor’s correction and Owner’s review again.
S4: An approved draft goes from Owner to Print Coordinator, who creates a paper proof and compares its text with that approved draft. A matching proof completes this checking process; it does not authorize production or publication.
S5: If proof text differs, Print Coordinator returns the proof and differences to Editor. The source supplies no next handoff, corrected-proof approver or approval rule after this return.
Need a text role-lane map, numbered handoffs with contents, normal and rejected-draft paths, and the blocked failed-proof path. Do not invent the missing gate. No real proof is created or inspected in this example.
Copies text only. For image or file tasks, use the source files named in the steps too.
Illustrative answer authored for this guide; not a recorded AI response.
Roles and handoffs
H1, Requester → Editor (S1): approved source text. Editor needs the actual text to check spelling.
H2, Editor → Owner (S2): draft after spelling check.
H3a, Owner → Editor (S3, return): that draft plus specific corrections. Editor revises and returns the revised draft to Owner via H2 for another review.
H3b, Owner → Print Coordinator (S3/S4, approve): the exact approved draft and its approval status. A rejected draft cannot take this handoff.
H4, Print Coordinator internal check (S4): create a paper proof and compare its text with the approved draft. If matching, end at “proof matches approved text”; this ends only the checking process.
H5, Print Coordinator → Editor (S5, mismatch): proof plus the identified text differences.
H6, after H5: HOLD. No next recipient or corrected-proof approval rule is supplied. Ask the process owner who reviews and approves the corrected proof and what must be compared before completion.
Text role lanes
Requester: provide approved text → H1.
Editor: receive H1 → spelling check → H2; receive H3a → revise → H2; receive H5 → hold at the undefined next gate.
Owner: receive H2 → either H3a return or H3b approval.
Print Coordinator: receive H3b → H4 proof comparison → matching end, or H5 mismatch return.
Path walk-throughs
Normal: H1 → H2 → H3b → H4 matching end.
Rejected draft: H1 → H2 → H3a → Editor revision → H2 → Owner reviews again; approval is not assumed.
Failed proof after approval: H1 → H2 → H3b → H4 mismatch → H5 → H6 hold. The previous draft approval does not fill the missing corrected-proof rule.
This is a proposed text map of supplied responsibilities. No real handoff, paper proof, approval or publishing action occurred.
These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.
Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.
!
A few things to watch for.
A line between role names is incomplete unless it says what is handed over and what lets the next person start.
Earlier approval of a draft does not automatically approve every later proof or correction. Preserve the exact approval scope.