Military Forms Guide

DA Form 1999 — RESTRICTED AREA VISITOR REGISTER

restricted area visitor register

Every entry on DA Form 1999 exists because a record system needs it in writing. The form's official title is RESTRICTED AREA VISITOR REGISTER, and it is raised whenever an office must restricted area visitor register in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 01/01/2019, status ACTIVE, is what stands here, spread across 1 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.

The form has an author and an occasion, held by different authorities. CSLA owns the content and reshapes it when what is being recorded changes. TB 380-41 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.

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.

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.

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

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.

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.

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

  • CLEAR
  • CLEAR_1
  • CLEAR_10
  • CLEAR_11
  • CLEAR_12
  • CLEAR_13
  • CLEAR_14
  • CLEAR_15
  • CLEAR_2
  • CLEAR_3
  • CLEAR_4
  • CLEAR_5
  • CLEAR_6
  • CLEAR_7
  • CLEAR_8
  • CLEAR_9
  • ContentArea1
  • DAY
  • DAY_1
  • DAY_10
  • DAY_11
  • DAY_12
  • DAY_13
  • DAY_14

The routing in TB 380-41 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.

One boundary should be stated clearly. What is distributed here are copies of published Department of the Army forms; the site is independent, issues nothing of its own, and holds no position in the system it describes. Proponency, prescribing directives and retention schedules operate without reference to it. Consequently nothing here is legal advice and no assurance about acceptance is possible. Questions about a particular entry, a requirement or eligibility belong with CSLA or your servicing administrative office.

Questions and answers

What is DA Form 1999?
RESTRICTED AREA VISITOR REGISTER
Which edition is current?
01/01/2019
Who is responsible for this form?
CSLA
In which formats can it be downloaded?
PDF, XFDL, PDF

Publisher notes

  1. 14-REQUIRES PRIVACY ACT STATEMENT (AR 340-21)
  2. 42-ITEM ONLY PRODUCED IN ELECTRONIC MEDIA

Other forms in the series