How it works
You set up three facts: which certification, your exam date, and how many hours you have in a week. Everything after that is built from the exam’s published outline and recorded as work you have shown.
Your plan comes from the exam’s published outline (the blueprint), domain by domain — not from a course that happens to overlap it. As your test date gets closer, your remaining hours go to the areas where you’ve shown the least. They do not go back through material you finished months ago.
A mission is one piece of hands-on work in a practice lab, sized to fit your week. Your coach tells you why it’s next. Reading a chapter twice is not practice. Doing the work under time pressure, then explaining your choices, is.
Everything your map says about you is one of four marks: Not observed, Developing, Demonstrated, or Revisit. Each mark records something you did. There is no score and no predicted pass chance. A mark can move backward when your coach sees a skill slipping — that’s the map doing its job. You never walk into the exam trusting stale strengths.
Every domain, every concept, every mission outcome resolves to one of these four marks. Nothing here is a grade, a rank, or a predicted pass chance.
SAMPLE MISSION
Domain 3.0 — your IP addressing is solid. Deciding how to segment a network is where you’ve shown the least. Place these services into zones, then explain why you drew the lines where you did.
| DOMAIN | EVIDENCE | CONCEPTS OBSERVED |
|---|---|---|
| 1.0 General Security Concepts | Demonstrated | 21 / 24 |
| 2.0 Threats, Vulnerabilities & Mitigations | Developing | 11 / 26 |
| 3.0 Security Architecture | Developing | 8 / 21 |
| 4.0 Security Operations | Not observed | 0 / 28 |
| 5.0 Security Program Management | Revisit | 3 / 15 |
ILLUSTRATIVE SAMPLE — YOUR MAP STARTS EMPTY.