Engineering private beta · AU/NZ

Document security, made easy for operations teams.

Verified.Tools helps operations and admin teams manage important engineering PDFs through Identify, Envelope, Sign, and Negotiate. Keep verification records, controlled document packages, signing workflows, and negotiation history in one practical suite.

Request beta access Choose a product

All four products are planned for beta. Request access or join the waitlist for the document-security path your team needs first.

Document security suite

Private beta

Structural assessment package

Identify Organisation context before document work starts

Envelope Controlled packages for PDFs that should not live only in email

Sign Signature packets with status and audit detail attached

Negotiate Proposal, version, and decision history made easier to follow

Choose your product path

Start with the document-security problem in front of you.

Choose Negotiate, Envelope, Sign, or Identify. Each path gives operations teams a different way to bring structure, status, and evidence back into important PDF work.

All four products are expected in beta. Request access for the product your team wants to test first, or join the waitlist for the full suite.

Identify

Know which organisation is behind the document workflow.

Before a PDF is packaged, signed, negotiated, or issued, operations teams need the company context to be clear. Identify records the organisation details and checks that downstream document work can reference.

Identify gives the document workflow a clearer starting point. It records defined company attributes before downstream document actions rely on that organisation context.

✓Confirm the organisation context before document workflows begin.

✓Use domain, phone, address, and related checks as narrow evidence.

✓Carry the verified organisation context into Envelope, Sign, and Negotiate.

What Identify records

A practical company-association layer before document action.

Identify is intentionally narrow. It does not prove a document is technically correct or legally sufficient. It records the organisation attributes that downstream document workflows can reference.

Domain control

Confirm that the organisation controls the domain connected to its workspace and outbound document activity.

Phone and address checks

Strengthen the organisation association with business phone and address checks where the account has completed those steps.

Workflow context

Carry the verified organisation context into packaged documents, signature requests, negotiation records, audit logs, and recipient-facing verification.

Workflow

Built around organisation checks before document work starts.

Start by verifying the company association, then use that context across document packages, signing workflows, and negotiation records.

Verify the domain

Confirm the workspace is associated with a domain the organisation controls.

Strengthen the company profile

Add phone, address, and related checks as the beta workflow permits.

Use the context

Carry verified organisation context into Envelope, Sign, Negotiate, and audit records.

Keep claims narrow

The page describes what was checked and avoids claiming more than the evidence supports.

Private beta focus

Engineering first.

The current beta is focused on Australian and New Zealand engineering consultancies that need organisation checks connected to document workflows.

✓Domain, phone, address, and related organisation checks.

✓Verified company context before packages, signatures, and negotiations.

✓Clear boundaries between organisation evidence and legal outcomes.

Start with Identify Read more

Verify domain

Confirm the company controls the domain attached to the workspace.

Add checks

Complete phone, address, and related organisation checks as required.

Use in workflows

Carry the organisation context into Envelope, Sign, and Negotiate records.

Envelope

Email alone is no longer enough for important PDFs.

Operations teams still need to send files, but important engineering PDFs should not depend on an inbox as the only source of truth. Envelope keeps the document set, recipient list, delivery state, and verification context in one controlled package.

Envelope is for the controlled document package. It helps teams organise what is being sent, who is involved, and what state the package is in before downstream signing, issue, or review steps happen.

✓Group documents into a controlled package.

✓Record recipients, roles, and distribution status.

✓Keep package evidence visible without conflating it with signing.

Package control

One record for the document package.

Envelope is designed for teams that need controlled distribution and a clean record of what was sent, who was included, and where the package stands.

Document set

Keep the files in the package together so later review starts from the same document set.

Recipient routing

Record the people or organisations involved and the role each recipient plays in the package.

Package state

Show whether a package is being prepared, sent, viewed, completed, or ready for a downstream workflow.

Workflow

Designed for controlled document distribution.

Build the package, define recipients, distribute it, then keep the package evidence available for review.

Add documents

Start from certified files or upload new documents into the workspace.

Set recipients

Define who receives, approves, or only views the package.

Distribute package

Send the controlled document package without forcing signing-field placement.

Review evidence

Keep the document set, recipients, status, and audit history together.

Private beta focus

For teams that need controlled packages before execution.

Envelope is useful when a document set needs to move as a package, with recipient roles and distribution evidence clear before a signature or negotiation workflow starts.

Start with Envelope Read more

Prepare

Group the document set and define the package purpose.

Route

Add recipients and decide who receives, approves, or views.

Track

Keep package status and evidence available as the workflow progresses.

Sign

Keep signature packets connected to the document record.

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. Operations 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.

