Issuer details
Show the recorded organisation attributes attached to the document record, so recipients know which issuer the record refers to.
Verified.Tools gives engineering firms a recipient-accessible record of who issued a PDF, which file was recorded, when its hash was timestamped, and its current status.
Built for issued reports, certificates, drawings, and other engineering PDFs that may be forwarded, uploaded, archived, or checked long after delivery.
Engineering documents often move through clients, builders, certifiers, councils, insurers, and archives. When a question comes back months or years later, the practical issue is simple: can the file in hand be compared with a clear record of the file that was issued?
Verified.Tools is designed to add that missing record. The beta workflow records defined issuer information, the submitted file hash, timestamp evidence, and current platform status in a page a recipient can check.
The verification record is intentionally narrow. It does not claim the report is legally valid, technically correct, or suitable for a particular use. It records the file evidence and current status behind the issued document.
Show the recorded organisation attributes attached to the document record, so recipients know which issuer the record refers to.
Represent the submitted PDF with a SHA-256 hash and timestamp evidence, so the received file can be compared with the record.
Surface whether the record is active, revoked, or superseded, giving recipients a clearer view of the document lifecycle.
Start with a verified organisation, then create a verification record each time a report or drawing is issued.
Prove domain control and complete the required account checks before issuing records.
Upload the issued file so the platform can record the submitted hash and timestamp evidence.
Send the PDF with its verification link or QR-linked page as part of the normal delivery workflow.
Recipients compare their file with the record and review the current platform status.
The current beta is focused on Australian and New Zealand engineering consultancies issuing PDFs that may be relied on outside the original delivery context.
The engineering team releases the PDF through its existing client workflow.
The verification link travels with the document or appears as a QR-linked reference.
A recipient can compare the file and review whether the record is active, revoked, or superseded.
Pricing shown here matches the plans currently configured in the product. Availability and onboarding remain controlled during the engineering private beta.
For small engineering teams testing the workflow on issued PDFs.
For firms issuing higher document volumes or validating integrations.
For organisations that need broader access, higher-volume use, and direct implementation support.
Private-beta onboarding is controlled. We will confirm fit, volume, and implementation needs before activating a plan.
Verified.Tools is being developed for firms that need a practical record behind issued PDFs. The focus is not to replace professional sign-off, legal advice, delivery records, or document management systems. The focus is to make the provenance record easier for a recipient to check.
Tell us how your team issues reports today. We will confirm whether the private beta is a fit before you spend time onboarding.
Request beta access