FRM Part I Study Plan
Build an FRM Part I plan from the 2026 Learning Objectives, a timed four-domain diagnostic, formula practice, and weekly mixed sets.
- GARP’s 240-hour average comes from a 2015 survey, so use your own gaps and calendar to set the schedule.
On this page9 sections
- Start with a baseline
- Organize a weekly cycle
- A sample 16-week structure
- Use checkpoint results to adjust
- Phase one: build the conceptual map
- Phase two: practice by objective and repair errors
- Phase three: mix topics and practice pacing
- Phase four: consolidate without cramming
- Adapt the plan when it falls behind
Start with a baseline
Before choosing a calendar, take a short diagnostic that samples Foundations, Quantitative Analysis, Financial Markets and Products, and Valuation and Risk Models. Time it, but do not treat the score as a pass prediction.
For each miss, label the cause: unfamiliar reading, formula recall, wrong method, arithmetic, interpretation, or time. This turns a score into a study task. If the question was correct only by guessing, mark it as uncertain.
Compare errors with the 2026 Learning Objectives and turn them into a checklist. Mark each objective unseen, learning, practiced, or retrievable under mixed conditions. Use current readings and approximate weightings to give weak topics and important tasks appropriate attention; watching a video is not evidence that you can solve a new problem.
Choose a confirmed administration, then count backward and estimate the weekly hours you can protect around work, family, travel, and rest. Leave slack for missed sessions and difficult topics. Include reading, problem solving, mixed retrieval, and review. GARP’s survey average of about 240 hours is historical context, not a required total.
Organize a weekly cycle
Assign new material to focused sessions. Read a section, then close it and explain the core concepts from memory. Solve problems before looking at worked solutions, and write down the assumptions each answer uses.
Add formula retrieval on separate days. For each formula, state variables, units, conditions, and what the result means. Rework a new numerical example so the process is not tied to one answer.
Use mixed questions at the end of each week. Mix conceptual and quantitative topics so you must identify the right tool. Review correct but uncertain responses alongside mistakes.
Every week, update an error log and choose one or two priorities for the next cycle. Avoid trying to fix every topic at once.
A sample 16-week structure
Weeks 1 and 2: diagnostic and Foundations of Risk Management. Focus on governance, risk appetite, organizational roles, and event analysis. End with short mixed sets.
Weeks 3 through 6: Quantitative Analysis. Divide time among probability, estimation, regression, time series, and simulation according to the 2026 Learning Objectives. Practice calculations and interpretation together.
Weeks 7 through 10: Financial Markets and Products. Work through instruments and contract mechanics. Compare forwards, futures, options, bonds, and other products, then apply the concepts in risk examples.
Weeks 11 through 14: Valuation and Risk Models. Practice valuation, risk measures, and model assumptions. Include VaR, tail-risk limitations, stress tests, and credit concepts assigned for 2026.
Weeks 15 and 16: timed mixed practice, formula review, error correction, and test logistics. This calendar is illustrative; adjust it for your background and available study hours.
Use checkpoint results to adjust
At each checkpoint, review the time spent and the nature of errors. If you understand a formula but are slow, practice setup and calculator use. If you do not know when it applies, return to the underlying concept.
After a full practice exam, review uncertain correct answers. A guessed answer can mask a gap. Keep a list of formulas you could not retrieve without notes.
Check the official appointment confirmation and calculator policy before exam day. Registration, scheduling, and exam readiness are separate tasks.
Keep rest in the schedule. A plan that permits recovery is more reliable than one that assumes every evening can be used for study.
Phase one: build the conceptual map
In the first phase, move through each domain once and identify how the concepts connect. For a product, note its cash flows and market risk factors. For a quantitative method, record the inputs, output, and conditions. For a risk measure, note the horizon and interpretation. This map prevents a formula list from becoming detached symbols.
Keep first-pass notes concise. Capture the idea that changes how you solve a question, not every sentence in a reading. For example, write that historical simulation applies observed risk-factor changes to current positions, then note that the method depends on the selected data window. Add a practice problem that forces you to explain the implication of a different window.
Do not wait until the entire syllabus is finished to solve problems. After a small concept group, close the material and retrieve the relationship. Then solve a fresh example. If you cannot set it up, reopen the source and locate the missing step. This early loop prevents passive familiarity from masquerading as mastery.
Phase two: practice by objective and repair errors
For each learning objective, use practice that matches its verb. A calculation objective needs numerical work; a comparison objective needs both methods in the same question; a limitation objective needs a scenario where assumptions break. If a resource offers only recall questions, supplement it with your own variations and explanations.
After a question set, classify each miss. Was the concept unknown, the formula selected incorrectly, the setup reversed, the arithmetic wrong, or the time spent too long? Write the correction in a few lines and solve a different problem on the same idea later. Repeating the exact item immediately can conceal whether the reasoning transferred.
A useful error log entry is specific: “Used P(signal|default) when asked for P(default|signal); denominator must be all signals.” This gives you a procedure for the next problem. “Review Bayes” is too broad to guide a short study session. Revisit the correction after several days to test retention.
Phase three: mix topics and practice pacing
When most objectives have had an initial pass, begin mixed sets. Change the topic order so you must identify the method from the question rather than the chapter heading. Include computations and interpretation questions. Use the official exam timing as a full-session benchmark, while remembering that an average pace is a budget and not a target for every item.
A first timed pass can use a two-stage approach. Answer items with a clear solution path, mark questions requiring longer work, then return to them after covering the full set. During review, distinguish time lost to difficult arithmetic from time lost to rereading or indecision. Adjust the next session to address the actual bottleneck.
Do not infer the GARP pass cutoff from practice scores. Third-party questions vary in difficulty and coverage, and repeated questions inflate results. Treat practice as a diagnostic: is performance stable across domains, are answers explainable, and can you maintain accuracy under time limits? Use the official result standard only for the actual exam outcome.
Phase four: consolidate without cramming
In the final phase, focus on weak objectives, formula recall, and mixed practice. Avoid opening several new resources at once. Rework selected errors using new values and explain the assumptions. Review distinctions that are easy to reverse, such as payoff versus profit, forward price versus contract value, and a conditional probability versus its reverse.
Use one full-length practice session early enough to learn from it, not the night before. Plan time afterward to review every uncertain answer, including correct guesses. If the practice set is reused or open book, label that limitation instead of treating the result as a live score estimate.
Protect sleep and practical exam logistics near the appointment. Confirm the location, allowed calculator, identification, and current test-day rules from GARP. A late-night formula marathon can reduce attention on a four-hour computer exam. The final days should reinforce retrieval and confidence in the process, not introduce an unreviewed pile of material.
Adapt the plan when it falls behind
If the first pass takes longer than planned, identify why. A difficult prerequisite may need a focused refresher, while overlong notes may need to be shortened. Protect some unscheduled capacity each week for work demands or missed sessions. Cut repeated passive reading before cutting an entire domain. Every exam domain should receive enough attention to recognize its concepts and practice the listed objectives.
If work removes a week, revise future sessions using available time rather than pretending the missed hours will fit into the next few days. Shift low-priority repetition, combine related reviews, and preserve mixed practice. If the remaining time cannot support meaningful coverage, compare the current administration's deferral rules with the later calendar and decide using official terms.
The best plan is a feedback loop: set a weekly target, record actual work, test recall, and adjust. It should expose a problem early enough to fix it. A perfect calendar that is never revised is less useful than a modest schedule that responds honestly to performance and available time.
Common questions
When should I take a diagnostic?
Take a short mixed diagnostic early, before committing to a detailed schedule. It can reveal foundational gaps but does not predict the official result.
Should I study one domain at a time?
A first pass by topic helps build context, but later practice should mix domains so you must identify the method from the question.
How often should I review mistakes?
Return to an error after several days with a new problem. Immediate repetition can test memory of the solution rather than transferable understanding.
How many mock exams should I take?
Use full-length practice to learn pacing and stamina, but review each session carefully. A mock count or score alone does not establish readiness.