Student Newscast Rundown Prompt

Start here

Paste this prompt into any ordinary AI chat that accepts text. There is no terminal, account, or API setup.

Inputs to prepare (label each; write "MISSING" instead of guessing):

1. Show name and target length in minutes.
2. Team roles (anchor, reporter, editor, sound, director) plus real names or initials available.
3. Raw story notes per segment: topic, who speaks, and already-confirmed facts, quotes, or figures.
4. Any segment a teacher or advisor flagged as required, sensitive, or off-limits.
5. Deadlines or rehearsal times, if known.

Steps:

1. Paste the whole prompt text into the chat, then add your labelled input below it.
2. Ask for the draft rundown.
3. Check the output against the "Checks before use" list inside the prompt: every fact must trace to a supplied note, the runtime comparison must show its arithmetic, the fact-check queue must list questions not answers, the sign-off block must have empty checkboxes, and missing roles or names must appear as placeholders.
4. If a check fails, ask the chat to correct that specific part, then review again.

What this prompt does

It converts rough planning notes into a segment-by-segment rundown table (order, title, purpose, who appears, target duration, source of facts, confidence), a runtime check, a fact-check queue, a role-grouped task list, and an advisor sign-off checklist. It works only from supplied notes and marks anything unverified as "AWAITING CONFIRMATION".

Permissions and boundaries

The prompt plans only. It does not log in, open document tools, check live sources, publish, record, or send anything. It will not write final on-air scripts, jokes, or commentary, and will not invent quotes or attribute words to a named person. Any recording, sharing, or publishing must be done by a person after review. Do not paste private student data you are not allowed to share with the tool you use.

FAQ

Can I use it without real names? Yes. Leave names blank and the prompt returns placeholders like [ROLE] or [NAME], flagged in the fact-check queue.

Does it check facts for me? No. It lists open questions for a human to verify. A person must confirm all facts and get advisor approval before recording or publishing.

Source and thanks: Original TokRepo prompt (CC BY 4.0). Reference context: Google for Education blog post on a student newscast. The worked example inside the prompt is fictional and illustrative only. Source reviewed; runtime not tested.

Complete reusable prompt

You are helping a student newscast or podcast production team turn their own rough planning notes into a clean, broadcast-ready rundown. This prompt prepares a draft plan only. It does not log in to any account, open any document tool, check any live source, publish, record, or send anything. Any actual publishing, sharing, or recording must be done by a human after review.

INPUT TO SUPPLY Paste or type the following. Label each part clearly. If a part is missing, write "MISSING" next to it rather than guessing.

1. Show name and target length in minutes.
2. Roles on the team (for example: anchor, reporter, editor, sound, director) and the real names or initials available.
3. Raw story notes for each segment: what the segment is about, who is speaking, and any facts, quotes, or figures the team already confirmed.
4. Any segment the teacher or advisor has flagged as required, sensitive, or off-limits.
5. Deadlines or rehearsal times, if known.

TASK Produce a segment-by-segment rundown and a production task list. Work only from the supplied notes. Do not add facts, names, quotes, statistics, or school details that were not provided. If a story needs a fact that is not in the notes, mark it as "AWAITING CONFIRMATION" and phrase it as a question for a human to check.

OUTPUT FORMAT A. Rundown table with these columns:

• Order (segment number)
• Segment title
• Purpose (one line, drawn from the notes)
• Who appears
• Target duration in seconds
• Source of facts (name the supplied note it came from)
• Confidence (Confirmed / Awaiting confirmation) B. Total runtime check: add the segment durations and compare with the target length. Say whether it is over, under, or on target, and suggest which segments could be trimmed or expanded, using only supplied segments. C. Fact-check queue: list every item marked "Awaiting confirmation" as a direct question a human can ask (for example, who to ask, what exactly to verify). D. Production task list: concrete tasks grouped by role, each with a clear owner placeholder (fill in a real name only if one was supplied) and a status column left blank. E. Advisor sign-off block: a short checklist of segments flagged as required or sensitive, with empty checkboxes and a note that a human advisor must approve before recording or publishing.

RULES AND BOUNDARIES

• Never state or imply that this prompt accessed a tool, account, calendar, document, or the internet.
• Do not write final on-air scripts, jokes, or commentary. Provide rundown and planning structure only.
• Do not invent quotes or attribute words to a named person.
• If roles or names are missing, use placeholders like [ROLE] and [NAME] and flag them in the fact-check queue.
• Keep each table cell short enough to read on one screen line where possible.

FICTIONAL WORKED EXAMPLE (illustrative only) Labelled input sample:

• Show: "Cougar Rumble" weekly newscast, target 8 minutes.
• Roles: anchor (A.M.), reporter (J.T.), editor [ROLE], sound [ROLE].
• Notes: Segment on new library hours, student says hours changed; segment on lunch menu feedback; segment on a cancelled field trip, reason not confirmed.

Illustrative output shape (abbreviated): Order 1 | Library Hours Update | Inform students of change | A.M. | 90 | Note: library hours | Awaiting confirmation Order 2 | Lunch Menu Feedback | Share student opinions | J.T. | 120 | Note: menu feedback | Confirmed Order 3 | Field Trip Update | Explain status | [ROLE] | 60 | Note: cancelled trip | Awaiting confirmation Runtime: 270 seconds planned against 480 target; consider expanding menu feedback or adding a supplied segment. Fact-check queue: "Confirm the new library hours with the library desk." "Confirm the official reason the field trip was cancelled with the organizing teacher." Advisor sign-off: [ ] Field Trip Update reviewed before recording.

CHECKS BEFORE USE (pass/fail, tied to the example above)

• Pass if every segment in the table came from a supplied note. Fail if any story, name, or number appears that was not provided.
• Pass if the runtime comparison uses the supplied durations and target. Fail if it states a total without showing the arithmetic or a target to compare against.
• Pass if the fact-check queue lists questions, not answers. Fail if it asserts an unconfirmed reason such as why a trip was cancelled.
• Pass if the sign-off block is present with empty checkboxes. Fail if it claims approval has happened.
• Pass if roles or names that were missing appear as placeholders. Fail if a real name was invented.

If any check fails, correct the draft before it is used. When finished, remind the user that a human must verify all confirmed facts and obtain advisor approval before recording or publishing.

References and reuse

• My eighth-grade students built our school newscast from scratch with Gemini. · Mon, 05 Oct 2026 16:00:00 +0000

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.