Sign is for practical signing workflows. 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 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

Sign for engineering document operations.

The 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 wider document records.

Explore Sign Read more

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

Negotiations are hard. Make the document-change trail easier.

Technical documents often evolve through comments, mark-ups, redlines, spreadsheet extracts, drawing revisions, and long email threads. Negotiate gives operations teams a structured place to resolve proposals, record decisions, and move toward an agreed version before signing or release.

Negotiate is for controlled document differences. It keeps proposals, version decisions, review states, and agreed paths clearer before a document is executed or issued.

✓Structured change history for technical and project documents.

✓Review and approval states tied to document versions.

✓Clearer release points for documents that continue to evolve.

Change control

Built for change, review, and release history.

Negotiate brings version-control discipline to document-heavy project work, helping teams understand what changed, what was reviewed, and which version was released.

Version history

Track meaningful document versions, what changed, and which release point a team is discussing.

Review states

Separate drafts, internal review, client review, approved versions, and released snapshots more clearly.

Approval trail

Show who reviewed or approved a document state, with a clearer path from working draft to released version.

Workflow preview

A cleaner model for documents that keep changing.

Negotiate is designed around the practical rhythm of technical document work: organise the workspace, capture changes, review the version, and release the snapshot that matters.

Create the workspace

Keep related documents, versions, reviewers, and release points together.

Propose a change

Make it clearer what changed and why before a document moves forward.

Review the version

Route the document through review states without losing the history of prior versions.

Release a snapshot

Mark the version that was released, issued, superseded, or archived.

Early access list

Start with Negotiate when the document is not agreed yet.

Negotiate is for teams that already manage changing technical documents and want a clearer path through proposals, review, agreement, release, and superseded versions.

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

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

✓Connection points with Identify, Envelope, and Sign records.

Start with Negotiate Read more

Organise

Bring related documents, versions, and reviewers into one workflow.

Review

Move documents through review while preserving the path from draft to release.

Release

Make the released version clear, with superseded and archived states easier to follow.

Answers for operations teams

Three document-security questions the site should answer clearly.

These are the search themes we are targeting first: document provenance for engineering PDFs, verifying an issued PDF, and controlled document packages.

What is document provenance for engineering PDFs?

Document provenance is the record behind an issued file. For an engineering PDF, that can include the organisation context, the submitted file hash, the timestamp, and the current platform status. It helps a recipient check the record without implying the technical content of the PDF is automatically correct.

How can a recipient verify an issued PDF?

A recipient should be able to open a verification link or scan a QR code, see the recorded issuer details and status, and compare the file against the recorded hash. The result is a practical check on the document record, not a substitute for professional or legal review.

What is a controlled document package?

A controlled package keeps the document set, recipient list, delivery state, and related evidence together. It gives operations teams a better source of truth than a loose email thread when a package needs to be checked, signed, superseded, or reviewed later.

Current pricing

Five published plans for Verified.Tools.

Pricing shown here matches the plans currently configured in the product. Availability and onboarding remain controlled while we continue rolling out Identify, Envelope, Sign, and Negotiate workflows.

Free Forever

$0AUD

For initial evaluation and very light ongoing usage.

✓2 documents per month
✓Level 1 verification
✓Public verification pages
✓Included at onboarding

Ask about onboarding

Starter

$49AUD / month

For smaller teams moving into production use.

✓50 documents per month
✓Level 1 and 2 verification
✓Public verification pages
✓API access
✓Email support

Ask about Starter

Most selected

Professional

$99AUD / month

For practitioners and teams using Negotiate in production.

✓200 documents per month
✓Level 1, 2 and 3 verification
✓API access
✓Negotiate workspace
✓Priority support

Ask about Professional

Business

$149AUD / month

For growing firms that need branding, collaboration, and integrations.

✓500 documents per month
✓Level 1, 2 and 3 verification
✓API, Negotiate, and webhooks
✓Custom branding
✓Team management

Ask about Business

Enterprise

By QuoteFrom AU$499 / month

For organisations that need procurement, compliance, and tailored onboarding.

✓Negotiated or unlimited document volume
✓Level 1, 2, 3 and 4 verification
✓SAML SSO and SCIM
✓Audit export and data residency options
✓Commercial onboarding and SLA terms

Discuss Enterprise

Pricing is published in AUD. Starter, Professional, and Business align with the live in-product billing catalog. Enterprise onboarding remains quote-led.

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.

Request beta access or join the waitlist.

Tell us how your operations team manages engineering PDFs today. We will confirm whether Identify, Envelope, Sign, Negotiate, or the full suite is the right beta path before you spend time onboarding.

Request beta access Join waitlist