Every entry on DA Form 4790 exists because a record system needs it in writing. The form's official title is CERTIFICATION FOR DISTRIBUTION OF PUBLICATION(S) IN SUPPORT OF GOVERNMENT CONTRACT, and it is raised whenever an office must certification for distribution of publication(s) in support of government contract in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 06/01/2021, status ACTIVE, is what stands here, spread across 1 page(s) and about 108 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.
Behind any Army form sit two separate decisions. What the document asks is settled by CIO, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by PAM 25-38. That division is the reason a form can outlive several changes in the process it serves.
The heading blocks come first because the record is retrieved by them, not read into. Name as official records spell it, identification number, unit, date of preparation — those four are the index, and everything below them is content that only surfaces once the index has done its work. A form filed under a name written casually is not lost in principle, only in practice, which amounts to the same thing.
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.
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.
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
Formats exist because completion happens under different conditions, not because anyone wanted variety. The published set is PDF, XFDL. A fillable pdf carries live entry objects, so typed text lands in fixed positions and stays legible whoever reads it later. A printable pdf drops those objects and leaves the page as an image, which is what an office needs where a screen is unavailable and a pen is not. The document itself is unchanged between them; what differs is the circumstance each anticipates.
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.
No charge and no account apply: these are published documents, and access to them is not something a distributor is entitled to price.
What the form asks for
- COMP_NAME
- CONT_NO
- ContentArea1
- DATE
- EXP_DATE
- FROM
- NAME_A
- NAME_B
- PHONE_A
- PHONE_B
- Page1
- QTY_A
- QTY_A_1
- QTY_A_2
- QTY_A_3
- QTY_B
- QTY_B_1
- QTY_B_2
- QTY_B_3
- QTY_B_4
- R65
- R66
- R67
- R68
The routing in PAM 25-38 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.
Forms cluster by series and number for the same reason files do: shared proponency and a shared prescribing directive usually mean a shared process. So a document in the DA series referenced on the face of another is generally part of the same transaction, and continuation sheets, cover sheets and transmittals belong to the package from the outset rather than arriving after a query.
Revision follows the process, which is why editions appear without a fixed interval, and the printed date rather than any version number identifies them. Nothing on a stored copy signals that it has aged; the check is manual. Work already completed under a superseded edition stands as filed, because the record was made under those terms and is properly interpreted under them.
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. CIO 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 4790?
- CERTIFICATION FOR DISTRIBUTION OF PUBLICATION(S) IN SUPPORT OF GOVERNMENT CONTRACT
- Which edition is current?
- 06/01/2021
- Who is responsible for this form?
- CIO
- In which formats can it be downloaded?
- PDF, XFDL, PDF