Turn any certification exam's official objectives into a practical topic checklist — structure, granularity, columns and formats that keep prep on track.
Every reputable certification programme already publishes the raw material for your checklist: an official exam objectives document (sometimes called an exam guide, syllabus or content outline) that lists exactly what the exam can test. Building a topic checklist means converting that document into a row-by-row working tool you can tick, annotate and reorder. It takes about an hour, and it is one of the highest-leverage hours in your entire prep, because everything else — your schedule, your notes, your practice-test analysis — hangs off it.
This article covers the construction of the checklist itself: where to source topics, how granular to go, what columns to include, and which format to build it in. What you do with the checklist afterwards — recording evidence that a topic is genuinely learned — is its own discipline, covered in our guide to tracking the topics you have mastered.
Third-party course outlines, book chapters and video playlists all reorganise the syllabus to suit their teaching flow, and they routinely omit or compress items. The provider's own objectives document is the only source that defines the actual scope of the exam. For example, AWS publishes a formal exam guide for each certification — the AWS Certified Cloud Practitioner (CLF-C02) guide even specifies scoring mechanics such as compensatory scoring, meaning you pass on your overall result rather than needing to pass every domain. CompTIA, Microsoft and ISACA publish equivalent outlines for their exams.
Download the PDF (or save the web page) for the exact exam code you have booked or plan to book. Exam versions change on refresh cycles — CompTIA A+ moved to codes 220-1201 and 220-1202 in 2025, superseding the 1101/1102 series — so a checklist built from an outdated objectives list will send you off scope. Check the code on the provider's site before you build anything.
Most objectives documents follow a hierarchy: domains (with percentage weightings), then numbered objectives, then bulleted sub-topics. Copy all three levels into your checklist tool. Do not summarise at this stage — a checklist that silently drops bullets is worse than no checklist, because it manufactures false confidence in your coverage.
The single most common mistake is making rows too coarse. "Domain 2: Security" as one row tells you nothing when you tick it. A good rule: one row per testable idea — usually the bullet level of the objectives document, occasionally split further when one bullet packs in several distinct items (a list of protocols or tools, for instance, may deserve a row each if the exam expects you to distinguish them). For a typical certification exam you should end up with somewhere between 60 and 250 rows. If you have 15, you went too coarse; if you have 900, you have transcribed a textbook index, not built a checklist.
Add a column recording each domain's exam weighting from the objectives document. This matters later: when time gets tight, weighting is how you triage. (Deciding what to cut when the calendar is against you is a different problem — see how to study for exams with limited time.)
A checklist earns its keep through the columns beside the topic names. A practical minimum set:
Keep the status column honest by defining each value in writing at the top of the sheet. What actually qualifies a row for "Confident" — and how to test that claim rather than feel it — is the subject of the mastery-tracking article linked above; the checklist's job is only to give that judgement somewhere to live.
Whatever you choose, the test is behavioural: will you open it every study session? A beautiful checklist you check weekly is a worse tool than a plain one you check daily.
Once the skeleton exists, run a quick validation pass. Work through a set of practice questions for your exam and check that every question maps to a row on your list. Questions are written to test the published objectives, so an unmappable question usually means you dropped or over-compressed a bullet during transcription. ExamPractice's free sample questions are a convenient way to run this check before you have committed to a full study plan, and the certification exam directory covers exam pages across a wide range of providers if you are still confirming which exam code applies to you.
Suppose an objectives bullet reads: "Compare and contrast common backup types and recovery concepts." A coarse checklist gives that one row. A useful checklist gives it perhaps four: backup types (full/incremental/differential), backup media and rotation, recovery point vs recovery time concepts, and restore testing. Each row is now small enough that ticking it means something, and small enough to schedule into a single study session — which is exactly what you will want when you later build a personalised exam preparation schedule around the list.
An hour of honest transcription gives you a complete, weighted, provider-accurate map of your exam. From that point on, your prep questions become answerable: What have I not seen yet? Sort by status. What is worth the next session? Sort by weighting and staleness. Am I ready to book? Look at how many rows sit below "Practised". The checklist does not study for you — but it makes sure that when you do study, you are always working on scope, on purpose.
Build two. CompTIA A+ requires passing both Core 1 (220-1201) and Core 2 (220-1202), each with its own objectives document, passing score and booking. A merged list blurs which exam you are actually ready for.
Roughly 45–90 minutes for a typical certification, depending on how long the objectives document is. If it is taking a whole day, you are writing notes into it rather than transcribing structure.
Yes. Weightings cost one column and become essential the moment your timeline compresses or a practice test exposes a weak domain — decisions you cannot make well without them.
Some providers publish leaner outlines than others. Keep the rows at whatever level the document supports, then use practice questions to discover the implicit sub-topics and add rows as you meet them. The checklist is allowed to grow.
Exam facts in this guide were checked against official certification-provider pages on . Fees, exam codes and policies change — confirm on the provider’s own site before you book.
Put it into practice
Reading about an exam only takes you so far. Work through practice questions for your certification and find the gaps before exam day does.
·7 min read
Timing, score benchmarks and review technique for CompTIA practice tests — how to turn A+, Network+ and Security+ practice scores into a genuine pass signal.
Continue reading·8 min read
How to use CISA practice tests properly — when to take them, how to benchmark scores across the five domains, and how to turn wrong answers into study priorities.
Continue reading·8 min read
A practical buyer's checklist for choosing a reliable certification practice test: objective alignment, explanations, simulation features and red flags.
Continue reading
