Signatures

Customer signature (and other signers as the type requires). Capture on the job, Confirm signature, Clear to recapture before it is locked. This is a first-party pad, not DocuSign.

Screen path: job detail → Customer signature → /app/jobs/:appointmentId/signatures/:definitionId. Capability signatures on the workspace hides the card when off. Native Field is not the Field PWA.

Signature pad. Sample data. This documentation does not claim legal enforceability.

Preconditions

Type	When you can capture
customer_authorization	Arrived or Working
customer_acknowledgement	Working only
custom	Working only

You cannot invent a signature type. Too early: Not available yet. If the definition is not in the cache: This signature is not available offline.

Required unsigned signatures block Complete job. Capturing a signature does not Complete the work order.

Loop

1. Open the signature definition from job detail.
2. Read the exact server statement shown on screen.
3. Enter Signer name (required). Role (optional) is optional.
4. Sign on the pad. Clear lets you redo before confirm. Blank pad: “Please sign before confirming.”
5. Tap Confirm signature. Status: Signed · Pending sync until upload succeeds.

Row states: Required · Not signed, Signed · Pending sync, Signed, Not available yet. A sync waiter is not a missing signature.

What works / does not work

	Works	Does not work
Offline stroke	PNG + pending	Finishing multipart while the app is killed
Required signature	Blocks Closeout until captured	Legal-validity guarantee
Service report share	Not in this app	Promising a signed PDF before Sync is clear

A signature is an application artifact stored with the visit / later service-report snapshot. No legal-validity guarantee.

If the card is missing: capability off, or the snapshot has no definitions. If Closeout is still blocked after you signed: distinguish Required · Not signed vs Signed · Pending sync.

Related: Complete job · Sync Center.