Project-based learning & education workflows
Project-based learning that a teacher can actually sustain
Teacher-defined project goals, student collaboration, process evidence, reflection and portfolio — with assessment led by the teacher.
Operating context
The pedagogy is accepted; the workload is the obstacle
Project-based learning is widely agreed to be valuable. The reason it stops is that designing the project, organising the process, collecting the material and assessing the outcome is a large amount of teacher work.
Student work is produced across lessons, devices and group members, and then has to be reassembled by the teacher before it can be assessed or shown.
Schools want visible innovation outcomes but often have no systematic way to keep the process evidence that makes those outcomes credible.
The goal is not to remove the teacher from the loop. It is to make the loop repeatable.
Objects the work is attached to
- Course, class and project
- Project goal defined by the teacher
- Student group and member contribution
- Process artefact and milestone
- Reflection entry
- Portfolio and school teaching asset
People involved
- Teacher / project designer
- Student and student group
- Curriculum or teaching-research lead
- School information lead
Common operational problems
Where project-based learning stalls
Design cost falls on individual teachers
Each teacher rebuilds project structure, milestones and assessment criteria from scratch.
Process material is scattered
Group work is spread across devices and chats, so process evidence is lost and only the final artefact survives.
Outcomes are hard to show
Schools cannot easily present what students actually did, only what they produced at the end.
Assessment has no evidence trail
Process-based assessment requires process records. Without them, assessment defaults to the final product.
Proposed workflow
Design, run, evidence, reflect, assess
The chain applied to a classroom rather than a work site.
- 01Task
- 02Capture
- 03Verify
- 04Approve
- 05Sign
- 06Report
- 07Deliver
- 08Follow Through
- Task — the teacher defines the project goal, milestones and expectations.
- Capture — student groups record work, artefacts, contributions and reflection as the project runs.
- Verify — missing milestones, uneven contribution and incomplete submissions are surfaced to the teacher.
- Approve — the teacher reviews progress and gives formative feedback.
- Sign — the teacher confirms the milestone or the completed project.
- Report — a project record and portfolio view is assembled from the process evidence.
- Deliver — the project becomes a school teaching asset and a student portfolio item.
- Follow Through — the project structure is reused and improved for the next cohort.
What the system can capture
Field evidence, structured at the point of work
- Teacher-defined project goals and milestones
- Group formation and member contribution
- Work artefacts, drafts and iterations
- Inquiry notes and sources
- Reflection entries by student and by group
- Milestone completion and teacher feedback
- Final artefact and presentation material
- Portfolio view per student and per project
Capture is designed to support the engineer, not to police them: it should be faster than writing the same information twice.
Review and approval roles
Who decides what
Student group
Produces work and records process evidence and reflection.
Teacher
Defines goals, gives feedback, and leads all assessment.
Curriculum lead
Reuses project structures and reviews school-level outcomes.
Decision boundary. Assessment is teacher-led. AI is used to help design projects, organise material, draft structure and surface what is missing. It does not grade students, does not evaluate teachers, and does not make high-impact decisions about a learner.
Reports and follow-through
Process evidence, portfolio and reusable structure
The output is not a score. It is a record of how the project ran, which the teacher then assesses.
- Project record with process evidence
- Student and group portfolio view
- Milestone and contribution overview
- Reusable project template for the next cohort
What happens next
- Successful project structures are reused
- Portfolios accumulate across a student’s time at the school
- School-level teaching assets build up year on year
- Teaching-research leads can compare project designs
Evidence status
What is proven and what is not
Project-based learning platform — Delivered — internal record
Built with a working demonstration covering project design, mind mapping, deeper inquiry, a project showcase and assessment support. Named schools, screenshots and learning-outcome claims are not published.
Teacher work-record and developmental review platform — Delivered — internal record
Schools configure their own end-of-term reporting and review requirements; teachers complete it in steps and management reviews it. This is a school-defined, human-reviewed process — not AI evaluation of teachers.
European school deployment, local hosting and portfolio variants — Concept — validation required
School-local deployment, EU hosting, privacy design and portfolio variants are directions we can design for, subject to project validation.
Limitations
What this workflow does not do
- AI does not assess students and does not evaluate teachers.
- We publish no claims about learning gains or school deployment numbers.
- This is a secondary industry direction for JJ AI TECH, not our primary focus.
- We do not offer AI training courses.
- Data protection arrangements for student data are agreed per school and per jurisdiction; we make no certification claims.
One class, one project, one term
The useful test is a single project with a single teacher, where the process evidence is good enough for that teacher to assess from.