Packets need structure
The workflow should show the documents included, why they were grouped, and which project or account context sits behind them.
Envelope
Package documents, recipients, and delivery state in one record.
Envelope is for teams that need controlled document distribution before a file is signed, negotiated, issued, or archived. It keeps the packet, recipients, status, and supporting evidence context together so the workflow is easier to understand later.
Problem
Important documents should not be managed as loose attachments.
Engineering teams send reports, certificates, drawings, letters, and approvals to multiple parties. Once the documents leave the internal system, it can become unclear which files were grouped together, who received them, what state the packet reached, and how the packet relates to the wider document record.
Recipients need clarity
A controlled packet should make the intended recipients, organisations, delivery path, and status visible without forcing the team back into email archaeology.
State matters later
Draft, sent, cancelled, completed, superseded, or archived state should remain connected to the packet so future reviewers can see what happened.
Workflow
Designed for controlled document distribution.
Build the packet, add recipients, send or hold the envelope, and keep the outcome connected to the surrounding document workflow.
1
Create the packet
Add the documents, name the envelope clearly, and record the packet purpose.
2
Add recipients
Set who needs the documents and which organisation or contact context applies.
3
Track the state
Monitor whether the envelope is draft, sent, completed, cancelled, or archived.
4
Close the record
Keep the final packet state available for issue, signing, negotiation, or review.
Use cases
Useful wherever a document set needs a controlled delivery record.
Envelope is aimed at teams that need to keep document groups, recipients, and workflow state visible across engineering document operations.
✓Report packs, certificate packs, drawing sets, and release bundles.
✓Recipient lists involving clients, builders, certifiers, and councils.
✓Packets that may later move into Sign, Negotiate, or issue workflows.
The aim is controlled distribution. The packet should explain what was prepared, who it was for, what state it reached, and how it connects to the wider document workflow.
Common questions
Envelope FAQs.
Is Envelope the same as Sign?
No. Envelope is the controlled packet and recipient workflow. Sign is the signing workflow for packets that require signature activity.
What types of document sets does it suit?
It is suited to engineering document packs where the team needs recipient, state, and evidence context around the set rather than around a single attachment.
Can Envelope connect to Identify?
Yes. Envelope is designed to carry organisation context from Identify into document distribution workflows.
Is Envelope available in private beta?
Yes. Envelope is part of the current product suite for selected private-beta workflows.
Testing controlled document packets?
Tell us how your team packages and distributes document sets today. We will confirm whether the private beta is a fit before onboarding.
Request beta access