Every entry on DA Form 5246-R exists because a record system needs it in writing. The form's official title is ARMY CHILD DEVELOPMENT SERVICES (CDS) REPORT, and it is raised whenever an office must child development services (cds) report (lra) in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated July 1989, status not stated, is what stands here, spread across 18 page(s) and about 200 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give.
Two offices stand behind the form, and the distinction between them explains most of what follows. ACSIM is the proponent: it decides what the form asks and revises it when the underlying process changes. AR 608-10 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.
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
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.
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
- AC_CHK
- AFTER
- AFTER_1
- AFTER_2
- AFTER_3
- AFTER_4
- APCT
- APCT_1
- APFLABOR
- APFOTHER
- APFRMBRS
- APFSPLYS
- APFTRNG
- APF_STFF
- APP_FUND
- APP_FUND_1
- APP_FUND_2
- APP_FUND_3
- APP_FUND_4
- APP_FUND_5
- ARMY
- ARMY_N
- ARMY_Y
- ASPNO
Where the signed form goes is settled by AR 608-10 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.
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.
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.
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 ACSIM or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 5246-R?
- ARMY CHILD DEVELOPMENT SERVICES (CDS) REPORT
- Which edition is current?
- July 1989
- Who is responsible for this form?
- ACSIM
- In which formats can it be downloaded?
- PDF, XFDL