Administrative documents are written for readers who were not present, and DA Form 4322 is no exception. Titled ARMY OFFICER CANDIDATE CONTRACT AND SERVICE AGREEMENT, it is used to army officer candidate contract and service agreement — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date June 2001 and the status not stated. Its 1 page(s) and roughly 78 fields are sized to what the record must prove years later, which is always more than the moment appears to need.
Behind any Army form sit two separate decisions. What the document asks is settled by DCS, G-1, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 350-51. That division is the reason a form can outlive several changes in the process it serves.
Retrieval governs the order of entry. The head of the form takes name, identification number, unit and date, and those values become the handles by which the record is found later — the substantive blocks are never searched on. This is why the spelling must match official records exactly rather than approximately.
Tab order is not a convenience feature; it was fixed when the form was built and generally traces the page, so following it produces the sequence the designer intended and leaves fewer gaps than a mouse. Exclusive option groups clear the previous selection because the record is not permitted to hold two contradictory answers. Single-line fields do not wrap for the same reason the layout is fixed: the printed page has to fall in known positions, so text past the field width is cut at the margin even though the screen still shows it whole. Overflow belongs in remarks or on a continuation, where there is room designed for it. And an inapplicable field is marked rather than skipped, since a blank tells a later reader nothing about whether the question was considered.
Signing is the act that makes the document evidence, and until it happens the entries are only a proposal. Additional signatures — reviewer, approver, witness — each stand for a separate judgement, dated when applied so the record shows who accepted what and in what order. The common faults all damage that record in the same way: a blank mandatory field breaks the chain of required answers, swapped digits in an identification number detach the document from its subject, an inverted day and month misplaces it in time, and stale data from a reused copy states things nobody meant to state.
Behind the Privacy Act statement is a requirement that anyone asked for personal data be told, in advance, under what authority it is sought, for what purpose, who else routinely sees it, and whether refusal is possible. Reading it after completing the fields defeats its function. And the completed form is itself a personal record from that point on, subject to the handling rules such records carry.
Download the form
The published formats — PDF — reflect the range of places a form gets filled in. Where there is a computer, the fillable pdf supplies live fields that keep entries positioned and readable. Where there is not, the printable pdf gives the identical page as flat artwork for pen entry. The distinction is one of setting rather than of authority; the page is the same document in both.
The choice of application decides whether your work survives. Browsers render pdfs as documents to be read; where a viewer shows fields without a mechanism to store them, typed text disappears when the tab closes, and nothing announces the loss. A full reader treats the file as a form and preserves entries on save.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- BLANK
- CURRENT
- ContentArea1
- DATE
- DATE_A
- NAME
- Page1
- R67
- R68
- R69
- R70
- R71
- R72
- R73
- R74
- R75
- Rectangle1
- SIGN
- SSN
- Sign1
- T10
- T12
- T13
- T14
The routing in AR 350-51 decides where the document goes — a named office, the administrative channel, or the individual's file — and the records schedule for the series decides how long it stays. Neither is a local judgement, because a record system loses its meaning if each office keeps things for its own preferred interval. Copy the form before submitting it.
Series and number are how the DA series signals which documents belong together, and the grouping follows real process boundaries: a shared proponent or directive usually means a shared purpose. A form cited on the face of another is part of that same transaction, and continuation sheets, covers and transmittals complete it.
Editions change because the process changes, and the printed edition date is the only marker of which version a page belongs to. A copy saved locally cannot know it has been superseded, so the date on it is compared against the edition in force before reuse. Records already executed under an earlier edition are left alone — a document is read under the terms it was made, and reopening completed files to match a later form would falsify the account.
A word on where this page sits. These are reproductions of published Department of the Army documents, made available by an independent site with no official role and no authority to issue forms. The structure described above — proponent, prescribing directive, records schedule — exists apart from this site entirely, which is why nothing written here is legal advice and why acceptance by any office is not something that can be promised. Put questions of entry, requirement or eligibility to DCS, G-1 or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 4322?
- ARMY OFFICER CANDIDATE CONTRACT AND SERVICE AGREEMENT
- Which edition is current?
- June 2001
- Who is responsible for this form?
- DCS, G-1
- In which formats can it be downloaded?