CompTIA A+ Study Plan for Beginners: A 12-Week Template

A useful A+ study plan pairs each exam topic with something you can explain, practise and document. This twelve-week template gives you a starting structure. Extend a phase when your results show you need more time; the calendar is not a deadline for passing.

If you are still deciding whether A+ fits your first role, read Best First IT Certification and A+ vs Network+ before committing to this plan.

Start with the correct exam objectives

CompTIA currently lists A+ V15: 220-1201 for Core 1 and 220-1202 for Core 2. Both exams must come from the same version. You can take them in either order, and each exam lasts 90 minutes. Check the official A+ specification and objectives again before buying materials or booking.

This example studies Core 1 first, then Core 2. That is a planning choice, not a provider requirement. Keep separate objective checklists for the two exams so you do not mistake progress in one for readiness in both.

Build a six-hour week you can sustain

• Two 75-minute sessions: learn one topic, then explain it without reading your notes.
• One 90-minute session: perform a related task on a device or test environment you control.
• One 60-minute session: answer fresh practice questions and explain the wrong choices.
• One 60-minute session: revisit weak objectives and update your mistake log.

That is six hours a week, or 72 planned hours across twelve weeks. It is an example study budget, not an estimate of the preparation every beginner needs. If six hours is unrealistic, stretch the schedule. If a topic is familiar, use a short explanation and practical check to decide whether you can move on.

The twelve-week planning template

Weeks	Focus and evidence to produce
1–2: establish Core 1 foundations	Download the objectives, take a baseline practice set and inventory a test device. Study mobile devices, hardware and networking fundamentals. Save an inventory sheet and a list of weak objectives.
3–4: use Core 1 concepts	Continue hardware and networking; cover the virtualization and cloud concepts in your objective checklist. Practise describing a connection problem and choosing a diagnostic step. Save one network diagram and one troubleshooting record.
5–6: review Core 1 as a whole	Revisit every Core 1 domain, including troubleshooting. Use fresh timed practice and explain unfamiliar scenarios. Review readiness before booking; repeat this phase if gaps remain.
7–8: establish Core 2 foundations	Study operating systems and security topics from the Core 2 checklist. Practise ordinary account, permissions and operating-system tasks in a test environment. Record expected versus actual access.
9–10: connect Core 2 topics	Cover software troubleshooting and operational procedures, alongside remaining objectives. Complete a restore exercise with sample files and write a clear support handoff. Save the procedure and verification evidence.
11–12: review Core 2 as a whole	Review every Core 2 domain, return to weak topics and try fresh timed practice. Decide whether to book, extend the plan or change your study method based on the evidence.

The topic groupings help organize your week; they do not replace the complete provider objectives. A device inventory alone does not cover all hardware knowledge, and one permissions exercise does not cover all security topics.

Use a mistake log that changes what you do

For each important error, record four things: the objective, the mistaken reasoning, the corrected explanation and a task or new question that checks the correction. Avoid turning the log into a collection of copied answer keys.

Illustrative entry: I treated a name-resolution failure as proof that the entire connection was down. Next time, I will separate adapter configuration, reachability and name resolution, and explain what each observation can and cannot establish.

At the end of the week, choose the two gaps that would most affect your next lab or practice session. If the same mistake keeps returning, change the explanation or exercise instead of repeating the same questions until the answers feel familiar.

Turn a lab into useful evidence

• State the task or symptom in one sentence.
• Record the environment without publishing personal identifiers or credentials.
• Write your hypothesis and the observation you used to check it.
• Record one change at a time and the reason for it.
• Verify the result and explain what you would check next if the issue remained.

A concise case note is more useful than a screenshot folder with no explanation. Work with sample data and an authorized test environment. For a lab, describe the scope honestly; it is practice, not production support experience.

Check readiness before buying or booking

• You have revisited every objective for the exam you intend to take.
• You can explain important concepts in your own words and apply them to unfamiliar scenarios.
• You can explain why plausible wrong answers are wrong.
• Fresh practice is reasonably consistent; you are not relying on memorized sets.
• You can work within the real exam’s time limit and understand the provider’s current testing requirements.

A practice percentage is not a guaranteed real-exam result. Use it to locate gaps, alongside explanations and practical work. If one domain remains weak, spend another week there rather than treating the twelfth week as an automatic booking date.

Keep the budget tied to your plan

Account for both exam attempts, preparation, possible retakes and renewal. Check voucher validity and subscription terms before paying. Use the comparison checklist and the cost discussion in A+ vs Network+ to record the current figures rather than relying on an old price.

What comes after the study cycle?

If you are ready for an exam, book according to the provider’s current requirements. If you need more practice, repeat a focused phase. In either case, improve your project notes and begin connecting your skills to suitable support roles using the beginner IT roadmap. A second credential can wait until you know which gap it will close.

Editorial planning example prepared October 11, 2026. A+ version details were checked against CompTIA’s linked specification. The schedule is adjustable and does not promise an exam pass or a job.