AI PBL Bootcamp · Free · Three Mondays from 26 October
Launch

Prepare the exhibition and audience plan

Public presentation is treated as an end-of-project add-on, so audience, access, feedback and student roles are unresolved until too late.

AI does

Checklist drafting, schedule options and audience-feedback templates.

You do

Protect student dignity, accessibility, safety and the exhibition’s learning purpose.

1

Research

Why this matters, and what good looks like

An exhibition lets students explain their work to a real audience. Its operations plan records how that sharing will happen. A run-of-show is the timed sequence, including transitions. Start planning during launch so people can resolve access and permission questions before the event.

The sources are professional frameworks and practitioner guidance, not studies of this AI workflow. Early planning, role choices and the checks below are authorial process choices. The retained passages do not establish local permissions or AI benefit.

  • PBLWorks includes sharing and explaining work beyond the classroom.
  • HQPBL places public sharing during development and at the conclusion.
  • PBLWorks connects feedback with improving process and products.
  • Practitioner guidance warns that focusing only on the final product can obscure learning throughout the process.

Where the evidence comes from

Strong for public product/exhibition planning; AI benefit unvalidated.

2

Workflow

Brief it, steer it, check it
  1. Establish the planning boundary

    Bring your purpose, confirmed audience, space and timing. Optional D03, D05 and L07 outputs can supply these; equivalent teacher records work. Bound this session to one small exhibition with available student and partner reviewers.

    Prompt 1 · Inventory
    CONTEXT
    Teacher source record with IDs, versions, learning purpose, product, criteria, audience, space, timing, access provisions, roles and contingency boundaries: [source record]
    Aggregate permission and safeguarding status, checked outside AI, with version and scope but no personal records: [permission status]
    REQUEST
    Inventory the supplied exhibition requirements and gaps before drafting operations.
    QUALITY BAR
    Use supplied facts only. Do not invent audiences, commitments, policies or access needs. No names, images, personal data or permission records. If permission status or any essential purpose, audience, space, timing or safety information is missing, return HOLD and questions only. Proposals are not confirmed facts.
    FORMAT
    For complete inputs use columns: field | supplied requirement | source ID/version | open question. Cover purpose, product/criteria, audience, space, timing, access, permissions, roles and contingency. For missing essentials use HOLD followed by a numbered question list.
  2. Compare workable sequences

    Check the inventory against your records. Supply corrections explicitly. Ask for two sequences within your confirmed window; students and partners will choose with you. Include movement, quiet participation and feedback time without assigning individual learners.

    Prompt 2 · Options
    CONTEXT
    Exact step 1 inventory approved by teacher: [approved inventory]
    Teacher decisions and corrections with version, including allowed timing and role choices: [decisions two]
    REQUEST
    Draft two run-of-show options and one evidence-based audience feedback tool.
    QUALITY BAR
    Stay within approved facts. Label options PROPOSED. Include transitions, access provisions, dignity-preserving roles and contingency. Roles must offer equivalent learning participation, without public ranking or forced personal disclosure. Feedback asks for observed evidence against supplied criteria and a revision question, never popularity votes. Show duration arithmetic for teacher checking; your arithmetic is not verification. Missing approval or essential inputs means HOLD and questions only.
    FORMAT
    Use headings Option A, Option B, Feedback tool, Teacher checks. For each option use columns: start | end | minutes | activity | role | access | source. State proposed total minutes. Give three feedback questions. List checks still requiring humans.
  3. Consolidate the human selection

    Review options with students and the confirmed partner. Independently recalculate durations, transitions and the finish time before choosing. Record safe aggregate decisions, edits and outstanding issues; never upload individual choices, consent forms or private access explanations.

    Prompt 3 · Consolidate
    CONTEXT
    Exact step 1 approved inventory retaining original facts: [approved inventory]
    Exact step 2 options and feedback tool: [options]
    Versioned teacher/student/partner selection, edits, independent teacher arithmetic check and aggregate permission recheck: [decisions three]
    REQUEST
    Assemble the selected exhibition operations plan, applying only recorded human decisions.
    QUALITY BAR
    No autonomous selection or approval. If selection, student/partner review, independent arithmetic check or permission recheck is missing, return HOLD and questions only. Distinguish supplied decisions from remaining proposals. Carry unresolved issues as HOLD. Preserve learning purpose, access, dignified roles, evidence-based feedback and contingency. Do not include names, images or private records.
    FORMAT
    Use headings Purpose and audience, Run-of-show, Access and roles, Permissions, Feedback tool, Contingency, Open holds. Preserve the selected schedule columns and total. Attach source ID/version to each section and record human checks as supplied reports, not AI verification.
  4. Audit the selected plan

    Compare the consolidated plan with your source records and make final edits. Ask for an audit, then personally check every issue before release. Stop and reduce scope if this bounded planning session exceeds 60 active minutes.

    Prompt 4 · Audit
    CONTEXT
    Exact step 3 plan selected by teacher: [selected plan]
    Original teacher sources and versioned decisions, including final teacher edits or explicit none: [final records]
    REQUEST
    Audit the selected plan for unsupported facts, omissions and conflicts. Do not rewrite it.
    QUALITY BAR
    Check purpose, audience, schedule arithmetic report, access, dignity, aggregate permissions, evidence-based feedback and contingency. Missing or stale support stays HOLD. No popularity rankings. Do not certify permissions, safety or arithmetic independently; report what the supplied human records establish. Never release the plan. No personal data.
    FORMAT
    Use columns: check | exact plan text | source ID/version | finding | human action. Cover all eight checks even when no discrepancy is found. Finish with Remaining holds and Human release required.

Check before you use it

  • Have you independently checked all durations, transitions and the finish time?
  • Have students and partners reviewed access, roles and the learning purpose without pressure to disclose personal details?
  • Are actual permissions checked outside AI, with only safe aggregate status supplied?
  • Does audience feedback cite learning evidence and invite revision rather than rank popularity?
  • Have you verified every audience commitment, space arrangement and contingency with the responsible humans?
  • Have you removed names, images and identifying records, resolved holds and personally authorised the final plan?

Stop rule

Stop if images/names lack consent, feedback is popularity-based or spectacle displaces evidence of learning.

3

Reuse it

So the next one takes minutes
Suitable

Build a skill

Save this as a reusable instruction you can run on any project.

The sequence can be reused with new source records and deliberate human checks.

Not suitable

Build an agent

Chain the steps, with a checkpoint where you approve.

Local permissions and event decisions need direct human coordination rather than autonomous monitoring.

Help us improve this method

Anonymous, and it takes under a minute.

Did you get something usable?
How useful was this method?
1 = wasted my time · 5 = I'll use it again
Where did it break down?

Please don't include names, school names or anything about individual students.

No account, no email, nothing stored about you.

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.