CSCS Mock Tests: How Many to Do and When (2026)

Most CSCS test failures aren't from lack of effort - they're from people doing mock tests too early or too often. A mock test taken before you know the material is just a quiz that tells you what you already knew: you don't know it yet. This guide explains the right order: topic practice first, then mock tests, then targeted revision on the topics that still score below 90%.

The CSCS Health, Safety and Environment Test is 50 questions in 45 minutes, pass mark 47/50. That's three errors maximum. The questions are drawn from a public bank covering general responsibilities, accident reporting, health hazards, working at height, electrical safety, hand-arm vibration, COSHH, manual handling, and PPE.

When to start mocks (not on day one)

The biggest mistake new candidates make: download a mock test app, run it immediately, score 28/50, panic, run another mock the same day, score 31/50, panic harder. By session three the mocks are no longer testing - they're just exposing the same gaps repeatedly. The candidate memorises answers without understanding why those answers are correct.

Right order:

Phase 1 (week 1) - Topic study, no mocks. Read the official CITB book or app content one topic at a time. Take notes by hand on the bits that surprise you. Don't quiz yourself yet. Goal: get familiar with the vocabulary (RIDDOR, HAVS, exposure action value, prohibition notice) so questions don't feel foreign.

Phase 2 (week 2) - Topic-specific quizzes. Quiz one topic at a time, 20 questions, then review every wrong answer. Goal: 90%+ per topic before moving to the next. If a topic stays below 90%, return to phase 1 reading for that section.

Phase 3 (week 3) - First mock test. Only now. Full 50 questions, 45 minutes, timed, no breaks, no checking answers mid-test. Most candidates score 42-45 on the first mock. That's fine. The mock isn't a test - it's a diagnostic.

Phase 4 (week 4) - Targeted mocks. Two mock tests per day for 5-7 days. After each mock, drill the wrong-answer topics for 15 minutes. The score should climb from 44 to 48 to 49. When you hit 49+ twice in a row, you're ready.

What to do when stuck below 47

Some candidates plateau at 44-46. They keep doing mocks, keep getting similar scores, and feel stuck. The pattern is almost always the same: two or three weak topics are dragging the score down, but mock tests randomly sample all topics, so the candidate doesn't see which ones are the problem.

Diagnosis step. Take three consecutive mocks. Write down every wrong answer. Group them by topic. You'll usually find 70% of the wrong answers come from 2-3 topics - typically COSHH, exposure action values, or working at height regulations. Those are the topics to drill, not generic mocks.

Drill strategy. For each weak topic: read the official source material again, slowly. Make flashcards for the specific numbers (e.g. HAVS exposure action value 2.5 m/s squared, exposure limit value 5 m/s squared; lone working 30-minute check intervals; scaffolding inspection every 7 days; LOLER lifting equipment inspection every 6 months). The CSCS test loves specific numbers, and most failures are from confusing two numbers.

The CSCS Quiz app's filter. The app lets you filter the question bank by topic. After identifying weak topics from your wrong-answer log, you can drill that specific topic 50 questions in a row - far more effective than another generic mock.

Quick comparison

Common pitfalls and how to avoid them

Across every domain this article touches, the same shape of mistake recurs. Practitioners new to the field overweight the most visible piece of the system — the screenshot, the paywall, the exam question, the headline price — and underweight the underlying constraint that actually determines outcomes.

The five most common failure modes:

