GP User Guide

For investor relations, fund operations, counsel and GP signatories · Draft for customer review, 15 November 2026

About this draft. This guide describes zSign as designed for v1. Screens referenced here are in the clickable prototype (prototype/index.html). Names and figures in the prototype are sample data. Tell us where the guide or the product doesn’t match how your team works — see feedback/Customer_Feedback_Kit.md.

What zSign does

zSign sends subscription packets, LPAs, side letters and tax forms to your investors already filled in from Investor Onboarding, routes them to every person who needs to act — joint holders, trustees, IRA custodians, tax preparers, counsel — and gives each signer a plain-English briefing of what they’re signing. You countersign in batches, and every completed packet is sealed and filed to Secure Data Room automatically.

It sits in the Zive platform beside LP Roster, KYC & AML and Secure Data Room. Pick your firm and fund in the top bar; everything you see is scoped to that fund.

Who does what

Role Typical person What they do in zSign
Sender Investor relations, fund operations Creates and sends packets, chases signers, answers questions investors choose to send
Template author Fund operations, counsel Uploads documents, maps fields, builds templates
Approver / counsel General counsel, CCO Approves templates, AI explanations and any edited labels; replaces document versions
GP signatory Managing partner Countersigns subscriptions, records admission
Auditor External auditor Reads certificates and audit trail only

Templates can require a second person to publish (separation of duties). Seeing unmasked tax IDs needs its own permission.

Your closing dashboard

Prototype: 01 Closing dashboard

The dashboard shows one close at a time: how many packets are sent, with investors, waiting for your countersignature, completed and overdue. The Needs attention list tells you why each packet is stuck — a delegate who hasn’t finished, someone re-reading a page, a decline — and the fastest action for each.

Questions sent to IR shows only questions investors chose to send you. Questions investors ask the AI about the document stay private to them.

Sending one packet

Prototype: 04 New packet — prefill review

  1. Investor. Choose the investor from LP Roster. Their capacity (individual, joint, IRA, trust, entity) comes from onboarding.
  2. Signing setup. If the investor has a saved signing profile on Zive and has shared it with your firm, it fills in who signs, delegates and CC. You can propose changes; the investor approves them.
  3. Templates. zSign picks the right templates for the investor’s capacity — for example, a W-8BEN-E for a non-US entity, spousal consent where your rules require it.
  4. Prefill review. Check what was filled in. The colors are the same as in KYC & AML:
  5. Routing and message. Confirm steps, people, reminders and CC.
  6. Preflight and send. Preflight freezes the documents, values and routing. If anything changes afterwards, run preflight again.

If a send times out, the packet shows Send uncertain while zSign checks what happened. It will never send twice; don’t resend by hand.

Routing, delegates and CC

Prototype: 03 Packet detail

A packet runs in steps. Everyone inside a step acts at the same time; steps run in order.

Situation How to set it up
Joint holders One step, both holders, “all must sign”
Tax preparer completes a W-8 first Step 1 preparer → step 2 investor
Family-office counsel approves first Step 1 approver → step 2 signer
IRA Beneficial owner step → custodian step
Entity with two authorized officers, either can sign One step, “any 1 of 2”
Your countersignature Final step, optionally gated on KYC cleared and subscription accepted

Delegates only see what they’re granted: specific documents, fields and actions, until an expiry date. A tax preparer can fill a tax form but can never certify or sign it. A spouse, an assistant or a shared inbox never gets authority automatically — someone signs for an investor only when there’s an authority record (trust certificate, incumbency, power of attorney) behind it. If an investor asks for someone else to sign, the request goes to an authority review queue.

CC recipients get only the documents you allow. You can strip tax forms from CC copies.

Bulk sends and the objection forecast

Prototype: 05 Bulk send

Pick a close and an LP list from LP Roster. zSign builds one packet per investor, groups them by capacity, and holds back anything it can’t send (missing signatory, missing email, conflicting tax status) in an Exceptions list you can fix in place. Nothing is sent until you approve the dry run. If some sends fail, retry just those rows.

The Objection forecast lists clauses likely to draw questions or side-letter requests in this close, with the clause reference and suggested FAQ text you can attach to the packets. It’s for your team only. It uses your firm’s past side letters, declines and shared questions only if an admin has turned that on in Settings (off by default), and it never compares against another investor’s side letter.

