The reason DA Form 5701-47 looks the way it does is that a file has to speak for itself. Officially CH-47 PERFORMANCE PLANNING CARD, it serves to ch-47 performance planning card, and the record it produces outlasts the people and the circumstances behind it. Edition 12/01/2022, status ACTIVE, is the version published here: 1 page(s), close to 200 fields, each one present because some later reader will need that fact without being able to ask for it. Because a subsequent edition has appeared, this copy stays available — a record made under one edition is interpreted under that edition.
Behind any Army form sit two separate decisions. What the document asks is settled by T2COM, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by TC 3-04.12. 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.
Much of the form's behaviour follows from its being a fixed page. Tab order was set at build time along the reading sequence, which is why tabbing catches boxes a pointer passes over. Exclusive groups release one choice when another is made because a record cannot carry two answers to a single question. Single-line fields refuse to wrap because every entry must print where the layout expects it — text beyond the width is lost at the margin, visible on screen to the end. That is what remarks areas and continuation sheets are for. Marking a field that does not apply matters for a related reason: emptiness is ambiguous, and a reviewer reading the file later cannot distinguish an omission from a decision.
The signature is the point at which entries become an assertion someone stands behind, so it follows everything else and its absence leaves a draft. Countersignatures by reviewing, approving or witnessing officials each carry their own weight and are dated at signing, which is how the file preserves the order of responsibility. Seen that way, the familiar errors are not clerical trivia: an unanswered mandatory field, digits transposed in an identification number, day and month reversed, and residue from a reused file each put something false or unresolved into a document that will be relied upon.
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, XFDL — 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.
Software determines whether an entry lasts. A browser viewer is designed for reading, and several will take typed input into fields without any means of writing it back — the text is simply absent when you reopen. A standalone reader handles the form structure properly. The xfdl file is IBM Lotus Forms, carried in Army systems for the routing and signature support it provides, which is why the Lotus Forms Viewer is its only reader.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- A1A
- A2A
- AA1AA
- AA1AA1
- AA2AA
- AA2AA1
- AA3AA
- AA3AA1
- AA4AA
- AA4AA1
- B1B
- Burnout
- C1C
- C2C
- CGI_A
- CGI_AB1
- ContentArea1
- D1D
- D1D1
- D2D
- D2D1
- D3D
- D3D1
- D4D
The routing in TC 3-04.12 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 T2COM or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 5701-47?
- CH-47 PERFORMANCE PLANNING CARD
- Which edition is current?
- 12/01/2022
- Who is responsible for this form?
- T2COM
- In which formats can it be downloaded?
- PDF, XFDL, PDF