What is blocked?
Name the actual systems and transactions that are failing: supply requisition, freight delivery, billing, WAWF/PIEE setup, property accountability, or contract-writing office identity.
!
Start here
The plain-language version.
Everyone tends to overcomplicate this. The whole thing in plain English:
1. Go to DoDAAD Central Service Points (CSP).
2. Find your service's POC for your DoDAAC series. Don't be shy — reach out.
3. If you're CONS (the contracting squadron), tell them you need an FA-series DoDAAC. They'll either find one that already exists for your unit or help you stand up a new one.
4. If you're standing up under a real operation, say so. They'll expedite.
5. Plan on about seven days under normal pace. They'll link you to a page where you fill out the application. That's the whole thing.
What a DoDAAC actually is.
A DoDAAC (Department of Defense Activity Address Code) is the six-character identifier your unit uses to plug into DoD business systems. It's how supply, transportation, finance, and contracting all know who you are. No DoDAAC, no system identity, and every transaction either bounces or has to be hand-walked.
Why this matters once you have one.
Getting your DoDAAC stood up is the gate that opens up the rest of the system stack:
- Contract writing system. You can stop running pure manual contracts. The unit gets an identity that the writing system can issue contracts against.
- EDA (Electronic Document Access). Even your manual contracts can be loaded into EDA so they're in the corporate record where everyone — finance, audit, the next CCO — can find them.
- WAWF (Wide Area Workflow). Electronic invoicing instead of paper invoices chasing finance around the office.
If you can't get one.
Reach back to the NAF (Numbered Air Force). For most Middle East deployments that's AFCENT (Air Forces Central). They can help, particularly with uploading your manual contracts into EDA when you can't do it from where you are. Even with that backstop in place, keep pushing to get your own DoDAAC, and tell your customers (the requiring activities) to apply for one too. Finance — FM (Financial Management) — is critical here as well. They need a DoDAAC of their own, or your invoices have nowhere to land on the system side.
Why this is on the page.
This isn't something most CCOs go through on most deployments. The unit usually shows up with a DoDAAC already and you'd never notice. With the 2026 situation in Iran and SOUTHCOM, more units are setting up at locations that don't have one yet, so it's worth knowing the route. Even more useful: get it set up before you fly. It saves CONS, FM, and your mission partners a lot of pain on day one.
1
Decision rhythm
Move like this: recognize, check first, execute, bring back evidence.
Everything below is the longer version of the plain-language section above. Use it when the CSP comes back with questions, when the request gets bounced for a missing piece, or when you're walking a customer or finance shop through the same path.
New code or update?
Before asking for a brand-new DoDAAC, check whether an existing unit, base, tenant, or parent-code arrangement can support the mission.
Send a usable packet.
Give the monitor/CSP the activity identity, purpose, TAC addresses, effective date, duration, and enough context to prioritize a deployed-unit action.
Close the loop.
Capture the assigned or updated DoDAAC, confirmation message, effective date, authority/purpose limits, and who was told to update local systems.
Source check: DLM 4000.25, Volume 6, Chapter 2 describes DoDAACs as six-character identifiers for activities that requisition, contract for, receive, ship, or fund/pay bills for materials or services. It also states that DoDAACs support acquisition, procurement, contracting, shipping, billing, pay, maintenance, and other DoD business systems.
2
Check first
Decide what problem you actually have before asking for a new code.
Most stalled DoDAAC problems fall into one of three lanes. Pick the lane first, then route the action. That keeps the request from turning into a vague "systems are down" email.
Use or update an existing DoDAAC Often fastest
- The unit is falling in on an existing U.S. location or tenant footprint.
- The parent command already has a supporting activity code.
- Only the TAC 2 freight address, TAC 3 billing address, effective date, or local system profile is wrong.
Request a new DoDAAC Use when needed
- The activity genuinely needs its own identity for requisitioning, shipping, billing, property, contracting, funding, or system interfaces.
- The mission duration and system footprint justify a separate record.
- The monitor/CSP can tie the record to a service/agency owner and authority/purpose limits.
Stop and redirect Wrong lane
- The need is only user access to eDAASINQ or another system, not a new activity code.
- The request is for a contractor DoDAAC. That has a separate PIEE contractor DoDAAC path.
- The request would expose deployed location details outside approved channels.
Use the right phrase from the start. Ask for the "DoDAAC monitor" or "Central Service Point," not "who handles this at the MAJCOM J4." The internal route runs through the unit support chain that owns logistics, resource, supply, or parent-command data. Joint and theater staff can help with operational context like APOD/WPOD or host-nation, but the record itself belongs to the service/agency DoDAAD owner.
3
Working file
Build the DoDAAC request packet like a clean handoff.
The monitor or CSP is the one who can make the official update. Your packet should make the action easy to validate: what activity needs the code, what the code must do, what addresses and authority limits apply, and when the change needs to be effective.
| Packet element | What to send | Why it matters |
|---|---|---|
| Activity identity Unit/activity name, parent command, UIC/PAS or local equivalent, deployed support relationship. | Use the official unit identity and parent organization. Do not invent a temporary name just because the team is forward. | DoDAAC ownership follows the service/agency and delegated record owner. The monitor needs a real activity to attach to the record. |
| Operational need What is blocked today and what systems need the code. | Examples: requisitioning, freight receiving, billing/payment, property accountability, PIEE/WAWF routing, contract-writing office setup. | DoDAAC purpose and authority are not cosmetic. They control what systems can do with the record. |
| Authority and purpose Requisition, ship-to, bill-to, procurement authority, funding office, or administrative use. | State the intended use in plain language. Let the monitor/CSP set the actual authority and purpose codes. | Wrong authority can block transactions or create a fiscal-control problem. Procurement authority deserves extra review. |
| TAC 1 Owner or mailing address. | Provide the correct official mailing identity. If an APO/FPO format applies, use it cleanly and do not blend it with commercial postal lines. | TAC 1 is mandatory. It identifies the owner/mailing information for the activity. |
| TAC 2 Ship-to or freight address. | Provide enough freight detail to move cargo: location, delivery point, consignee support, APOD/WPOD if applicable, and any official routing constraints. | TAC 2 drives freight movement when the activity will receive shipments. For OCONUS records, APOD/WPOD can matter. |
| TAC 3 Bill-to address or payment responsibility. | Identify the responsible billing/payment office or funding/payment relationship through official channels. | TAC 3 supports bill payment. If the activity pays or funds bills, this cannot be guessed. |
| Effective date and duration When the activity needs the record and whether it is temporary. | Give the mission start date, requested effective date, expected redeployment/end date, and a review point for deletion or update. | DLM procedures allow effective-date handling and deletion/inactivation. Temporary deployment records need lifecycle attention. |
| Existing-code check Nearby, parent, host, or prior-rotation DoDAACs considered. | Tell the monitor what you checked and why the existing record does or does not fit. | This prevents duplicate records and helps the CSP choose update versus new assignment. |
| POCs and handling Government POC, support-chain POC, and marking/handling instructions. | Use official email channels. Keep deployed location and operational details inside approved systems and marked as required. | Aggregated DoDAAD data and deployed-location details can be CUI/OPSEC-sensitive. |
Source check: DLA's DoDAAD page identifies TAC 1 as mailing/owner, TAC 2 as freight or ship-to, and TAC 3 as billing. DLM 4000.25, Volume 6, Chapter 2 adds authority-code rules, APOD/WPOD considerations, effective dates, deletion dates, and purpose flags.
4
Friction and safeguards
The problems are predictable. Handle them directly.
DoDAAC work gets messy when people blur ownership, authority, address data, and user access. Cleaner facts and clear stop points fix far more of it than escalating up the chain.
Parent command versus theater
The location may be in a combatant command AOR, but the DoDAAC owner still follows service/agency record ownership and delegated DoDAAD management.
Move: Route through the parent unit support chain to the service monitor/CSP. Use theater staff only for theater-specific address, APOD/WPOD, host-nation, or operational coordination.
Wrong TAC, right code
A DoDAAC can exist and still fail the mission because freight, billing, or mailing details do not match the deployed setup.
Move: Ask for a correction/update when the activity identity is right but TAC 1, TAC 2, TAC 3, APOD/WPOD, or effective-date data is wrong.
Contractor DoDAAC confusion
A contractor DoDAAC is not the same as a deployed unit DoDAAC. DLM procedures point contractor DoDAAC requests through the PIEE contractor DoDAAC request module and contract validation.
Move: If the request is for a contractor, stop the unit-code workflow and send it to the contract/program owner path.
Data handling
DoDAAD data can reveal deployed locations, duty station addresses, operational status, and internal controls. Treat the request packet as operational support data, not a public worksheet.
Move: Keep real addresses, POCs, location details, and system screenshots inside official channels with required markings.
Procurement authority flag
Some DoDAAC records carry purpose flags, including procurement authority. The flag does not create contracting authority; the warrant does.
Move: Route procurement-authority records through the contracting chain and the monitor/CSP so the flag matches a real warrant. Do not request it as a convenience setting.
Processing-time folklore
People may remember a fast contingency turnaround, but a public guarantee is not the same thing as a procedure.
Move: Request priority handling, explain the mission impact, and track the action. Do not promise a fixed short-turn timeline unless your current CSP/local procedure says it.
5
Look it up
Official source anchors and caveats.
Use these links to verify the current path before you send a real request. This page is a training aid, not a substitute for your service's current internal procedure.
DLM 4000.25, Volume 6, Chapter 2
Primary DoDAAD procedure source. Covers DoDAAC/RIC roles, CSP/monitor responsibilities, TAC rules, purpose flags, output, and data security.
AFMAN 23-230
Air Force-specific DoDAAC manual. Describes the Air Force DoDAAC WMS, MAJCOM monitor, SME, and CSP route to establish, change, or terminate Air Force DoDAAC records.
Defense Activity Address Directory
DLA's public DoDAAD page explains what a DoDAAC is, how it is used, and where to find CSP and DoDAAD resources.
DoDAAD Central Service Points
Public CSP listing by DoDAAC/RIC series and service/agency. Verify current Air Force or other service POC before using.
DoDAAD simple search and eDAASINQ
DLA notes that known DoDAACs can be queried publicly one at a time, while broader eDAASINQ access requires a SAR and CAC/PKI.
Israel and CENTCOM
DoD announced the 2020 UCP shift of Israel to CENTCOM AOR in January 2021; CENTCOM assumed responsibility for U.S. forces in Israel on Sept. 1, 2021.
DoD Class Deviation 2026-O0013
Checked because current DoD RFO/DFARS Part 211 purchase-request guidance references DoDAAC verification. It does not govern creating or updating DoDAAC records.
Don't carry these into the packet
There is no public Air Force "contingency W-series" DoDAAC shortcut; W series belongs to Army in the current public CSP listing. There is no published 24-72 hour processing promise; DLM directs CSPs to prioritize deploying units but does not name a fixed turnaround. There is no "DD 448-2 equivalent" form to submit; the current path is the DoDAAD update through your CSP/monitor.
Source-check details and date sensitivity
- Sources were checked on May 20, 2026.
- DLM 4000.25, Volume 6 was published as revised October 03, 2025 in the PDF viewed during this build.
- DoDAAC monitors and CSP POCs can change. The public CSP listing should be checked again before publication or operational use.
- RFO/DFARS cross-check: DoD Class Deviation 2026-O0013 for FAR Part 11/DFARS Part 211 mentions DoDAACs for purchase request numbering and verification, but it does not replace DLM/DAAS procedures for DoDAAC establishment or update.
- This page avoids FAR/DFARS threshold framing. The controlling source for DoDAAC establishment and DoDAAD maintenance is DLM 4000.25, Volume 6, Chapter 2, plus current service/agency supplemental procedures.
- The fictional scenario references Israel only to mirror the training need. Do not include real deployed addresses, POCs, operational names, system screenshots, or aggregated DoDAAD data in public training artifacts.