How to Contact the EES Help Desk for Technical Support

The U.S. Army Evaluation Entry System (EES) supports the preparation, routing, tracking, and processing of evaluation reports. When the system fails to load, a form will not open, or a report becomes stuck in a workflow, the right support request can save considerable time.

EES Army is an informational resource and is not an official Army government help desk. Soldiers and Army personnel should use authorized Army channels for account assistance, while using general guidance to prepare a complete and useful technical support request.

Before contacting anyone, identify whether the problem is caused by EES, your network, your browser, your account permissions, or a separate personnel records system. That basic distinction helps direct the issue to the correct support office.

Identify The Type Of Problem

Start by recording exactly what you were trying to do. Examples include creating an evaluation, opening an assigned report, signing a document, sending a report to the next participant, or checking the status of a submission. A precise description is more helpful than saying that “EES is not working.”

Separate technical errors from policy or workflow questions. A missing rating chain, an incorrect duty title, or an unclear suspense date may require assistance from your unit S1, administrative section, or rating officials rather than a system technician. Technical support is generally most useful when the application itself produces an error or fails to perform an expected function.

If the issue involves a completed evaluation that cannot be found in your records, check the appropriate records system before opening a support case. This guide to accessing an NCOER through iPERMS can help distinguish a records-access question from an EES workflow problem.

Use Authorized Support Channels

The first contact point is usually the official help or support option available inside the Army system. Look for a help-desk link, support icon, service portal, or contact information displayed after signing in. Official portals may change their contact details, so relying on an old phone number or unofficial email address can delay assistance.

Your unit S1, brigade or command administrative office, and local information technology support team may also help identify the proper escalation path. These offices can often confirm whether the problem affects one user, an entire unit, or a broader service. They may also know whether scheduled maintenance or access restrictions are already being reported.

If you cannot access EES at all, explain that limitation when contacting support. Ask your local administrator which authorized channel should be used for a locked account, missing permissions, certificate issue, or sign-in failure. Do not send sensitive personnel information to an unverified address.

Prepare A Complete Support Request

A strong request gives the technician enough information to reproduce the problem. Include your full name, rank, duty organization, preferred official contact method, and the date and time of the failed attempt. If permitted by your organization, include a callback number and the best time to reach you.

Describe the device and connection used, such as a government computer, approved personal device, installation network, or remote connection. Add the browser name and version, operating system, and whether the problem occurs on another authorized workstation. These details can reveal whether the issue is local or account-wide.

Record the exact error message and the sequence of actions that produced it. A screenshot may be useful, but review it first to remove unnecessary personally identifiable information, report content, Social Security numbers, and other protected data. Include only the minimum information needed to investigate the problem.

Information To Include In An EES Request

Item	What To Provide	Why It Helps
User details	Name, rank, unit, and official contact method	Allows support to identify the account and respond
Time of failure	Date, time, time zone, and frequency	Helps match the event with system logs
Task attempted	Report creation, routing, signing, viewing, or submission	Narrows the affected workflow
Error details	Exact wording, code, and screenshot when authorized	Gives technicians a reproducible symptom
Technical environment	Device, browser, network, and access method	Helps isolate local and system-wide causes
Case history	Previous ticket number or administrator contact	Prevents duplicate troubleshooting

Avoid placing complete evaluation narratives or unrelated personnel documents in an initial message. If support needs a particular record, ask how it should be transmitted through an approved channel. Keep a copy of your original request and any ticket number for future follow-up.

Troubleshoot Before Escalating

Basic checks can resolve temporary access problems. Close and reopen the browser, clear an outdated session, verify that the device has a stable approved connection, and try the system again from another authorized workstation if available. Do not install unapproved software or change security settings to bypass a warning.

If certificates or smart-card authentication are involved, reconnect the card, confirm that the correct certificate is selected, and contact authorized IT support if the device does not recognize it. Account lockouts, expired credentials, and permission problems should be handled through official procedures rather than repeated guessing.

Keep notes on every step you take. If the problem disappears, record what fixed it. If it continues, those notes give the help desk useful evidence and reduce the chance that you will be asked to repeat unsuccessful steps.

Keep Evaluation Work Moving

An EES technical issue can affect rating timelines, signatures, corrections, and submission deadlines. Notify your rating chain or administrative office promptly when a system problem threatens a suspense date. A documented support request may help establish that the delay resulted from an access or system issue rather than inaction.

Some questions concern evaluation content rather than software behavior. For example, uncertainty about how a rater profile relates to an NCOER should be addressed through evaluation guidance, the rating chain, or a knowledgeable administrative adviser. The resource on the rater profile block provides background, but it does not replace official policy or command direction.

Use the following habits when requesting assistance:

• Contact an authorized support channel instead of an unverified third party.
• Provide the exact error, time of failure, device, browser, and network details.
• Remove unnecessary personal or evaluation data from screenshots and attachments.
• Notify the S1 or rating chain when a technical issue may affect a suspense.
• Save ticket numbers, replies, and troubleshooting notes for follow-up.

Follow Up With Useful Records

If the first request does not resolve the issue, reply within the existing ticket or case thread when possible. Restate the original symptom briefly, add any new error messages, and explain which troubleshooting steps have already been completed. Opening several duplicate tickets can make tracking harder.

Escalate through your unit’s established administrative or IT chain when the issue remains unresolved or affects multiple personnel. Ask for the case to be reviewed by the appropriate system owner, rather than forwarding sensitive records broadly. Continue protecting account credentials and never include passwords, PINs, or authentication codes in a support request.

A clear report, authorized contact method, and timely notification to responsible leaders give an EES help desk the best chance to resolve a technical problem before it affects an evaluation deadline. Document the issue today, submit it through the approved channel, and retain the case information until the evaluation workflow is complete.