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 available in the current product suite. Negotiate is coming soon for legal professionals and commercial teams managing multi-party document negotiations.

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.

Negotiate · Coming Soon

Multi-party negotiations need a verifiable record, not just a final signature.

Legal documents often travel through multiple parties, redline cycles, and version exchanges before reaching agreement. When the deal is signed — or disputed — the record of how agreement was reached matters as much as the final text. Managing what each party sees, tracking proposals and responses, and proving what was agreed and when are operational problems that Verified.Tools - Negotiate is designed to solve.

Verified.Tools - Negotiate is a browser-native legal document negotiation product. It handles the structured back-and-forth before signature — with admissibility mode selection, staged disclosure controls, and an append-only record of every proposal, response, and acceptance.

✓Coming soon: multi-party negotiation with staged disclosure controls.

✓Coming soon: admissibility mode selection for AU, UK, and US jurisdictions.

✓Coming soon: cryptographic record of every proposal, redline, and acceptance.

Coming soon

What the negotiation record shows.

The Negotiate record is designed to be legally useful and operationally precise. It does not replace legal advice or professional sign-off. It records the evidence behind how agreement was reached — who proposed what, who accepted, and what admissibility protections were in place.

Negotiation history

Every proposal push, redline, and acceptance is recorded in an append-only event log. The complete negotiation path is preserved when the document closes.

Admissibility mode

Each negotiation declares its evidential posture: without-prejudice, with-prejudice, or without-prejudice save as to costs. The platform enforces the mode — export and deletion rules follow automatically.

Staged disclosure

Control exactly what each party sees and when. Sub-parties are kept confidential from main parties. Disclosure rules are enforced by the platform, not by manual discipline.

Workflow preview

From first draft to closed record, in one place.

Negotiate is being designed around the practical rhythm of multi-party legal document work: configure the negotiation, invite the parties, work through proposals, and close with a verifiable record.

Configure the negotiation

Upload or import the document, set the admissibility mode, define the party structure, and configure staged disclosure rules before invitations go out.

Invite the parties

Send browser-based invitations. Counterparties participate without creating an account. Sub-parties are kept confidential from other main parties throughout.

Negotiate to agreement

Push proposals, review redlines, and respond. The platform controls staged disclosure — each party sees only what they are entitled to see at each point in the process.

Close with a record

Once all main parties accept the final proposal, the negotiation closes with a complete timestamped record of how agreement was reached.

Early access list

Be first to hear when Negotiate is ready.

Verified.Tools - Negotiate is being built for legal professionals and commercial teams that manage multi-party document negotiations. The early access list is open for law firms, in-house legal teams, and commercial operators with active negotiation workflows.

✓M&A transactions, commercial agreements, and multi-party contracts.

✓Teams that need to control what each party sees during a live negotiation.

✓Legal professionals who need admissibility protection built into the process record.

Configure

Set the admissibility mode, party structure, and staged disclosure rules before invitations go out.

Negotiate

Push proposals and review redlines. The platform enforces what each party can see and when.

Close

Accept the final proposal. The negotiation closes with a complete, timestamped record.

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. Negotiate is coming soon and is not included in current private-beta plans.

Starter

$49AUD / month

For small teams testing document provenance and e-sign workflows.

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

Request Starter access

Most relevant for beta

Professional

$99AUD / month

For legal and professional services teams using Negotiate alongside Sign and Identify.

✓200 documents per month
✓Level 1, 2 and 3 verification badge
✓Negotiate access
✓Public company profile
✓API access and webhook delivery
✓Email support

Request Professional access

Business

$149AUD / month

For firms issuing higher document volumes or validating integrations at scale.

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

Request Business access

Enterprise

$499+AUD / month

For organisations that need higher volume, dedicated support, and custom implementation.

✓Higher-volume document use
✓Level 1, 2, 3 and 4 verification badge
✓Negotiate access
✓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. Negotiate is coming soon and will be introduced separately from the current private-beta plans.

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