NueSign — E-Signatures Inside Your Forms

NueSign lets you collect legally-binding electronic signatures directly within your forms. No separate signing service, no external redirects — contracts are just another question type in the form builder.

What Is NueSign?

NueSign adds a contract question type to NueForm. A contract question displays a document (written in markdown or uploaded as a PDF) with fillable fields — text inputs, signature pads, date pickers, checkboxes — that can be assigned to one or more signer slots.

Key concepts:

• Contract question — a form question that renders a signable document
• Signer slots — numbered positions on the contract (e.g. "Slot 1: Buyer", "Slot 2: Seller")
• Signing sessions — instances of the contract sent to real people with unique signing links
• Inline fields — fillable fields embedded in the contract text using markdown tokens

Because contracts live inside your forms, you can combine them with any other question type — collect intake information, run logic jumps, show statements, then present the contract for signing.

Creating a Simple Consent Form (1 Signer)

The simplest use case: a single person signs a document.

Step 1: Add a Contract Question

1. Open the form builder and click the Add tab
2. Scroll to Advanced and click Contract
3. Click Manage Contract Settings in the side panel

Step 2: Write the Contract Text

In the Document tab, select Write Contract and enter your text:

# CONSENT FORM

I, {{text:Full Name | required, slot=1}}, consent to participate
in the study described above.

Date: {{date:Consent Date | required, slot=1}}

Signature:
{{signature:Participant Signature | required, slot=1}}

Step 3: Configure the Signer Slot

Switch to the Signer Slots tab. You should see Slot 1 auto-created. Give it a label like "Participant".

Step 4: Create a Signing Session

Switch to the Sessions tab and click Create New Session. Fill in the signer details (optional) and click Create Session. You will receive a unique signing link.

Step 5: Share the Link

Copy the signing link and send it to the participant. When they open it, they will see your form, fill in the contract fields, and sign.

Employee Onboarding Form with Contract

Combine intake questions with a contract for a complete onboarding flow.

Form Structure

1. Welcome screen — "Welcome to Acme Corp"
2. Short text — Full legal name
3. Email — Work email address
4. Date — Start date
5. Address — Home address
6. Contract question — Employment agreement

Contract Text Example

# EMPLOYMENT AGREEMENT

This Employment Agreement is entered into on {today_date}
between **Acme Corp** ("Company") and **{slot1_firstName} {slot1_lastName}**
("Employee").

## 1. POSITION

Employee will serve as {{text:Job Title | required, slot=1}},
reporting to {{text:Manager Name | required, slot=1}}.

## 2. COMPENSATION

Employee will receive an annual salary of
${{number:Annual Salary | required, slot=1}}.

## 3. START DATE

Employment begins on {{date:Start Date | required, slot=1}}.

---

**Employee Signature:**
{{signature:Employee Signature | required, slot=1}}
Date: {{date:Employee Sign Date | required, slot=1}}

With one signer slot, the employee fills out the intake questions, then signs the contract at the end.

Business Agreement with Counter-Signing (2 Signers)

For agreements between two parties — buyer/seller, client/vendor, landlord/tenant.

Contract Text

# SERVICE AGREEMENT

This agreement is entered into on {today_date} between
**{slot1_firstName} {slot1_lastName}** ("Client") and
**{slot2_firstName} {slot2_lastName}** ("Provider").

## SCOPE OF WORK

Provider agrees to deliver the services described below:
{{text:Service Description | required, slot=2}}

## COMPENSATION

Client agrees to pay ${{number:Amount | required, slot=1}} upon
completion of services.

---

**Client Signature:**
{{signature:Client Signature | required, slot=1}}
Date: {{date:Client Date | required, slot=1}}

**Provider Signature:**
{{signature:Provider Signature | required, slot=2}}
Date: {{date:Provider Date | required, slot=2}}

Signer Slots

Creating the Session

1. Click Create New Session
2. Enter names and emails for each signer (optional but recommended)
3. Set Signing Order to "Sequential" if the client must sign first
4. Click Create Session

Each signer receives their own unique link. When they open it, they see the full form but can only fill in their assigned fields.

Multi-Party Deal (3+ Signers)

NueSign supports unlimited signer slots for complex agreements.

Sequential Signing

Signers must sign in order. Signer 2 cannot access the document until Signer 1 has completed. Use this for approval chains.

Set Signing Order to Sequential in the session settings.

Parallel Signing

All signers can access and sign the document simultaneously. Use this when order does not matter.

Set Signing Order to Any order in the session settings.

Example: Three-Party Agreement

# PARTNERSHIP AGREEMENT

