机构学校版School & Institution

协调人要的不是四份报告，而是一屏看全的视图A coordinator does not need four reports — they need one screen

学校社团同时带几支团队时，真正的困难不是单份材料写得好不好，而是没人能一眼看清全批的状态：哪支队的成员名单还对不上、哪支队的引用来源没人核过、哪支队已经把不该公开的结构细节挂到网站上了、哪支队的许可材料只停留在"口头问过"。这些问题分散在各自的聊天记录里，等到临近截止才一起爆发。When a school club runs several teams at once, the real difficulty is not the quality of any single artifact — it is that nobody can see the whole cohort's state at a glance: whose roster no longer matches, whose citations nobody verified, who already published structural detail that should have stayed private, whose permissions never went past "we asked verbally". These live in separate chat threads and surface together right before the deadline.

社团版做的是批量：按团队名册逐队跑完整交付流，每队各自出 M1/M2/M3 与九关台账，再汇成一张协调人视图：横向风险总表、逾期与无进度项、批量倒排、批次共性提醒。协调人看的是代号、状态与风险，看不到任何一支团队的机密创意细节，这是隔离要求，不是权限设置。The School club tier works in batch: the full delivery flow runs team by team down the roster, each team gets its own M1/M2/M3 and nine-gate ledger, and everything rolls up into one coordinator view — a cross-team risk table, an overdue-and-stalled list, a batch backward schedule, and cohort-wide reminders. The coordinator sees codes, status, and risk — never any team's confidential concept detail. That is an isolation requirement, not a permission setting.

适合有科创社团、同时带多支 Conrad 团队的学校。只有一支团队的，请看团队赛季包；只想在提交前做一次外部把关的，请看 Innovation Brief 批评。A good fit for schools running a science-innovation club with several Conrad teams at once. With a single team, see the Team season tier; if you only want one external check before submitting, see the Innovation Brief critique.

逐队三件套 + 协调人视图 + 全菜单，三种格式Per-team core reports + the coordinator view + the full menu, in three formats

名册上的每一支团队都拿到自己的 M1/M2/M3 与九关台账，缺一即未完成；协调人另外拿到跨团队的汇总视图。全部交付件均出 HTML / PDF / DOCX 三格式，且每一份都经人工复核后才交付。Every team on the roster gets its own M1/M2/M3 and nine-gate ledger — missing any one means the delivery is incomplete — and the coordinator additionally gets the cross-team roll-up. All deliverables ship in HTML, PDF, and DOCX, and every one of them passes human review before delivery.

"批量"到底是什么意思What "batch" actually means

这一档是一份合同、几支团队、一年：照名册逐队把完整的检查流程走一遍，名册、排队顺序和老师的汇总表我们统一维护。每支队的材料放在自己的目录里，创意内容不跨队可见：一起管的是流程，不是把数据合到一起。This tier is one contract, several teams, one year: the full checking flow runs team by team down the roster, and we maintain the roster, the queue order, and the teacher’s roll-up. Each team’s materials stay in that team’s own directory and concepts never cross team boundaries — what is shared is the process, never the data.

对照另外两档：Brief 批评是查一次交一套；赛季包是一支团队整周期改一版批一版。社团版还多一条：每份报告都有人工复核过才交。For contrast: the Brief critique is one check, one report set; the Season tier re-checks one team across the cycle. The School club adds one more rule: every report is human-reviewed before it goes out.

每份交付报告必经，不可去除Mandatory on every delivered report — it cannot be removed

本档人工复核为包含项，不是加购项，也不能为了赶工跳过：每一份交付报告都要由人工逐项复核（规则依据与官方链接可解析、无代写或代生成概念的痕迹、无入选与获奖暗示、时序与 D-0 正确、未获官方通知的团队的 Power Pitch 项确为"未适用"、IP 段落未给出法律结论），复核记录未由人工填写完成，交付不得标记完成。Human review is an included item at this tier, not an add-on, and it cannot be skipped to save time: every delivered report is reviewed item by item by a human (rule bases and official links resolve, no ghostwriting or concept-generation traces, no selection or award implication, timing and D-0 correct, Power Pitch items marked "not applicable" for teams without an official notice, IP passages giving no legal conclusion). Until a human has completed the review record, the delivery may not be marked complete.

