What a readiness number actually is
A readiness estimate projects your practice performance to exam day: your accuracy on FRESH questions (never seen before), weighted by domain importance, adjusted for confidence calibration (confident-wrong counts extra) and pace. It is a forecast, not a grade. Forecasts have error bars.
Why fresh questions decide everything
Second attempts at the same question score dramatically higher from memory alone, one 2026 study of 9,000+ learner-question pairs found 73.5% first-attempt vs 90.5% on repeat. A 90% built on repeats predicts far less than 80% on fresh items. Honest readiness counts fresh performance heavily and says so, any number that doesn't distinguish is marketing.
How SecLern computes it
- Fresh-question accuracy per domain, weighted by exam weights (a miss in 28%-weighted Operations hurts more than one in 12%-weighted Concepts).
- Calibration adjustment: confident misses drag the estimate (misconceptions fail exams); unsure-correct answers schedule review instead of credit.
- Simulation agreement: full sittings under time confirm or veto the estimate. Daily-session numbers without simulation backing stay provisional. The dashboard says exactly this.
The booking rule
Book when TWO full fresh simulations, a week apart, both land in your comfort zone AND the domain breakdown shows no red topics. One great sitting is luck; repeats-based confidence is memory; two fresh passes with clean domains is readiness.
A worked example (the weights matter)
Suppose fresh-question accuracy of 85% in Operations (28%), 70% in Threats (22%), 90% elsewhere. Weighted: (.85×28 + .70×22 + .90×50)/100 = (23.8 + 15.4 + 45)/100 = 84.2%. Then calibration: two confident misses in Threats drag it ~3 points (misconceptions fail exams), landing near 81%, 'close, patch Threats, simulate again'. Same raw average without weights would have hidden the weak heavy domain entirely.
Red flags in your own breakdown
- A heavy domain under 70% (Operations, Threats): weeks of work, not days. Reschedule study order around it.
- Confident misses anywhere. Misconceptions fail exams disproportionately. Contrast-drill each one the same day.
- Slow correct answers on ports/subnetting: fluency gaps that cascade into scenario questions. Drill for speed, not just accuracy.
- Great daily sessions, weak simulations: the classic transfer gap. The fix is more full-length practice under time, not more daily questions.
What readiness cannot do
It cannot account for exam-day nerves, a bad night's sleep, or an unlucky form heavy in your weakest domain. Keep a margin: 'ready' means passing with room, not passing on a good day. And no vendor, us included, can guarantee a pass. The number informs your decision; it is not the decision.
How to raise the number honestly
Four levers move readiness, in order of impact. Fresh coverage of unseen objectives removes blind spots and usually lowers the number before it raises it. Review of confident misses fixes misconceptions, which are the most expensive kind of error. Full simulations under time close the transfer gap between daily practice and exam performance. Speed work on ports and subnetting buys back minutes that scenario questions need.
What does not move it: rereading notes, watching another video without questions, and repeating questions you have already seen. Those feel like studying because they are comfortable. The number is designed to notice the difference.
The four-week runway
Four weeks out, take one full simulation and write down the domain percentages. Three weeks out, spend the week on the two lowest domains and one lab a day. Two weeks out, take a second full simulation with fresh questions, then patch only what it exposes. One week out, review your mistake page, drill ports and formulas, and do one short mixed set a day. No new domains in the last week.
If the second simulation disagrees with the first, trust the lower one and move the exam if you can. A reschedule fee is cheaper than a retake and a month of lost momentum.
When to ignore the number
Ignore it for a day after a new domain is introduced, because fresh material always drags the average. Ignore it when you are sick or short on sleep, because the estimate assumes a normal session. Ignore it entirely if it is built on repeated questions. And ignore a high number that comes only from daily sessions with no full simulation behind it.
Do not ignore a low number because you feel ready. Feeling ready is often familiarity with the material, not retrieval under pressure. The simulation is the honest test.
What the dashboard counts, and what it does not
It counts answers, confidence marks, review outcomes, and full sittings. It does not count video hours, pages read, or notes highlighted. That is deliberate: those activities are inputs, not evidence. It also does not count questions you skipped or answers you changed after seeing the explanation. Changed answers are practice, not assessment.
One number, three questions
When the dashboard shows a single percentage, ask three questions before you trust it. How fresh is the evidence? How heavy is the weakest domain? What does a full sitting say? The number is a summary, and summaries hide the details that decide an exam. Open the domain breakdown every time you open the number.
A booking checklist
Two fresh simulations a week apart, both above the pass mark. No heavy domain below your comfort band. No confident miss left unexplained. A full sitting completed inside the time limit, not just at your own pace. ID ready, appointment confirmed, and a buffer day before the exam with no new material. If every line is true, book. If one line is false, fix that line first.
If the line you cannot tick is the simulation itself, the Security+ practice test comparison covers what each paid option is actually good for, and which of them include performance-based questions.