Every entry on DA Form 5613 exists because a record system needs it in writing. The form's official title is DISPATCHER`S RECORD OF TRAIN MOVEMENTS (S&I COMMANDANT, USATALS, ATTN: ATSP-TDP, FT EUSTIS, VA 23604-5403), and it is raised whenever an office must dispatcher`s record of train movements (s&i commandant, usatals, attn: atsp-tdp, ft eustis, va 23604-5403) in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 12/01/1986, status ACTIVE, is what stands here, spread across unknown page(s) and about unknown fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give.
The form has an author and an occasion, held by different authorities. T2COM owns the content and reshapes it when what is being recorded changes. not stated governs the event that calls for the form and the route the finished document takes afterwards. Keeping those two apart is what allows a procedure to be amended without the page being rebuilt each time.
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.
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.
The Privacy Act statement is on the page because collecting personal information requires the collector to disclose the terms first — the authority relied on, the purpose, the routine uses, and whether an answer is required or may be withheld. That order is the point: the statement is read before the entries it governs, since consent given afterwards is not consent. Once completed, the copy is a personal record and carries the handling obligations that attach to one.
Download the form
The published formats — none published here — 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.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
Disposition is prescribed, not chosen. not stated names the destination, whether that is a specific office, the unit administrative channel or the personal record, and the applicable records schedule governs how long it survives there. Both rules exist to keep the file consistent across offices with different habits. Take your copy before the document leaves, since it will not come back.
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.
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. T2COM 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 5613?
- DISPATCHER`S RECORD OF TRAIN MOVEMENTS (S&I COMMANDANT, USATALS, ATTN: ATSP-TDP, FT EUSTIS, VA 23604-5403)
- Which edition is current?
- 12/01/1986
- Who is responsible for this form?
- T2COM
- In which formats can it be downloaded?
- No file published here