A score history is more informative when you record what happened during each session. A short practice log can connect results to specific skills and conditions instead of leaving you with a list of numbers to overinterpret.

Record a few useful fields

FieldExample entry
FormatFresh numerical practice set
ConditionsTimed; no interruption
Result7 of 10 correct
Main errorUsed the final amount as the percentage-change base
Next actionSolve three fresh reverse-percentage examples

The example is a fictional practice entry, not a starp user result. Your own log can be brief; specificity matters more than length.

Compare similar sessions

Note whether questions were new, repeated or closely related to examples you recently studied. Record changes in time limits or assistance. A score increase across different conditions may be interesting, but it does not isolate a single cause.

Avoid choosing only your best session as the baseline. A complete record makes ordinary variation easier to see.

Track understanding as well as totals

Can you explain the rule without the solution open? Can you solve a changed version? Can you identify why a tempting alternative fails? These questions reveal more about your practice than speed on an item whose answer you remember.

Set one next action after each review. Trying to fix every possible weakness at once can make the plan too vague to follow.

Keep your practice notes in context

Keep a short record of the exercises you try, the mistakes you review and the conditions in which you practice. You can download a purchased starp report and use it alongside your own notes about strategies and conditions.

The score mapping is shared, but generated forms and practice exposure still matter when comparing sessions. A trend is a record of performance under those conditions, not automatic proof of a broad change in intelligence. Keep the learning goal concrete: more accurate explanations, fewer repeated mistakes and better use of the information supplied.