The bill of lading is the legal contract the customer signs at the door. It declares the shipment value, the liability coverage the mover is accepting, and the terms under which the move is happening. It is the single most important document in a moving job — the one that holds up in court when something goes wrong.
For interstate US moves, You Move Me uses three bill-of-lading variants:
- Full Value Protection (FVP). The mover assumes full liability for the declared shipment value. The customer pays a valuation charge for the coverage.
- Released Value Plus (RVP). A middle tier — the mover assumes liability above the federal minimum but below full value.
- Released Value (PVP). The federal minimum — 60 cents per pound per article. The customer pays nothing extra for this coverage, and the mover’s liability is capped.
Each variant has a different declared shipment value calculation, different liability language, and different signature requirements. Getting any of it wrong means the customer is underprotected and the mover is overexposed — or the customer is paying for coverage they’re not getting.
Why We Ported Them from PandaDoc
We built AegisDoc to replace PandaDoc for the reasons we’ve written about before: per-envelope fees that scaled with every document, third-party outages that stopped our customers from closing jobs, and roadmap lock-in that meant we waited on someone else’s editor to build a template we could have written in an afternoon.
The bills of lading were the hardest templates to port. They’re legal documents. The language has to match the PandaDoc originals word for word. The declared shipment value calculation has to be mathematically correct. The signature blocks have to support multiple roles — the shipper and the carrier both sign the same document — and the prefilled fields have to be editable by the customer at the door, bound to the job data so the numbers on the page match the numbers in the system.
We did it anyway. Here’s what the migration involved.
The Field-by-Field Audit
Every bill of lading was audited field-by-field against its PandaDoc original. Three things surfaced in the audit. All three were already wrong in the PandaDoc originals — which means they were wrong on every bill of lading that had been generated for months before the port.
The PVP declared shipment value bug
The Released Value (PVP) bill of lading declared shipment value was calculated with a ×6 multiplier. It should have been ×12. The result: the declared shipment value on every PVP bill of lading was understated by half. The customer was told their shipment was worth $X when the actual declared value under the federal minimum was $2X. The mover’s liability was understated. The customer’s coverage was understated. Nobody noticed because the number looked plausible.
The fix (Changelog_2608.md !2296) corrected the multiplier to ×12 and wired the weight fields to carry the job inventory total, so the declared shipment value is now calculated from the actual inventory weight — not a hand-entered number that could drift from what’s on the truck.
Restored total weight
The total weight field had been dropped from the PandaDoc template at some point — probably during an earlier edit, probably by someone who didn’t realize it was a required field for interstate compliance. The Aegis port restored it.
Six dropped recipient fields
Six recipient fields — the fields that identify who’s receiving the shipment at the destination — had been dropped from the PandaDoc original. The Aegis port restored all six.
Rebuilt on reference PDFs
The layout was rebuilt on reference PDFs provided by Sarika Kumra — the actual printed bills of lading that had been used before the PandaDoc migration. The Aegis templates match the reference PDFs, not the drifted PandaDoc templates. Typography, column widths, signature placement, and page breaks all follow the reference documents.
Multi-Role Signatures, Radio Buttons, and Editable Prefilled Fields
The Aegis bill-of-lading templates (Changelog_2608.md !2256) introduced three capabilities that PandaDoc’s template builder couldn’t match.
Multi-role signatures. A signature block can have multiple placements per role. The shipper and the carrier both sign the same document — two signature blocks on the same page, each tied to a role, each with its own signing ceremony. The server knows which roles have signed and which haven’t, and won’t mark the document complete until both are done.
Radio buttons and textareas. Templates can now declare radio-button inputs (for the liability-coverage selection — FVP, RVP, or PVP), textareas (for the customer’s notes about high-value items), and inline field references (so a single input field can render in multiple places on the same document — the declared shipment value appears on the cover page and on the signature page, and editing one updates both).
Editable prefilled fields bound to job data. The estimate data — the inventory, the charges, the declared shipment value — is prefilled on the bill of lading from the job. The customer can edit the prefilled fields at the door if something changed during the walk-through. The edits are persisted as draft fields and stamped at the document instant, not at now, so they don’t drift during a long signing session.
The 16 Template Families
The bills of lading were three of sixteen template families ported from PandaDoc to Aegis in August 2026 (Changelog_2608.md !2288). The full list:
- Post-load walkthrough — the document the crew fills out after the truck is loaded.
- Additional valuation — the customer’s election of coverage above the federal minimum.
- Move and pack acknowledgement — the customer’s acknowledgement of the packing terms.
- OTR customer packet — the over-the-road move packet, with in-document promo placement so marketing pages can be interspersed at any point in the document.
- Damage report — the document the crew files when something is damaged during the move.
- Walkthrough acknowledgement — the customer’s acknowledgement of the pre-move walkthrough.
- Relentless customer satisfaction release — the goodwill settlement release for the Relentless franchise brand.
- Oregon moving contract — the state-specific contract for Oregon moves.
- Vancouver Island ministry estimate — the estimate for Vancouver Island moves, with GST number, per-event tax breakout, and provincial tax handling.
- Portland confirmation email — the confirmation email sent to customers in the Portland franchise territory.
- Interstate agency move — the contract for interstate moves handled through an agency relationship.
- Lehigh Valley release of liability — the liability release for the Lehigh Valley franchise, with corrected acknowledgment fields.
- Denver protection plan — the protection plan election for the Denver franchise.
- Charlotte two-signature estimate — the Charlotte estimate that requires two signatures — shipper and carrier.
- Charlotte customer contract — the Charlotte customer-facing contract.
- YMM on-site estimate — the one-page work order an estimator fills in at the customer’s door, now an Aegis template with PandaDoc remaining the default until zones opt in (!2297).
Each was audited against its PandaDoc original. The estimate family fixes a long-inventory overflow that pushed charges onto the next page — rooms are now chunked into page-sized blocks across the whole estimate family, so a 40-room inventory doesn’t break the layout. The OTR packet gained in-document promo placement, so marketing pages can be inserted at any point in the packet rather than appended at the end.
What This Means for Moving Company Owners
If you’re a moving company operator who was paying PandaDoc per envelope for your bills of lading, estimates, contracts, and customer packets, you were paying a third party for the privilege of signing your own legal documents. You were also one PandaDoc outage away from not being able to close a move at the door.
The Aegis port fixes both. No per-envelope fees. No third-party outages in your document pipeline. Legal documents audited field-by-field against their originals — with bugs fixed that the originals had been shipping with for months. Multi-role signatures, editable prefilled fields, and a template system where a new franchise contract is a single merge request, not a week-long back-and-forth in a third-party template builder.
The bill of lading is the contract that holds up in court. It should be owned by the company whose name is on it, rendered by the system that runs the move, and audited against the reference documents — not rented from a third party that charges you every time you hand a customer a piece of paper.
MoveRight is the moving company CRM that owns its document engine, ports its legal templates field-by-field, and fixes the bugs the previous vendor shipped with — because the bill of lading is the contract that holds up in court, and it should be ours.
References:
- August 2026 Changelog — !2256, !2288, !2296 — bill-of-lading port, 16 template families, PVP multiplier fix, multi-role signatures, editable prefilled fields
- Why We Replaced PandaDoc with AegisDoc — the original migration story and the per-envelope cost problem
- AegisDoc Document Settings: One-Click Engine Swap — how zones flip between Aegis and PandaDoc without a cutover event