CompTIA A+ Study Plan: Week-by-Week Schedule (2026)

Quick Answer

A realistic CompTIA A+ study plan runs eight to twelve weeks at ten to twelve hours per week, split into two halves: roughly five weeks for Core 1, sit that exam, then roughly five weeks for Core 2. Study the heaviest domains first within each Core exam, run domain-restricted practice questions as you go, and book each exam once timed full-length practice is consistently in the mid-eighties.

Total Duration

8-12 Weeks

Weekly Hours

10-12

Structure

Core 1 then Core 2

Booking Trigger

Mid-80s timed

The Shape of the Plan

Treat A+ as two sequential projects rather than one long one. Study Core 1, sit it, then study Core 2 and sit that. Running both in parallel is the most common structural mistake — it doubles the material you are holding at once and delays your first pass, which is the thing that sustains motivation.

Within each Core exam, the sequence is the same: cover the heaviest domains first, run domain-restricted practice after each domain, then finish with mixed timed practice and book once your scores stabilize.

The default timeline assumes ten to twelve hours per week, which typically means around two hours on four weekdays and a longer weekend session. That produces roughly five weeks per Core exam plus a short buffer, landing in the eight to twelve week range overall.

Adjust honestly rather than optimistically. Someone with hands-on hardware experience may cover Core 1 in three weeks. Someone entirely new to IT should plan for six or seven per exam and should not treat that as failure — the timeline is not the achievement.

The non-negotiable parts are the sequencing and the booking trigger. Everything else flexes.

Core 1: A Five-Week Block

Week 1 — Hardware, part one. The heaviest domain, started while motivation is highest. Cables and connectors, RAM types, storage devices and RAID, motherboards and expansion cards. Begin the ports-and-protocols flashcard deck now and run it daily for the rest of your preparation.

Week 2 — Hardware, part two, and networking. CPUs and cooling, power supplies, printers and consumables. Then networking: ports and protocols, networking hardware, wireless standards, addressing basics. Run domain-restricted practice on hardware at the end of the week.

Week 3 — Mobile devices and virtualization and cloud. The two lightest Core 1 domains, deliberately placed mid-plan as a lighter week. Laptop hardware replacement, display components, mobile connectivity and synchronization; then cloud models, shared resources, and client-side virtualization requirements. Practice both domains.

Week 4 — Troubleshooting. The domain that decides the exam. Work the methodology explicitly, then symptom-based scenarios across hardware, display, storage, network, and printers. This week should be mostly practice questions rather than reading, and every miss gets attributed to an objective bullet.

Week 5 — Mixed timed practice and repair. Full-length timed sets, review every question including correct ones, and target the specific bullets from your miss table. Book the exam when two consecutive timed full-length sets land in the mid-eighties with no domain badly trailing.

Core 2: A Five-Week Block

Start Core 2 within a week or two of passing Core 1. The gap is where momentum dies.

Week 1 — Operating systems, part one. The heaviest Core 2 domain. Windows editions and features, Control Panel and Settings utilities, system utilities including task manager, disk management and event viewer. Start the command-line flashcard deck.

Week 2 — Operating systems, part two. Command-line tools and switches in depth, OS installation and upgrade methods, partitioning and file systems, workstation network configuration, and working knowledge of macOS, Linux, and mobile operating systems. Domain practice at week's end.

Week 3 — Security. Physical and logical controls, wireless security, malware types and the removal steps in order, social engineering, workstation security settings, mobile device security, and data destruction methods. Card the malware removal sequence — order questions are reliable points.

Week 4 — Software troubleshooting and operational procedures. Troubleshooting Windows, application, mobile, and security symptoms. Then operational procedures as a fast block: documentation, change management, backups, safety, environmental controls, privacy handling, communication, scripting basics, and remote access. It is dense reading with low difficulty and it is worth doing properly.

Week 5 — Mixed timed practice and repair. Same as Core 1: full-length timed sets, attribution, targeted repair, and book on the same mid-eighties trigger.

The Weekly Rhythm That Makes It Work

Within each week, the distribution matters as much as the total hours.

Four weekday sessions of roughly ninety minutes to two hours. New content in the first hour, practice questions on that content in the remainder. Ending each session with questions on what you just read is what converts reading into retention.

One longer weekend session. Domain-restricted practice across everything covered that week, plus review of the miss table. This is also where hands-on or simulator time fits best, since it needs unbroken time.

Ten to fifteen minutes of flashcards daily, including on days you do not study. This is the cheapest retention insurance available and it keeps early material alive while you move through later domains.

One rest day. Deliberately. Study schedules without rest days get abandoned in week three.

Two habits sustain the whole plan. First, keep a single miss table mapping wrong answers to objective bullets, and let it drive what you re-study rather than studying by feel. Second, protect a short weekly review of the previous week's domain — twenty minutes is enough — because the biggest risk on an eight-to-twelve week timeline is that week one has evaporated by week five.

Step-by-Step Guide

1. Download the current objectives for both Core exams

   Build your plan against the actual blueprint. Convert every sub-bullet into a checklist you can mark off as you go.

   Print the domain summary page and keep it visible. It is your progress bar.

2. Block the time in your calendar before week one

   Four weekday sessions, one weekend session, one rest day. Time that is not scheduled does not happen once work gets busy.

   Schedule the sessions at the same times each week so they become routine rather than decisions.

3. Work Core 1 in weight order and practise as you go

   Hardware first, then networking, then the lighter domains, then troubleshooting. Domain-restricted questions after each domain.

   Start the ports-and-protocols deck in week one — it needs the most repetitions.

4. Book Core 1 on the practice trigger, not the calendar

   Two consecutive timed full-length sets in the mid-eighties with no domain badly trailing. Book then, and sit within about two weeks.

   Booking creates a deadline that stops indefinite studying, which is the most common way A+ preparation stalls.

5. Start Core 2 immediately and repeat the cycle

   Within a week or two of passing Core 1. Same structure: heaviest domains first, practice as you go, same booking trigger.

   Keep a short weekly Core 1 review going only if a long gap is unavoidable — otherwise momentum handles it.

Expert Insight

The plan detail that changes outcomes most is the booking trigger. Candidates who book on a date study to the date; candidates who book on a practice-score threshold study to readiness and then create a short deadline for themselves. The second group passes at a noticeably higher rate, and they usually finish sooner — because open-ended study expands to fill whatever time it is given.

Study Tips

• Study one Core exam at a time. Running both in parallel doubles what you are holding and delays your first pass.

• Book each exam on a practice-score trigger rather than a date, then sit it within about two weeks.

• End every study session with questions on what you just read. That is what converts reading into recall.

• Keep one miss table mapping wrong answers to objective bullets, and let it decide what you re-study.

• Take a rest day every week. Schedules without one get abandoned around week three.

Common Mistakes

• Studying Core 1 and Core 2 simultaneously, which delays the first pass and doubles retention load.

• Leaving a long gap after passing Core 1, then having to re-study material and losing momentum.

• Reading through material without practice questions until the final week, when gaps can no longer be fixed.

• Spending equal time on all domains regardless of weighting, so troubleshooting never gets enough depth.

• Setting an exam date first and hoping preparation catches up, rather than booking on a readiness signal.

Frequently Asked Questions

Ready to Start Your Certification Journey?

Practice with real exam-style questions and track your progress.