Total submissions
60+12 this week
Info@ninecode.vn
Report02
Exam analyticsTurn assessment data into
Turn assessment data into
decisions you can act on
From submission counts, score distribution, and time spent to correct, incorrect, and unanswered items, NineQuiz helps you find what needs attention instead of leaving you with a spreadsheet of grades.
Reports update as new attempts are submittedResults overviewAll submissions⌄
Average score
7.8+0.6 vs. last assessment
Min / Max
3.5 / 106.5-point range
Median time
36:124 minutes faster
Score distribution
N = 60 submissionsExcellent8 · 13%
Proficient26 · 43%
Developing18 · 30%
Needs support8 · 13%
Six questions for reading a report
Start with the decision you need to make
You do not need every metric at once. Choose the question that matches your goal: check participation, understand the cohort, find unfinished learning, review item quality, or support one person.
Did everyone submit?
Compare the submission count with the expected roster and remove practice, duplicate, or incomplete attempts before analyzing results.
→What is the overall performance level?
Read the average together with the minimum and maximum to understand the general level and the full score range.
→Where are scores concentrated?
Use the distribution to see where most candidates fall and whether the average is hiding a smaller group that needs support.
→Was the test length reasonable?
Compare typical completion time with the limit, then open outliers to separate confident work from rushing or unanswered items.
→Which content caused difficulty?
Sort by incorrect and unanswered rates, then check both the learning objective and the wording or key of each item.
→Who needs targeted support?
Open an individual attempt to review score, time, and the answer map, then assign practice for the exact topic that is missing.
→Question-level analysis
Find items that discriminate well—and items that need revision
Compare correct, incorrect, and unanswered responses, then open the item before deciding what the pattern means. A high incorrect rate may reflect difficult content, unclear wording, a bad key, or insufficient time.
CorrectIncorrectUnanswered
Item 01Foundational conceptStable
86% correct10% incorrect4% unanswered
Item 08Applied scenarioReview
42% correct53% incorrect5% unanswered
Item 14Data interpretationUseful spread
64% correct31% incorrect5% unanswered
How to interpret four common response patterns
A mastered prerequisite—or an item that is too easy
A high rate is positive for a required foundation. If the goal is selection, the item may not create enough separation between candidates.
Do not assume the learners are the problem
Check whether the content was taught, the difficulty is intended, the wording is clear, the key is correct, and the distractors are defensible.
Time or presentation may be the issue
If several items at the end are blank, the test may be too long. If one item stands out, check rendering, missing information, and instructions.
Potentially useful discrimination—after validation
An item answered correctly by some but not all candidates may separate levels. After exporting data, compare how higher- and lower-scoring groups responded.
A number becomes useful only when it has context
A report surfaces signals; it does not explain them automatically. Combine the testing conditions, exam design, and assessment goal with the six data groups below.
01Submission count
Use it to check participation
Compare it with the assigned roster to find missing attempts or unexpected submissions.
02Average score
Use it for a quick cohort view
It is helpful when comparing assessments with similar goals, difficulty, and scoring.
03Min / Max
Use it to see the score range
A wide range can point to a split cohort or a few attempts worth opening.
04Score distribution
Use it to find result clusters
See how many candidates are proficient, developing, or in need of support—often more actionable than one average.
05Time spent
Use it to review pacing and test length
Long times across the cohort may signal a heavy exam, complex interactions, or unclear directions. Very short times need to be compared with wrong and blank answers.
06Correct / incorrect / blank
Use it to examine content and item quality
Find topics not yet learned, overly easy items, skipped questions, or a time-pressure pattern near the end.
From 60 submissions to a reteaching plan
Imagine a class with 60 submissions, a 7.8 average, and a median completion time of 36 minutes 12 seconds. The report says more than “the class did well”; it separates the issues that need a response.
60submissions
7.8average score
8/60need support
53%incorrect on item 08
Score distribution
The average is hiding a smaller group that needs help
Thirty-four students are proficient or excellent, but eight still fall in the needs-support band. Looking only at 7.8 would miss them.
Item 08 · 53% incorrect
Validate the applied item before reteaching
More than half of the class missed it, but the report cannot tell whether the cause is the concept or the item itself.
Median time · 36:12
Overall timing looks workable, but outliers still matter
The median does not reveal very fast or very slow attempts, and those groups may have different needs.
Individual attempt · 8.5/10
A strong score can still contain a specific gap
A student with 26 of 30 correct may still miss every item from the same topic.
JL
Jordan Leejordan.lee@example.com
SubmittedScore8.5 / 10
Time31:08
Correct26 / 30
123456789101112131415161718192021222324252627282930
From the cohort to one submission
Open the right record when a number needs an explanation
Review score, time spent, and the answer map for one candidate. This helps distinguish a broad knowledge gap from one weak topic, rushed work, or unanswered items at the end.
↖ Results overviewOne report can support very different decisions
Use results according to the original goal. A classroom check should lead to reteaching; a placement assessment should guide grouping; a hiring test should remain one input in a broader evaluation.
K–12 and college01
A quick check after a unit
- Objective
- Find the concepts the class has not yet mastered.
- How to use it
- Sort the most-missed items, group them by standard or topic, and select two or three priorities for the next lesson.
- Example
- If three graph-reading items are each missed by more than 45%, reteach axis interpretation and give a short practice set instead of repeating the entire unit.
Placement02
Program or course placement
- Objective
- Place learners in an appropriate starting group.
- How to use it
- Combine score distribution with performance by topic. Two people with the same total score may have very different needs.
- Example
- Two language learners both score 70%, but one needs grammar support and the other needs reading practice, so they receive different bridge modules.
Workplace learning03
Track understanding of a required process
- Objective
- Identify retraining needs by team or role.
- How to use it
- Export results, attach the relevant department, and summarize accuracy by topic, prioritizing safety and compliance items.
- Example
- If many staff miss the customer-data scenario, rerun that module and follow it with a short knowledge check.
Hiring04
Add evidence to an early screening step
- Objective
- Check job-related knowledge or scenario judgment.
- How to use it
- Treat score, time, and answers as one input, then combine them with the application, interview, and work sample.
- Example
- A candidate with a high total score who misses every security item should be asked deeper questions in the interview—not automatically accepted or rejected from one number.
Question bank05
Improve the exam after every use
- Objective
- Keep useful items and revise those with unusual response patterns.
- How to use it
- Flag items that are extremely easy, difficult, or frequently blank, then review the wording, key, and candidate feedback before reuse.
- Example
- If 70% miss an item but several instructors also read it in two ways, revise the item instead of using the statistic to label learners as weak.
Conclusions the report cannot support on its own
Assessment data reflects performance under a particular set of conditions. It does not explain the cause, and it should not be the sole basis for a high-impact decision about a learner or applicant.
A low score does not automatically mean low ability
A device issue, unclear directions, time pressure, or an assessment that misses the intended skill can all affect the result.
A fast attempt is not automatically suspicious
A well-prepared candidate may finish early. Investigate only when the time is unusually short and other answer or proctoring evidence also needs review.
A high incorrect rate does not prove the content is difficult
Ambiguous wording, a bad key, missing information, or material that was not taught can create the same pattern.
Do not compare assessments that are not equivalent
To track growth, the tests should be similar in purpose, difficulty, length, scoring, and participant group.
Small samples need cautious interpretation
With few submissions, one or two results can move a percentage dramatically. Read the count as well as the rate.
Bring results into the rest of your workflow
Export data to summarize by class, department, or testing cycle; retain a record; track several administrations; or continue analysis in a familiar tool.
Excel
Filter, sort, and summarize submissions for internal analysis
Save a stable report for a program lead or case file
Print report
Prepare a paper copy for a meeting or required record
Understand the metrics in a NineQuiz report
Metrics update when a new attempt is submitted or a grade changes.
From data to action
Read results faster and improve the next assessment
Create an exam in NineQuiz and follow every submission, question, and score in one report.