a DA Form 67-10-1 for a civilian rater through EES

The Evaluation Entry System (EES) handles most of the Army's officer evaluation paperwork online, including the supporting forms that accompany an Officer Evaluation Report (OER). When the senior rater needs written assessment from a civilian supervisor, the rater's input is captured on a DA Form 67-10-1, the official OER support form. Generating that document correctly within EES avoids delays at the S1 shop, prevents mismatched rater profiles, and keeps the rated officer's file aligned with AR 623-3.

For readers based in Australia, the process mirrors familiar evaluation work in the Australian Defence Force, where written input from non-uniformed supervisors is often required for joint postings or liaison roles. A soldier in Sydney working alongside a contracted civilian mentor, or an officer in Darwin embedded with a US training team, may face the same form challenges as their counterparts at Fort Bragg or JBLM. The steps below walk through how a soldier or HR professional prepares the form in EES, what data must be gathered ahead of time, and where civilian rater records commonly break down.

Understanding the role of the OER support form in EES

The DA Form 67-10-1 sits between the rater's narrative and the official OER, giving the senior rater a structured space to summarise the civilian supervisor's assessment. EES treats this form as a controlled document: every field is tied to a rater profile, and the system will not allow submission unless the rater's record is matched to the rated officer's evaluation cycle.

In practice, the support form is often drafted by the rater's office and then routed through the senior rater for inclusion in the OER packet. Because civilian raters do not have a standard Army login, EES creates a limited profile based on their duty position, organisation, and contact details. That profile is what binds their comments to the rated officer's record.

Soldiers posted to joint training environments around Adelaide or to coalition support cells in Townsville often encounter civilian raters from partner agencies. Their inputs must still flow through the same EES validation rules, which means the form cannot be skipped or hand-substituted even when the rater is not a uniformed soldier.

Preparing civilian rater information before logging into EES

Before opening EES, gather the civilian rater's full legal name, work email, duty title, organisation name, and the dates they supervised the rated officer. EES will reject records where the duty title contains unsupported characters, so spell out acronyms and avoid abbreviations like "Sr." or "Mgr." unless they match the official position description.

The rater's organisation should be entered exactly as it appears on official correspondence. A civilian mentor working for a defence contractor in Melbourne, for example, should be listed under the contractor's legal entity, not a colloquial project name. This matters because EES cross-references organisation codes against the Army's authoritative data tables.

You will also need the rated officer's information, including DOD ID, branch, rank, and the evaluation period covered. If the rated officer recently returned from an exchange posting with the ADF, double-check that their branch code reflects their current assignment rather than a previous unit. Soldiers who split time between Canberra and a US installation sometimes find outdated branch codes in their record, which can stall form generation.

Step-by-step navigation in the EES portal for the support form

Once logged in, navigate to the "Create New Support Form" option under the OER menu. Select the rated officer from the dropdown, choose the senior rater, and then click "Add Civilian Rater." EES will prompt you to search the rater database by name or email; if the rater does not yet exist, you will need to create a new profile from scratch.

After the rater profile is saved, EES opens the DA Form 67-10-1 template. Fill in each rated officer section: duty description, performance areas, and the rater's overall assessment. Use plain text where possible, avoiding copy-pasted formatting from Word that can introduce hidden characters. The system saves drafts every few minutes, but it is worth exporting a local copy after each section is completed.

When the form is complete, click "Route for Senior Rater Review." The senior rater will receive an email notification and must log into EES to approve the content. At that point, the form becomes part of the OER packet and flows into the rated officer's iPERMS file automatically. A useful checklist of related records can also be found when you locate your DD-214 through EES, since both requests rely on the same profile-matching logic.

Verifying the DA Form 67-10-1 details before submission

Verification is where most civilian rater forms fail. Open the form in EES and confirm the rater's duty title, organisation, and email match what was entered during profile creation. Even a single typo in the email field will prevent the senior rater from receiving the approval request and will block the entire OER packet.

Check the dates carefully. EES requires the rater's start and end supervision dates to fall within the rated officer's evaluation period. A civilian mentor who started two weeks before the period began, for instance, is still eligible, but the dates must be entered as inclusive. If the dates fall outside the window, EES will flag the form and require a justification note from the senior rater.

Confirm that the rater's comments do not exceed the field length limits and that no classified or controlled unclassified information has been pasted into the narrative. Once everything checks out, lock the form. From that point, edits require a formal request through the S1, so it pays to slow down and review before locking.

Common issues soldiers encounter with civilian rater profiles

The most frequent problem is a duplicate rater profile, often created when a previous EES user added the same civilian under slightly different spellings. EES will not merge profiles automatically, so you may need to contact the EES help desk to consolidate the records before the form can be associated with the rated officer.

A second common snag involves organisation codes for contractors or partner agencies. Civilian raters from multinational defence firms or government departments outside the US Army structure sometimes lack an entry in the system's lookup table, which means the rater profile cannot be saved. Submitting a request through the author info page can clarify who to contact for adding a new organisation code.

A third issue relates to timing. Soldiers preparing an OER close to a posting cycle, particularly those moving between Australian postings and US assignments around Brisbane or Perth, often wait until the last week of the evaluation period to generate support forms. EES can become slow during peak windows, and late submissions may miss the senior rater's review window entirely.

Coordinating with your S1 and the civilian rater after submission

After the form is locked and routed, send a courtesy email to the civilian rater explaining that they may be contacted by the senior rater. Civilian supervisors are not familiar with Army timelines and often do not realise that their comments are time-sensitive. A brief note explaining the disciplined approach the Army places on punctual reporting, without overstating any parallel, can set expectations clearly.

Work closely with your S1 to confirm the form has reached iPERMS and is visible in the rated officer's record. If anything looks off, request a status pull rather than generating a new form, since duplicates are difficult to remove. Once the OER is finalised, archive a copy locally for your own records, in case the rater needs to reference it for a future posting or a civilian career milestone review.

Practical recommendations for smooth OER support form processing

• Build a one-page civilian rater template that captures name, email, duty title, organisation, and supervision dates before opening EES.
• Verify organisation codes in the EES lookup table at least one week ahead of the submission deadline.
• Use plain text in narrative fields and avoid pasting from Word or Google Docs to prevent hidden characters.
• Lock the form only after a deliberate review with the senior rater and the S1 in the loop.
• Keep a local backup of every DA Form 67-10-1 you generate, in case the rater or rated officer needs a reference copy later.