Tracking Your Progress
SecureCodingHub tracks your progress across all challenges and scenarios. See your XP, completion rates, and performance metrics in one place.
XP System
Every challenge and scenario awards XP (experience points) as you complete them:
| Activity | XP Awarded | Details |
|---|---|---|
| Practice Challenge | Up to 100 XP | 50 XP for Phase 1 (find the vulnerability) + 50 XP for Phase 2 (select the fix) |
| Learn Scenario | XP on completion | Awarded when you finish all steps of an interactive scenario |
XP accumulates across all topics and categories. Your total XP is visible on your profile and the organization leaderboard.
Practice Progress
For each topic, the platform tracks your completion and performance:
| Metric | Description |
|---|---|
| Challenges completed | Number of challenges completed vs total available for the topic |
| Average score | Your average score across all attempted challenges in the topic |
| Language used | The programming language you used for each challenge |
| Progress indicator | A visual bar showing your completion percentage at a glance |
Learn Progress
For each interactive scenario, the platform tracks where you are:
| Metric | Description |
|---|---|
| Current step | Which step you're on and how many steps remain in the scenario |
| Status | Not Started In Progress Completed |
| Resume | You can resume from your last step at any time — no need to start over |
Assignments Progress
If your admin assigned training to you, you'll see your assignments with additional tracking details:
| Field | Description |
|---|---|
| Assigned topics/scenarios | The specific training content your admin selected for you |
| Deadline | The due date for completing the assignment |
| Completion status | Your current progress toward finishing the assignment |
| Priority flag | Mandatory or Optional |
Data Persistence
Progress is saved to your account and syncs across devices. If you're using the platform without an account (demo mode), progress is stored locally in your browser.
What Progress Metrics Actually Predict
Completion percentage is the metric most teams look at first, and the one most likely to mislead. A learner who has marked every challenge complete with a fifty percent average score has not learned the material; they have moved through it. Completion alone tells you that activity happened, not that retention happened. The metric pairs that actually predict real-world skill are accuracy on first attempt and consistency over time. A learner finishing two Practice challenges per week with an average score above eighty percent over a quarter is internalizing the material. A learner finishing twenty in one week with a fifty percent average is not.
Spaced repetition is the missing variable. The vulnerabilities you saw three months ago in Practice Mode are the ones you forget first. Returning to the same topic after several weeks, even briefly, is where retention compounds. Encourage learners to revisit older topics rather than only progressing into new ones. The dashboard does not enforce that pattern but the data supports it.
Reading Progress as an Org Admin vs as a Learner
As a learner, the most useful reading of your progress is per-topic accuracy paired with which language you used. If your score in SQL injection is sixty percent in Python and ninety percent in TypeScript, that is a real signal about where to focus next. Total XP is fine for motivation but is not diagnostic on its own. Use the per-topic breakdown to find your weakest area and pair it with the matching Learn scenario before going back to Practice on the same topic.
As an Org Admin, progress dashboards are not individual performance reviews. The right read is at the team and category level: which categories does the team consistently struggle with, and which assignments are stalling near the deadline. A category with low average scores across the team is a training gap, not a person problem, and it tells you where to assign more Learn scenarios. An individual with low completion is more often a workload or onboarding issue than a skill issue. See Quick Start for assignment design tips that keep weekly load realistic.