CSRS & FERS Medical Disability Retirement: Tying Together the Loose Strands

When a medical condition impacts a Federal or Postal employee, whether under FERS or CSRS, and prevents him or her from performing one or more of the essential elements of one’s job, the process of preparing, formulating and filing for Federal Disability Retirement benefits from the U.S. Office of Personnel Management begins.  

One may conceptually distinguish between a “formal” beginning of the process, as opposed to an informal or “real-time” beginning; but in any event, from a retrospective vantage point, it is clear that the “beginning” occurred at that point when the coalescence of medical-to-job impact manifested itself and it became obvious that the Federal or Postal employee could no longer continue in the same fashion as before.  

During this initial part of the process, when the Federal or Postal employee is simply struggling to survive — by going to medical appointments; attempting to continue to work; trying to ignore the reality of the medical condition by striving to perform all of the essential elements of one’s job as before; attempting to maintain the same balance of work-to-personal life, etc. — there is rarely a coordination of efforts, and the disparate strands of life’s compartments never come together in any comprehensible manner.  

But at the “formal” point of preparing and formulating a Federal Disability Retirement application, it is important to engage in the “tying” together of the disparate strands of life — if only to package a cogent and coherent presentation of one’s Federal Disability Retirement application to the U.S. Office of Personnel Management.  

Life may be a series of messes; a successful Federal Disability Retirement application, however, should be a serious compilation of proof, evidence, argumentation and logical structure.

Sincerely,

Robert R. McGill, Esquire

1 thought on “CSRS & FERS Medical Disability Retirement: Tying Together the Loose Strands”

Leave a Reply

Your email address will not be published. Required fields are marked *