How to Complete a Rater Profile Update for a Deployed Rater

A rater profile update becomes important when an Army rater is deployed, changes duty position, or completes evaluations from a location with limited connectivity. The aim is to keep the Evaluation Entry System record aligned with the rater’s actual rating history and profile data. Learn more about Nguynquanghi.com.

This guidance is written for Australian readers who may support U.S. Army personnel, work with multinational units, or manage records while a soldier is posted in places such as Canberra, Sydney, Melbourne, or overseas. The U.S. Army process is separate from Australian Defence Force administration, even where similar performance-reporting terms are used.

Deployment can affect access, dates, signatures, and supervisory relationships. A careful update should therefore be supported by orders, rating-chain information, evaluation records, and a clear explanation of any unusual timing.

Rater Profile Basics

A rater profile shows the evaluations a rater has completed and helps establish the pattern behind performance assessments. It is closely connected to NCOER administration, OER processing, rating history, and the senior-rater profile where applicable.

Before changing anything, identify whether the issue concerns a rater profile, an individual evaluation, a rating-chain change, or a document already filed in iPERMS. These records may interact, but they are not interchangeable.

Record or action	Main purpose	Typical evidence	Common timing
Rater profile update	Correct the rater’s evaluation history or profile data	Approved evaluations and duty records	After a verified change
Rating-chain update	Show who rated, senior-rated, or supervised the soldier	Duty appointment, orders, or command guidance	When responsibilities change
NCOER or OER correction	Fix an error in a specific report	Report copy and supporting explanation	Before or after filing
iPERMS document review	Confirm that the final record contains the right file	Filed document, transfer record, or receipt	After approval or upload

For background on retrieving military documentation, the guide to military records can help distinguish publicly available information from protected personnel records.

Confirm the Correct Evaluation Context

Start by confirming the deployed rater’s name, rank, component, unit, duty title, and inclusive dates. Check whether the rater remained responsible for the soldier throughout the relevant period or whether an interim, supplementary, or alternative rater became necessary.

Deployment alone does not automatically invalidate a rating relationship. The key questions are whether the rater had sufficient observation, maintained a legitimate supervisory connection, and complied with the applicable evaluation policy. A change in location may require coordination, but it does not necessarily require a new profile.

Australian staff should also account for time-zone differences. A rater working in Afghanistan, Europe, or the Indo-Pacific may submit actions while the supported office operates on Canberra, Sydney, or Melbourne time. Preserve the system timestamp and local correspondence rather than rewriting dates to fit local business hours.

Gather Documents Before Accessing EES

Collect the evidence before opening the update screen. This reduces repeated logins and helps prevent a rushed amendment based on memory. Use the latest approved version of each evaluation and compare it with personnel and duty records.

Useful supporting material includes:

• Deployment or temporary-duty orders
• The relevant NCOER, OER, or AER
• Rating-chain approval or duty appointment documentation
• Assignment, relief, or change-of-supervisor records
• System notices, emails, and prior correction requests

Use the EES users guide for navigation and field descriptions, but treat it as general guidance rather than an official Army directive. Policy, command instructions, and the current system interface take priority.

Enter And Validate The Update

Sign in using the authorised account and locate the rater profile or evaluation-management area. Check the profile identifier before editing. Similar names, changed ranks, and concurrent assignments can make it easy to select the wrong record.

Enter only verified information. Pay particular attention to the rating period, rater status, unit, duty position, and relationship to the rated soldier. If the system requests a reason, use a concise factual explanation such as deployment, reassignment, corrected duty title, or delayed administrative processing.

Review the completed screen before submitting. Confirm that the change affects the intended evaluation and does not alter unrelated reports. Save a receipt, screenshot, or transaction reference where policy permits, and record the date in the unit’s administrative log.

Handle Deployment Timing And Access Problems

A deployed rater may have intermittent network access, a restricted workstation, or limited access to a home-station portal. Avoid using personal devices or unapproved networks to handle protected information. If access fails, contact the designated unit administrator or support channel rather than creating duplicate profiles.

When a rater cannot complete an action before a suspense date, notify the chain of command promptly. A short written record should explain the operational reason, the affected evaluation, and the expected next action. This is especially useful when offices in Australia and the United States observe different public holidays or working hours.

Do not treat a forwarded email as a substitute for formal approval. The final action should remain traceable to an authorised official, system transaction, or approved personnel record.

Keep The Record Audit Ready

After submission, compare the updated profile with the evaluation history and the copy stored in the official personnel record. If the report belongs in iPERMS, verify that the correct final document—not a draft, scan of an email, or duplicate page—has been filed.

A practical audit trail should include the original discrepancy, supporting documents, approval authority, submission date, and final result. Store this information according to Army records rules and local privacy requirements. Australian organisations should avoid placing U.S. personnel data in consumer cloud storage or ordinary workplace drives without authorisation.

A useful administrative reference may explain general military paperwork, but unrelated entertainment sites such as this media news site should never be used as recordkeeping or login resources. Bookmark only verified portals and official support pages.

Common Errors To Avoid

Several mistakes can create a second problem while correcting the first. The most frequent are selecting the wrong evaluation, using an outdated rating relationship, or changing dates to make the record appear cleaner.

• Editing a profile without checking the underlying evaluation
• Treating deployment location as automatic proof that the rating relationship ended
• Uploading drafts, duplicate pages, or unsigned copies
• Sharing credentials or protected documents through personal email
• Failing to retain the transaction reference and approval evidence

Before closing the case, perform a final comparison between the system entry, the signed evaluation, and the personnel record. If the three sources disagree, stop and escalate the discrepancy instead of submitting multiple speculative corrections.

Final Review And Record Control

A completed update should leave a clear explanation of what changed and why. The rater’s profile, the relevant evaluation, and the supporting file should tell the same story about dates, duties, and authority.

For Australian-based administrators, good record control also means respecting local privacy expectations, using approved government or defence networks, and allowing for time differences between Australian offices and U.S. Army commands. Keep the process factual, traceable, and limited to the personnel who need access.

Once the correction is accepted, monitor the record long enough to confirm that downstream documents and profile calculations reflect the update. A successful submission is useful only when the authoritative record is accurate.