Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 2963 is one of those instruments: Service Treatment Record (STR) Certification, created to Service Treatment Record (STR) Certification. 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.
This is why the arrangement matters to you rather than only to the archivists. not stated governs the form throughout the Department, with not stated as the responsible office, so the record you create is legible outside your own component. Joint assignments, agency details and cross-service transactions all depend on that: the paperwork does not have to be reconstructed each time it crosses a boundary.
Current edition: not stated, status not stated. Understand why that date is worth attention here. When the Department reissues a form, the replacement takes effect across every component simultaneously, so an older copy is not merely locally out of date — it is out of date in every office that might receive it.
Work down the page in the printed order, and understand why the order exists. The identifying block establishes whose record this is and under what circumstances it arises. The body of the form then answers questions that are only meaningful once that context is fixed. The signature block comes last because a certification signed before the entries are complete certifies nothing.
Check the edition date before you type anything, against not stated. Old blanks accumulate in shared drives for years, and the cost of one is not obvious until a reviewer cannot find a field. Because DD forms are revised centrally and replaced across the Department in a single action, there is no component still tolerating the old layout as a local practice.
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.
Understand what the Privacy Act Statement is doing on the page. It exists because collecting personal data from an individual triggers a duty to explain the collection: under what authority, for what purpose, to whom the information may routinely go, and whether you are obliged to answer. That explanation precedes the fields for the obvious reason — afterwards it is merely a notice, beforehand it is a basis for deciding.
Signature is the point at which a completed form becomes a certification, and the requirement follows from that. On paper it means ink in the designated block; electronically it means a credentialed digital signature, ordinarily applied with a Common Access Card in software that supports it. A name typed into the signature field is data, not an act — it demonstrates nothing about who entered it. The date beside the signature fixes when the certification was made, which is why a signed but undated block is treated as incomplete.
The defects that return forms are the same ones year after year: a superseded edition, required fields left blank, handwriting that fails on reproduction, dates in a convention the form did not ask for, and certification without a signature or without a date. Where a specific field is genuinely unclear, the instructions printed on the form come first and not stated governs where the two do not agree.
Download the form
Formats available: PDF, across unknown pages and about unknown fields. That several formats coexist is a consequence of scale — the Department cannot standardize the software on every desk that needs this form, so it standardizes the document instead.
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.
Xfdl appears in the set for reasons of institutional inertia rather than preference. It is the IBM Lotus Forms format, once the Department's electronic forms standard and deployed widely enough that it outlived the decision to move on. IBM Lotus Forms Viewer or an equivalent client opens it; a pdf application will not.
All of it downloads without charge. Where care is needed is in the reader you choose. A fillable pdf depends on field properties that desktop applications honour and browser previews frequently ignore, so work locally rather than inside a browser window.
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 2963 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.
It helps to see the DA and DD sequences as what they are: separate registries with separate custodians. One serves a single service under a service proponent, the other serves the Department under not stated or an equivalent office, and neither was ever indexed against the other. A number that appears in both systems points to two unrelated documents, which is why reading the prefix comes before reading the digits.
A form is downstream of the policy that requires it, and revision usually starts there: a directive is reissued, a collection requirement is altered, notice language is updated by statute. The form is republished as a consequence. Since none of that reaches individual users, an archived copy quietly becomes wrong, and verifying not stated each time you download is the whole remedy.
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 2963?
- Service Treatment Record (STR) Certification
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?