# Student Newscast Rundown Prompt

> A reusable prompt that turns a student team's planning notes into a segment rundown, fact-check queue and role-based task list, with accuracy gates.

## Install

Copy the content below into your project:

# Student Newscast Rundown Prompt

A reusable prompt that turns a student team's planning notes into a segment rundown, fact-check queue and role-based task list, with accuracy gates.

## 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](<https://blog.google/products-and-platforms/products/education/gemini-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.](https://blog.google/products-and-platforms/products/education/gemini-student-newscast/) · Mon, 05 Oct 2026 16:00:00 +0000

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 学生新闻播报流程提示词

一套可复用的提示词，帮助学生制作团队把自备的策划笔记整理成分段流程表、待核实问题清单和按角色分工的任务列表，并带有准确性与审核检查项。

## 开始使用

把这段提示词粘贴到任何能接受文本的普通 AI 对话中即可。不需要终端、账号或 API 配置。

**准备输入（逐项标注，缺失就写“MISSING”，不要猜）：**
1. 节目名称和目标时长（分钟）。
2. 团队角色（主播、记者、编辑、音效、导演）以及可用的真实姓名或缩写。
3. 每段的原始故事笔记：主题、出镜人，以及团队已确认的事实、引语或数据。
4. 老师或指导老师标记为必需、敏感或禁止的内容。
5. 截止时间或排练时间（如已知）。

**步骤：**
1. 把整段提示词粘贴到对话中，然后在下方附上你标注好的输入。
2. 让它生成草稿流程表。
3. 用提示词内的“使用前检查”逐条核对：每条事实都要能追溯到提供的笔记；时长对比要显示算术过程；待核实清单要列问题而非答案；审核签字区应保留空复选框；缺失的角色或姓名应显示为占位符。
4. 若有检查不通过，指出具体部分让它修正，然后再核对一次。

## 这个提示词做什么

它把粗略的策划笔记整理成分段流程表（顺序、标题、目的、出镜人、目标时长、事实来源、可信度）、时长核对、待核实问题清单、按角色分组的任务清单，以及指导老师审核清单。它只依据提供的笔记工作，未确认的内容会标记为“AWAITING CONFIRMATION”。

## 权限与边界

它只做策划。它不会登录、打开文档工具、查询实时来源、发布、录制或发送任何内容；不会写最终播报稿、笑话或评论，也不会编造引语或把话安到具名者头上。任何录制、分享或发布都必须由人工审核后完成。不要把不允许提供给所用工具的私密学生信息粘贴进去。

## 常见问题

**没有真实姓名也能用吗？** 可以。姓名留空时，它会返回 [ROLE]、[NAME] 之类占位符，并在待核实清单中标记出来。

**它会替我们核实事实吗？** 不会。它只列出需要人工核实的问题。录制或发布前，必须由人确认全部事实并取得指导老师批准。

