Forms, waivers, and e-sign

Site admin → CRM → Documents is the library for waivers, intake forms, letterhead, and uploaded PDFs. You prepare a letter or PDF by dragging Standard fields onto the page—the same idea as DocuSign Prepare, without a nested field form. Attach a package to a service (required before confirm, or after), or send it from automations.

Packages, answers, and signed PDFs live only on the site. They are not copied into NurtureSite’s sales CRM and never appear on factory lead webhooks.

NurtureSite is not a DocuSign clone. We copy the eSignature core local service businesses actually use (templates, fields, embedded/remote sign, audit + certificate). We skip DocuSign IAM, CLM, identity verification, notary, bulk send, and in-document payments.

Compose or upload

The editor is a Prepare workspace (DocuSign-familiar): pick a recipient, drag Standard fields onto the page, click a tag for properties. Composed letters are edited in place; PDF uploads are tagged on the page.

• Compose — US Letter or A4. Content rail: heading, section, body, logo, image, divider. Insert customer data puts {{name}}, {{site_name}}, … at the caret. Fields appear as colored tags (not a form grid). Gold = Primary (booker); other recipients get their own color plus a label.
• Starters — blank, letterhead, waiver, intake.
• Upload PDF — drag Signature / Initials / Date signed onto each page. Use the page guide for multi-page PDFs. Word and Pages files are not converted on this server; export to PDF first.
• Form only — stacked fields without a letter page (same field catalog).
• Preview as signer — interactive pads and inputs; nothing is saved. Preview / print uses the same layout as the signed PDF.

Click a tag for Field properties: required, recipient, data label, read only. More details (collapsed): prefill from customer data, save answer to CRM, validation, options, show-if. Bindings store keys (not “Patient” labels), so renaming the CRM noun does not break packages. Save warns if the document has no Signature or Initials field.

Attach to a service

On Scheduling → Services, attach packages as:

When	What visitors see
Required before confirm	Slot stays held until signed. The widget returns a sign URL instead of Stripe Checkout. After every required envelope is complete, Checkout starts if the service has a deposit; otherwise the booking confirms.
After confirm	Sent once a CRM record exists (after the appointment confirms). Uses a record signing link, not the booking manage token.

The booker is the signer at booking time. Phone-only bookers can sign in the widget without an email. Remote email send is skipped unless the package collected an email — we do not mail empty addresses.

Hold while signing uses max(slot hold minutes, 30) and bumps while the envelope is in progress (cap 60 minutes from create when any required package exists). Cancel or an expired hold voids open envelopes.

Staff calendar bookings that skip to confirmed (force_confirmed) can skip required-at-book and send the package later from the CRM record.

Group classes and waitlists

• Group: one envelope per booking (the person who reserved). Party size is not N signatures.
• Waitlist join has no package. Packages start when promotion creates a held appointment.

See Group and class bookings and Booking waitlists.

After the record exists

Confirmed bookings create or match a CRM record, then attach the flattened PDF and Certificate of Completion. Mapped answers write back to custom fields / additional_data / contact fields after that record exists — never into the factory create payload.

Merging duplicate records re-points Lead envelopes (and signer contacts) onto the survivor so signed PDFs do not vanish.

Automations

Node / trigger	Behavior
Fill document	Internal: merge tags into the package and attach the PDF. Does not email. Allowed in HIPAA mode.
Request signature	Sends a signing link to one person (send-to, primary, or a contact role such as guardian/parent). Never “all contacts.” HIPAA: requires PHI communication consent, like email.
Wait until document signed	Continues when that envelope completes (envelope_completed).
Document signed / declined	Triggers (document_completed / document_declined).
Attach document	Still copies a media-library file (unchanged).

Signer role is not the same as Send to. Preschool “all contacts” would email the student — request signature maps to a contact role instead.

Conditions can read envelope.status and form.* field values stored on the enrollment.

Demo/preview sites do not run live automations. The library and embedded booking sign still work.

Do not email filled health-history PDFs in HIPAA mode. Request signature is consent-gated; fill document stays internal.

Evidence (ESIGN / UETA)

Before signing, the recipient accepts a click-through electronic signature disclosure. They can type a name or draw a mark. The site stores an audit trail (IP, time, events), a SHA-256 of the flattened PDF, and a Certificate of Completion. Signed files are private (staff or the original signing link), not public media URLs.

This is an evidence pattern for typical service waivers and intake — not a notary, identity-verification, or legal-advice product. Help copy stays honest: typical US waivers, intake, and photo consent — not closings, loans, or wills.

Delete a package

You cannot delete a package while envelopes are in flight. Detach it from services first. Completed envelopes keep the pinned version bytes.

Industry examples

Industry	Typical seed
Dental	Required waiver on New patient exam
Fitness	Optional class waiver
Preschool	Enrollment forms, then the $200 deposit
Restaurant	Library only (no booking types required)
Home services	Homeowner / spouse signer on the household

DocuSign: what we copy vs skip

DocuSign’s current product is three platforms (eSignature, IAM/Maestro, CLM). We copy eSignature for local businesses, not IAM, CLM, or identity verification.

Copy (in this product)

DocuSign-class capability	How it shows up here
Templates	Document packages (compose or upload) with a Prepare workspace and versioned field catalog
Tabs / fields	Signature, initials, date signed, text, number, date, checkbox, radio, select, file, image; required vs optional; validation; locked merge-tag prefill; simple show-if
Embedded signing (PowerForms analog)	/sign/{token} in the booking widget or a hosted page
Remote send	Email or SMS to one mapped CRM contact role (never all contacts)
Envelope lifecycle	Complete, decline, void on cancel or expired hold, expire, hourly reminders, resend (new token)
Pin versions	In-flight envelopes keep the field map they started with
Audit + Certificate of Completion	Envelope events + CoC PDF
ESIGN disclosure / intent	Click-through disclosure + typed or drawn mark + IP/user-agent/timestamps + SHA-256
Prefill from CRM	Merge tags and appointment booker fields
Write-back	Explicit mappings to custom/additional fields after a CRM record exists

Native flatten ships first (composed HTML → PDF, uploaded PDF overlays). A vendor driver later can reuse the same field map if a customer wants a third-party certificate (pass-through cost).

Schema now, UI later

These can be stored on the field/signer map today; staff UI is later:

• Two-role serial routing (guardian then patient)
• In-person kiosk on a front-desk device
• View-only acknowledgments (HIPAA notice / house rules)

Skip (not this product)

DocuSign / IAM / CLM area	Why we skip it
Identity verification (IDV), KBA, SMS OTP ID, biometrics	Extra vendor + HIPAA/PII surface
Notary / SES / qualified eIDAS / EU QES	Different legal product
Bulk send / PowerForms lists	Wrong fit vs per-booking and per-record envelopes
In-document card payments	Stripe deposits and invoices already exist
Fax / WhatsApp / Teams delivery	Email, SMS, and embedded cover v1
Formula fields and AI field placement	Out of scope for v1 waivers/intake
CLM, contract lifecycle, Salesforce/CLM connectors	Not a legal-ops suite
Admin IAM, Maestro, SSO to DocuSign, org-wide template sharing across brands	Each site has its own library
Word/Pages conversion	Client containers have no LibreOffice — export to PDF first

Do not market this as “court-ready like DocuSign.”