An Army Memorandum for Record (MFR) is a formal document used by the military to record significant events, decisions, or actions. It serves as a permanent record and can be referenced in the future for historical purposes or to resolve disputes. Understanding how to write and use an MFR is crucial for anyone serving in the military or working with military documents.

In this comprehensive guide, we will delve into the world of Army MFRs. We will explore what they are, when to use them, how to write them, and provide examples to illustrate key points. By the end of this article, you will have a solid understanding of Army MFRs and be able to create and use them effectively.

Understanding Army Memorandums for Record
Before we dive into the details of writing an MFR, let's first understand what they are and why they are important.

An MFR is a formal, written record of an event, decision, or action taken by an individual or organization within the Army. It is not a command or an order, but rather a record of what has occurred. MFRs are used to document significant actions, to provide a historical record, and to resolve disputes or answer questions in the future.
Purpose of Army MFRs

Army MFRs serve several purposes. They are used to:
- Document significant events, decisions, or actions.
- Provide a historical record of activities and decisions.
- Respond to Freedom of Information Act (FOIA) requests.
- Resolve disputes or answer questions about past actions.
- Meet legal or regulatory requirements.
When to Use an Army MFR

An MFR should be used whenever there is a need to document a significant event, decision, or action. This could include:
- Decisions that have a significant impact on personnel or operations.
- Actions that deviate from standard procedures or policies.
- Incidents or accidents that result in injury, damage, or loss.
- Decisions that involve the use of discretion or judgment.
Writing an Effective Army Memorandum for Record

Now that we understand what Army MFRs are and when to use them, let's discuss how to write an effective MFR.
Writing an MFR involves several steps. Here, we will outline the key components of an MFR and provide tips for writing each section.




















Header Information
The header of an MFR should include the following information:
- To: (The recipient of the MFR)
- From: (The author of the MFR)
- Subject: (A brief description of the event, decision, or action)
- Date: (The date the MFR is written)
- File Reference: (A unique identifier for the MFR)
Body of the MFR
The body of the MFR should provide a clear and concise description of the event, decision, or action. It should include:
- A brief summary of the event, decision, or action.
- Background information that provides context.
- Factual details about what occurred.
- Any relevant policies, procedures, or regulations that were followed or considered.
- Any discretion or judgment that was exercised and why.
- Any follow-up actions that are planned or required.
Signature
The MFR should be signed by the author. This serves as a certification that the information in the MFR is accurate and complete.
Army Memorandum for Record Examples
Now that we have discussed the purpose and components of an Army MFR, let's look at some examples to illustrate these concepts.
Example 1: Documenting a Decision
This example shows how an MFR can be used to document a decision to cancel a training exercise due to inclement weather.
TO: Commander, 1st Battalion, 5th Infantry Regiment
FROM: Executive Officer, 1st Battalion, 5th Infantry Regiment
SUBJECT: Cancellation of Training Exercise 'Iron Hawk'
DATE: 12 March 2023
FILE REFERENCE: 2023-03-12-MFR-001
1. On 12 March 2023, I made the decision to cancel Training Exercise 'Iron Hawk' scheduled for 13-15 March 2023 due to forecasted inclement weather.
2. The exercise was planned to include live-fire training and field maneuvers. The forecast calls for heavy rain and thunderstorms, which would make these activities unsafe and impractical.
3. I considered the safety of our personnel and the potential damage to equipment as my top priorities. I consulted with the Operations Officer and the Safety Officer, and we agreed that cancellation was the best course of action.
4. I have informed all participating units and will reschedule the exercise at a later date.
5. This MFR is being filed in accordance with AR 25-50, paragraph 3-12.
Executed this 12th day of March, 2023
Lieutenant Colonel Jane Doe
Executive Officer, 1st Battalion, 5th Infantry Regiment
Example 2: Documenting an Incident
This example shows how an MFR can be used to document an incident involving a vehicle accident.
TO: Commander, 1st Brigade, 1st Infantry Division
FROM: Safety Officer, 1st Brigade, 1st Infantry Division
SUBJECT: Vehicle Accident Involving HUMVEE U12345678
DATE: 20 February 2023
FILE REFERENCE: 2023-02-20-MFR-002
1. On 20 February 2023, at approximately 1400 hours, a HUMVEE (U12345678) assigned to Charlie Company, 1st Battalion, 5th Infantry Regiment, was involved in an accident while traveling on Route 66.
2. The vehicle was driven by Sergeant John Smith, who was the only occupant. He was transported to the nearest medical facility with non-life-threatening injuries.
3. The accident occurred when Sergeant Smith attempted to avoid a deer in the roadway. He lost control of the vehicle, which left the roadway and rolled over.
4. I have initiated an investigation into the cause of the accident in accordance with AR 15-6. I will provide a follow-up report upon completion of the investigation.
5. This MFR is being filed in accordance with AR 385-10, paragraph 4-1.
Executed this 20th day of February, 2023
Major Robert Johnson
Safety Officer, 1st Brigade, 1st Infantry Division
In the dynamic and complex environment of the Army, effective communication is crucial. Army Memorandums for Record play a vital role in this communication, ensuring that important information is documented, accessible, and usable. By understanding and effectively using MFRs, you can contribute to the smooth operation and success of your unit and the Army as a whole.