Placing fields on documents

Working prototype: switch to Dana Whit → Templates & fields → Subscription · Individual

Every template holds one or more documents and the fields each recipient fills in or signs, like DocuSign.

  1. Pick the recipient on the left (Investor, Spouse, GP signatory, or any role you add). Each has its own colour; new fields go to the highlighted one. The number beside a role is its signing order.
  2. Add fields. Drag a field type onto the page, or click the type and then click where it goes. Available types: Signature, Initials, Date signed; Full name, First name, Last name, Email, Company, Title; Text, Number, Checkbox, Radio button, Dropdown, Date, Formula and Attachment.
  3. Arrange. Drag a field to move it, drag its corner to resize, use the arrow keys to nudge (Shift for bigger steps). Delete removes it, Ctrl/⌘+D duplicates it, Undo takes back the last change.
  4. Set properties in the right-hand panel: recipient, label and help text, required, read-only, and Prefill from Onboarding / LP Roster so investors never retype what they already gave you. Depending on the type you can also set validation (email, ZIP, phone, SSN/TIN), number ranges and currency format, dropdown options, radio and checkbox groups (“at least one of these”), formulas, and conditional logic (“show only when Subscribing as = Entity”).
  5. Review AI suggestions. zSign scans uploaded documents for blanks and signature lines it thinks need a field; add or dismiss each.
  6. Preview as signer. Fill the template as any recipient with sample data and run the same required-field check a signer hits.
  7. Publish. Template checks list anything that would break signing (a recipient with nothing to sign, a dropdown with one option, a formula with no source). Fix the errors and publish a new version. Packets already sent keep the version they were sent with.

Fixing things after you send

What changed What happens
A recipient’s email, before they act Corrected in place; logged
Adding a CC or a read-only reviewer Added in place; logged
Any document content, a filled-in value, or who signs The packet is voided and reissued. Everyone signs the new one, including people who already signed. The voided packet keeps its full record.

Signatures are never moved from one version of a document to another.

Replacing a document version

Prototype: 08 Version manager

When counsel sends a new version, upload it once.

  1. zSign shows what changed clause by clause (counsel approves this summary before investors see it).
  2. It maps every field from the old version to the new one and shows the result: Exact, Moved, Changed context, Ambiguous, Missing or New.
  3. You review everything that isn’t Exact. Signature and certification boxes always need a person to confirm their placement, even if they only moved pages.
  4. Choose who gets the new version: new packets only; also drafts; or also packets already sent (they’re voided and reissued, and anyone who signed signs again).

Completed packets are never changed. If a completed agreement needs to change, send an amendment or a new agreement. If an investor finishes signing while a replacement is running, their completed packet stands.

AI explanations and your approval

Prototype: 09 AI review

For every document version, zSign drafts a short briefing, key terms and a hint for each section people sign. Your counsel reviews them before they reach investors:

The AI explains; it never gives legal, tax or investment advice and never tells anyone whether to sign.

Countersigning and admission

Prototype: 06 Countersign queue

Packets appear here once every investor-side step is done. Select several and countersign with one SSO + MFA approval. Packets blocked by KYC show why, with a link to KYC & AML.

After countersigning, zSign seals each packet, verifies it and files it to Secure Data Room. Only then does it show Completed and send copies.

Admission is separate. Signing doesn’t admit an investor. Record admission (or rejection) when funding and your other checks are done; it’s logged with your name and the effective date.

The completed record

Each completed packet has:

Download them from the packet, or find them in Secure Data Room. Tax form details write back to LP Roster after your CFO or fund operations approves the change.

Settings

Prototype: 10 Settings — connectors

Common questions

Can I see what an investor asked the AI? No — unless they choose to send it to you.

Can an investor’s advisor see the tax form? Only with an explicit tax grant on their delegate access.

What if the AI is down? Investors still see the full document with “Explanation unavailable”. Whether they can sign meanwhile is a template setting.

Can I reuse a W-9 from another fund? Not automatically. Tax forms are collected per request.

Does zSign replace our counsel’s review? No. It helps investors read and helps your team prepare; counsel stays in control of the content.