Rewrite for stakeholders
Adapt one update for different readers while retaining facts.
Complete prompt
Task
Adapt one update for different readers while retaining facts.
Instructions
Rewrite [UPDATE] for [STAKEHOLDER TYPES]. Keep factual content stable. For each audience, lead with the decision or impact, then risks, required action, and timing. Keep unknowns visible and flag any sentence that needs confirmation.
Expected output
One version per audience plus a shared fact ledger.
Checks
- Facts do not drift between versions.
- Audience specific actions are clear.
- Claims requiring a source are identified.Expected output and checks
Expected output
One version per audience plus a shared fact ledger.
Checks
- Facts do not drift between versions.
- Audience specific actions are clear.
- Claims requiring a source are identified.
Worked example
Rewrite for stakeholders: recorded example
Original input
Task
Adapt one update for different readers while retaining facts.
Instructions
Rewrite Synthetic update: Workshop date 19 September 2026; session 14:00–16:00; capacity24; allocated budget$180; volunteers needed4; registration page due10 September. The hall booking and projector availability are not confirmed. Ada owns the page. Do not promise admission or a confirmed venue. for project sponsor,volunteers,participants. Keep factual content stable. For each audience, lead with the decision or impact, then risks, required action, and timing. Keep unknowns visible and flag any sentence that needs confirmation.
Expected output
One version per audience plus a shared fact ledger.
Checks
- Facts do not drift between versions.
- Audience specific actions are clear.
- Claims requiring a source are identified.
What the checks found
- All three rewrites preserve September 19, 14:00–16:00, capacity 24, budget $180, four volunteers, Ada and the September 10 page deadline.
- Each version retains the unconfirmed hall and projector. Audience actions are explicitly proposals, not invented assignments.
Revisions after the first output
- No factual correction. A public announcement could be shortened once the venue and response channel are known.
Original output
All versions below describe the same fictional update. “Requested action” is proposed wording for the audience, not evidence of an existing assignment. No version confirms a venue or guarantees admission.
Project sponsor
The workshop is scheduled for 19 September 2026, 14:00–16:00, with capacity for 24, an allocated budget of $180, and a need for 4 volunteers. The hall booking and projector availability remain unconfirmed. Requested action: help resolve those two open items and support filling the volunteer need. Ada owns the registration page, which is due 10 September; no deadline or owner for confirming the hall or projector is supplied. [Needs confirmation before adding a commitment: who will resolve each open item, and by when.]
Volunteers
We need 4 volunteers for the workshop on 19 September 2026, 14:00–16:00, serving up to 24 participants with an allocated budget of $180. The hall booking and projector availability remain unconfirmed. Requested action: indicate your interest and availability for the session; roles and any time needed outside the session still need confirmation. Ada owns the registration page, due 10 September; no volunteer response deadline is supplied. [Needs confirmation before adding a commitment: volunteer roles, full attendance times, response channel, and response deadline.]
Participants
The workshop is scheduled for 19 September 2026, 14:00–16:00, with capacity for 24 participants; this update does not reserve or guarantee a place. The hall booking and projector availability remain unconfirmed. Requested action: check the registration page once it is published for the registration process and venue updates. Ada owns that page, which is due 10 September; the due date is not a promise that it is already available or will definitely be live then. The workshop has an allocated budget of $180 and needs 4 volunteers. [Needs confirmation before adding a commitment: the registration link, admission process, and confirmed venue.]
Shared fact ledger
| Item | Supplied fact / status | Source and limit |
|---|---|---|
| Workshop date | 19 September 2026 | Synthetic update; no real-world verification |
| Session | 14:00–16:00 | Time zone and volunteer setup/cleanup times not supplied |
| Capacity | 24 | Capacity is not guaranteed admission |
| Allocated budget | $180 | Allocation, not spending or a participant fee; currency denomination beyond “$” not supplied |
| Volunteers needed | 4 | Recruitment status, roles, and response deadline not supplied |
| Registration page due | 10 September | Due date, not completion; year understood as 2026 from workshop context |
| Page owner | Ada | No other ownership supplied |
| Hall booking | Not confirmed | Venue must not be presented as secured |
| Projector availability | Not confirmed | Availability must not be promised |
The factual statements above come only from the supplied fictional update. Audience actions are requests, not new project facts; bracketed items explicitly identify details requiring confirmation before they can be stated as commitments.