Requesting a DA Form 67-10-1 OER Support Form

Working as a military rater in the U.S. Army means juggling evaluations across multiple subordinates, and the DA Form 67-10-1 OER support form often sits at the centre of that paperwork. The form captures the rated officer's administrative data, duty description, and the rater's proposed narrative inputs before the formal Officer Evaluation Report is finalised. Getting it right early saves weeks of back-and-forth, especially for soldiers posted overseas or balancing duties across time zones like AEST during joint training events with the Australian Defence Force.

For raters who have never requested the form through official channels, the process can feel opaque. The support form is not a publicly downloadable PDF — it flows through the rater profile in the Army Evaluation Entry System after a rating chain is established. This walkthrough covers the practical steps, the paperwork to gather, and the pitfalls that regularly slow down first-time requesters based in places such as Sydney, Townsville, or wherever the rotation takes them.

What the DA Form 67-10-1 Actually Does

The 67-10-1 is the administrative backbone of every OER. It records identifying details, the period of the report, the chain of command, and the duty description that the rated officer will be assessed against. Raters use it to draft their narrative, block check the appropriate boxes, and pass the document up the chain for senior rater review. Without a properly initiated 67-10-1, the OER cannot enter the evaluation system at all.

Think of it as the scaffolding around the actual report. The senior rater relies on the duty description and the rater's proposed boxes to write a fair narrative, while the rated officer reviews the form to confirm accuracy before signing. For Australian-based personnel working through joint postings or exchanges, the form also clarifies which U.S. reporting requirements still apply when day-to-day duties shift toward coalition tasks.

Gathering the Information Before You Request

Before logging in to request the form, raters need a short list of items ready. The rated officer's full name, DOD ID, rank, and branch must match personnel records exactly. The period of report, including start and end dates, should be confirmed against any memoranda or counselling forms already on file. A draft duty description, written in the rated officer's voice, is the single piece that prevents the most rework later.

Most raters who get this stage right report a smoother ride through the rest of the process. Those who rush tend to receive the form back with administrative flags that bounce it from one desk to another. If the rated officer has changed duty positions mid-period, capture both assignments on a single form and flag the changeover in the duty description block.

Submission step	What the rater does	Typical time to clear
Initiate support form	Log in, select rated officer, confirm details	Same day
Senior rater review	Review duty description and proposed boxes	2–5 business days
Rated officer sign-off	Verify administrative data, sign	1–3 business days
Final routing into EES	Submit to HRC for record	1–2 business days

How the Request Travels Through EES

Once the information is ready, the rater logs into the evaluation portal and navigates to the rater profile, where the option to initiate a new support form appears under the rated officer's record. The system generates the 67-10-1 with the rated officer's details pre-populated, and the rater fills in the duty description and proposed senior rater before submitting for routing. For step-by-step visuals on this part of the workflow, the EES submission walkthrough covers the screen flow in detail.

After submission, the form moves to the rated officer for review, then upward through the senior rater and into the Army's records pipeline. Raters who want a refresher on how the broader evaluation cycle works alongside the NCOER process can review the NCOER application process overview, which mirrors several of the same routing rules.

Login Glitches and Routing Delays

Few things stall a request faster than a locked account or a profile that does not show the rated officer under the rater's chain. Authentication problems hit even experienced raters, particularly after a PCS move or a role change that has not yet propagated through Army directories. When the portal refuses to load or throws a session error, the EES login troubleshooting guide walks through the most common fixes before raising a ticket.

Routing delays are a separate beast. If the form sits untouched for more than a few business days, a polite nudge to the senior rater's NCO usually moves it along. Time zone gaps matter here — a rater in Darwin corresponding with a senior rater based at the Pentagon loses almost a full day each way, so plan ahead and avoid leaving things until the rating period closes.

Following Up After the Form Is Submitted

Once the 67-10-1 has been submitted, the rater's job is to monitor the form's status and stay available for edits. Most senior raters return the document with tracked changes, and a quick turnaround keeps the report on schedule. A handy rule of thumb is to check the evaluation queue at the start and end of each working day, especially during the rating period crunch when everyone's rushing to beat the suspense date.

For raters who need additional context on related administrative workflows outside the standard EES pipeline, Permeti Jone offers broader guidance on military documentation processes that complement the official channels.

Items to Have Ready Before Requesting

• Rated officer's full name, DOD ID, rank, and branch
• Confirmed period of report with start and end dates
• Draft duty description covering all assigned responsibilities
• Copy of any change-of-duty memo if a mid-period reassignment occurred
• Senior rater's name and accurate reporting sequence
• Recent counselling form, if available, to anchor the narrative

Common Reasons a Support Form Gets Bounced

• Mismatched DOD ID or misspelled name in the personnel block
• Duty description that does not align with the rated officer's actual position
• Missing or incorrect senior rater in the chain
• Form submitted outside the rater's authorised evaluation window
• Authentication error that prevented the final save from registering