Quick planner
If you have 30 minutes today, pick one pathway and complete a small task that produces evidence. A few consistent outputs are more useful than a long list of bookmarks.
Write a learning goal
One sentence: role, timeframe, and the first topic you will study.
Pick one practice task
A lab, a small script, or a troubleshooting note you can reuse.
Document what you did
Keep a short log: problem, steps, result, and what you would do next.
Resource library
This library is designed for quick use. Each card explains the purpose, the output you should aim to produce, and how to validate the result. If you need broader context for costs or time commitments, review Funding and Programs.
4-week study plan template
A simple weekly plan that mixes learning, practice, and reflection. Use it to avoid overloading a single week with videos and no hands-on work.
Output: a schedule with three repeatable blocks: learn, build, document.
Portfolio checklist (entry level)
A checklist for portfolio quality: clear readme, reproducible steps, screenshots, and notes on trade-offs. Works for IT support and software projects.
Output: two to four projects you can explain in under two minutes each.
Role guide: IT Support
A practical outline of tasks you may see in a support role: ticket triage, user communication, device setup, and common troubleshooting patterns.
Output: a short list of scenarios you can practise and document as case notes.
Role guide: Cyber security basics
A foundation view of security that emphasises process and evidence: asset awareness, risk thinking, and safe handling of data and credentials.
Output: a small threat model for a project you built, plus mitigations you can explain.
Cloud lab log template
A format for recording labs: goal, environment, steps, mistakes, and clean-up. This helps you avoid repeating errors and improves interview storytelling.
Output: a set of lab notes that show you understand cost and access control basics.
CV evidence builder
A set of prompts that convert learning activity into evidence lines. It focuses on outcomes, tools used, and communication, rather than buzzwords.
Output: three bullet points per project that map to job descriptions without exaggeration.
Want a curated set for your pathway?
Tell us the role you are aiming for and your weekly availability. We will point you to relevant pages on this site so you can compare programmes and plan a sequence of practice tasks.
We do not request sensitive personal data. Keep messages focused on programme questions, availability, and learning goals.
How to use these resources
The most useful resources are the ones that produce consistent evidence. Use a repeatable loop: plan a small task, complete it, and document it. Documentation makes your learning visible, helps you reflect, and can later support applications and interviews.
If you are comparing providers, treat the resources as a baseline. A strong programme should help you create outputs like these, with feedback that improves clarity and correctness. Use Programs for learning format comparisons and Funding for the cost context you may need before you commit.
-
1
Pick one pathway and one weekly target
Set a target that is measurable. Examples include completing a support troubleshooting note, building a small script, or writing a short project readme. Keep it achievable with your schedule.
-
2
Use a template to capture evidence
Templates reduce friction. Use a consistent lab log or case note format so it is easy to review progress and identify repeated mistakes or knowledge gaps.
-
3
Validate using a simple checklist
Before you move on, check for basics: clear naming, reproducible steps, safe handling of credentials, and a short explanation of trade-offs. If something is unclear, revise it while the memory is fresh.
-
4
Map outputs to programme or role requirements
Use Programs to compare what a course claims to teach and what you can actually show. If you contact a provider or apply for an apprenticeship, you will have concrete examples to discuss.