Engineering private beta · AU/NZ

Document provenance, made checkable.

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.

Verification record
Active

Structural assessment report

Issuer Example Engineering Pty Ltd
Recorded file assessment-final.pdf
Timestamp RFC 3161 evidence
Hash 7f2a…c91b

Issued PDFs keep travelling after they leave your office.

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.

Give recipients a verification page to check alongside the PDF.
Keep the message precise: issuer, file, timestamp, and status.
Fit the workflow engineering firms already use to issue reports.

One page for the facts a recipient needs to 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.

01

Issuer details

Show the recorded organisation attributes attached to the document record, so recipients know which issuer the record refers to.

02

File hash and timestamp

Represent the submitted PDF with a SHA-256 hash and timestamp evidence, so the received file can be compared with the record.

03

Current status

Surface whether the record is active, revoked, or superseded, giving recipients a clearer view of the document lifecycle.

Built around the way engineering PDFs are issued.

Start with a verified organisation, then create a verification record each time a report or drawing is issued.

1

Verify the organisation

Prove domain control and complete the required account checks before issuing records.

2

Record the PDF

Upload the issued file so the platform can record the submitted hash and timestamp evidence.

3

Share the link

Send the PDF with its verification link or QR-linked page as part of the normal delivery workflow.

4

Let recipients check

Recipients compare their file with the record and review the current platform status.

Engineering first.

The current beta is focused on Australian and New Zealand engineering consultancies issuing PDFs that may be relied on outside the original delivery context.

Structural, civil, geotechnical, mechanical, and electrical reports.
Compliance certificates, marked drawings, assessments, and sign-offs.
Recipient-accessible records for clients, builders, certifiers, and councils.
A

Issue the report

The engineering team releases the PDF through its existing client workflow.

B

Attach the record

The verification link travels with the document or appears as a QR-linked reference.

C

Check later

A recipient can compare the file and review whether the record is active, revoked, or superseded.

Plans for the engineering private beta.

Pricing shown here matches the plans currently configured in the product. Availability and onboarding remain controlled during the engineering private beta.

Starter
$49AUD / month

For small engineering teams testing the workflow on issued PDFs.

  • 50 documents per month
  • Level 1 and 2 verification badge
  • Public company profile
  • API access and webhook delivery
  • Email support
Request Starter access
Enterprise
$499AUD / month

For organisations that need broader access, higher-volume use, and direct implementation support.

  • Higher-volume document use
  • Level 1, 2, 3 and 4 verification badge
  • Public company profile
  • API, webhook and MCP access
  • Dedicated support channel
Discuss Enterprise

Private-beta onboarding is controlled. We will confirm fit, volume, and implementation needs before activating a plan.

Built from direct experience with engineering document workflows.

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.

Testing document provenance with issued engineering PDFs?

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