Assessment and Completion
Assessments are not exams. They are the tasks and challenges you already do throughout Sprints 1–5. We check the evidence you produce along the way — you do not sit a separate test. You must complete all seven assessments to be eligible for Bootcamp.
Where you submit: the Assessment Tracker (AT)
Every assessment is submitted and tracked in one place: the Assessment Tracker (AT). You will use AT to submit links, files, or written work, and to see whether each assessment is marked Achieved, Not Yet Achieved, or awaiting review.
Inside AT, each assessment has its own page with a Requirements checklist, tips, and what to submit. Use that checklist to confirm you have covered everything before you submit — it is the definitive list for that assessment.
◎ Watch the AT walkthrough video in Sprint 1 before your first submission is due.
AT Walkthrough
Password reset link not working?
If clicking the reset link directly from the email doesn't work, copy the link address from the email and paste it into the same browser you started the password reset process from. Reach out to your facilitator if you need help.
Step-by-step submission instructions live on each task's own handbook page. See Submitting Your Work for deadlines and general submission rules.
The seven assessments
| Sprint | Assessment | AT code | What you submit |
|---|---|---|---|
| 1 | Git and Terminal | FND01 | Merged pull request on ko-wai-koe |
| 2 | Deploy a Static Website | FND02 | my-collection fork link, deployed page link, and a screenshot |
| 2 | HTML and CSS | FND03 | Links to index.html and main.css on GitHub, plus mobile/tablet/desktop screenshots |
| 2 and 5 | Learning Plan and Reflection, 2 parts | FND05 | Essay |
| 4 | Healthy Learning Habits | FND07 | Essay |
| 5 | JavaScript Programs | FND04 | Branch submission |
| 5 | Values, Empathy and Self Awareness | FND06 | Essay |
All seven are submitted through AT. Your facilitator may refer to an assessment by its AT code (e.g. "FND05") — use this table to match the code to the task.
What we are looking for
Completing a challenge does not mean having the correct answer, the perfect code, or the best explanation. It means your own, honest, best attempt using the processes we teach. We are interested in how you learn and problem-solve, not the "right" answer.
An attempt that does not fully work can still be a valid submission. Do your best to check that it is functional and meets the requirements. We also look at your engagement with the course and your skill development.
If you get stuck and cannot finish:
- Write a comment in your code or submission explaining where you got stuck
- Submit it as-is via AT
- Ask your cohort mates if anyone has solved it, and pair with them