TransmittalProof — Sample workspace
This demo walks through the core workflow: issuing controlled drawings, matching PDFs to a register, anchoring proof on XRPL, and giving field teams a public verification link. All data is fictional.
Drawing control is broken in the field
- 📧 Drawings issued by email — no tamper-evident record
- 🤷 Field teams can't confirm which revision they have
- 📂 Document controllers manage versions in spreadsheets
- 🔍 Auditors can't trace what was issued and when
Issue with proof. Verify in seconds.
- ✅ Each issue is anchored immutably on the XRP Ledger
- 🔗 Every drawing gets a unique QR stamp + verification URL
- 📱 Anyone can verify a drawing — no login, no app needed
- 🧾 Full audit trail: who issued what, and when
Four steps from issue to verified
Import your document register (CSV/Excel). Each row defines a drawing — doc number, revision, title.
Upload the PDFs for this issue. The app matches each file to a register row by document number and revision.
Approve the release. A manifest hash is generated and anchored as an immutable record on the XRP Ledger.
Each PDF gets a QR stamp. Field teams scan the QR to verify the drawing is the latest approved revision.
Sample project
A project groups all issues, register history, and verification records together.
Ridgemont Gas Processing Facility
3 issue events · 13 drawings issued · 2 XRPL-anchored proofs
Issue releases
Each issue is a controlled release event — a set of drawings sent to site, a contractor, or a client, with a timestamped proof record.
IFC-2024-001
Issued for Construction · Mechanical & Piping — Phase 1
IFC-2024-002
Issued for Construction · Instrumentation & Control — Phase 1
AFC-2025-001
Approved for Construction · Civil & Structural
Matched drawings and verification PDFs
After uploading a register and PDFs, the app matches files to register rows. Matched files get a stamped PDF with an embedded QR code and verification link.
IFC-2024-001
Issued for Construction · Mechanical & Piping — Phase 1
Stored PDFs
All 8 files matched and stamped. Showing the first 3 for the demo.
View details
In the real product, a verification PDF button appears here. The stamped output embeds a QR code, issue metadata, and a unique verification URL that links back to the public proof record.
a3f7c2e1b9d4f6a0…b0e3a7d1e9b3a7d1f4c2e6b0…c0f4b7e2View details
In the real product, a verification PDF button appears here. The stamped output embeds a QR code, issue metadata, and a unique verification URL that links back to the public proof record.
c5f8b2e4a7d0c3f6…a9d2c5f8f2a6d9c3b7e0f4a8…b8e2f6a1View details
In the real product, a verification PDF button appears here. The stamped output embeds a QR code, issue metadata, and a unique verification URL that links back to the public proof record.
d1e8b4f7a2c5d9b3…c2d6b0e3b9f3d6a0c4e7b2f5…c5e9b3f7What the QR stamp looks like on a drawing
Every released PDF has a verification stamp embedded in the corner — no separate tool, no app, no login.
Every issued drawing gets a verification stamp
When a drawing is released, TransmittalProof embeds a QR code into the bottom corner of the PDF. The QR links to a public verification page showing the document number, revision, issue type, and whether the file hash matches the anchored record on the XRP Ledger.
- 📄 Unique per drawing — document number, revision, issue date
- 🔗 Links to a permanent, public verification URL
- 🔒 Hash-verified — tamper-evident proof
- 📱 Works offline: scan on-site, verify on the spot
Release record and XRPL anchor
When the issue is approved, a manifest hash is created from the full release record. That hash is anchored on XRPL as an immutable, timestamped proof.
IFC-2024-001 — Issued for Construction
Blockchain Proof Record
sha256:a3f7c2e1b9d4f6a0e5c8b3d2a7f1e4c9b6d0e5a2c3f8b1e4d7a9c6f2b0e3a7d1Each drawing in this issue has a unique public verification URL. Field teams can open the link or scan the QR stamp on the drawing to confirm it matches the anchored record — no login, no app, no email chain needed.
What field teams see when they verify
This is a simulation of the public verification page that anyone can access via the QR stamp on a drawing. No login required.
Every issued PDF has an embedded QR stamp. A field engineer scans the QR, lands on a page like this, and instantly knows whether the drawing in hand matches the anchored record — no login needed.
An issue before release
Not every issue is fully matched and anchored yet. This shows what an issue looks like mid-workflow, with some drawings still needing attention.
AFC-2025-001
Approved for Construction · Civil & Structural
Acknowledgment Workflow
Track transmittal delivery, receipt, and formal acknowledgment
Escrow Milestone Payments
Automated payment release tied to document delivery milestones
Wallet Management
Managed and external XRPL wallets for receiving and sending payments
- Platform-managed keys
- Automatic escrow operations
- No wallet software needed
- Your own Xaman / hardware wallet
- Full custody of your keys
- Withdraw to exchange any time
Industry Use Cases
TransmittalProof works across any industry that issues controlled documents
Oil & Gas
P&ID packages, inspection reports, HAZOP studies. Prove delivery to operators, regulators, and joint venture partners.
Legal
Contracts, court filings, regulatory submissions. Tamper-evident proof of service with payment tied to delivery milestones.
Construction
IFC drawings, submittals, RFIs. Track every revision, prove contractor receipt, release payments on approval.
Real Estate
Lease agreements, inspection reports, closing documents. Prove delivery with automatic escrow release on signing.
Ready to use this on a real project?
Request access to set up your workspace, create projects, issue controlled documents, track acknowledgments, and automate milestone payments — all with XRPL-anchored proof.