Modification work orders (MWOs), explained

A modification work order (MWO) is the Army publication that contains the technical requirements to carry out a mandatory modification to equipment. AR 750-10, Army Modification Program, dated April 29, 2026 and effective May 29, 2026, sets the policy and superseded the edition of October 23, 2019. The Army Publishing Directorate record shows a change dated July 14, 2026, which moved proponency from the Deputy Chief of Staff, G-4 to the Assistant Secretary of the Army for Acquisition, Logistics and Technology (ASA(ALT)). The core rule: no equipment may be modified before the MWO is published.

What counts as a modification

AR 750-10 defines a modification as any alteration, conversion, or modernization of an end item or a component that changes or improves its original purpose or operational capacity. The list includes retrofits, software revisions, and service life extension programs. Adding only a label or data plate is not a modification.

The usual starting point is an engineering change proposal (ECP). For fielded items, a Class I ECP, which affects form, fit, or function, must be developed into an MWO, or into a software change package if only software changes. Class II ECPs do not generate an MWO.

Kits and applications come at no cost to the user. An item the Army plans to retire within five years after the modification is complete may not be modified, except for safety modifications or changes costing less than $100,000. Other exceptions need the Secretary of the Army.

Three priorities

Paragraph 3-6 classifies every MWO:

• Emergency. All affected equipment is deadlined at once and reported not mission capable (NMC) until corrected. The Deputy Chief of Staff, G-8 approves emergency MWOs.
• Urgent. Applied within 2 years of the MWO effective date. Equipment not modified by then is reported NMC.
• Routine. Applied within the stated timeframe, which cannot exceed 5 years. An unapplied routine MWO does not make equipment NMC.

DA Pam 738-751, the aviation records pamphlet of February 28, 2014, carries these priorities into aircraft status. Receipt of an emergency MWO is a grounding X condition. A routine MWO overdue for application takes a dash, the symbol for unknown condition.

AR 750-10 lists safety-of-flight and aviation safety action messages among the sources of modifications, and implementing a safety message is one of the nine objectives an MWO may serve. The post on those messages covers how they are issued and logged.

Approval, numbering, and release

The materiel developer, the office responsible for the system, convenes a configuration control board to review a proposed modification. If the board approves it, the life cycle management command (LCMC) MWO coordinator assigns a materiel change number (MCN), and the publications control officer assigns the MWO number. The MCN is a nine-digit number that never changes. The first digit names the developer (1 for the Army Materiel Command), the next two the fiscal year, the next two the equipment category (01 for aircraft), and the last four the modification. The MWO itself is prepared to MIL-PRF-63002.

The developer builds a fielding plan on DA Form 7591. A fielding release board, chaired by the LCMC MWO coordinator, is the approval authority to release the MWO, and DA Form 7592 records concurrence, with a safety signature from the LCMC safety office.

DA Pam 25-40, dated February 1, 2024, numbers an MWO the same as its equipment technical manual (TM) plus a series number. The two-digit level shows the lowest maintenance level allowed to apply it. The directorate's MWO index lists, for example, MWO 1-1520-240-20-1, dated July 3, 2014, for replacing a control unit, listed as DECU/ECU, on CH-47D helicopters. The two documents differ on approval. DA Pam 25-40 (2024) requires G-4 approval of every MWO before publication; AR 750-10 (2026) names the G-8 for emergency MWOs and the release board for release.

Applying and recording

Only teams the developer designates apply MWOs, barring a field-application exception such as low risk, a developer-funded kit, and no special tools. Every application is recorded in the Modification Management Information System (MMIS), even when no kit is needed. The record includes the MCN, MWO number, serial number, date applied, and man-hours. Unit commanders must ensure all MWOs are applied to their equipment and recorded.

For aircraft, under ATP 3-04.7, the October 2020 aviation maintenance publication, technical inspectors enter each MWO that applies to an assigned aircraft on DA Form 2408-5, the Equipment Modification Record. Sustainment-level activities, such as contract field teams or Corpus Christi Army Depot, normally apply aircraft MWOs and complete the entry. An MWO not applied by its date goes on DA Form 2408-13-1. DA Pam 738-751 calls DA Form 2408-5 the only historical record that shows an aircraft's current MWO status, and says not to destroy it.

How an MWO changes the manual

AR 750-10 requires changes to be incorporated into the appropriate TMs and software user manuals. The developer documents every kit change, including TM updates and repair parts. Spares and supporting test equipment are modified along with the end item. DA Pam 25-40 adds that a TM change sent for publishing while the MWO is in work should be published as close as possible to the MWO effective date. Each MWO must show data plate or decal locations, so inspectors can confirm it without taking the equipment apart.

In a General Accounting Office (GAO) report of October 1997, maintainers at Fort Hood and Fort Campbell said TM updates came out only yearly. A Fort Campbell aviation maintenance officer described a July 1996 Apache fuel subsystem modification that arrived without a revised parts manual. The aircraft was grounded, and maintainers lost many hours troubleshooting because the old manual did not show the new fuel transfer valve. GAO counted 95 Apache MWOs approved since 1986.

What to check

• Is there a published MWO for the change, as AR 750-10 requires before any modification?
• What are the MWO's priority and effective date, and has an urgent MWO passed its 2-year window?
• Does the MWO number match the equipment TM, and does the MCN carry category 01 for an aircraft?
• Was the application recorded in MMIS and, for an aircraft, on DA Form 2408-5?
• Did the TM change, parts list, and test equipment update arrive with the kit?

Azcuna's TRACE is one offline viewer for S1000D, MIL-STD-3001 XML, and PDF technical manuals. It keeps the source location and the markings of everything it shows and never modifies the source. It was proposed to NAVAIR under Navy SBIR Phase I topic DON26BZ05-NV078, and the proposal was submitted on September 23, 2026.

Sources

1. 1AR 750-10, Army Modification Program · Headquarters, Department of the Army, April 29, 2026 (administrative revision July 14, 2026)
2. 2Record Details for AR 750-10 · Army Publishing Directorate
3. 3DA Pam 25-40, Army Publishing Program Procedures · Headquarters, Department of the Army, February 1, 2024
4. 4Modification Work Orders · Army Publishing Directorate
5. 5DA Pam 738-751, Functional Users Manual for the Army Maintenance Management System-Aviation · Headquarters, Department of the Army, February 28, 2014
6. 6ATP 3-04.7, Army Aviation Maintenance · Headquarters, Department of the Army, October 20, 2020
7. 7GAO/NSIAD-98-14, Army Equipment: Management of Weapon System and Equipment Modification Program Needs Improvement · U.S. General Accounting Office, October 10, 1997

Where this shows up in our work

• TRACE, the offline S1000D and IETM viewer opens S1000D, MIL-STD-3001 and PDF technical manuals on a tablet with every marking intact.
• ELLMENT, the offline LLM for E-2D crews answers a crew's question from the aircraft's own manuals and cites the page, with no network.