When it comes to travel documents in DTS, an AO — an Authorizing Official — controls the document's status by reviewing, approving, or returning it within the Defense Travel System, and no travel can be ticketed until that approval is recorded. The AO's action moves a document out of "Signed" and into "Approved," or back to the traveler for correction. Until that happens, the document sits in a holding pattern regardless of how complete the traveler's portion looks. In short, the AO holds the gate, and the status you see reflects exactly how far that gate has opened.
What "AO" Means in a DTS Travel Document Status
AO stands for Authorizing Official, the person in the Defense Travel System who reviews a completed travel document and either approves it or sends it back, and that role is what drives every status change on the document. The traveler builds the authorization or voucher, signs it electronically, and then the document routes to the AO for the decision that actually authorizes the trip or the reimbursement.
The status field you see in DTS is not a vague label. It maps to a specific step in the routing chain. "Signed" means the traveler finished and certified the document but the AO has not yet acted. "Approved" means the AO signed off and the document can proceed to ticketing or payment. "Returned" means the AO kicked it back, and the traveler must fix something and re-sign. Each one is a distinct state with its own consequences.
Confusing the AO with the traveler is the most common error. The traveler can sign a document and still not have an approved trip, because signing is the traveler's certification, not the authorization. The AO's separate signature is what unlocks funding and ticketing authority. Mixing these up leads people to assume a "signed" document is ready to travel when it is not.
A third role, the approving official at a higher level or a reviewing official in some organizations, can add another layer in certain commands. But the AO is the core decision point in the standard routing. If you understand what the AO does, you understand the status field.
Reading the DTS Status Field Line by Line
The status field in a DTS travel document tracks the routing chain, and each label tells you exactly who is holding the document and what they must do next. A "Signed" status means the traveler's signature is on file but the AO has not yet acted. It is not an approval, and it does not authorize anything.
"Approved" is the status you want before booking or traveling. It means the AO reviewed and signed, so the document has cleared the authorization gate. Only then does the system treat the trip as officially sanctioned and fundable.
"Returned" means the AO reviewed the document and sent it back, usually because something is missing, wrong, or out of policy. The traveler must correct the issue and re-sign, which restarts the routing. "Cancelled" and "Completed" round out the lifecycle once the trip is over or abandoned.
Read the status as a sentence about location in the workflow. Signed equals "waiting on the AO." Approved equals "cleared." Returned equals "back with the traveler." That mental model prevents most misreads.
| Status label | Who acted last | What it authorizes | Traveler's next move |
|---|---|---|---|
| Signed | Traveler | Nothing yet | Wait for or prompt the AO |
| Approved | AO | Ticketing and travel | Book or proceed |
| Returned | AO | Nothing | Fix the issue, re-sign |
| Cancelled | Traveler or AO | Nothing | Start a new document if needed |
Why the AO's Approval Determines Whether You Can Travel
In the Defense Travel System, the AO's approval is the moment a travel document becomes actionable, because DTS is built to route every authorization through an authorizing official before funds are committed. A signed document that has not been approved is still pending, and booking against it risks a denied or unpaid trip.
This gate exists because the AO is accountable for the funds. The traveler proposes a trip and a cost estimate; the AO confirms it is mission-necessary, within budget, and compliant with policy. That confirmation is what makes the spend legitimate, so the system will not release ticketing authority without it.
Consider a traveler who signs an authorization the night before a trip and assumes they are cleared. The AO has not logged in, the status still reads "Signed," and the travel management company cannot issue a ticket. The traveler shows up at the airport without a confirmed reservation. That failure is entirely a status problem, not a systems problem.
If you see "Signed" and your departure is close, treat it as a red flag rather than a formality. The document is not authorized until the status changes. The practical rule: never book or depart on a signed-but-unapproved document.
How the AO Moves a Document From Signed to Approved
The AO changes the document's status inside DTS by opening the signed travel document, reviewing the details, and applying the approve action, which moves it to "Approved." The steps below reflect the standard DTS workflow, though your organization's menus and permissions may vary slightly by service branch or agency configuration.
1: Log into DTS with your AO credentials and open the document from your inbox or the group's document list. 2: Review the itinerary, cost estimate, and any attachments against policy and mission need. 3: Check for flags, missing receipts, or out-of-policy items that require justification. 4: Apply the approve action to move the document to "Approved," or the return action if corrections are needed. 5: Add any required comments so the traveler knows what to fix or that the trip is cleared.
If the AO finds a problem, the return action sends the document back with the status "Returned," and the traveler must correct it and re-sign to restart routing. Watch for the failure case where an AO approves a document but the funding line is already exhausted — the status reads "Approved," yet payment can still be refused downstream. Approval is necessary, not automatically sufficient, when the budget line is dry.
The Returned Status: What the AO Sending It Back Actually Means
A "Returned" status means the AO reviewed the document and chose not to approve it, sending it back to the traveler, and that status is a request for correction rather than a rejection of the trip. The traveler must identify what the AO flagged, fix it, and re-sign, which sends it back through the routing chain.
Common triggers include a missing justification for a cost that exceeds policy, an itinerary that does not match the mission, absent receipts on a voucher, or a cost estimate that looks unreasonable. The AO's comment field usually says what needs fixing, so read it before guessing.
The cost of ignoring a return is real. Each round trip through the traveler and back to the AO adds time, and a departure date does not move. A returned document one day before travel can leave a traveler without authorization.
If a return happens close to departure, contact the AO directly rather than resubmitting blind. Ask what specifically blocks approval and whether an expedited path exists. The status will not clear on its own.
Signed but Not Approved: The Most Common Status Mix-Up
The single most common confusion is treating "Signed" as if it means "Approved," when in DTS those are two separate statuses held by two different people. The traveler's signature certifies the traveler's own information; only the AO's signature authorizes the trip.
This mistake shows up constantly in practice. A traveler finishes a document, hits sign, sees a confirmation, and assumes they are done. Days later the status still reads "Signed" because nobody forwarded it or the AO has a backlog. The trip is not authorized, and nobody told the traveler.
The fix is a habit, not a technical trick. After signing, check that the document has routed to the AO and watch the status field until it reads "Approved." If it stalls in "Signed," follow up with the AO or your unit's travel coordinator.
Expect a waiting period in normal operations. The AO is often a supervisor with other duties, so approval is not instant. Build that lead time into your trip planning rather than assuming same-day clearance.
When an AO Can't or Won't Approve: Edge Cases and Workarounds
An AO may be unavailable, on leave, or unable to approve for conflict-of-interest reasons, and in those cases DTS routing usually allows a designated alternate or a higher-level official to act. The status stays "Signed" until someone with the authority takes the approve action.
Conflict-of-interest routing is a specific edge case. If the AO is also the traveler — common for senior personnel — the document must route to an alternate approver. The system or your organization's policy handles this, but the status will not advance until the alternate acts.
A backlogged AO is another real scenario. During high-travel periods or absences, documents pile up in "Signed," and travelers who assumed quick approval get stuck. The workaround is early submission and direct coordination with the alternate.
If you cannot get the status to move and your departure is imminent, escalate to your unit's travel coordinator or the DTS help desk for your organization. Do not travel on an unapproved document and hope it resolves. The status is the system's record of authority, and it does not forgive assumptions.
How AO Approval Differs From Supervisor and Reviewer Roles
In many DTS configurations, the AO is distinct from a supervisor or a reviewing official, and each role can affect a document's status at a different stage. The supervisor may review for mission or attendance reasons, while the AO authorizes the funds. A document can pass one and stall at the other.
This layering explains why a document sometimes sits in a status that looks like approval but is not the final gate. If your organization routes through a reviewer before the AO, "Signed" may mean "awaiting reviewer," and the AO has not even seen it yet. The status label alone may not tell you which desk holds it.
The practical implication: know your organization's routing order. A document approved by a reviewer is not authorized for travel until the AO signs. Confirm which signature is the binding one in your chain.
If you are unsure whether your document needs only the AO or also a reviewer, check with your travel coordinator before submitting. Getting the routing right the first time avoids a document bouncing between statuses.
Keeping Your Document From Stalling in a Pending Status
The status field is your dashboard, and the simple discipline of checking it daily after signing keeps a document from silently stalling in "Signed." Most stalled documents are not stuck in the system; they are waiting on a person who has not looked yet.
Submit early. A document signed a week before travel has room for a return-and-resubmit cycle; one signed the night before has none. Build the AO's review time into your planning as a fixed cost, not an afterthought.
Communicate directly when the status does not move. A short message to the AO or travel coordinator asking them to review a pending document is far more effective than waiting. The status will not change without action.
Keep your contact and routing information current in DTS. A document that routes to an outdated supervisor or a deactivated AO account can sit in "Signed" indefinitely. Verify your routing chain before you need it.
What the Status Means for Vouchers After Travel
AO approval applies to vouchers as well as authorizations, and a voucher that has not been approved will not pay, no matter how complete the traveler's portion is. The same routing logic applies: the traveler signs, the AO reviews and approves, and only then does the voucher move toward settlement.
The status mechanics mirror the authorization flow. A signed voucher sits in "Signed" until the AO acts. A returned voucher must be corrected and re-signed. An approved voucher proceeds to payment processing.
Travelers often focus all their attention on pre-trip authorization and forget the post-trip voucher. A voucher stuck in "Signed" is money the traveler has not been reimbursed for, so watch that status just as carefully.
If a voucher is returned after travel, fix the flagged item, attach any missing receipts, and re-sign promptly. The longer a voucher sits in a pending or returned status, the longer the reimbursement waits.
FAQ
Does "Signed" in DTS mean my travel is approved?
No. "Signed" only means the traveler certified the document; the AO has not acted, and nothing is authorized for ticketing or travel until the status changes to "Approved." You should watch the status field rather than the signing confirmation.
Can I travel if my DTS document is still pending AO approval?
You should not. An unapproved document leaves the trip unauthorized and the ticket unissuable, and booking against it risks denial or nonpayment. Get the status to "Approved" before you go.
How long does an AO usually take to approve a DTS document?
There is no fixed interval, because the AO is a person with competing duties and the wait depends on backlog, availability, and your organization's routing order. Submit well ahead of departure and follow up if the status does not move.
What happens if the AO returns my travel document?
The status becomes "Returned," which is a request for correction, not a final rejection. Read the AO's comment, fix the flagged item, and re-sign so the document restarts routing toward approval.
Can someone other than my usual AO approve my document?
Often yes. DTS routing usually supports designated alternates or higher-level officials when the primary AO is unavailable, and conflict-of-interest cases require an alternate. Confirm your organization's alternate-approver path before you rely on it.
Is the AO the same person as my supervisor in DTS?
Not always. Many configurations separate supervisor review from AO funding authorization, so a document can pass the supervisor and still await the AO. Check your routing order so you know which signature actually authorizes travel.
Does AO approval of an authorization also cover the voucher?
No. The voucher routes through its own approval cycle, and a voucher stuck in "Signed" will not be paid. The AO's authorization approval does not automatically approve the post-trip voucher.
Where can I confirm my organization's specific AO routing rules?
Check with your unit's travel coordinator or the DTS help desk for your service branch or agency, since menus, permissions, and routing order vary by configuration. The status field tells you where the document is, but your coordinator confirms who must act next.
This article is general educational information about how the Defense Travel System routes travel documents, and it is not official policy, legal advice, or a substitute for your organization's DTS procedures. Approval authority, routing rules, and status definitions vary by service branch, agency, and local configuration. Consult your unit's travel coordinator, the DTS help desk, or a qualified official for decisions about your specific document, and never treat this overview as authorization to travel or to claim reimbursement.