Turn a client conversation into a concise handoff with context, feedback, scope changes and unresolved decisions for colleagues in another time zone.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
Client or project name. Default: Cedar Community Workshop
Who needs the handoff. Default: The product and support team starting the next morning
Source notes, confirmed context and any supplied links. Default: Client call September 8: Ana said the booking page is clear, but asked for a printable attendee list. No scope change was approved. Jo will send a sample list by September 10. Product must decide whether printing fits the pilot. Client asked for the next update on Friday; time and time zone were not specified. Existing pilot deadline remains September 30.
Write an asynchronous handoff about Cedar Community Workshop for The product and support team starting the next morning.
Call notes and existing project context:
Client call September 8: Ana said the booking page is clear, but asked for a printable attendee list. No scope change was approved. Jo will send a sample list by September 10. Product must decide whether printing fits the pilot. Client asked for the next update on Friday; time and time zone were not specified. Existing pilot deadline remains September 30.
Start with the current state and why the receiving team needs this update. Summarize confirmed client feedback, proposed scope changes, decisions already made and decisions still requiring team input. Include action items only with the owners and dates actually stated; use Not assigned or Not stated for gaps.
Separate client requests from approved commitments. Preserve exact short quotes when wording matters and mark unknown time zones instead of silently converting times. Include links only if supplied. Finish with the next contact, dependency or decision the team should attend to and a list of clarifications needed. Do not invent account history, communication preferences or delivery promises. The handoff should stand on its own for someone who missed the call.No public examples yet for version 1
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Plan an online session minute by minute, including speaker cues, technical preparation, audience participation and contingencies for common disruptions.
No public results yet
Apply your own expense categories consistently, preserve original transactions and flag ambiguous items, duplicates and possible recurring charges.
No public results yet
Create a practical packing list matched to trip length, activities, expected conditions, laundry access and the luggage limits you provide.
No public results yet
Surface the values behind competing priorities and prepare shared criteria, compromise options or a small experiment to resolve disagreement.
No public results yet
Prepare a scope workshop with proposed Must, Should, Could and Won’t categories, explicit tradeoffs and questions for disputed requirements.
No public results yet
Build a work breakdown with concrete deliverables, dependencies, role needs and checkpoints while keeping uncertain estimates explicit.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.