Military Forms Guide

DA Form 1613 — RECORDS CROSS REFERENCE

records cross reference

Administrative documents are written for readers who were not present, and DA Form 1613 is no exception. Titled RECORDS CROSS REFERENCE, it is used to records cross reference — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date 06/01/2008 and the status ACTIVE. Its 1 page(s) and roughly 56 fields are sized to what the record must prove years later, which is always more than the moment appears to need.

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-403. 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.

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.

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

Why several files for one page? Because the form has to be completed in a headquarters and in places without a workstation, and PDF, XFDL covers both. The fillable pdf holds interactive fields that fix each entry in place and remove handwriting from the equation. The printable pdf is the same layout without those fields, meant for a printer and a pen. Neither is a lesser copy of the other; each answers a condition the other cannot.

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.

There is no charge and no sign-up. Published documents are distributed as published, without modification.

What the form asks for

  • Address
  • CHECK1
  • CHECK2
  • ContentArea1
  • DOB
  • ESSAY
  • Email
  • FIELD1
  • FIELD2
  • Name
  • Page1
  • Phone
  • R34
  • R35
  • R36
  • R37
  • R38
  • R39
  • R40
  • R41
  • R42
  • R43
  • R44
  • R45

Where the signed form goes is settled by PAM 25-403 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.

Related documents are located by series and number, and the relation is rarely accidental — forms under one proponent or one directive tend to serve steps of a single procedure. Anything the DA series form names on its face normally travels with it, as do the continuations, covers and transmittals the process generates. Assembling them together is what makes the submission a complete account.

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 CIO or to the administrative office servicing your unit.

Questions and answers

What is DA Form 1613?
RECORDS CROSS REFERENCE
Which edition is current?
06/01/2008
Who is responsible for this form?
CIO
In which formats can it be downloaded?
PDF, XFDL, PDF

Other forms in the series