OPM ORA Digital Retirement Application: How the Online Portal Works

What ORA Changed About Filing

Before OPM launched the Online Retirement Application portal, federal retirement was a paper-and-mail process: you completed SF 3107 by hand, your agency HR assembled the physical package, payroll certified it, and the whole bundle was mailed to OPM's retirement office. Lost mail, illegible handwriting, and multi-week transit times were built into the system.

ORA replaced that workflow. Since OPM declared its "Last Day of Paper" on July 1, 2026, more than 95% of retirement applications are now initiated, completed, and signed digitally through the portal. The result: digital applications average 98 days to adjudication, compared with 156 days for the remaining paper submissions.

But ORA didn't simplify the underlying requirements. The same forms, the same schedules, the same supporting documents are all still required. ORA digitized the transmission, not the substance. And because the portal pre-fills certain fields from agency databases, errors in those databases now propagate directly into your digital application without the manual review step that used to catch them.

How the ORA Process Works

Step 1: HR Initiates Your Case

Your agency HR specialist creates the ORA case in the system. They enter your identifying information, initiate the SF 3107-1 (Certified Summary of Federal Service), and grant you access to complete your sections. You don't initiate the case yourself — it starts with HR.

Step 2: You Complete Your Sections

Once HR opens the case, you log in to complete the sections that require your input: marital status, survivor benefit election, insurance continuation choices, and direct deposit information. The fields map directly to the sections of the paper SF 3107 (Sections A through F).

Pay attention to pre-filled data. ORA pulls information from existing agency databases, which means your legal name, service computation date, and employment history are auto-populated. If any of these are wrong — and they can be, especially for employees with breaks in service or agency transfers — the pre-filled data becomes part of your official application the moment you sign digitally. Review every field as if you were filling it in from scratch.

Step 3: Upload Supporting Documents

Certain documents that historically accompanied the paper package now get uploaded as digital attachments to your ORA case:

• DD-214 (Member Copy 4) for military service
• Marriage certificates and certified divorce decrees
• Military deposit paid-in-full receipts
• RI 20-97 (Estimated Earnings During Military Service)

Use the file formats and size limits shown in your ORA case. Scan quality matters — illegible uploads get flagged during adjudication just like illegible photocopies did in the paper era.

Step 4: SF 3107-2 Handling

If you're married and electing less than the full survivor annuity, the notarized SF 3107-2 (Spouse's Consent) still requires a physical signature from your spouse in front of a notary. Some agencies scan and upload the notarized form; others transmit the original separately. Confirm with your HR office which method they use. The notarization rules — same-date signatures, no corrections, no white-out — apply identically regardless of whether the form enters ORA digitally or on paper.

Step 5: Digital Signature and Submission

You apply your digital signature to finalize the application. This is the point of no return for most elections — particularly the survivor benefit choice in Section D. After signing, your HR office completes Schedule D (the agency checklist), payroll begins generating your Individual Retirement Record (IRR), and the entire package is transmitted to OPM electronically.

Common ORA Mistakes

Trusting pre-filled data without verifying. The most consequential ORA-specific error. If your service computation date is wrong in the agency database, it's wrong in ORA, and it becomes part of your signed application. Verify pre-filled fields against your own eOPF audit.

Uploading low-resolution scans. A DD-214 scanned on a phone camera in poor lighting may be unreadable to the OPM adjudicator reviewing your file. Use a flatbed scanner at 300 DPI or higher for critical documents.

Missing the attachment window. Some agencies set deadlines for uploading supporting documents to the ORA case. If you miss the window, the documents may need to be transmitted separately, which can delay case assembly at OPM.

Not confirming SF 3107-2 transmission method. Whether the notarized original is scanned into ORA or mailed separately varies by agency. If your HR office mails it and you assume it was uploaded, your case may sit incomplete at OPM without either side realizing.

What ORA Doesn't Do for You

ORA handles the transmission and signature workflow. It does not:

• Audit your eOPF for completeness
• Verify that your military deposit was paid
• Check whether your FEHB enrollment meets the five-year continuity rule
• Calculate whether postponing retirement would increase your annuity
• Confirm that your SF 3107-2 notarization meets formatting requirements

These are all things you need to verify independently, before you reach the digital signature step. Once you sign, the application enters the processing pipeline, and corrections require a separate correspondence cycle that adds time to adjudication.

Prepare Before You Sign

The FERS Retirement Application Guide provides a pre-ORA checklist — a document-by-document verification sequence designed to catch errors in pre-filled data, confirm supporting documents are scan-ready, and verify that your service records match what the portal will pull from agency databases.

See more United States guides →