Completing the AF Form 910

Before you begin writing the EPR, you need the RIP (short for Report on Individual) as a reference. In most cases, RIPs are generated and delivered to your office through distribution 60 days prior to the closeout date of a performance report. But occasionally the system fails and you have to request it. If you need a RIP for a report, contact the CSS. Provide the CSS with the ratee’s name, SSN, the closeout date of the report, and the reason for the report. If the report is a CRO report, then provide the name and SSN of the new supervisor.

Writing Effective Performance Reports

Writing effective performance reports comes down to one thing: good writing. It requires the use of hard-hitting, fact-filled words and statements that paint an accurate picture of the ratee in the mind of the reader. It is important that performance reports “come alive” to the reader and contain meaningful information about the ratee’s technical and managerial skills. Critical facts, specific achievements, and performance-based potential must be easily identified by the reader.

The worst and most common error made by rating officials is to write comments so ambiguous, technical, or specialized that people reading the reports don’t understand the significance of what is written. Many performance reports are so full of such comments they become ineffective. Meaningful EPRs contain the following characteristics:







Clarity. Your objective is to inform the reader about the ratee’s job performance and potential. Avoid unique acronyms and terminology. Describe the impact in clear, concise sentences. Use language that is alive, informal, and illuminating. Write to communicate, not to impress.







Credibility. Avoid exaggerations. For example, claiming someone is the “best in the Air Force” is probably an exaggeration if the person hasn’t won an Air Force-level award. Statements like this sound great, but reduce the rater's credibility, making the entire report suspect. The challenge is to express your estimation of the ratee without exaggeration using reasonable, believable descriptions of the ratee’s performance.







Composition. Making someone's performance “come alive” through effective writing is achieved when the reader automatically forms a mental image from your words and piques his interest to continue reading the report.













SECTION I RATEE IDENTIFICATION DATA



See EPR notice for ratee identification data. If any data is incorrect, notify the CSS and MPF for computer correction. Abbreviations may be expanded for clarity.



Block 1. Name. Enter last name, first name, MI, and Jr., Sr., etc. If there is no middle initial, use of “NMI” is optional. The name may be all upper case or a combination of upper and lower case.



Block 2. SSN. Enter SSN.



Block 3. Grade. Enter appropriate grade.  If the member is: 






    

  • a. On AD, enter the grade held on the close-out date.

  • b. On EAD under Title 10 U.S.C. 12310 (AGR program), also enter “AGR”.

  • c. Non-AD, enter the grade he or she served in on the report's close-out date and also enter “Non-EAD”.

  • d. On Active Guard/Reserve tour, enter “AGR”.

  • e. On limited EAD tour (Title 10 U.S.C. Section 12301 (d)), enter “LEAD”.










Block 4. DAFSC. Enter DAFSC held as of the “THRU” date of the report, to include prefix and suffix (if applicable).



Block 5. Organization, Command, Location, and Component.  Enter information as of close-out date. Nomenclature does not necessarily duplicate what is on the EPR notice. The goal is an accurate description of where and to whom the member belongs on the report close date.  Use the guidance below:






    

  • a. Enter the organizational designation, MAJCOM, and location (if classified, enter “Classified” in place of organization).

  • b. If the command assignment is an integral part of the organization name, such as "AMC/DP," it’s unnecessary to repeat the command (AMC) within parentheses.

  • c. If the ratee is assigned to one location but performing duty at another, enter assigned information followed by organizational designation, command, and location where duty was actually performed, such as: HQ AFPC Randolph AFB TX w/duty at Air Force Human Resources Lab (AFMC) Brooks AFB TX.





Block 6. PAS Code.  Enter PAS code for ratee’s unit of assignment as of close-out date.



Block 7. SRID.  Enter Senior Rater ID (SRID) for ratee’s unit of assignment as of close-out date.



Block 8. Period of Report. Enter day following the last report’s close-out date. Use the date on the EPR notice or see guidance below to determine the close-out date. If the member is: 






    

  • a. On AD or non-AD, and has a previous report on file, use the day following the close-out date of the previous report.

  • b. On AD but has not had a previous report on current AD tour, use the day of entry/reentry on AD (the EAD date in the PDS).

  • c. Non-AD and has not had a previous report, use the date of assignment to the Reserve or DOR to SSgt, as applicable.







