Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 1368 is one of those instruments: DD Form 1368, Modified Use of Leased Communication Facilities, August 1996, created to Communication Facilities, Modified Use of Leased. The reason it carries a DD number rather than a service designation is structural — the Department maintains a single body of forms for matters that arise identically in every service, so that a record created in one component remains intelligible in another.
The practical effect of Department-level issue is interoperability. not stated establishes the requirement across the Defense enterprise; not stated keeps the document current for all of it. No service maintains its own variant, which means a completed record travels between components — service to agency, agency to joint command — and arrives in a format the receiving office already knows how to read.
You are looking for edition not stated, listed as not stated. Department-wide supersession is a single event rather than a rollout, which is what distinguishes edition currency on a DD form from the same question on a service publication: nobody anywhere is still accepting the previous version out of habit.
The sequence printed on the form is the sequence in which a reviewer will read it, and the two should agree. Header data frames every entry below it; the substantive fields depend on that frame; the certification stands at the end because its whole function is to vouch for what came before. Entries made out of sequence commonly contradict entries made earlier.
Verify the printed edition against not stated first. Field structure shifts between editions, and the office that receives your record is reading the current one. That office may sit outside your service, which removes even the informal accommodation you might expect from a colleague who used the old version last month.
Fill all of it, marking inapplicable items N/A. A record with gaps cannot later demonstrate whether the gap was a decision or an oversight, which is exactly the ambiguity documentation exists to remove. Dates go in the form's own format — on a document that crosses service lines, an ambiguous date is a real hazard rather than a pedantic one.
Where the form collects personal identifiers, a Privacy Act Statement accompanies it, and its placement is meaningful. The statute requires disclosure at the point of collection — authority, purpose, routine uses, and the consequence of declining — so that the person supplying the information does so knowing what becomes of it. Reading it after you have filled the fields inverts the arrangement entirely.
What the signature block asks for is an act, not a text. Ink on a printed copy performs that act; a digital signature bound to your credential performs it electronically, CAC-based in most Defense systems. Typing your name performs nothing, since anyone with the file could type the same characters. Enter the date at the same moment: the certification is a statement about a point in time and needs one recorded.
Recurring defects have a pattern to them, and it is mostly the pattern of a record that cannot be relied on: an edition that does not match, gaps that cannot be interpreted, entries that cannot be read after scanning, dates that could mean two things, and a certification nobody executed. For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
The set published here is PDF, covering 1 pages with roughly 85 fields. More than one format survives because the Department serves users under very different conditions, from a desk with current software to a location where a printer is the only reliable output.
Two states of the same page circulate, and the reason is worth knowing. In the fillable pdf, the boxes are real fields holding real data; in the printable pdf, the boxes are drawings. Where a record will cross components — as Department records regularly do — the typed version is the safer artifact. Each scan, each forwarding, each reproduction costs handwriting a little legibility, and the office that finally files the record is rarely the office that received it first.
What the form asks for
- 1. C S A/Circuit Number.
- 2. C C S D Number.
- 3. Reporting Period.
- 4. Report Control Symbol.
- 5. To. Activity Address: Street, City, State, Zip Code.
- 6. From. Activity Address: Street, City, State, Zip Code.
- 7. Terminal point A.
- Terminal point B.
- 8. Modified use. Press space bar to mark X in first box if outage, second box if overtime, third box if EMC activation, or fourth box if other.
- 8. MODIFIED USE. If marked OTHER, please Specify.
- 9. Time started, line 1 of 10.
- 10. Time Ended.
- 11. Duration: Hours.
- 11. Minutes.
- 12. Reason for modified use.
- 13. Contract Representative.
- 14. Remarks.
- 9. Time started, line 2.
- 10. Time Ended.
- 11. Duration: Hours.
- 11. Minutes.
- 12. Reason for modified use.
- 13. Contract Representative.
- 14. Remarks.
Route the executed form as not stated or local guidance directs, and retain a duplicate first. Cross-component routing is ordinary for DD forms, which is precisely why a personal copy earns its keep: the receiving office may belong to an organization you have no standing to query about a missing document.
When DD Form 1368 cites another form, the citation is self-sufficient. The DD series is a single sequence administered at Department level, so the number resolves to exactly one document without any need to establish which component issued it — a convenience that exists only because the sequence was never allowed to fork.
Where a service form is cited in the same instruction, the two numbering systems should not be read across. DA numbering belongs to the Army and is administered by an Army proponent; DD numbering belongs to the Department and is administered by not stated or an equivalent Department office. The systems developed separately and were never harmonized, so identical digits in each identify two documents with nothing in common. The prefix, not the number, tells you which system you are in.
Understanding why editions change explains why checking them is not optional. Revision follows directive reissue, changes in what data is required, and amendments to mandatory notice text — decisions made at Department level and communicated through publication rather than notification. The file you saved does not update itself, so the edition date at download is what you rely on.
A word on what this page is. It distributes a published Department of Defense document and describes what the document contains and how it is completed. It is not the issuing authority, does not speak for one, and offers no legal advice; nothing written here determines whether a particular submission will be accepted, because that determination belongs entirely to the office receiving it. Questions of applicability, eligibility or procedure go to not stated, to your servicing personnel office, or to the office identified in not stated.
Questions and answers
- What is DD Form 1368?
- DD Form 1368, Modified Use of Leased Communication Facilities, August 1996
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?