Draft a proposal with a workable action plan
“We will test our labels” leaves too much undecided
- The materials team wants approval for its A/B task. A teacher needs to know the question, participants, procedure, scoring and privacy arrangements. A promise to “collect some data” does not explain what will happen or whether it is appropriate.
- This original GAC033-aligned lesson joins earlier work into a proposal. A proposal explains planned research and its reasons; it must not report expected success as a result. The main study in this sequence has not been conducted.
“我们将测试我们的标签”留下了太多未决事项
- 材料团队希望获得其A/B任务的批准。教师需要知道问题、参与者、程序、评分和隐私安排。“收集一些数据”的承诺并不能解释将会发生什么或这是否合适。
- 本原创GAC033对齐课程将早期工作与提案结合起来。提案解释了计划的研究及其理由；它不应将预期成功报告为结果。此序列中的主要研究尚未开展。
A proposal should describe an expected favourable pattern as if it were an observed result.
Planned or expected outcomes are not collected evidence. State the hypothesis without inventing results.
Connect purpose, evidence and question
- Start with the observed problem and driving question. Then give a brief synthesis of real verified sources and explain why a local comparison is useful. Do not paste the fictional teaching cards from unit 5.5 into a real literature review as if they were published studies.
- State the research question precisely: among the planned 24 class volunteers, does B yield more completely correct four-item sorting sheets than A under equal instructions and a two-minute limit? Explain why sorting success, rather than preference, is the selected outcome.
连接目的、证据和问题
- 从观察到的问题和驱动性问题开始。然后给出真实验证过的来源的简要综合，并解释为什么本地比较是有用的。不要将第5.5单元的虚构教学卡粘贴到真实文献综述中，仿佛它们是已发表的研究。
- 精确陈述研究问题：在计划的24名班级志愿者中，在相同的指令和两分钟限制下，B是否比A产生更多完全正确的四项分类表格？解释为什么选择分类成功而非偏好作为结果。
Which background can support an actual proposal?
Use sources you have examined and can trace. Teaching examples cannot become real citations.
Specify a repeatable procedure
- Describe 12 participants per layout, shuffled assignment slips, identical item choices and no coaching. Each person sees one layout. Fix the answer key and the complete-success rule before collection. Store the approved task versions so a later revision cannot silently change what participants saw.
- Explain recruitment, voluntary participation, stopping or withholding a sheet, anonymous submission and the inability to retrieve an individual's sheet after anonymous submission. Name the teacher-approved record location, who can access it and when it will be disposed of.
Method summary: “With approval, we invite willing peers and assign one layout by shuffled slips. We give the same four-item task for two minutes without help. A sheet counts as a complete success only when all four placements match the fixed key. We report successes and group sizes without names.”
指定可重复的程序
- 每布局描述12名参与者，随机分配的分配单，相同的物品选择和无指导。每人只看到一个布局。在收集前固定答案键和完全成功规则。存储已批准的任务版本，以防日后修订时悄悄更改参与者看到的内容。
- 解释招募、自愿参与、停止或扣留表格、匿名提交以及匿名提交后无法检索个人表格的情况。命名经教师批准的记录位置、谁可以访问它以及何时销毁。
方法摘要：“经批准后，我们邀请自愿的同伴并通过随机分配单分配一种布局。我们给予同样的四项任务两分钟且不提供帮助。只有当所有四个放置位置都与固定键匹配时，表格才计为完全成功。我们在不提及姓名的情况下报告成功数和组大小。”
Which method detail prevents silently changing what success means?
Advance definition keeps the outcome consistent with the research question.
Plan the analysis before the result
- Report complete successes out of participants for each condition. With 12 per group, counts share a denominator. If the actual groups differ in size, report both counts and proportions. Do not convert a small project result into an official test score or a claim about every classroom.
- List limits and possible interpretations. A difference could be consistent with a layout benefit under these conditions; reading differences or chance variation may still matter. A tie is a valid result. No outcome requires you to declare the preferred design successful.
The proposal's expected pattern is a hypothesis, not evidence. Do not fill a results table with invented participant scores to make an unfinished project look complete.
在结果出来之前规划分析
- 报告每种条件下参与者的完全成功人数。每组12人时，计数共享分母。如果实际组大小不同，则同时报告计数和比例。不要将小型项目的结果转化为官方考试分数或关于每个班级的断言。
- 列出局限和可能的解释。差异可能与这些条件下的布局优势一致；阅读差异或偶然变化仍可能重要。平局是一个有效的结果。没有结果要求你宣布首选设计成功。
提案的预期模式是假设，而非证据。不要填充虚构的参与者分数以使未完成的项目看起来完整。
If 9 of 12 participants succeed, what percentage succeeds?
9 ÷ 12 × 100 = 75%. State the denominator and do not treat this illustrative calculation as collected study data.
Make the action plan depend on approval
- Separate drafting, review, approval, pilot, revision and main collection. A plan can set intended dates but must make participant work conditional on approval. If permission is delayed or declined, revise the scope rather than bypassing it to meet a presentation date.
- Assign owners and evidence of completion. “Team handles ethics” is vague; “Procedure lead prepares the information script; teacher checks it before the pilot” identifies a task and a dependency. Allow time for revision after feedback.
| Stage | Completion evidence | Dependency |
|---|---|---|
| Draft | Question, source record, method and ethics text | Scope agreed |
| Review and approval | Comments addressed and approval recorded | Complete draft |
| Pilot and revision | Clarity notes and fixed materials | Approval |
| Main task, if authorised | Anonymous sheets and procedure log | Approved final procedure |
使行动计划取决于批准
- 分开起草、审查、批准、试点、修订和主要收集。计划可以设定预期日期，但必须使参与者工作取决于批准。如果许可延迟或被拒绝，请修改范围，而不是为了赶上演示日期而绕过它。
- 分配负责人和完成证据。“团队处理伦理”是模糊的；“程序负责人准备信息脚本；教师在试点前检查它”明确了任务和依赖关系。允许在反馈后进行修订的时间。
| 阶段 | 完成证据 | 依赖关系 |
|---|---|---|
| 草稿 | 问题、来源记录、方法和伦理文本 | 范围已商定 |
| 审查和批准 | 评论已解决且批准已记录 | 完整草稿 |
| 试点和修订 | 清晰度笔记和固定材料 | 批准 |
| 主要任务（若授权） | 匿名表格和程序日志 | 已批准的最终程序 |
Order the approved project stages.
Participant work follows approval and a fixed method. A schedule cannot override the gate.
Check coherence across the document
- Read the question, method and analysis side by side. If the question is about accuracy but the method asks only preference, the proposal is inconsistent. Correct the mismatch before improving the cover page or wording.
- Draft a one-page proposal with purpose, verified background, question, method, ethics, analysis, limits, schedule and references. Mark unconfirmed details as pending. A complete structure with unresolved approval is a reviewable proposal, not authority to begin.
A proposal is a connected argument for planned work: why this question, why this method, how it will run, how evidence will be analysed and what permissions and limits apply.
检查文档各部分的连贯性
- 并排阅读问题、方法和分析。如果问题是关于准确性但方法只询问偏好，则提案是不一致的。在改善封面或措辞之前，纠正不匹配之处。
- 起草一页提案，包含目的、验证过的背景、问题、方法、伦理、分析、局限、时间表和参考文献。标记未确认的细节为待处理。结构完整但批准未决的是可审查的提案，而非开始工作的授权。
提案是为计划的工作提供的连贯论证：为什么这个问题，为什么这种方法，它将如何运行，证据将如何分析以及适用哪些许可和局限。