Space Force Evaluation Writing for Guardians

What the GER is and who writes it

The Space Force evaluates Guardians with its own evaluation reports, which grew out of the Air Force system it separated from but are increasingly shaped around the Space Force's mission and culture. Raters write them for both enlisted and officer Guardians.

Because the service is small and highly technical, a Guardian's report is often read by people who do not work the same mission set. That makes translation into plain impact more important than in almost any other branch.

Guardians who move between operations crews, staff jobs, and joint assignments often find that each rater expects something slightly different. Keeping a clear record of results, written in plain and unclassified language, makes it easier to give any rater useful input, and it helps the final report make sense to a promotion board that may not know the mission area.

How Space Force GER writing differs

Space Force writing has a particular problem: much of the work is invisible. Tracking objects, maintaining satellite networks, or defending systems in cyberspace rarely produce a dramatic event. Good statements explain what the work protected or enabled, such as forces that stayed connected or missions that launched on time.

Compared with Air Force EPBs, Guardian statements tend to need more context about the system and its users. Compared with Army or Navy writing, they rely less on people-led numbers and more on readiness, availability, and mission assurance.

Guardians also tend to work on small, specialized crews, so the people-leadership story looks different from a large maintenance or infantry unit. Instead of headcounts, strong statements describe how a Guardian trained a crew, certified operators, or built procedures that others now follow. When a Guardian supports joint or allied partners, naming the type of partner, without sensitive details, shows reach that a board can understand at a glance.

How to use MilPath for your GER

1. In the Bullet Generator, choose Space Force and the Guardian Evaluation Report (GER) format.
2. Pick the section, such as Executing the Mission or Leading People, and choose the rated grade.
3. Describe the work in unclassified terms, focusing on who benefited, then generate.
4. Space Force also offers SPR and ORR formats for other statement types.
5. Review the draft with your rater, and remove anything that should not leave your workspace.

Before and after examples

Illustrative only. All names, units, and numbers are fictional.

• Before: Worked on the ground station.

  After: Restored a fictional ground station antenna 6 hours ahead of schedule, keeping a satellite contact window open for 3 user units.

• Before: Updated training for the crew.

  After: Rebuilt crew training scenarios around 5 new threat profiles; certification pass rate rose from 70% to 95%.

• Before: Did a good job on shift.

  After: Led an 8-Guardian crew through 120 consecutive error-free operations shifts, sustaining coverage for a fictional joint task force.

• Before: Wrote new checklists.

  After: Authored 12 operations checklists adopted by 3 fictional squadrons, reducing crew errors 40% across 6 months.

Tips

• Write at the unclassified level only. Describe effects, not system details.
• Explain who relied on your work: joint forces, allies, or other units.
• Use readiness and availability numbers when people counts are small.
• Keep wording plain; Space Force boards include readers from many career fields.

Frequently asked questions

Does MilPath have a Space Force-specific format?

Yes. The Guardian Evaluation Report format uses Space Force sections and language, separate from Air Force formats.

Can I enter classified details?

No. Never enter classified or controlled information into MilPath or any public tool.

Does it work for officers and enlisted?

Yes. Choose the rated grade that applies and the tone adjusts to it.

Who approves the final statement?

Your rater and the review chain. MilPath drafts are starting points only.