Electronic signature release form

Release forms (liability waivers, photo releases, contractor releases) repeat the same fields: name, date, signature, sometimes witness lines. Treat them as templates, not one-off uploads every time.

What a release form needs

Typical fields:

Field	Party	Notes
Printed name	Signer	Text
Signature	Signer	Drawn or typed
Date signed	Signer	Auto or manual
Event or project description	Signer	Optional text
Parent/guardian signature	Second party	Minors only

Atlas detects signature and date lines on PDF or DOCX uploads. Confirm placement in review before the first send.

Workflow: first send vs repeat sends

First send (trust ladder):

Upload the release PDF or DOCX via dashboard or POST /api/envelope
Open review_url, verify fields bind to the right party
Add signer email and send
Save as template once legal approves field layout

Repeat sends (template-as-product):

curl -X POST https://atlaswork.ai/api/templates/$TEMPLATE_ID/send \
  -H "Authorization: Bearer $ATLAS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "parties": [
      {"email": "participant@example.com", "name": "Jamie Lee", "role": "Participant"}
    ],
    "auto_send": true
  }'

Send number two should be one API call, not a re-upload ritual. Auto-send skips manual review when the template is trusted.

MCP path for events

Event staff with Claude connected:

Agent calls send_contract_from_template with template ID and participant email
Signer gets link on phone
Staff polls check_signing_status before admitting participant

Good for pop-up activations where speed beats dashboard clicks.

Sequential parties

If a guardian must sign after a minor, add two parties with order 1 and 2. Atlas promotes the waiting party when the first finishes. No simultaneous signing.

Release forms still require consumer disclosure on the sign page. Do not strip disclosure to speed lines at events. Atlas enables disclosure on every send.

Storage and proof

After signing:

Download signed PDF via API
Store envelope_id in your event CRM
Optionally handle envelope.signed webhook to attach file to participant record

Common mistakes

Mistake	Fix
Re-uploading the same PDF daily	Create a template
Wrong email typo	Verify in review; void and resend if needed
Missing date field	Add manually in review or fix source PDF

Credits

Drafts and detection are free. Each send consumes one credit. Bulk events should budget credits upfront at /dashboard/billing.

Industry-specific releases

Photo and video: Confirm talent name, shoot date, and usage rights paragraph reference match the body text. Detection may label lines "Printed name" generically; rename labels in review for clarity.

Contractor / liability: Often needs a second paragraph initial or checkbox. Add checkbox fields manually in review if detection missed them.

Healthcare / HIPAA: This guide is operational, not compliance advice. BAAs and retention rules are between you and counsel.

Bulk send from spreadsheet

For recurring classes or events, middleware can read CSV rows and call template send:

while IFS=, read -r email name; do
  curl -s -X POST "https://atlaswork.ai/api/templates/$TEMPLATE_ID/send" \
    -H "Authorization: Bearer $ATLAS_API_KEY" \
    -H "Content-Type: application/json" \
    -d "{\"parties\":[{\"email\":\"$email\",\"name\":\"$name\",\"role\":\"Participant\"}],\"auto_send\":true}"
done < participants.csv

Rate-limit responsibly. Each row consumes one credit on send.

Void and reissue

Wrong email on a release? Void the pending envelope, fix the address, resend from template. Resend on an already-sent envelope is free; void refunds credit only when no signer completed.

Version control

When legal updates release language, upload the new PDF, run review once, and update the template. Old envelopes in flight keep their original document version. Do not edit signed PDFs in place.

Tag template versions in your internal wiki (release-form-v3-2026-06) so ops knows which ID to pass to middleware.

Accessibility at events

Signers on phones need readable field labels. Zoom the PDF preview in review if detection placed tiny boxes. Test one signing session on iOS Safari before opening the registration line.

Offline and connectivity

The sign page requires network access. For outdoor events, plan a hotspot or delay send until the signer confirms connectivity. check_signing_status from MCP helps staff confirm completion before check-in.

Parent and minor flows

When both guardian and participant must sign, create two parties with routing order 1 (minor or participant acknowledgment where applicable) and order 2 (guardian). Atlas sends the second email only after the first party submits. Verify in review that each field's party binding matches your legal template before the first production send.

Store signed releases alongside the event record for at least as long as your counsel requires. Export via webhook attachment or scheduled API download jobs.