# Build one fact sheet for a program launch
More time on the field. Less time in the office.

Audience: administrators
Status: practical assisted writing guide, not an automatic launch or registration integration.
Existing program and registration tools remain the official records.

## Outcome and inputs
Outcome: one approved fact sheet plus consistent draft landing-page, FAQ and announcement copy.
Inputs: owner-approved program/cycle facts, supplied dates/times/time zone/venue/criteria,
approved registration destination/status, publishing owner and staff clarification process.

## Master fact sheet
- Exact program and cycle:
- Version/date:
- Program owner:
- Publishing owner:
- Intended audience:
| Fact ref | Approved fact | Source/version | Owner approval | Unknown/conflict |
|---|---|---|---|---|
| | | | | |
Keep event dates, arrival/session times and registration deadlines distinct.
Do not infer missing criteria, fees or dates from an older cycle.

## Five-step workflow
1. Collect approved facts with source/date/owner. Missing details stay questions.
2. Log conflicting sources and hold disputed claims for the owner. A reachable link does not
   establish open registration. Confirm destination/status without submitting a test record.
3. Draft channel copy only from approved facts. Retain private source references beside claims.
   Do not invent remaining capacity, selection guarantees, testimonials, deadlines or urgency.
4. Check each call to action against program/cycle, destination and confirmed process status.
   Do not conflate an RSVP with completed registration or say register now before opening.
5. Owner reviews claims; publishing owner approves version/audience/destination.
   Record what must be rechecked after changes. Forms, sending and publishing are separate actions.

## Reusable copy structure (draft only)
Landing-page introduction:
[Exact program/cycle] offers [confirmed description]. [Confirmed dates/location, if approved].
Next step: [owner-approved action matching the confirmed registration status].
FAQ:
- What is the program? [approved description; fact ref]
- When and where is it? [approved details; fact ref, or hold]
- How do I participate? [approved process/status; fact ref]
Short announcement:
[Program/cycle] — [approved one-sentence description]. [Confirmed next step].
Keep unresolved placeholders in private drafts only, never as accidental release copy.

## Synthetic example
DEMO-P1 has a confirmed cycle and venue; registration is confirmed not yet open.
Draft: Registration details will be provided through the organizer's confirmed channel.
HOLD: Register now - last spaces.
Reason: open registration and remaining capacity are not supported.
This is fictional, not a live program announcement.

## Channel consistency check
| Channel/version | Program/cycle match | Dates/process match | CTA and destination match | Owner approval |
|---|---|---|---|---|
| Landing page | | | | |
| FAQ | | | | |
| Announcement | | | | |

## Optional sanitized AI prompt
Use only this approved public/synthetic program fact sheet to draft a landing intro, FAQ and
short announcement. Keep fact references beside claims for private review.
Separate approved copy from held claims/questions. Do not invent dates, criteria, costs,
urgency, capacity, guarantees, testimonials or registration status.
Do not create forms, submit registrations, contact applicants, send or publish anything.
Fact sheet/source versions: [paste]
Confirmed registration destination/status: [paste approved public details]
Audience/tone: [paste]
Return: source-linked draft copy | held items/questions | channel consistency check.

## Approval/privacy checkpoint
- Approved public copy version/date:
- Program owner claim review:
- Publishing owner destination/audience review:
- Change/recheck owner:
Exclude applicant data, children's identities, private contacts, unpublished access links
and credentials. Keep the internal source/approval log private. This worksheet sends nothing.