Every entry on DA Form 5573-R exists because a record system needs it in writing. The form's official title is LOAN AGREEMENT, and it is raised whenever an office must loan agreement (lra) in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated September 1998, status not stated, is what stands here, spread across 1 page(s) and about 96 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give.
Behind any Army form sit two separate decisions. What the document asks is settled by OCSA, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 870-20. 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.
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
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.
The choice of application decides whether your work survives. Browsers render pdfs as documents to be read; where a viewer shows fields without a mechanism to store them, typed text disappears when the tab closes, and nothing announces the loss. A full reader treats the file as a form and preserves entries on save. The xfdl format comes from IBM Lotus Forms, used across Army systems because of the routing and signature functions built into it, and it opens in the Lotus Forms Viewer alone.
No charge and no account apply: these are published documents, and access to them is not something a distributor is entitled to price.
What the form asks for
- ADDRESS_A
- ADDRESS_B
- CONDITIONS
- ContentArea1
- DATE
- DESCRIPT
- EMAIL_A
- EMAIL_B
- FAX_A
- FAX_B
- FROM
- IN_WRITING
- LENDER
- LEND_SIGN
- MUSEUM
- NOTIFIED
- PHONE_A
- PHONE_B
- PROVIDED
- PURPOSE
- Page1
- R68
- R69
- R70
The routing in AR 870-20 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.
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.
Revision follows the process, which is why editions appear without a fixed interval, and the printed date rather than any version number identifies them. Nothing on a stored copy signals that it has aged; the check is manual. Work already completed under a superseded edition stands as filed, because the record was made under those terms and is properly interpreted under them.
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. OCSA 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 5573-R?
- LOAN AGREEMENT
- Which edition is current?
- September 1998
- Who is responsible for this form?
- OCSA
- In which formats can it be downloaded?
- PDF, XFDL