Every entry on DA Form 7273 exists because a record system needs it in writing. The form's official title is ACCESS AGREEMENT FOR ORAL HISTORY MATERIALS, and it is raised whenever an office must access agreement for oral history materials in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 05/01/2015, status ACTIVE, is what stands here, spread across 1 page(s) and about 54 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give. A later edition has since been published, which is why this one remains: records executed against it must still be readable in the terms they were written.
Two offices stand behind the form, and the distinction between them explains most of what follows. AASA is the proponent: it decides what the form asks and revises it when the underlying process changes. AR 870-5 is the prescribing authority: it decides when the form is raised at all and where the completed document travels. Content and occasion are separated deliberately, so that a change in procedure does not require redesigning the page.
Identification precedes substance for a structural reason. Name, identification number, organisation and date of preparation are how the finished document is located in a file or a database; the body of the form is what someone reads after the search has succeeded. Spell the name as official records spell it, since the search runs against those records and not against habit.
The rules of entry all trace back to the page being fixed in advance. Tabbing follows the order built into the form, which usually matches how the page reads and misses less than clicking. An exclusive group discards the earlier selection because contradictory entries would make the record unusable. One-line fields have no wrap because print positions are predetermined, so an overlong entry displays fully and prints truncated. Longer text goes to the remarks area or a continuation, both provided for exactly that. Where nothing applies, the nil mark is entered — a blank leaves the reader unable to tell a considered answer from a skipped one.
A signature is what converts entries into a record, which is why it comes last and why an unsigned form remains a draft however complete it looks. Where a reviewing official, an approving authority or a witness also signs, each adds a distinct attestation, and each dates the day of signing rather than the day of preparation — the dates trace the sequence of responsibility. The recurring defects are worth knowing precisely because they defeat that purpose: an empty mandatory field leaves an obligation unmet, transposed identification digits attach the record to nobody, a date with day and month reversed puts events in the wrong order, and entries left in a reused working copy assert facts nobody intended.
Personal information may not be gathered silently, and the Privacy Act statement is how that obligation is met on paper: it names the collection authority, the purpose, the routine uses and whether disclosure is mandatory. Because it exists to inform a decision, it belongs before the fields it covers rather than after them. A filled copy then holds personal data and is stored and transmitted under the corresponding safeguards.
Download the form
Why several files for one page? Because the form has to be completed in a headquarters and in places without a workstation, and PDF, XFDL covers both. The fillable pdf holds interactive fields that fix each entry in place and remove handwriting from the equation. The printable pdf is the same layout without those fields, meant for a printer and a pen. Neither is a lesser copy of the other; each answers a condition the other cannot.
Where a file opens matters more than it appears to. A browser will display a pdf, but browser viewers were built to read documents, and some accept keystrokes into fields they never intended to store — the entries are gone at tab close, without warning, because saving was never part of what that viewer does. A dedicated reader is built around the file's own structure and keeps what you enter. The xfdl file belongs to a different lineage entirely: IBM Lotus Forms, adopted across Army systems for the routing and signature handling built into it. That is why only the Lotus Forms Viewer reads it.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- ACCEPTED
- ContentArea1
- DATES
- DATE_A
- DATE_B
- FROM
- L10
- L11
- L12
- NAMEAGEN
- NAMEINTER
- PARTICIPAT
- Page1
- PageArea1
- T14
- T15
- T16
- T17
- T18
- T19
- T20
- T21
- T22
- T23
Where the signed form goes is settled by AR 870-5 rather than by the office holding it — a named recipient, the unit administrative channel, or the individual's own file, depending on why it was raised. Retention likewise belongs to the records schedule for the series, which exists so documents are kept for as long as anyone might need them and no longer. Keep a copy before release; the original serves the file from then on, not you.
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.
An edition marks the form at a point in a process that keeps moving, and the date printed on the page is what distinguishes one from another. Since a saved file never announces its own obsolescence, compare its date against the current edition before using it again. Prior executions remain valid: the change applies forward, and a record is read against the edition it was written under.
It is worth being plain about what this page is within all of the above. The files are reproductions of published Department of the Army documents, offered for download by a site with no official standing and no part in issuing anything. That matters because the machinery described here — proponency, prescribing directives, records schedules — runs entirely elsewhere. Nothing written here is legal advice, and no statement can be made about whether an office will accept a given document. AASA and the administrative office servicing your unit answer questions of entry, requirement and eligibility, and they are the ones positioned to.
Questions and answers
- What is DA Form 7273?
- ACCESS AGREEMENT FOR ORAL HISTORY MATERIALS
- Which edition is current?
- 05/01/2015
- Who is responsible for this form?
- AASA
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 14-REQUIRES PRIVACY ACT STATEMENT (AR 340-21)
- 42-ITEM ONLY PRODUCED IN ELECTRONIC MEDIA,