Quiz Progress and Review Centre

Best score shows a level reached once, latest score today’s performance and attempts the amount of repetition. None proves learning alone; lesson practice and transfer to a new scenario are also required.

A due review is not a red alarm. It is a prompt to check retention through brief recall, missed questions and a small application.

Quiz history is kept in localStorage. It is not sent to a server, analytics service or another device. Clearing browser data removes the record and different devices do not share progress.

The JSON download is only for personal backup or review. It contains no name, email, school or contact information—only quiz identifiers, dates, scores and question statistics.

The progress centre does not rank all quizzes on one league table. Each quiz is interpreted within its module, question count and purpose. A score of 90 on a starter quiz is not the same knowledge level as 90 on an advanced module quiz. The centre mainly helps users compare their own attempts over time.

In Week 1, review the latest score and missed questions. In Week 2, complete a small application in the related lesson or project. In Week 3, explain the concept in a new context. In Week 4, use a due quiz or mixed review to check retention. This cycle is more meaningful than taking the same quiz repeatedly in a short period.

If the score rises while application quality falls, the learner may be memorising option patterns. Conversely, a stable score can accompany progress when reasoning becomes clearer, errors are found faster or a safer second version is produced. Numerical records should be read alongside qualitative learner work.

For a knowledge gap, revisit the lesson’s short answer and core concept. For rushed reading, rewrite the question stem. For an evidence error, compare expected and actual results. For a safety error, check risk, consent and reversibility. For a unit or condition error, list the given values separately.

When the same question is missed twice, rereading the explanation is not enough. Produce a new example that uses the correct principle, explain the assumption behind the wrong option and solve a similar but different question. Correct use in two contexts is stronger evidence than option memory.

When many questions become difficult, do not automatically reread the whole module. Look for a common pattern: source verification, units, safety, data interpretation or something else. Build a focused 20–30 minute review around that shared issue.

The centre does not measure intelligence, talent, school achievement, career suitability or psychological condition. Results are not an official examination, diagnosis, certificate or teacher assessment. The question pool is limited, and very frequent repetition can create option memory.

Different devices and browsers keep separate records. Private browsing or clearing browser data can remove history. The downloaded JSON is only a backup; the site does not import it. This design protects privacy by avoiding accounts and server tracking.

A deleted record cannot be reconstructed. Important learning evidence should also live in a project file, error journal or learner portfolio rather than only on this screen.

When a family member or teacher uses the progress centre, the conversation should not begin with “Why did you not score higher?”. Discuss where the learner felt uncertain, what changed after reading the explanation, which small application they want to attempt and whether the review date fits the school workload. Preserve the learner’s right not to share results and to clear local history.

When several quizzes become due, they do not all need to be taken on the same day. Prioritise safety-critical topics, modules related to a current project or lesson, and finally concepts not used for a long time. Two source quizzes or one mixed review are usually sufficient for one sitting; mental fatigue can reduce answer quality.

In a monthly review, list artefacts as well as scores: explanations, code, drawings, experiment tables, source comparisons, safety checks or project versions. A quiz result belongs in a portfolio only when it is accompanied by the date, learning goal and real application completed afterwards.

There is no automatic account synchronisation for moving progress to another device. The JSON download provides a human-readable backup, but the site does not import it for security reasons. When a record must be transferred, summarise the scores and goals in a learning journal.

When school examinations, sport, sleep or project workload conflict with a review date, the date can be postponed. This suggestion is not a compulsory schedule but a useful reminder. Record the new date and reason so the review is not forgotten while the learner’s need for rest and daily balance is protected.

When comparing quizzes, consider question count, difficulty and module scope. A score of 80 on a ten-question starter quiz does not measure the same detail as 80 on a twelve-question advanced module quiz. The healthiest comparison is between attempts on the same quiz and the real application completed between them.