Military Forms Guide

DA Form 3685 — JUMPS-JSS PAY ELECTIONS

jumps-jss pay elections

Administrative documents are written for readers who were not present, and DA Form 3685 is no exception. Titled JUMPS-JSS PAY ELECTIONS, it is used to jumps-jss pay elections — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date September 1990 and the status not stated. Its 1 page(s) and roughly 122 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 ASA(FM&C), which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 37-104-4. 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.

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

Formats exist because completion happens under different conditions, not because anyone wanted variety. The published set is PDF, XFDL. A fillable pdf carries live entry objects, so typed text lands in fixed positions and stays legible whoever reads it later. A printable pdf drops those objects and leaves the page as an image, which is what an office needs where a screen is unavailable and a pen is not. The document itself is unchanged between them; what differs is the circumstance each anticipates.

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

  • ACCTHLD
  • AMNTH
  • CHKADD
  • CITY
  • COUNTRY
  • CTSTZIP
  • ContentArea1
  • DATE
  • FINORG
  • HLDPAY
  • NAMADDR
  • PAYDIR
  • PRTNAM
  • Page1
  • R101
  • R102
  • R103
  • R104
  • R105
  • R106
  • R107
  • R108
  • R109
  • R110

Where the signed form goes is settled by AR 37-104-4 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.

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 ASA(FM&C) or your servicing administrative office.

Questions and answers

What is DA Form 3685?
JUMPS-JSS PAY ELECTIONS
Which edition is current?
September 1990
Who is responsible for this form?
ASA(FM&C)
In which formats can it be downloaded?
PDF, XFDL

Other forms in the series