Building a GS-6+ Promotion Case After the 52-Week Rule Ends

The clock is not the case

You have been counting weeks. OPM adopted a rule lifting the governmentwide time-in-grade requirement for covered competitive-service General Schedule positions at GS-6 and higher. The former governmentwide restriction generally required employees to spend 52 weeks at a lower grade before promotion consideration. The final rule takes effect January 14, 2027. The rule does not give federal workers a right to a promotion after one year, and it does not force agencies to move employees up sooner in every situation. The government's time-in-grade restrictions for competitive-service General Schedule employees have been in place since the 1950s.

The practical question is what still has to be true before you can be considered. Keep the clock separate from the case.

• Agency prerequisites
• Job standards and specialized experience
• Competencies or training
• Manager timing

If one item is missing, identify the gap before you ask for the promotion.

Agency rules set the remaining hurdles

Read the agency merit promotion plan and any local rules before you prepare examples. OPM turned down a proposal to create governmentwide standards for faster promotions of federal workers. Agencies may continue to include additional promotion prerequisites such as demonstrated competencies and required training. The same employee in different offices may face different hurdles.

Do not assume a headquarters policy is the whole picture. Local offices can add requirements, and a supervisor may have a different selection process. Put the source of each requirement in your note. If you cannot find the rule, ask the human-resources office for the current version.

Match the job standard and specialized experience before you argue for yourself. Pull the position description for the grade you want and mark the duties that require the higher level of judgment, scope, or complexity. If the standard says you must have led a project, do not describe a project you supported. Build a side-by-side table: the standard on the left, your evidence on the right, with no blank cells.

Use the language of the standard, not your resume. If the standard says directed, do not write participated. If it says developed, show the artifact. A reviewer should be able to connect your sentence to the requirement without guessing.

The mistake that weakens cases is treating a heavier load as higher-grade work. More tasks do not prove the higher level of judgment. A file that says you did more will not satisfy a reviewer who has seen many strong candidates. Tie each claim to a duty, a decision, or a result.

Stack competencies and training where the agency requires them. If the plan names a leadership course, a technical certification, or a demonstrated behavior, get the record in writing. A transcript, a completion certificate, or a supervisor note is better than a promise to learn later. The file is complete when the prerequisite is met, not merely in progress. For a course, get the completion date. For a demonstrated behavior, ask your manager to point to the specific instance. A vague promise to develop leadership will not meet the prerequisite.

Manager timing depends on the org chart

Check the org chart before you ask. A promotion usually needs a vacancy, a reorganization, a new position, or a manager who can justify moving you into an existing slot. If the next grade is not open, the case may be strong but the opportunity may be unavailable. Ask the manager what the org chart looks like for the upcoming selection window. When the answer is unclear, request the staffing plan or the succession note.

Do not treat the manager's enthusiasm as proof of a vacancy. Enthusiasm is useful, but it cannot replace a position description. Ask for the grade, the series, the location, and the date the slot can be filled.

A reviewer must be able to follow the file

Build the file as if a reviewer has never met you. Start with a short summary that names the position, the standard, and the strongest evidence. Then attach the supporting records: performance ratings, project artifacts, training completions, and supervisor statements. Keep the order simple.

A reviewer should find the answer early and the proof nearby. Use numbers only when you can verify them. A project that saved time needs the measure. An improved-quality claim needs the before and after. When you cannot document it, say what you did and let the duty speak. A file full of adjectives will not support a case.

Ask the manager for a decision, not a nod. Say you are ready for consideration and ask what the next step is. A yes should come with a date and the paperwork, and a no should name the gap or the evidence that would change it. Leave with a next step, not a compliment.

The human part matters, but it cannot support the file alone. A sympathetic manager cannot replace a record that shows the next level of responsibility. Seek feedback on the weak parts of the case before the formal window. If the feedback says you need more evidence, treat that as useful, not personal. Then bring the revised file to the manager before the next review cycle.