Military & government
A PCS move is won on the paperwork. So the paperwork is built in.
DD-1299 and twelve more DoD forms drawn straight from the order record. Entitlement tracked against net weight with pro-gear separated out. SIT that opens a real storage account. And every piece of the member's information encrypted, with every read logged.
This readiness panel is a working demo. Select a form and see what it still needs.
Go over the entitlement and the member pays for it.
A service member gets a weight allowance based on rank and dependants. Every pound over it comes out of their own pocket, and they usually find out weeks later. Meanwhile the form with one empty field comes back rejected, the claim has no evidence behind it, and the file that carries a rank, a home address and an order number sits in a shared drive that nobody can tell you who opened. None of that is a moving problem. It is a record-keeping problem, and it is where military work is actually lost.
The tender record
The DoD fields are fields. Not a note in the comments box.
GBL and tender number, PCS order, branch, rank, dependency status, code of service, origin and destination installation. Real columns on a real record, so they can be validated, reported on and put on a form, instead of being retyped from an email every time.
Built for the tender, not bolted on
Every military order carries its own tender record. Nothing about a PCS move is squeezed into fields designed for a household move across town.
Installations and dates that matter
Origin and destination installations, both required delivery dates, and the spread. The earliest and latest dates are worked out for you rather than counted on a calendar.
SIT that becomes a real account
Authorise storage in transit and a storage account opens against the job, tagged to the PCS order or GBL and already billing. Un-authorise it and it closes. No parallel spreadsheet.
Domestic, international, DP3
Government work sits on the same platform as the rest of your business, so a military job and a corporate job are the same kind of record with different rules.
Weights and pro-gear
Every pound, against the allowance. While there is still time to do something.
The whole ladder is tracked: household goods, pro-gear, spouse pro-gear, tare, gross and net, against the entitlement the member's rank and dependants actually give them.
Net against entitlement, live
Net weight is computed as you go and shown against the allowance, over or under, in the open. Not discovered on a scale ticket after the truck has left.
Member and spouse pro-gear, separately
Pro-gear is tracked apart from household goods, and the spouse's is tracked apart from the member's, because the allowance treats them differently.
Pro-gear totals from the real inventory
The totals come from the items themselves, tagged as you survey. Anything untagged is surfaced so it gets classified before it counts against the wrong allowance.
Weight certificates on the record
Origin and destination weight certificates attach to the order itself, next to the numbers they evidence. When the entitlement is questioned, the proof is on the job rather than in somebody's cab. Survey the house first with a video survey and the inventory that produced those weights is on the same record too.
The forms
Thirteen DoD forms, drawn from the order. Not typed again.
DD-1299, DD-1797, DD-619, DD-3157, DD-1840 and DD-1840R, DD-1252, the GBL, DP3 notification and more. Each one generated from the record you already filled in, as a real document on the job.
Generated, not filled in
The form is drawn from the tender record. Change the record and the next form is right, because there is no second copy of the truth to keep in step.
It tells you what is missing first
Every form shows how complete it is and exactly which fields it still needs. You find out before you generate it, not when it comes back rejected.
Claims with the evidence attached
DD-1840 and DD-1840R sit with the survey, the photos and the inventory that support them, so a loss and damage claim is a file rather than an argument.
Restricted by default
Generated government forms land on the job marked restricted and are not customer-visible. A DD-1299 carries a rank, an order number and a home address; it should not be one wrong click from a customer portal, so it is not.
Handling the member's information
Encrypted in the database. And every read is on the record.
This is the part most moving software does not do at all. Military personal information is not just access-controlled in the interface, it is encrypted in the database itself, and every time someone reads it that is logged.
Field-level AES-256-GCM
The GBL, rank, PCS order number, code of service, transportation office contact and special handling notes are encrypted at rest as individual fields, not merely behind a login.
Every access logged
Each read of a member's protected information writes an audit entry: who, when, which record. "Who looked at this file" is a question with an answer.
NIST SP 800-171 controls, implemented
Specifically 3.13.10 and 3.13.16, cryptographic key management and protection of information at rest. Named in the code, not in a brochure.
Certified as a company, engineered as a product
Moveezi holds ISO 9001, ISO 27001, NIST SP 800-171 and CMMC Level 1 and Level 2. Those are the company's certifications. Separately, the software implements the specific controls above in the code that handles a member's file. We think you should be told which is which, because plenty of the industry quotes a certification and leaves the data in plain text.
Why it matters
Government work is repeat work. If you can hold the standard.
The moves are predictable, the season is known and the volume comes back every year. What loses it is a rejected form, a blown entitlement and a file you cannot account for.
