Configure once, stream securely, and receive results in minutes — with your highest-priority members always processed first.

1. Pick your matching approach

   Choose how Rocket Vetting confirms identities: SSN for the highest confidence, or Name + Date of Birth if SSNs aren’t available, or if you choose not to use SSN.

2. Decide who should go first

   New roster members are automatically placed at the front of the processing queue. You can also identify other high-priority members (for example, absentee ballot requests) to be processed first.

3. Set up secure communication

   Secure, key-based authentication is used to stream your data to and from our server. Our plug-and-play setup generates a public/private key pair. Use the portal (Account → SSH Key) to register your key, then test the connection using the instructions in your Welcome Email.

4. Configure your launch pad(s)

   Launch pads are configuration presets (Windows or Linux) that control data movement and throughput. Enable or disable them as needed—your account still uses a single secure inbox and outbox. Our plug-and-play tooling makes this step straightforward. We recommend you start with one launch pad, monitor throughput, then add more launch pads as needed.

5. Stream your roster data

   Each SSN-based launch can include up to 75,000 records; Name/DOB launches up to 14,000. Your launch pad streams data 24×7 to our servers, where it’s queued for vetting. Launch pads can be activated or deactivated as needed.

6. Matches are performed

   Our load-balanced service processes the stream within minutes (priority streams are processed first). Each record is matched against the LADMF using your selected vetting method. Results (excluding SSNs) are written to your outbox and all other submitted data removed from our server.

7. Reentry & results

   The lightweight reentry process (part of the launch pad) checks the outbox continuously. When results are available, they’re downloaded and posted to your results table so your team can take action. After reentry, streamed data is removed from the outbox. Launch logs track every step for auditability.

   Each returned record always includes:

   • Roster identifier — the unique ID you supplied
   • Supplied data (echo) — for Name + DOB vetting, echoes of provided name and DOB
   • Date of death
   • Middle name / suffix (from LADMF)
   • Verification method — how the death was confirmed
   • Quality of match — SSN; Full name + DOB; Middle initial + DOB; First/Last name + DOB
   • Issuing state (of SSN, when available from source)
   • Warnings — e.g., approximate date indicators

   Cemetery/obituary data (available for ~30% of decedents):

   • Funeral home
   • Cemetery
   • Date of interment
   • Plot
   • Burial method
   • Obituary

   Additional non-cemetery data (often ≤10% of decedents):

   • Place of birth — city, county, state, country
   • Place of death — city, state, country
   • Last residence — street, city, county, state, country
   • Name of spouse
   • Veteran indicator