Nathaniel Pyron on the DD1391: The One-Page Document Behind Every Military Building

Every barracks, hangar, and operations center in the U.S. military began as a piece of paper before it became a building. Not a rendering, not a ribbon-cutting photo — a project data sheet called the DD Form 1391, and it carries more weight than its plain format suggests. Congress authorizes and funds military construction projects on the strength of what that document says. Get it wrong and the project stalls. Get it right and a decade of planning finally becomes concrete.

Nathaniel Pyron, a military urban planner whose professional work centers on the military construction programming pipeline, puts it this way: “The 1391 is the one document where planning becomes a request. Everything before it is analysis. Everything after it is execution. The form sits exactly in between.”

What the DD1391 actually is

The DD Form 1391 — the “Military Construction Project Data” sheet — is the standard document each military service uses to describe, justify, and cost a proposed military construction (MILCON) project. It travels with the project from the installation, through service and Department of Defense review, into the President’s budget submission, and ultimately before Congress, which authorizes and appropriates the money. One form, one project, one ask.

Planners key the project’s data into the service’s programming system — for the Navy, the PAX system populates the 1391 — so that the document the chain of command reviews is consistent, auditable, and comparable with every other project competing for the same limited construction budget. That comparability is the point: the 1391 forces every project, from a fire station to a runway, to make its case in the same format.

Blocks 1 through 8: the project’s identity

The top of the form is identification, and experienced reviewers read it the way a mechanic reads a dashboard. Block 1 names the military department — the Component. Block 2 is the date. Block 3 identifies the installation and its location. Block 4 gives the project title, and Block 5 the program element that funds it. Block 6 carries the category code — the five-digit number from the facility classification system that says exactly what kind of facility the project is, from a maintenance hangar to a dining facility. Block 7 is the project number, and Block 8 states the total project cost.

Nathaniel Pyron notes that these eight blocks are where most misunderstandings start. “A wrong category code misstates what the project is. A wrong project number breaks the link to every other system tracking it. The header looks like clerical work. It is actually the project’s legal identity.” Precision here is not fussiness — it is how a multi-hundred-million-dollar request stays attached to the right project through years of review.

Block 9: the cost story

Block 9 is where the money is itemized: the primary facility, the supporting facilities (utilities, paving, site improvements), the contingency allowances, and the government’s costs for supervision and design. Each line is a claim that must be defensible — reviewers will ask whether the contingency is justified, the supporting facilities are complete, and the estimate reflects the local construction market.

Cost credibility is the planner’s and estimator’s shared responsibility. Professional practice demands real estimating tools — parametric models, engineering estimates, and comparable project data — rather than guesses. A 1391 whose costs cannot be defended is a 1391 that does not survive review, no matter how strong the requirement.

Block 10: what gets built

Block 10 is the description of the proposed construction: the scope, the size, the systems, the standard the facility will be built to — the architect’s summary written for non-architects. It must be clear enough for a budget analyst to see what the money buys, yet specific enough that a designer can build exactly what was promised. Scope discipline lives here: what the form describes is what the appropriation covers.

Block 11: why it must be built

If Blocks 1 through 10 are the what and the how much, Block 11 is the why — the requirement. It lays out the current situation, the deficiency, and the impact if the project is not provided. This is the persuasive core of the document: the mission argument, the readiness consequence, the cost of doing nothing.

“The current-situation paragraph is where the mission either speaks or stays silent,” Nathaniel Pyron says. “Reviewers fund requirements, not wishes. The difference between the two is evidence — documented deficiencies, validated missions, and a straight line from the problem to the proposed solution.”

Block 12: the fine print

Block 12 carries supplemental data: environmental compliance status, the technical reviewer, and the items still to be resolved. It is the honest corner of the form — good 1391s name their open items, because a reviewer who finds a hidden problem trusts the document less than one who finds a disclosed one.

Why it matters beyond the fence line

The DD1391 process is one of the most transparent capital-programming systems in the world: every project makes the same case, in the same format, to the same ultimate approver — the American taxpayer’s representatives. For communities near military installations, the form is the clearest public window into what the base plans to build and why.

Nathaniel Pyron’s view: the 1391 rewards exactly what good planning produces — validated requirements, defensible costs, honest documentation. “The form cannot rescue a bad project, and it does not need to sell a good one. It just asks the same questions of both — and the good projects answer them.”

About the author

Nathaniel Pyron is a military urban planner specializing in military master planning with an airport/airfield focus. A U.S. Navy veteran who served in 1995, he later spent three years as a civilian community planner working with the U.S. Marine Corps at Camp Blaz and Darwin, Australia. He studied at the Arizona State University School of Urban Planning, class of 2007, and is an active LEED AP BD+C. Based in Honolulu, Hawaii, he writes about installation planning, airfield land use, and where military readiness meets community design. His LinkedIn title is Urban Planner (Land Use & Airspace).