A two-hour OSCP study routine works best when you choose one question, one useful result and a clear place to resume. Start with the plan below, then shorten it to fit the time you actually have after work. The allocations are adaptable editorial examples; they do not predict an exam result.
Start with this 120-minute plan
| Minutes | What to do | Leave with |
|---|---|---|
| 0–10 · Prepare | Read the previous note, confirm the permitted lab and choose one question. | A starting state and a question written in one sentence. |
| 10–50 · Practise | Run the smallest useful exercise or collect the observations needed for that question. | Original output and a short account of what happened. |
| 50–60 · Break | Step away. On returning, check whether the same task still fits. | A decision to continue, narrow the task or finish early. |
| 60–100 · Follow up | Compare one condition, repeat a result, or investigate one blocker. | A supported conclusion or a precisely named uncertainty. |
| 100–120 · Close | Write what you found, which help you used and the next starting action. | A note you can use tomorrow. |
Example goal: inspect one HTTP response and explain how it differs from a missing-page response. Result to keep: the two responses, your interpretation and one next check. Completing the entire machine is a separate goal.
Total: 10 + 40 + 10 + 40 + 20 = 120 scheduled minutes, including a 10-minute break and 20 minutes for closing notes.
Choose one task from where you are now
Before opening another target, decide which kind of session you need. Use your last saved result, error or unexplained concept to choose. You can change the task when new evidence shows the original question was too broad.
| Your starting point | Choose this session | A useful finish line |
|---|---|---|
| A concept or tool option is unfamiliar | Read its documentation and try a small permitted exercise. | Explain the concept in your own words and save one example. |
| You are returning to an unfinished lab | Rebuild the previous state from notes, then check one question. | Save one new observation and connect it to the earlier record. |
| The same attempt keeps failing | Identify the first failing stage and inspect one assumption. | State the exact error, what you ruled out and one next check. |
| A result works but your notes are incomplete | Reproduce it and write the steps while doing so. | A record another technically competent reader could follow. |
| Work has left little time or concentration | Read one saved output, organise a note or choose the next task. | A clear explanation or restart point, then stop. |
Make the question smaller: replace “finish enumeration” with “identify which observed service to investigate next and explain why.” Replace “learn Active Directory” with one defined concept or relationship from your current course exercise. These are task examples, not a complete OSCP syllabus.
Before the session: make the starting point usable
Keep the permitted lab, current target identity, notes and recovery reference ready. Check adapters and addresses when the environment has changed. If the lab cannot boot or connect, choose an environment-repair session rather than hiding that work inside an investigation goal.
For a local Kioptrix exercise, use the setup-to-first-scan guide. For saved scan interpretation, open the result-to-next-tool guide. You do not need to change hypervisors just to use a study schedule.
Use a 30-, 60- or 120-minute session
Choose the block you can actually protect tonight. Reduce the task before removing all closing time. The examples below are starting points; add breaks or stop earlier whenever needed.
| Available time | Example allocation | Suitable task |
|---|---|---|
| 30 minutes | 5 prepare + 15 focused work + 10 close | Interpret one saved output or clarify one unfamiliar option. |
| 60 minutes | 5 prepare + 35 focused work + 20 close | Check one bounded question and write the result. |
| 120 minutes | 10 prepare + 40 practise + 10 break + 40 follow up + 20 close | Compare or reproduce a result and preserve a restart note. |
If interrupted: save the current command or action, the latest result and the next intended step. A missed evening does not create an automatic catch-up debt. Re-plan the remaining sessions around your actual availability.
When you get stuck, choose the kind of help you need
Before repeating a command, ask which part is unclear. The answer determines whether you need documentation, setup repair, interpretation or a focused hint.
| The obstacle | Try next | Keep in your note |
|---|---|---|
| You cannot explain an option or term | Read the relevant documentation and test a small example. | The meaning, example and remaining question. |
| The command does not run or the target cannot be reached | Read the exact error and check the first failing local or network stage. | The error and the configuration you actually inspected. |
| Output appears but its meaning is unclear | Compare the expected result with the literal output. | What is observed, what is inferred and what remains unknown. |
| You have results but no next direction | Write an observation, possible explanation and a check that could distinguish it. | The question a conceptual hint or review should answer. |
| Fatigue makes reasoning unreliable | Record the current state, reduce the task or finish. | A usable starting action for another day. |
Ask for the smallest useful amount of help: a term explanation, output interpretation, a next-question hint or a worked step. Record what the help supplied. Learning from a walkthrough can be useful; distinguishing assisted reproduction from independent discovery makes the next practice choice clearer.
See one completed session
Illustrative learning example: this is a fictional planning record, not a report of a test performed for this article.
| Block | What the learner does | Record left behind |
|---|---|---|
| 0–10 | Reads yesterday’s service inventory and selects the HTTP question. | “Does the candidate path differ from a deliberately missing page?” |
| 10–50 | Saves comparable responses from the identified authorised lab service. | Original responses, URLs and conditions. |
| 50–60 | Takes a break and reviews the question. | The comparison is still worth investigating. |
| 60–100 | Compares content and redirects, then repeats the relevant difference. | Which responses differ and what the comparison does not establish. |
| 100–120 | Writes the interpretation and discloses any reference or hint used. | “Next time, inspect the recorded redirect destination after confirming it remains in scope.” |
If no useful difference appeared: the session could still finish with the saved comparison and that result. Choose another question later from the remaining evidence. Do not invent progress just to fill the last row.
Plan one week, then adjust it
Put available sessions into the calendar first. Give each one a question and a result to keep. The example below shows one possible week, not mandatory weekdays or an optimal rotation.
| Day | Minutes | Example task and deliverable |
|---|---|---|
| Monday | 120 | Service investigation: save a comparison and explain the result. |
| Tuesday | 120 | Current Windows exercise: check one permissions question and record the evidence. |
| Wednesday | 0 | Unavailable or rest. |
| Thursday | 120 | Current AD lesson: explain and verify one relationship in the permitted lab. |
| Friday | 0 | Unavailable or rest. |
| Saturday | 120 | Repeat an earlier result from the saved notes and repair missing steps. |
| Sunday | 60 | Review the week’s records and choose the next priority. |
Time arithmetic: four 120-minute sessions plus 60 minutes total 540 scheduled minutes, or 9 hours. The four scheduled breaks account for 40 of those minutes. Record actual work separately; scheduled hours do not measure learning or predict a score.
At the end of the week, compare these five things:
- Explain: which result can you now explain without relying on someone else’s account?
- Reproduce: which note lets you resume or repeat the work?
- Repair: what blocked you more than once?
- Assistance: which decisions came from hints, documentation or a walkthrough?
- Time: was the task too broad for the sessions actually available?
Keep what worked, shrink oversized tasks and choose the next practice from a named gap. For a longer preparation sequence, use the multi-week planning guide alongside your current course material.
Write a plan you can use tonight
Fill in what you know. Fields stay in this page only, with no automatic saving or submission. Generate, copy or download the note before leaving or reloading. Use sanitised practice details; do not enter passwords, tokens or private client information.
For a more detailed write-up, use the practice report outline. For service-by-service notes, use the enumeration note template. Start with the small session note above if you do not need a full report.
Official exam rules and the limits of this study template
This is an independent study-planning aid. Use the official OSCP+ exam guide and official FAQ for current assessment, reporting and tool restrictions. The linked pages were reviewed for this editorial update on October 26, 2026; their displayed update date was October 21, 2026.
OffSec requires reproducible reporting and prohibits chatbots during the exam and reporting phase. Study assistance outside an exam must not be confused with permission during it. Review the current rules when preparing a rehearsal or booking an assessment.
A short session practises part of a workflow. Use longer rehearsals to test sustained investigation, evidence capture and reporting when appropriate; a two-hour block does not reproduce the complete assessment. Use demonstrated skills and current provider guidance rather than this planner to judge readiness.
Common planning questions
Is two hours a day enough?
It is an available block to plan around. What you need depends on your starting skills, course progress and independent practice. Review what you can explain and reproduce instead of treating a duration as a guarantee.
Should I practise without notes?
You can use recall exercises to check understanding. Also practise reconstructing work from your own notes; they need to be useful when you return. Consult the official rules for resources allowed during an actual exam.
What if work leaves me too tired?
Choose a smaller review, save a restart note or rest. Update the week’s plan rather than automatically adding the missed work to tomorrow.
What about course access and costs? Check the provider’s current access period and booking terms against your realistic calendar before committing. This timetable is not a reason to buy a subscription you cannot use.
Tonight’s finish line: answer one question or explain why it remains open, preserve the result and leave the first action for your next session. Adjust the next plan using that record.
Editorial update: October 26, 2026. Moved the usable timetable to the top, added shorter sessions, a fictional worked example, blocker choices and an editable session/weekly planner. This is an editorial planning template, not a personal exam-success account or a measured optimal schedule. No new VM exercise or learning-outcome test was performed.