Sign how you want.
Field what you need.

Three creation methods all produce legally valid signatures. Drawn signatures captured by mouse or touch screen for the most natural handwritten feel. Uploaded image signatures for signers who have an existing handwritten signature they prefer using consistently across documents. Typed signatures where the signer types their name and picks from styled signature fonts. Signers choose which method to use at the moment of signing, and the platform records the method along with the audit trail.

Drag any field type from the toolbar onto any page of the document, drop it where needed. Field positioning is pixel precise rather than snapping to a grid. Resize handles let the sender adjust dimensions. Multi page documents show every page so fields can be placed on any page, not just the first or last. The placement preview shows exactly how the field will appear to the signer when they receive the contract.

Five field types cover every common contract need. Signature fields capture the signing action. Initial fields capture per-page acknowledgement, smaller and visually distinct from signatures. Text fields capture typed inputs like names, addresses, and deal terms. Checkboxes handle opt-ins and conditional terms. Date fields capture execution dates, validity windows, or effective dates with consistent format. Each type can be marked required so signing cannot complete without all required inputs.

Each field gets assigned to one specific signer. The client signs the client signature field. The counsel initials the counsel initial fields. When the document goes out for signing, each signer only sees and can interact with their own assigned fields. Other signers' fields are visible as context but not editable. This prevents the wrong person signing the wrong field, filling out fields meant for the other party, or skipping fields they should have filled.

Sender only fields hold information the sender fills but the signer never sees or touches. Internal reference numbers, deal classifications, routing codes, account identifiers, classification tags. The data lives on the document for the team's records and reporting, but it never appears in the signer's view of the document. The signer cannot accidentally see internal data and cannot modify or interfere with fields meant only for internal use.

Signature Fields & Types covers what gets signed. Signing Workflows covers how the signatures get collected. Signature Fields & Types is about creating signatures, placing fields, and assigning per signer. Signing Workflows is about whether signing happens sequentially or in parallel, whether approval chains apply, whether public embedded forms or scheduled sending is used. Together they cover both the field setup and the routing pattern that defines how the document moves through signing.