复核记录位由人工填写，系统只留空位、绝不代填：复核人 / 复核日期 / 结论（通过或需修改及要点）/ 修改闭环确认。记录随交付档案存于内部交付记录；团队台账只记复核状态与非敏感证据指针。The review record is filled in by a human and the system only leaves the slot blank, never filling it: reviewer / review date / verdict (passed, or changes required with the points) / change-closure confirmation. Records are stored with the delivery archive in the internal delivery record; the team ledger keeps only the review status and non-sensitive evidence pointers.

这一档有什么，和免费、其他档比This tier vs free and the other tiers

✓ 是我们来完成；「自己跑」是工具免费给你们、自己动手；「加购」可选；— 不提供。三档的完整对照在总览页。✓ = we do it; “self-run” = free tools, your hands; add-on = optional paid; — = not offered. Full four-column comparison on the overview page.

什么情况该选，什么情况别选When to choose it — and when not to

该选它：学校有科创社团、同时带多支 Conrad 团队，难处在多队管理，需要一张给指导老师的汇总视图。Choose this tier when the school runs a science club with several Conrad teams at once, the difficulty is managing many teams, and the teacher in charge needs one summary view.

三种情况别选它：只有一支团队的，看赛季包就够；想让协调人看到各队机密创意细节的，这一档不提供，协调人视图只有代号、状态与风险；想做"哪支队更有戏"排序的，不提供，任何价格都不提供。学校只想给学生一个免费自查起点的，先用公开套件，付费应当对应真实的管理需求。Three cases where you shouldn’t: one team only (the Season pack is enough); wanting the coordinator to see each team’s confidential concept details (the coordinator view carries codenames, status and risk only); wanting a “which team has the best shot” ranking (we don’t make one, at any price). A school that just wants a free self-check starting point should begin with the public suite — pay only for a real management need.

诚实清单：这一档也没有的东西The honest list: what this tier does not have either

• 跨团队的机密概念对比或"哪支队更有戏"的排序：不提供，协调人视图只有状态与风险，没有优劣排名Cross-team comparison of confidential concepts, or any ranking of "which team looks stronger" — not provided; the coordinator view carries status and risk, never a merit ranking
• 未获官方 Finalist 通知的团队的 Power Pitch 练习：同批其他队收到通知也不放宽Power Pitch practice for teams without an official Finalist notice — not relaxed even when other teams in the cohort received one
• 学生姓名、出生日期、联系方式等直接身份信息的收集与留存：名册只用团队代号与非敏感字段Collecting or retaining student names, dates of birth, contact details, or other direct identifiers — the roster uses team codes and non-sensitive fields only
• 主办方页面与他队材料的缓存、嵌入或商业检索：不提供，只用官方链接与团队授权的本地文件Caching, embedding, or commercially retrieving organizer pages and other teams' materials — not done; only official links and team-authorized local files are used
• 代学校或团队与主办方沟通、申诉或取得口径：须由团队自己完成Communicating, appealing, or obtaining rulings from the organizer on the school's or team's behalf — the team must do this itself

四步，从来信到批量交付Four steps from first email to batch delivery

1. 来信Write in邮件说明学校社团情况、团队数量与各队当前进展，注明申请"机构学校版"。Email us about the club, how many teams there are and where each stands, requesting the "School club" tier.
2. 资格确认与建册Eligibility confirmation and roster setup逐队确认人数与年龄资格、教练登记、成员变更时点与概念自持；确认协调人身份与学校授权；建立只含代号与非敏感字段的名册。Team by team we confirm size and age eligibility, coach registration, membership-change timing, and that each concept is the team's own; we confirm the coordinator's role and the school's authorization; and we build a roster of codes and non-sensitive fields.
3. 材料收取与排队Intake and queueing各队按 Brief 批评口径各交一套材料；与协调人共同确定队列顺序与批次排期。Each team submits one bundle following the Brief-critique intake list; queue order and batch scheduling are set together with the coordinator.
4. 批量交付Batch delivery逐队交付 M1/M2/M3 与授权 O 项（每份经人工复核），协调人另收汇总视图；后续轮次在各队 M3 原表更新状态。M1/M2/M3 and authorized O items are delivered team by team (each after human review), the coordinator receives the roll-up, and later rounds update each team's M3 status in place.

不代写、不替团队想创意、不预测入选、不替团队断言事实、不贩卖焦虑。规矩每一档都一样，全文在总览页。No ghostwriting, no concept generation, no selection prediction, no asserting facts for the team, no fear-based selling — the same rules in every tier; full text on the overview page.

常见问题Frequently asked