THRU Date: Use the date on the EPR notice.  To determine the close-out date, if the reason for the report is:






    

  • a. Annual, use the date one year from the close-out of previous report, or:



    

   
      
   
    • (1) If needed, adjust the close-out to the date on which the rater achieves the number of days of
   supervision or points required by Table 3.1. or Table 3.2., as appropriate.
   
    • (2) If one year has already passed and a CRO is processed before the rater achieves the minimum
   120 days of supervision, adjust the close-out to the date prior to the CRO effective date, provided
   the rater has completed at least 60 days supervision.
   
    • (3) If the member is non-AD USAFR who has not had a previous report, and the “FROM” date is
   the member’s DOR to SSgt, the thru date will be two years from the DOR to SSgt (i.e., DOR and
   “FROM” date is 1 May 96, then “THRU” date will be 1 May 98).
   
    • (4) The date approved by the appropriate waiver authority per a request for an extension of the
   close-out date.
   
    



    


  • b. CRO (including events of emergency or no-notice departure), use the day before the effective date of change, or:
      
      
      
    • (1) If the report is mandatory as a result of pending separation, retirement, or PCS of the rater, or
      PCS or separation of the ratee, use the date 30 calendar days before the rater’s or ratee’s projected
      departure date, or:
          
        
          
      • (a) If the 30-day Rule will cause a ratee to be ineligible for a report due to lack of supervision,
          adjust the close-out to the date within the 30-day window on which the rater completes 120 days
          of supervision.
          
      • (b) If the ratee is non-AD, adjust the close-out date within the 30-day window to the date the ratee
          completes the minimum 16-point requirement.
          
      • (c) To record significant events, use the adjusted date (within the 30-day window) approved by
          the commander.
     
      
   
    



    


  • c. Directed by (HQ USAF or Commander [MAJCOM, wing, group, squadron], as appropriate), then use the date:


      

    • (1) As specified in the message directing the report.

    • (2) The ratee was placed in MIA, captured, or detained in captive status.

    • (3) One day before being placed on the control roster if the report is directed as a result of placement on the control roster.

    








NOTE: Never close a report out on or after the actual departure, retirement, or separation date of the rater
or ratee. If a departure, separation, or retirement date changes after establishment of the “THRU” date of
a report, it is not necessary to adjust the close-out date if it is no more than 40 days before the actual
departure date, unless the change causes the number of days of supervision to meet or exceed the specifications
of Table 3.7. and Table 3.8. Reports prepared and accepted for file under the CRO rule remain
valid even if the condition is later canceled.







Block 9 No. Days Supervision.  Enter number of days ratee was supervised by rater during reporting period.  If the report is being written by the rater’s rater, enter number of days the evaluator had written or personal knowledge of the ratee's duty performance during the reporting period. For non-AD USAFR personnel promoted to SSgt, compute period of supervision for their first report as a SSgt from ratee’s date of rank as a SSgt.







a. Deduct all periods of 30 or more consecutive calendar days during which the ratee did not perform
normal duties under the rater's supervision because either the ratee or the rater was TDY, on
leave, in patient status, in classroom training (such as attending PME at home station), AWOL,
Dropped From Rolls, or in confinement. This deduction period does not include periods of loan
to another section or organization when authorities do not change the rater or publish TDY orders.


b. If the ratee or rater normally performs TDY in order to fulfill duties, do not deduct those periods
of TDY (For example: inspector general team members, cable installers, combat communications
personnel, etc.). Unit commanders are in the best position to determine if their unit members
meet this criterion.




Block 10. Reason For Report.  Enter reason for the report from EPR notice or as determined by AFI 36-2406 Table 3.7. (active duty) or Table 3.8. (AF Reserve)




Choices are:

-Initial

-Annual

-Change of Rating Official (CRO)

-Biennial (for AFR Non-Active Duty)

-Directed by Commander

-Directed by HQ USAF









Next Page