Salesforce Administrator Study Plan

Picture the evening you decide to go for the Admin certification. You open Trailhead, see several hundred hours of badges that could plausibly be relevant, and close the laptop. That moment — too much material, no sequence — is where most Salesforce Certified Platform Administrator attempts quietly die, weeks before anyone sits an exam.

The fix is not more resources; it is a calendar. Below is an eight-week schedule that turns the exam's official outline into a sequence of Trailhead modules and, crucially, hands-on builds in a free Trailhead Playground org. Eight weeks assumes roughly an hour on weekdays plus a longer weekend session and little prior Salesforce exposure; community discussion typically puts total preparation anywhere between about four and twelve weeks depending on experience, and there is no official figure — so treat this as a template to compress or stretch, not a promise. (For timelines across other Salesforce certs, see how long Salesforce certification preparation takes.)

Two boundaries before we start. This article is the schedule. The full breakdown of what each exam domain contains lives in Salesforce Administrator exam topics explained, and the craft of using mock exams — scoring thresholds, weak-domain analysis, when you are ready to book — belongs to the practice test strategy article. Registration mechanics, fees and format are in the Administrator certification guide; in brief, expect 60 scored questions in 105 minutes, US$200 plus applicable taxes, and a 68% pass mark on the current English exam per the official guide.

Before week one: set up your practice environment

Everything in this plan assumes you study by doing. Spend one evening on setup:

1. Create a Trailhead account and spin up a Trailhead Playground — a free practice org you can configure and break without consequences. Trailhead itself costs nothing; you never need to pay for study content to pass this exam.
2. Download the official exam guide from Salesforce Help and keep it open beside every study session. It is your syllabus; badges are just the teaching material.
3. Invent a pretend company. Give it a name, two sales teams, a support desk and some products. Every feature you learn, you will implement for this company. Configuring for a fake business forces the "why would I use this?" thinking that scenario questions test; clicking through a module's prescribed steps does not.
4. Block the calendar now — recurring weekday slot, longer weekend slot, exam date pencilled at the end of week eight. An unbooked exam is the easiest one to postpone forever.

The eight-week schedule

Week 1 — Platform orientation and org setup

Goal: stop feeling lost in Setup. Work through Trailhead's admin-beginner content on navigating Setup, company settings (fiscal year, business hours, currencies) and user management. In your Playground, create a handful of users for your pretend company, deactivate one, and explore what each setting changes.

Milestone: you can find any Setup page within a few clicks and explain what a profile is to a colleague.

Week 2 — The security model

Goal: internalise layered access. Study organisation-wide defaults, role hierarchy, sharing rules, profiles and permission sets. Then run drills in your org: make records private, watch a user lose visibility, restore it three different ways, and note how each mechanism differs.

This is the week that determines how the whole exam feels. Access control threads through scenario questions in every domain, so do not advance until you can predict — before clicking — what a given user will be able to see and edit.

Milestone: given any "user can't see X" complaint in your pretend company, you can name the responsible layer without opening Setup.

Week 3 — Data model and app building

Goal: build your company's custom app. Create custom objects, choose field types deliberately, and connect objects with both lookup and master-detail relationships so the differences (deletion behaviour, roll-up summaries) become concrete rather than memorised. Add record types, tune page layouts, and assemble a Lightning page in the App Builder.

Milestone: a working custom app with at least two related objects, built from requirements you wrote yourself.

Week 4 — Sales and service applications

Goal: run one record through each business process end to end. On the sales side: create a lead, convert it, and follow the resulting account, contact and opportunity through stages to close, adding products and a price book along the way. On the service side: configure a queue, an assignment rule and an auto-response rule, then submit a case and watch the machinery route it.

These two 10% domains reward exactly this kind of walkthrough, because the exam asks what happens next in a process far more often than it asks for definitions.

Milestone: you can narrate lead conversion and case routing from memory, including which records are created or updated at each step.

Week 5 — Data management, reports and dashboards

Goal: get comfortable with the exam's heaviest domain. Import a CSV of accounts into your Playground, deliberately include duplicates, and clean them up. Add a validation rule and try to break it. Then spend the back half of the week in analytics: build reports in each format, create a custom report type, and assemble a dashboard for your pretend company's sales manager.

Milestone: you can pick the right import/export tool for a described situation and explain why, and your dashboard answers a question your fake executives would actually ask.

Week 6 — Automation and Agentforce

Goal: cover Flow and the newest exam domain. Build three flows: a screen flow that gathers input, a record-triggered flow that updates a related record, and a scheduled flow. Add an approval process and note when it, rather than a flow, is the right tool. Then move to the Agentforce material — the current outline gives it 8%, and it is the section least covered by older study resources, so lean on up-to-date Trailhead content for agent concepts and building blocks. One sentence of context if AI credentials tempt you further: the Salesforce AI certification guide maps that separate path.

Milestone: three working flows in your org and a plain-English explanation of what an Agentforce agent is and what an administrator configures.

Week 7 — Consolidation and first full mock

Goal: convert coverage into readiness data. Early in the week, sweep the domains you have not touched in a fortnight — productivity and collaboration features (activities, Chatter, mobile configuration) fit naturally here as a lighter revision topic. Then sit your first full-length, timed mock exam and score it by domain, not just overall; ExamPractice's timed practice-test simulation supports exactly that kind of run, and its free sample questions are a lower-stakes warm-up if a full mock feels premature. How to interpret the scores and set a booking threshold is the practice-test strategy article's territory — the schedule's job is simply to reserve this week for it.

Milestone: a written list of your two weakest domains, with evidence.

Week 8 — Targeted repairs and exam week

Goal: fix the two weakest domains, not re-study everything. Return to the Playground and rebuild something in each weak area — repairs made with your hands stick better than re-read modules. Mid-week, take a second timed mock to confirm the gaps closed. Keep the final two days light: skim the official exam guide once more end to end, re-check the logistics for your onsite or online-proctored sitting, and stop studying the night before.

Milestone: exam sat. If it does not go your way, a retake costs US$100 (plus taxes) — regroup on the weak domains, do not restart the whole plan.

A daily rhythm that survives a full-time job

The schedule above fails if each session starts with "what should I do today?" Use a fixed shape:

• 10 minutes — recall first: write down, from memory, three things from yesterday's session before opening anything.
• 30–40 minutes — new material: one Trailhead module or unit, aligned to the current week's theme.
• 15–20 minutes — hands-on echo: implement what you just learned in your Playground for your pretend company, even trivially.
• Weekend session — the week's bigger build (the app, the flows, the dashboard) plus a review of anything flagged during the week.

The recall-first habit matters more than it looks. The exam happens without notes, and daily retrieval is the cheapest way to train for that.