**来源与致谢：** TokRepo 原创提示词（CC BY 4.0）。参考背景：[Google for Education 关于学生新闻播报的博文](<https://blog.google/products-and-platforms/products/education/gemini-student-newscast/>)。提示词内的示例为虚构，仅作说明用途。已审阅源材料；未进行运行测试。

## 完整可复制提示词

你正在帮助一个学生新闻播报或播客制作团队，把他们自己粗略的策划笔记整理成一份干净、可供播出使用的流程表。本提示词只准备草稿计划。它不会登录任何账号、打开任何文档工具、查询任何实时来源、发布、录制或发送任何内容。任何实际的发布、分享或录制都必须由人工审核后完成。

需要提供的输入
粘贴或输入以下内容。清楚标注每一部分。如果某部分缺失，就在旁边写“MISSING”，不要猜测。
1. 节目名称和目标时长（分钟）。
2. 团队中的角色（例如：主播、记者、编辑、音效、导演）以及可用的真实姓名或缩写。
3. 每段的原始故事笔记：该段讲什么、谁出镜说话，以及团队已经确认的任何事实、引语或数据。
4. 老师或指导老师标记为必需、敏感或禁止的任何段落。
5. 截止时间或排练时间（如已知）。

任务
产出一份逐段流程表和一份制作任务清单。只依据提供的笔记工作。不要添加未提供的事实、姓名、引语、统计数据或学校细节。如果某个故事需要一个笔记中没有的事实，就将其标记为“AWAITING CONFIRMATION”，并把它表述为一个供人工核实的问题。

输出格式
A. 流程表，包含以下列：
   - 顺序（段号）
   - 段落标题
   - 目的（一行，来自笔记）
   - 谁出镜
   - 目标时长（秒）
   - 事实来源（指出它来自哪条提供的笔记）
   - 可信度（已确认 / 有待确认）
B. 总时长核对：把各段时长相加，并与目标时长比较。说明是超出、不足还是正好达标，并仅使用已提供的段落，建议哪些段可以删减或扩充。
C. 待核实问题清单：把每个标记为“Awaiting confirmation”的事项列成一个供人工直接提问的问题（例如，该问谁、具体要核实什么）。
D. 制作任务清单：按角色分组的、具体的任务，每项都有明确的负责人占位符（只有在已提供真实姓名时才填入真实姓名），并留一列空白的“状态”列。
E. 指导老师审核签字区：针对被标记为必需或敏感的段落，列出一份简短清单，带空复选框，并注明人工指导老师必须在录制或发布前批准。

规则与边界
- 绝不要声称或暗示本提示词访问了任何工具、账号、日历、文档或互联网。
- 不要写最终播报稿、笑话或评论。只提供流程表和策划结构。
- 不要编造引语，也不要把话安到具名者头上。
- 如果角色或姓名缺失，使用 [ROLE] 和 [NAME] 之类的占位符，并在待核实问题清单中标记出来。
- 尽可能让每个表格单元格足够短，以便在一行屏幕内读完。

虚构示例（仅作说明用途）
标注输入样例：
- 节目：“Cougar Rumble”每周新闻播报，目标 8 分钟。
- 角色：主播（A.M.）、记者（J.T.）、编辑 [ROLE]、音效 [ROLE]。
- 笔记：关于新图书馆开放时间的段落，学生说时间变了；关于午餐菜单反馈的段落；关于一次被取消的实地考察的段落，原因未确认。

示意输出形式（简略）：
顺序 1 | 图书馆开放时间更新 | 告知学生变更 | A.M. | 90 | 笔记：图书馆开放时间 | 有待确认
顺序 2 | 午餐菜单反馈 | 分享学生意见 | J.T. | 120 | 笔记：菜单反馈 | 已确认
顺序 3 | 实地考察更新 | 说明状态 | [ROLE] | 60 | 笔记：取消的考察 | 有待确认
时长：计划 270 秒，目标 480 秒；可考虑扩充午餐菜单反馈或添加一个已提供的段落。
待核实问题清单：“向图书馆服务台确认新的图书馆开放时间。”“向组织此次活动的老师确认实地考察被取消的官方原因。”
指导老师签字：[ ] 录制前已审核“实地考察更新”。

使用前检查（通过/不通过，对应上方示例）
- 如果表中的每一段都来自提供的笔记，则通过。如果出现了未提供的故事、姓名或数字，则不通过。
- 如果时长对比使用了提供的时长和目标时长，则通过。如果只给出总数而未展示算术过程，或没有可比对的目标，则不通过。
- 如果待核实清单列出的是问题而非答案，则通过。如果它断言了未经确认的原因（例如某次出行为何取消），则不通过。
- 如果审核签字区存在且复选框为空，则通过。如果它声称已获得批准，则不通过。
- 如果缺失的角色或姓名以占位符形式出现，则通过。如果编造了真实姓名，则不通过。

如有任何检查不通过，请在使用前修正草稿。完成后，提醒用户：录制或发布前，必须由人工核实所有已确认事实并取得指导老师批准。

## 参考资料与复用

- [My eighth-grade students built our school newscast from scratch with Gemini.](https://blog.google/products-and-platforms/products/education/gemini-student-newscast/) · Mon, 05 Oct 2026 16:00:00 +0000

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/student-newscast-rundown-prompt-4e89e1d4
Author: Prompt Lab