Engineering private beta · AU/NZ

Issue, sign, and verify important documents.

Verified.Tools gives engineering firms a practical suite for document provenance, e-sign workflows, and version-controlled document work. Start with the workflow you need, then keep the record clear enough for recipients, reviewers, and future teams to check.

Request beta access Choose a workflow

Document Provenance and E-sign are presented for the current product suite. GITDoc is scoped but not written yet, and is shown as coming soon.

Suite record

Private beta

Structural assessment package

Provenance Issuer, file hash, timestamp, and current status

E-sign Envelope, signer sequence, document status, and audit trail

GITDoc Coming soon: change history for technical documents

Choose your workflow

One product area. Three workflows. One visible at a time.

Use the bean menu to switch the content in this section. The page does not stack every product story underneath each other; the selected workflow controls what you read.

Keyboard users can tab into the selector and use arrow keys to move between products. The selected product panel below is the only detailed product content shown.

Document Provenance

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?

Document Provenance 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.

What the record shows

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.

Issuer details

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

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.

Current status

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

Workflow

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.

Verify the organisation

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

Record the PDF

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

Share the link

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

Let recipients check

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

Private beta focus

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.

Start with Document Provenance

Issue the report

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

Attach the record

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

Check later

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

E-sign

Signing should leave a clear operational record, not just a final PDF.

Engineering firms often need signatures on appointments, acceptance letters, inspection forms, contractor acknowledgements, change approvals, and report release packs. The signature is only part of the job. Teams also need to know who was asked to sign, what they received, whether the envelope is complete, and where the signed record can be checked later.

Verified.Tools E-sign is written for practical signing workflows. The product story is deliberately restrained: prepare the signing packet, send it to the right people, track the envelope, and keep a clear audit trail around the completed document.

✓Package documents for signature without losing the context around the signing request.

✓Track signer progress, envelope status, and completed document versions.

✓Keep signing evidence close to the document record for future review.

What the signing record shows

One place for the facts behind a signing workflow.

The e-sign record is designed to be operationally useful. It does not make broad legal claims or replace professional advice. It records the envelope, signer flow, document status, and audit trail information that helps a team understand what happened.

Envelope and document set

Show which files were included in the signing packet, how they were labelled, and which version was sent for signature.

Signer sequence and status

Track who has been asked to sign, which steps are waiting, and whether the envelope is draft, sent, completed, cancelled, or expired.

Audit trail detail

Keep a structured trail of signing events, timestamps, delivery activity, completion state, and the final signed package.

Workflow

Designed for signing packets that need to keep moving.

Prepare the envelope, define the signer flow, monitor the status, and keep the completed package tied to a clear record.

Prepare the envelope

Add the documents, name the packet clearly, and define what each signer needs to complete.

Add signers

Set the signer list, message, signing order, and any internal review steps required before sending.

Send and monitor

Track who has opened, completed, or still needs to act, so the team can follow up with the right person.

Close the record

Store the completed packet and audit trail with the status needed for future reference.

Private beta focus

E-sign for engineering document operations.

The e-sign workflow is aimed at teams that already issue technical documents and need a better way to manage the signing steps around approvals, releases, acknowledgements, and delivery records.

✓Appointments, acceptance letters, fee approvals, and change confirmations.

✓Internal sign-offs and external acknowledgements around issued reports.

✓Signing packets that should remain connected to document provenance records.

Explore E-sign

Send the packet

The team sends a signing envelope with the right files, signers, and message.

Track the state

The envelope shows which signer has acted and which step is still pending.

Keep the trail

The completed document and event trail stay available for later operational review.

GITDoc · Coming Soon

Version-controlled document work is scoped, but not written yet.

Technical documents often evolve through comments, mark-ups, redlines, spreadsheet extracts, drawing revisions, and long email threads. GITDoc is the planned Verified.Tools product for teams that want clearer change history and review flow around project documents.

GITDoc is not available yet. The product is scoped as a future workflow for document versioning, review states, and approval trails. It is shown here so buyers understand where the suite is going, not because it can be purchased or onboarded today.

✓Coming soon: structured change history for technical/project documents.

✓Coming soon: review and approval states tied to document versions.

✓Coming soon: clearer release points for documents that continue to evolve.

Planned scope

The future product is about change, review, and release history.

GITDoc is intended to bring some of the discipline of version control into document-heavy project work. The language here is intentionally future-facing until the product is built and evidence-tested.

Version history

Planned: track meaningful document versions, what changed, and which release point a team is discussing.

Review states

Planned: separate drafts, internal review, client review, approved versions, and released snapshots more clearly.

Approval trail

Planned: show who reviewed or approved a document state without pretending that future functionality exists today.

Planned workflow

A working model for documents that keep changing.

The intended workflow is still being shaped. This is the direction currently being scoped for future development.

Create the workspace

Planned: keep related documents, versions, reviewers, and release points together.

Propose a change

Planned: make it clearer what changed and why before a document moves forward.

Review the version

Planned: route the document through review states without losing the history of prior versions.

Release a snapshot

Planned: mark the version that was released, issued, superseded, or archived.

Discovery focus

Register interest before we build the wrong thing.

GITDoc needs input from teams that already manage changing technical documents. The next step is discovery: what documents change, who reviews them, where approval happens, and how released versions are identified today.

✓Technical reports, specifications, procedures, and project deliverables.

✓Teams that need review trails before a document is released or superseded.

✓Future connection points with provenance and signing records.

Scoped

The product direction is documented and positioned as a future suite workflow.

Not written

The marketing site should not imply live availability, onboarding, or purchase.

Discovery next

Interested teams can register the workflows they want this product to solve.

Private-beta pricing

Plans for the active private beta.

Pricing shown here matches the plans currently configured in the product. Availability and onboarding remain controlled during the engineering private beta. GITDoc is coming soon and is not currently included as a purchasable product.

Starter

$49AUD / month

For small engineering teams testing the workflow on issued PDFs and early signing use cases.

✓50 documents per month
✓Level 1 and 2 verification badge
✓Public company profile
✓API access and webhook delivery
✓Email support

Request Starter access

Most relevant for beta

Professional

$149AUD / month

For firms issuing higher document volumes or validating document and signing integrations.

✓500 documents per month
✓Level 1, 2 and 3 verification badge
✓Public company profile
✓API access and webhook delivery
✓MCP server access
✓Priority email support

Request Professional 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. GITDoc is scoped as a future product and should be treated as coming soon until released.

About Verified.Tools

Built from direct experience with engineering document workflows.

Verified.Tools is being developed for firms that need practical records behind issued, signed, and changing documents. The focus is not to replace professional sign-off, legal advice, delivery records, or document management systems. The focus is to make the relevant document record easier for a recipient, signer, reviewer, or future team to check.

Testing document provenance or e-sign workflows with engineering documents?

Tell us how your team issues, signs, or reviews documents today. We will confirm whether the private beta is a fit before you spend time onboarding.

Request beta access