Write the competencies out as rows you can score.
Every course announces what it certifies. Before you open a single learning resource, copy those competency statements into a document of your own, one per row, and leave three empty columns beside each: a confidence mark, the date you last worked on it, and the evidence you have that it is genuinely closed. This document is your plan. The course materials are just what you feed into it.
Score yourself honestly in the confidence column right away, before studying anything. You will be wrong in both directions, and that is the point of the next step, but the first pass tells you where your instinct says the risk sits. Students who skip this step tend to study the topics they enjoy, which are almost always the ones they already know.
Let the practice attempt correct your guesses.
Take the practice assessment far earlier than feels reasonable, while you still expect to do badly, because you are not testing yourself, you are sorting the rows in your table. The report that comes back tells you which competencies came out weak, and that report is worth more than any reading list, because it is specific to you rather than to the average student taking this course.
Now update your table and be ruthless about what you delete from it. Time spent on a competency already marked strong buys you nothing at all, since a passing standard does not award extra credit for comfortable topics. Everything from here goes to the weak rows, and each of them gets a date in your calendar rather than a place on a list.
The week grid that survives a working life.
A competency plan collapses when it is written as an intention rather than as a grid. Assign the rows to slots you can actually defend, and keep the shape identical from week to week so that no decision has to be made on a tired Tuesday.
- Two short weekday sessions on one weak competency each, active recall rather than rereading
- One longer weekend block for the competency that scored worst, worked with a blank page
- A fifteen-minute review on a separate day of everything covered so far, spaced out on purpose
- One repeat practice attempt at the end of the week to update the table with evidence
- A named day when you will book the real assessment, decided in advance rather than when you feel ready
A performance assessment needs a different plan shape.
Submitted tasks are not studied for, they are constructed, so the plan becomes an outline instead of a drill schedule. Open the task instructions and the rubric side by side, then build a document whose headings are the lettered requirements in the order the task lists them. Anything an evaluator cannot find quickly reads as missing, and making the mapping obvious is simple courtesy rather than a trick.
Then plan for the wait, because evaluation time belongs to somebody else's calendar and no amount of urgency on your side shortens it. Submit with days in hand, keep working on the next course while the task is under review, and treat a returned task as a normal step rather than a verdict: it names the aspects that fell short, so fix those, note what changed, and send it straight back.
The last week, and the day you actually sit it.
Book the assessment while the material is still warm rather than waiting for a feeling of readiness that tends not to arrive. In the final week, stop adding new topics and spend the hours on retrieval: close the book, write what you know about a competency from memory, then check what you missed. Put a rest day between your last practice run and the real sitting, because tiredness costs recall before it costs anything else.
Treat the setup as part of the exam too. Check the equipment, the identification and the room the day before rather than in the hour before, since technical trouble eats the calm you were saving for the questions. Students who want a plan built for them rather than by them can enroll in EDL 340, which is quoted free within two hours. If holding the weekly grid is the harder part, the blocking method is the companion piece to this one.
Common questions.
How early should I take a practice assessment?
Sooner than you want to, ideally in your first week with the course. Its value is diagnostic rather than evaluative: you are finding out which competencies are weak so your study hours land where they change the outcome. Waiting until you feel prepared inverts that, because by then you have already spent the hours you were trying to allocate.
Should I study the whole course of study or only the gaps?
Work the gaps, and use the whole course of study only as a map of what those gaps are. Competency-based assessment asks whether you meet a standard, not how far past it you sit, so hours spent polishing what you already know return nothing. Keep a written table so a topic can be marked closed and honestly left alone.
What should I do when a task comes back for revision?
Read it as a list rather than as a judgment. A returned task names the specific rubric aspects that fell short and leaves the rest of your work alone, so revise exactly those, mark what changed, and resubmit quickly. Most of the time lost to revisions is spent dreading them rather than doing them, and the second reading is usually faster than the first.
Is Edlaurel affiliated with Western Governors University?
No. Edlaurel is an independent academic coaching college, not affiliated with, endorsed by, or sponsored by Western Governors University. The school appears here only because our faculty have coached inside competency-based programs for years and the tactics come from that work. We never contact your school or your mentor about you.
