Carry a CAS project from planning to completion
Use dependencies, shared reviews and practical evidence to deliver a collaborative project.

Turn the brief into a sequence
Once the coordinator has approved the direction, list the actions needed to produce the intended outcome. Identify dependencies: a design may need user feedback before printing, and an event may need a venue before invitations. Give each action an owner, a target date and a completion condition. Check the minimum month-long project requirement against your plan. Treat the duration as part of sustained collaboration, not as a reason to leave a finished task inactive until the calendar says enough time has passed.
Agree how the team will work
Choose a simple communication channel, meeting rhythm and place for current files. Make clear which version is ready for others to use. Record important decisions and unresolved issues briefly. Agree how to raise missed actions without blaming individuals. If availability changes, redistribute work openly and keep expectations realistic. Every collaborator needs enough understanding of the purpose to make sensible decisions within their role. Frequent activity does not guarantee coordination; a small team can still lose progress when responsibilities and dependencies are unclear.
Use a pilot to test assumptions
Before committing all resources, try a smaller version where possible. Test instructions with a few intended users, rehearse a section of the performance or inspect one part of an event process. Define what the pilot should reveal. Keep feedback specific enough to act on. A pilot is valuable if the team changes a decision in response to what it learned, even when it exposes a problem. Record both the observation and the revision rather than presenting the original plan as if it worked perfectly.
Follow a worked delivery adjustment
Imagine a team preparing a repair-awareness workshop with an existing community group. Their pilot shows that participants need more time to understand the demonstration. The team reduces the number of activities, creates clearer instructions and asks the partner to review the revised session. One student updates materials while another reorganizes the schedule. Their evidence includes the initial plan, feedback and changed version. This makes collaboration and problem solving visible. It also avoids claiming success merely because a workshop happened on the planned date.
Monitor outcomes and obligations
At review points, compare actual progress with the purpose and partners' needs. Check whether the team is still delivering what it agreed, whether anyone is carrying an unreasonable share and whether new ethical issues have arisen. Tell stakeholders about changes early. Keep evidence that is proportionate and respects privacy. If an event is cancelled, discuss an honest alternative with the coordinator; do not fabricate a completion story. A responsible response to a disruption can offer learning, but school guidance determines how your project requirements are completed.
Close the project deliberately
Confirm that the final product or activity has reached the intended people and that outstanding commitments are resolved. Request appropriate feedback, thank collaborators and hand over materials where agreed. Each student should reflect on their own role, significant decisions and learning. Keep enough evidence to make the account understandable, and discuss completion with the coordinator. Ask what could be continued or improved without promising future work you cannot sustain. A project ends well when it leaves clear outcomes, an honest evaluation and respectful relationships.
Your next-step checklist
Checklist choices stay in this browser.
Official references
This is an original practical guide from IBvia. The examples are illustrative; your subject guide, assessment year and school instructions determine the requirements.

