AI does
Plain-language drafting, organization and omission checks.
You do
Set expectations, ensure alignment and make the pack usable for the actual class.
1 Research
Why this matters, and what good looks like
Students need one reliable place to see what the project asks and what happens first. The PBLWorks Project Planner gathers learning goals, the entry event, driving question, major products, learning experiences and the calendar in one plan. It also links to a project information sheet. Its teaching practices call for tasks, schedules, checkpoints, deadlines and resources to be planned from launch to culmination.
- Put the purpose, driving question, product and audience up front.
- Use approved dates, milestones and first-week actions.
- State the criteria and checkpoints students will use to judge their work.
- Link only confirmed resources, contacts and policies.
- Keep related information together so students do not have to piece it across files.
These sources support project planning and information sheets. They do not test whether AI improves clarity or saves time. Treat the AI draft as a first pass. The teacher remains responsible for every fact and decision.
Where the evidence comes from
Strong for project information sheets and launch materials; AI benefit plausible but unvalidated.
2 Workflow
Brief it, steer it, check it
Gather approved source material
Start with an approved internal project design brief. If you did not build one in the library, gather the same approved decisions from your own documents. Mark anything unconfirmed as missing.
Prompt 1 · InventoryCONTEXT Approved internal project design brief: [paste it]. Verified calendar and first-week actions: [paste them]. Approved criteria and resource links: [paste them]. Confirmed policies, contacts and commitments: [paste them]. Existing launch pack, if you are improving one: [paste it or write none]. REQUEST Build an inventory of the information available for the student launch pack. Identify missing details and conflicts between the supplied documents. QUALITY BAR Use only the material above. Do not infer or repair dates, policies, contacts, commitments or criteria. Mark an item as missing when the source material does not confirm it. FORMAT Use a table with four columns: pack field, supplied information, source, and missing or conflicting details.
Draft the pack for first use
Turn the checked inventory into one document that students can scan when the project begins.
Prompt 2 · DraftCONTEXT Checked information inventory: [paste it]. Year group and subject: [add them]. Reading and language requirements, without student names: [add them]. School terms students already know: [add them]. Teacher-approved definitions for terms students may not know: [paste them or write missing]. REQUEST Draft the student project launch pack. Support both routes: create a new pack, or improve the existing pack included in the inventory. QUALITY BAR Keep every fact faithful to the checked inventory. Do not add dates, rules, links, contacts, promises, definitions or claims about current conditions. Use only teacher-approved definitions. Mark a missing definition as [teacher to define]. Use direct language and make the first action easy to find. FORMAT Use these headings: Why this project, Driving question, Product and audience, Timeline, What good work looks like, Resources, and Your first actions. Keep paragraphs short. Use bullets for dates, criteria and actions.
Check how students will use it
Give the draft a usability check. The AI can flag wording and navigation problems; it cannot know what your students understand.
Prompt 3 · Usability checkCONTEXT Draft launch pack: [paste it]. Year group and subject: [add them]. Reading and language requirements, without student names: [add them]. Terms already taught: [list them]. REQUEST Find places where a student may struggle to locate an action, understand a term or tell what happens next. QUALITY BAR Do not claim that a student will understand the pack. Do not rewrite the pack. Flag only issues you can point to in the text. Keep curriculum and project terms when they are necessary, and ask for a short explanation beside them. FORMAT Return a table with four columns: location, issue, evidence from the draft, and teacher decision needed. Group issues under Findability, Clarity and Action.
Compare the draft with its sources
Run a final comparison before you edit and publish. Treat every unsupported detail as a release blocker.
Prompt 4 · Release checkCONTEXT Approved information inventory: [paste it]. Revised student launch pack: [paste it]. REQUEST Compare the launch pack with the inventory. Find omitted required information, changed facts, contradictions and unsupported details. QUALITY BAR Use the inventory as the only source of truth. Do not rewrite either document. Quote the exact line that causes each issue. Treat every date, policy, contact, link and commitment as unverified unless the inventory confirms it. FORMAT Return two lists. 1. Release blockers: issue, exact line, source evidence and teacher action. 2. Verified items: pack field and matching source. If there are no release blockers, say that the comparison found none. Do not call the pack ready to publish.
Check before you use it
- Does every date match the approved calendar?
- Can a student find the first action in under a minute?
- Do the product, audience and criteria match the approved brief?
- Have you confirmed every link, contact, policy and commitment?
- Does the pack say where students should ask when something is unclear?
- Have you removed personal or confidential information before using an external tool?
Stop rule
Never publish AI-generated dates, policies, contacts or commitments without verification.
3 Reuse it
So the next one takes minutes
Build a skill
Save this as a reusable instruction you can run on any project.
The sequence, criteria and output stay stable while the project details change. A teacher can run it in one session and review the result before publishing.
Build an agent
Chain the steps, with a checkpoint where you approve.
This is a bounded release task. An agent adds setup and autonomy where the teacher needs direct control.
Use cases are starting points with one perspective. Disagree with the process, that's expected. Make it yours.
Co-funded by the European Union under Erasmus+ KA210-SCH. No student data. No teacher material stored.