**Partner A:** {{text:Partner A Name | required, slot=1}}
{{signature:Partner A Signature | required, slot=1}}

**Partner B:** {{text:Partner B Name | required, slot=2}}
{{signature:Partner B Signature | required, slot=2}}

**Witness:** {{text:Witness Name | required, slot=3}}
{{signature:Witness Signature | required, slot=3}}

Configure three signer slots in the Signer Slots tab and create a session with details for each party.

Using Markdown Inline Fields in Contracts

Syntax Reference

Inline fields use the {{type:label | properties}} syntax:

Properties

• required — field must be filled before signing (boolean, default false)
• slot=N — assign the field to signer slot N (number)
• Fields without slot are editable by all signers

Examples

Full name: {{text:Full Name | required, slot=1}}
Agree to terms: {{checkbox:Terms Agreed | required, slot=1}}
Preferred tier: {{dropdown:Service Tier | slot=1, choices=Basic;Standard;Premium}}
Initials here: {{initials:Page Initials | required, slot=1}}

Using Variables in Contract Text

NueSign supports two kinds of variables in contract text:

Form Variables

Use {variableName} syntax to insert answers from previous questions or system values:

• {today_date} — current date
• {form_title} — the form title
• Any previous question answer by its variable name

Slot Variables

Slot variables resolve from the signing session configuration:

• {slot1_firstName} — first name of Signer 1
• {slot1_lastName} — last name of Signer 1
• {slot1_email} — email of Signer 1
• {slot2_firstName}, {slot2_lastName}, {slot2_email} — for Signer 2
• Pattern continues for additional slots

These values come from the session creation form, where you enter each signer's details.

Managing Signing Sessions

Creating a Session

1. Open the contract question settings and go to the Sessions tab
2. Click Create New Session
3. For each signer slot, optionally enter first name, last name, and email
4. Configure session settings:
   • Signing Order — Sequential or Any order
   • Expiry — how long the signing links remain valid
   • Password — optional password protection
5. Configure privacy, copy distribution, and notification settings
6. Click Create Session

Tracking Progress

The Sessions tab shows all active and completed sessions:

• Each session displays its status (e.g. "1 of 3 signed")
• Individual signer status: Signed, Pending, or Declined
• Signed timestamps
• Signing links for pending signers

Voiding a Session

Click the Void button on an active session. All pending links are invalidated, signed parties are notified, and PDFs are watermarked "VOIDED".

Resending Signing Requests

Click the email icon next to a pending signer to resend the signing request email.

Privacy Settings

Hiding Other Signers' Fields

When creating a session, enable Hide other signers' filled fields. Each signer will see other signers' contract fields as blurred/redacted. The final signed PDF shows all fields unblurred.

Use this when signers should not see each other's information (e.g. salary details in multi-party agreements).

Email Verification

Enable Require email verification before signing. Signers must verify their email with a 6-digit code before viewing the contract. This adds an extra layer of identity verification.

Sending Custom Signing Request Emails

When creating a session with signer emails, you can enable Send signing request emails and customize the message:

Hi {slot_firstName},

Please review and sign the Service Agreement.

Click here to sign: {slot_link}

This document expires on {expiryDate}.

Available variables in the email template:

• {slot_firstName}, {slot_lastName}, {slot_email} — signer details
• {slot_link} — unique signing link for this signer
• {expiryDate} — session expiry date

Status Notifications

Configure notification emails when creating a session:

• Enter one or more email addresses to receive updates
• Choose which events trigger notifications:
  • Each signature — when any signer completes
  • All complete — when all parties have signed
  • Decline — when a signer declines
  • Expiry — when the session expires

Downloading Signed PDFs

After all parties have signed, the final PDF is generated with all signatures, filled fields, and an audit trail appended. You can download it from:

• The Sessions tab in the contract settings (click Download PDF on completed sessions)
• The dashboard response detail view

The audit trail page includes timestamps, IP addresses, and browser information for each signer.

Legal Compliance (ESIGN Act / UETA)

NueSign is designed to comply with the U.S. Electronic Signatures in Global and National Commerce Act (ESIGN Act) and the Uniform Electronic Transactions Act (UETA):

• Intent — signers click an explicit "Sign" button; signatures are never auto-submitted
• Consent — mandatory checkbox with legal disclosure before signing
• Association — signatures are embedded in the document and linked to the signer
• Retention — signed PDFs are stored indefinitely in secure cloud storage
• Audit trail — each signature is timestamped with IP address and browser details, appended to the PDF
• Opt-out — signers can decline with an optional reason
• Copy provision — configurable per session (ask, always send, or disable copies)
• Integrity — SHA-256 hash for tamper evidence