1. Optimising for the demo, not the durability. A working demo in a controlled environment proves nothing about reliability under real conditions. In iOS development, an in-app purchase flow that works in the Xcode Simulator says nothing about how it behaves in App Store sandbox with network latency and Ask to Buy approvals. In an exam, a 100% score on an untimed quiz tells you nothing about whether you can do 49/50 in 45 minutes with no second guesses. Build for the hardest realistic case from the start.
2. Skipping the first-principles documentation. Every system has a canonical specification. App Review Guidelines for iOS, the official EU regulations for tax deductibility, the CITB question bank for CSCS, the OMIE market rules for Spanish electricity. Reading them takes a few hours but saves weeks of wrong-direction work. Secondary sources (blogs, tutorials, this article included) are useful as orientation but never authoritative.
3. Ignoring the rate limit. Every external system has rate limits — explicit (APNs silent push throttling, RevenueCat API quotas, exam retake fees) or implicit (App Review patience, customer attention spans, your own working memory). Plan around them. A workflow that requires more rate-limited operations than the system allows will fail in production, not on day one but during the first stress event.
4. Underweighting localisation and regional variation. What is true for Germany is not always true for Italy. What is true for English-speaking users is not always true for Japanese ones. What is true for the UK CSCS test is not always true for the Irish equivalent. Always check the local rule before applying a general one.
5. Treating the documentation as static. Apple updates App Review Guidelines. The Bundeslaender change Schonzeiten. OMIE adjusts market clearing algorithms. Set up a periodic review (quarterly is enough for most things) and re-read the canonical sources. Workflows that worked perfectly a year ago can be silently broken today.

None of these are dramatic. The dramatic mistakes (catastrophic bugs, audit findings, exam failures) are the visible tip of a longer-running iceberg of small misses. Catching the small misses is what separates routine outcomes from problematic ones.

Key takeaways

• Phase 1 — Topic reading. No quizzes yet.
• Phase 2 — Topic quizzes. 90% per topic before next.
• Phase 3 — First mock. Diagnostic only.
• Phase 4 — Targeted mocks. Drill weak topics after each.

The pattern that runs through every section above: start with the constraint, not the wishlist. In an exam, the constraint is the question bank and the pass mark. In an electricity market, it is the auction clearing rule. In a tax workflow, it is the receipt-retention requirement. In a code architecture, it is the platform's design decision (StoreKit's transaction lifecycle, App Review's guideline, APNs's authentication model). Get the constraint right and the rest follows.

The opposite failure mode — designing for an aesthetic ideal, then trying to retro-fit the constraint — is the most common cause of wasted work in every domain covered here. A beautiful paywall that hangs in sandbox is rejected at App Review. A polished freelancer expense report that lacks receipts is disallowed by the tax office. A study plan that ignores the actual question distribution leaves the candidate stuck below the pass mark.

The practical recommendation: read the official rules of whatever system you are operating in, extract the binding constraints, and treat them as inputs to the design — not afterthoughts. Every section of this article is the application of that principle to a specific domain.

FAQ

How many mock tests should I do before the real exam?
Around 10-15 full mocks. More than that and you're memorising answers rather than understanding concepts. Quality (mocks followed by targeted drill on weak topics) beats quantity.

What score on mocks means I'm ready?
49/50 or 50/50 on two consecutive mocks, both timed and without checking answers mid-test. A single 50/50 on an untimed mock means nothing.

Should I take mocks on the app or on paper?
App. The real CSCS test is delivered on a touchscreen at a Pearson Vue centre. Practice on a touchscreen so the interface is familiar on test day.

Can I retake the CSCS test if I fail?
Yes, immediately. There's no waiting period. But each retake costs around 22.50 GBP (2026 fee), so most candidates wait a week to drill weak topics before retrying.

Further reading and references

The references below cover the official sources for the rules cited in this article. Where applicable, they include the canonical documentation, regulatory text, or vendor-provided guides. For each one, prefer the official source over secondary commentary — secondary sources go stale fast and frequently misquote the binding rule.

• Official documentation of the system in question (linked from each app or service's own help centre).
• Apple Developer Documentation for any iOS/macOS reference — the WWDC session videos and the corresponding Human Interface Guidelines pages are the authoritative source.
• For EU regulatory questions (taxation, data protection, energy market structure), consult the relevant national authority — most publish their guidance in English.
• For Spain and Italy energy market data, OMIE and GME both publish full historical price series in CSV format from their public websites — no API key required.
• For UK CSCS prep, the CITB publishes the official question bank book each year — buy a current copy if you want the authoritative source.

If you find a contradiction between this article and an official source, the official source wins. Article rules of thumb are summaries — they have edge cases, exceptions, and regional variations that the source documents specify exactly.