Sign in Apply for early access
Export

Client review on your terms,delivered with its record

The client checks.
You decide each request.

Send the client the draft of exactly the version QA passed, from your own email. Enpasse places each request on its page with a suggested change or reply, and your lead decides.

From the email to the report date

Each request keeps its words. One agreement writes the date in four places.

Also in client review

  • Enpasse sends nothingYour lead sends the draft. Every download is logged.
    The draft goes out from your own email. Each download names the person, the file and the version, and a shared link ends with the first delivery record.
  • Saying no costs no versionChanges wait together. One reopen starts the next version.
    A request kept as is records its reason. Requests that change a page wait until your lead reopens, so one round of changes makes one new version.
  • Agreement is a recordWho agreed, when, and to which version.
    Your lead records the client's agreement with the person, the date and the version. Nothing is signed in Enpasse.
  • The agreement dates the reportOne date fills four places, with no new version.
    The title page, section 1.2, the AOC cover and AOC Part 3 take the same date.

Seven close-out chores.
One press.

Press Finalize. What a record can do, Enpasse does. Sending stays with your lead.

Save as PDFDOCXROC_Northwind_2026_v3.docx
Name the finalPDFROC_Northwind_FINAL_v3_final2.pdf
Lock the Word fileRestrict editing
Match the AOC date to the ROCROC 1.216 NovAOC 316 Nov
Hash each file$ shasum -a 256 *.pdf
End the client's review linkAnyone with the link
Note who got which file17 NovL. ChenROC PDFv3?
Send the files to the client@To L. Chen, Northwind Retail
Final, version 3View only
Report on CompliancePDF91c6f3a0d2e8
Report on ComplianceWord5d02e8a1b7f4
Attestation of CompliancePDFc47e19b2d860
  • Dates checked across ROC and AOC
  • Every page view only
  • Client review share ended
  • Every download from here is logged
MRFinalized by Maria Reyes16 Nov, 10:02

Still your lead's: send the files, then record the delivery.

Finalize once.
Deliver with a record.

One press locks the files, each with a short hash that proves which file went out. Your lead sends them and records it.

Version 3, finalMaria Reyes, 16 Nov, 10:02
  • ROC_Northwind_2026_v3.docxReport on Compliance, 2.4 MB5d02e8a
  • AOC_Northwind_2026.pdfAttestation of Compliance, 0.6 MBc47e19b
  • Record of decisionsEvery act, approval to deliverya91f3c2

Final means final

Every page view only. The first delivery record ends every share.

An approved version
never changes

A late change is named, never absorbed. A fix after delivery is a correction: the next version, with a new agreement and report date, while the old files stay, marked Replaced.

QA checks only what changed

Every version keeps its changed pages, its files and their hashes. Scrub the history, or pick a version.

Any copy names
its version

Pick a copy that turned up. Its hash says which version it is, and who received it.

Copies that turned up

Pick a copy to check it against the record.

Delivery recordNorthwind Retail, ROC 2026
No copy picked
  1. Version 4Final, correctione2b9047d1c3a
  2. Version 3Delivered, replaced91c6f3a0d2e8
  3. Version 2Draft for client review3f80aa61c94e
  4. Version 1Draft, not sentb6d2147e08f5

The record keeps a hash of every file it ever released.

The delivery record

Questions the record answers

Months later, a reviewer asks what went out and why. The record answers, with names and times.

The record

Every act from approval to delivery. Pick a question to light its lines.

Agreed and final.
Delivered with its record.

Apply for early access Read about security