Prepare for the QKA by studying administration as one connected chain, not as separate topics. Eligibility, compensation, matching, vesting, and nondiscrimination testing all consume the same definitions from the plan document. Trace a single census participant through the entire cycle, then repeat with a second participant whose facts differ, and use a written rubric to confirm you can justify each step.
Why One Wrong Definition Distorts the Whole Administration Cycle
Every administration task reuses a small set of plan-document definitions: compensation, hours of service, entry dates, and employee classifications. Because these definitions feed every later calculation, studying them as a connected chain is more reliable than reviewing topics separately.
Consider how the cascade works in one illustrative case. If an administrator values a match formula using W-2 wages instead of the plan's compensation definition, the match for a participant with pre-tax insurance premiums comes out too high. That single definitional slip then changes the account balance, the vesting calculation applied to it, and the data that later feeds compliance testing. The error is invisible until someone reconciles the numbers.
A practical way to study this is to build a one-page definition ledger. For each term, record where it comes from (the plan document, a default in the law, or a rule the law fixes and no document can override), which tasks consume it, and what happens downstream when it is applied to the wrong base. Revisit the ledger every time a practice question uses a term, and update it when you notice a distinction you had merged, such as different compensation bases used by different formulas in the same plan.
- Ledger entry format: term, source (document, law, or non-overridable rule), tasks that use it, downstream effect of misapplying it
- Re-check the ledger after every practice question, not only when you answer incorrectly
Applying Eligibility and Entry Dates to a Real Census Row
Eligibility requires applying the plan's age and service conditions to hours of service computed under the governing rules, then placing the employee into the correct entry date. Worked census examples reveal where mechanical shortcuts produce wrong answers.
Worked scenario: a plan requires age 21 and one year of service with 1,000 hours, entry on the first of the January and July following completion. A part-time employee is credited for 12 monthly pay periods averaging 80 hours, so the administrator treats her as eligible immediately. Counting pay periods instead of computing hours is the mistake: her worked hours total 960, which falls short. The better decision is to sum hours of service per the governing rules — and note that hours for which she is paid for non-duty time, such as vacation or holidays, count as hours of service by rule, not as a plan-document option. If paid-leave hours push her past 1,000, she completes service earlier than a worked-hours-only reading suggests; if they do not, her entry defers to the next date. Either way, misplacing her entry date can obligate the employer to make up missed employer contributions plus earnings if she later claims entitlement.
Train this skill by taking three census rows and, for each, writing the age at hire, the hours of service in each computation period (worked hours plus any paid non-duty hours), the date service is completed, and the resulting entry date. Deliberately include a rehire, because service rules often bridge a break in employment. The observations to expect: a rehire's prior hours may complete service faster than a fresh-hire reading suggests, and an entry date is a specific calendar date you can state, not a vague 'next period.'
Tracing Vesting from Contribution Source to Account Balance
Vesting is traced contribution by contribution: employee deferrals are always fully vested, while employer money follows the schedule in the document. Mixing up which source carries which schedule is a definitional error worth drilling directly.
Cliff and graded schedules describe how employer contributions become nonforfeitable. A cliff schedule vests nothing until a stated point, then everything; a graded schedule vests in increments over time. The key study habit is anchoring vesting to the year each contribution was made, so a participant who terminates after several years has a mix of fully and partially vested employer money. The exercise is to pick one balance, list each year's employer contribution, apply the schedule year by year, and total the vested percentage.
The comparison below organizes the contribution sources you will trace. Use it as a retrieval prompt: cover the right-hand columns and reconstruct each row from memory, then verify against your notes. Expect to find that the nonvested portion of employer money is forfeited at termination and, depending on the document, may be used to reduce future employer costs, which is one reason vesting accuracy affects plan-level accounting as well as individual benefits.
Watch for a related trap in formulas: some employer contributions carry faster vesting than the schedule that governs the rest of the employer money. When you trace a balance, confirm which schedule applies to which contribution type before computing anything.
| Contribution source | Who funds it | Vesting treatment | Why it matters downstream |
|---|---|---|---|
| Elective deferral | Employee via salary reduction | Always fully vested | Counts in employee-directed testing measures and distribution elections |
| Employer match | Employer, tied to deferrals | Per plan schedule (cliff or graded) | Vesting percentage determines the forfeitable balance at termination |
| Nonelective employer contribution | Employer, not tied to deferrals | Per plan schedule; some designs vest faster | Feeds both individual balances and plan-level contribution obligations |
Choosing the Correct Compensation Definition for Each Formula
Plans commonly reference more than one compensation definition, and each formula uses a specific one. The administration skill is checking the formula's stated base before calculating, rather than assuming a single wage figure applies everywhere.
A plan document may define compensation for matching differently from compensation used elsewhere, and items such as pre-tax elective deferrals themselves can create gaps between a payroll wage figure and plan compensation depending on the definition's wording. The habit to build: for every formula you encounter in practice material, ask three questions — which definition does this formula name, does that definition include or exclude this participant's pay items, and does any limit cap the amount recognized? Answering all three in writing turns a vague familiarity with 'compensation' into a checkable procedure.
A short self-check exercise: take one participant with salary, a bonus, and a pre-tax deferral, and compute plan compensation under two differently worded definitions — one that includes all pay and one that excludes certain items. Expected observations are that the two bases differ, the match differs as a result, and the difference persists even before any limits are applied. If your two figures match, you have applied the same definition twice; that is the signal to re-read the document language rather than trust the coincidence.
Reading Testing Results Without Misclassifying the Groups
Nondiscrimination tests compare deferral and contribution behavior between employee groups, so classification must be completed and verified before any test is interpreted. A classification error changes the result in the direction that hides a problem.
Worked scenario: a plan determines its highly compensated group using a prior-year lookback, but the administrator runs the test using current-year pay and leaves a newly promoted executive in the non-highly compensated group. That inflates the non-highly compensated average, and the test appears to pass. The better decision is to treat classification as its own documented step, run before any averages are computed, using the lookback and definitions the document specifies. Why it matters: an apparent pass built on wrong groups is not a pass, and once the plan year closes, corrections such as adjusting highly compensated deferrals or funding additional employer contributions become more involved and more expensive.
Study testing by computing an illustrative example by hand: average the deferral percentages for each group from a six-person census, compare them, and articulate what a failure would mean before looking at any correction options. The observations to expect are that a single misclassified participant can flip the conclusion in a small census, and that the correction logic differs depending on which side of the comparison is too low. Practice questions that hand you a finished result are most useful when you reconstruct the groups and averages yourself first.
Distributions, Documentation, and Where Professional Boundaries Sit
Distribution work is procedural: verify the participant's status and elections, apply the document's distribution provisions, and document each decision. Professional standards require staying within the administrator's role on tax and legal questions.
Trace a terminating participant the same way you traced eligibility: confirm vested balance from the vesting trace, identify the distribution options the document offers, and note which elections require specific consent forms for a married participant. Illustrative distinctions worth drilling include a direct rollover versus a cash payment, and an in-service versus post-separation event. Each distinction changes paperwork, timing, and the participant's own tax outcome, which is why the administrator's job is to present the document's options accurately rather than recommend one.
Documentation is the layer that makes all of this defensible. For each task in your practice traces, write the one-line rationale a reviewer could follow: which document provision was applied, which definition was used, and where the input data came from. Professional standards also draw a boundary: explaining what the document provides is administration work, while advising a participant on their personal tax or investment situation is not. Recognizing that boundary in scenario questions is itself a testable skill, and it is learned by writing the boundary into your own case notes.
A Case-Trace Exercise, Self-Check Rubric, and Study Sequence
Combine everything in a repeated full-cycle trace of one census participant, scored against a rubric. Use the rubric as a learning milestone, then layer timed practice questions and a case journal on top.
The exercise: construct a fictional census of six employees, including one part-time worker with paid leave, one rehire, and one highly compensated participant under a prior-year definition. Trace each person through eligibility, entry date, compensation under two definitions, match, vesting by contribution year, and the group assignment for testing. Expected observations: the part-timer's entry date hinges on the hours-of-service computation, and her paid non-duty hours count toward the service threshold; the rehire's service completes sooner than a fresh-hire reading; and the highly compensated participant's group status depends on the lookback you chose. If all six traces feel mechanical, add a plan amendment mid-year and redo the affected steps.
Self-check rubric — award one point each, and treat the total as a milestone rather than a pass prediction: (1) hours of service computed under the governing rules — worked hours plus paid non-duty hours — not pay periods; (2) entry date stated as a calendar date; (3) each formula's compensation base identified before calculating; (4) vesting applied contribution year by contribution year; (5) group classification completed before testing; (6) a written rationale line for each decision. A suggested sequence: two weeks on the definition ledger and document mechanics, two weeks on census-level eligibility, vesting, and compensation traces, two weeks on testing and corrections, then two weeks of full-case traces with the rubric plus practice questions converted into new census rows for your exercise file. Readiness checks before the exam: you can trace a participant end-to-end without notes, explain which definition each formula consumed, and state the professional boundary in your own words.
For administrative details such as eligibility requirements, exam format, and scheduling, rely on the credential issuer's own credential page rather than secondary summaries; those logistics fall outside what study material should restate.
- Rubric score of 6/6 twice in a row signals the tracing habit is set, not that the exam outcome is known
- Convert every practice question into a census row so your exercise census grows over time
- Keep a case journal of each scenario's mistake, better decision, and downstream effect
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.