Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 1919C is one of those instruments: DD Form 1919C, Federal Wage System - Wage Data Collection (Continuation), July 2009, created to Federal Wage System - Wage Data Collection (Continuation). 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.
The edition in force is not stated, carried by the publisher as not stated, and edition discipline is stricter on a Department form than most people expect, precisely because supersession happens everywhere at once. There is no interval during which one service still works from the previous layout while another has moved on.
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.
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.
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.
The signature converts entries into an attestation, and that is why its form is prescribed. Ink, or a digital signature carrying a credential that identifies the signer — commonly issued on a Common Access Card. Typed characters in the box satisfy neither standard, because the whole value of a signature lies in being difficult to produce on someone else's behalf. Date it as you sign; an undated attestation cannot be placed in the sequence of events.
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
Formats available: PDF, across 1 pages and about 72 fields.
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.
What the form asks for
- 6. Area code.
- 7. Establishment code.
- 8. Job number.
- 13. Job match, column 1, line 1. Enter Y if yes, N if no.
- 14. Number of employees.
- 15. Straight time hourly rate.
- 13. Job match, column 1, line 2. Enter Y if yes, N if no.
- 14. Number of employees.
- 15. Straight time hourly rate.
- 13. Job match, column 1, line 3. Enter Y if yes, N if no.
- 14. Number of employees.
- 15. Straight time hourly rate.
- 13. Job match, column 1, line 4. Enter Y if yes, N if no.
- 14. Number of employees.
- 15. Straight time hourly rate.
- 13. Job match, column 1, line 5. Enter Y if yes, N if no.
- 14. Number of employees.
- 15. Straight time hourly rate.
- 13. Job match, column 1, line 6. Enter Y if yes, N if no.
- 14. Number of employees.
- 15. Straight time hourly rate.
- 21. Job sub-number, column 1.
- 25. Continuation number, column 1.
- 13. Job match, column 2, line 1. Enter Y if yes, N if no.
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 1919C 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 1919C?
- DD Form 1919C, Federal Wage System - Wage Data Collection (Continuation), July 2009
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?