Signature UX: draw, place and save the right copy

Ask for initials when initials are required

SignNow names its canvas as initials and provides drawing corrections before Done. Docusign also presents an Initials canvas, with Clear, Create and pen controls. Both examples make the requested kind of mark explicit before the person invests effort in drawing. That small distinction matters more than adding another decorative pen icon.

Carry that object identity into the next step. If the document requests initials in a small field, do not silently substitute a full saved signature because both are represented as images internally. Keep separate labels, previews and selection options for the supported mark types. Where a person can choose a different method, explain what will be inserted rather than making every option look like a generic signing action.

A notice beside the canvas may describe terms or consent, but its presence does not prove the entire signing workflow meets a particular legal requirement. Review those requirements separately with the appropriate specialists. From an interaction perspective, keep the notice readable and distinguish accepting it from clearing a drawing, creating a reusable mark or completing the document.

Make the move from canvas to page visible

FormaPDF tells the person that the drawn signature will be placed on the document page. SuperScan shows the other side of that handoff: a selected signature object on the page, with handles and a saved-mark thumbnail. Together they illustrate two different workspaces rather than two visual versions of the same completion state.

Use action labels that match the next transition. Continue to placement is clearer than Done if the mark still needs a location. Save signature is different from Save document. The exact wording can be short, but the person should know whether a button preserves the drawing, inserts an object or writes the document revision. Avoid reporting the final task as finished while the workflow is still waiting for placement.

Keep the receiving page visible enough to establish context, especially in a multipage file. If insertion defaults to the current page, preserve that page identity across rotation and navigation. When a captured mark returns from a separate canvas, do not position it on a different page simply because the document viewer restored an unrelated scroll location in the meantime.

Give drawing room without losing the task

PDF App Convert Create Sign uses a landscape drawing area with Save, Cancel and Clear. Documents File Manager also offers a landscape signature workspace with color, thickness and a save action. The larger canvas helps the gesture, but it temporarily removes the surrounding document context that made the mark necessary.

Preserve work through supported orientation changes and interrupted drawing. A rotation should not turn an almost-finished signature into a fresh blank state without warning. Keep canvas coordinates independent of the displayed viewport, and avoid stretching the resulting mark to fill its destination field. A wider capture area is not permission to distort the person’s strokes when the app returns to portrait.

Explain how to start over without confusing clearing the canvas with cancelling the whole document task. Offer supported non-drawing methods where appropriate, such as a typed or uploaded mark, with truthful labels about what each method creates. Do not force a fine motor gesture to be the only route through a document workflow when the product can provide an accessible alternative.

Keep pen changes and undo understandable

iScanner exposes stroke thickness, color and correction tools in Edit Signature. eSignApp places its drawing controls beside Clear, Cancel and Save. These are useful reminders that a signature editor is still an editor: a person may need to recover one stroke without losing every previous decision or accidentally leaving the task.

Define the scope of each correction. Undo should reverse a meaningful editing step, while Clear should empty the current capture with an appropriate recovery policy. Changing color or thickness can affect future strokes, the entire mark or a selected element; whichever behavior the product supports, show it consistently. A small preview should not hide a change that only becomes obvious after document placement.

Keep the enabled state of Save tied to a valid supported mark rather than simply to the presence of touch events. An accidental dot, an empty cleared canvas and an intentionally minimal mark need thoughtful handling without pretending that a visual heuristic can authenticate a person. Validation here should prevent obvious editing mistakes, not make unsupported claims about identity or legal acceptance.

Make selected-object controls safe to use

Scanner App Fast PDF Doc Scan shows a signature placement object with delete and resize controls. Scanner App Scan PDF Docs also displays a selected mark on a page with its own editing handles and a page indicator. Those controls should establish what is selected, not cover the very part of the document the person needs to inspect.

Provide enough room around handles and account for the zoom level of the document. The same finger movement should not produce wildly different results because the app mixed screen coordinates with page coordinates. Preserve the mark’s proportions when resizing unless the product intentionally offers another behavior. Make deletion a separate, named action rather than a tiny unexplained symbol beside a crowded corner.

Before saving, let the person inspect the mark against the actual page, including its relationship to nearby labels or fields. If the document revision changes, invalidate or review placements that no longer point to the intended content. A placement model tied only to page number and a fitted preview can fail when pages are inserted, reordered or replaced.

Model the mark and the document separately

Keep a captured mark asset, a placement instance and a document revision as different records. A placement references the intended page identity, geometry and mark asset. Saving a reusable mark should not automatically commit every pending placement, while saving a document should not silently add the mark to a reusable library. These are separate user choices even if the storage layer can perform them together.

Treat reusable signatures as sensitive personal material. Explain whether the mark remains on the device, is associated with an account or is uploaded, according to the actual implementation. Provide the relevant deletion and reuse controls without promising a storage policy that the product does not enforce. Do not put signature images or document contents into ordinary analytics events just to measure the editor.

Name the resulting artifact and preserve a recovery path. If writing or exporting fails, retain the editable placement and identify whether a previous copy still exists. A document saved inside the app is not automatically a file delivered to another person. Keep downstream sharing progress separate, and do not replace an uncertain outcome with an unconditional Signed and sent message.

Inspect the final copy, not only the canvas

Give a tester a multipage document and ask them to add initials on one page and a signature on another. Rotate during capture, undo a stroke, change thickness and cancel one placement. Ask which mark is reusable and which document revision contains it. A confident explanation is more informative than a fast sequence of taps through the happy path.

Test page reordering, zoomed placement, large text, screen-reader navigation and a failed save. Open the resulting document through the supported viewing path and inspect position, scale and page identity. This checks the implementation’s artifact behavior; it does not certify legal validity. Include deletion of a saved mark without assuming that already-created document copies change with it.

Measure misplaced objects, repeated capture, accidental clearing and failed-save recovery separately. Do not interpret every return to the canvas as friction: a person may be deliberately improving a mark. Use task observation to distinguish useful correction from confusion, and avoid collecting the actual signature or document text when aggregate editing events can answer the question.

Review capture, placement and output

Use these checks on a working build, not only on the polished reference state.

• ✓Initials and full signatures retain distinct identities.
• ✓Capture, reusable storage and document save have clear labels.
• ✓Rotation and undo preserve recoverable drawing work.
• ✓Placement survives zoom without stretching the mark.
• ✓Page changes cannot silently move a mark to unrelated content.
• ✓Sensitive mark storage and deletion reflect actual behavior.
• ✓A failed save does not masquerade as a delivered document.

Related design decisions

The camera and scanner examples cover the earlier capture stage. Keep the source document readable before asking someone to place a consequential mark on it.

Use the sharing and export examples to distinguish the edited document from a saved or delivered copy after placement is complete.