Completion signatures

Signatures record that a person reviewed the solution and accepted the organization's completion statement. They are not needed unless the policy allows or requires them.

Availability: both organization modes; configuration requires administration, while capture depends on the resolver or authenticated requester. Level: Advanced.

What it is for

It adds completion evidence to each resolution cycle, either through an on-site signature on the device or a remote request to the report creator.

Before you start

An administrator selects a policy:

Policy	Behavior
Disabled	The report is resolved with the usual summary and no signature.
Optional	The resolver may continue without a signature, capture one on site, or request it from the requester.
Required	Every cycle must have an on-site or remote signature. An administrator may record a justified waiver.

The administrator also configures the completion statement, up to 1,000 characters, and whether the signer's relationship or title and identity document are required. The name is always required.

On-site signature

In an In progress or Waiting report, choose Resolve.
Enter a summary from 5 to 4,000 characters.
Select Sign on site.
Enter the signer name and any required additional information.
The person draws the signature on the device and accepts the statement.
Save with Sign and complete.

The report becomes Resolved immediately. The confirmation preserves the solution, statement, supplied identity, time, channel, and signature for that cycle.

Remote signature

The assignee enters the solution and selects Request signature.
The report becomes Signature pending and its creator is notified.
The authenticated creator opens the report and reviews the solution and statement.
They provide title or document if required, draw the signature, accept, and confirm.
The report becomes Resolved.

A remote signature can be requested only from the authenticated report creator while that person retains an active membership. The name comes from their account and is not replaced in the form.

Cancellation and waiver

The assignee or an administrator can cancel a pending request with a reason from 5 to 500 characters. The report returns to its previous operational status if the assignee remains active; otherwise it becomes Open and unassigned.

When policy is Required, an administrator can use Complete with waiver and enter a 5-to-500-character reason. The waiver is recorded as evidence. An optional signature request cannot be waived.

Rules and effects

The signature confirms both the statement and resolution summary.
Consent is required for every signature.
Only one confirmation is stored per cycle. Reopening starts another cycle and may require another signature.
A required signature prevents directly closing active work without a signature or waiver.
Changing settings affects future attempts; it does not alter frozen evidence or existing requests.
While Signature pending, incompatible operational actions such as inventory and transfer are blocked.

Required and optional

The summary, name, drawn signature, and consent are always required. Title and document depend on settings. A waiver always requires a reason. Under Optional policy, using a signature is voluntary.

Example

A technician completes an installation in front of the site manager. She enters the solution, the manager provides name and title, signs on screen, and accepts the statement. The report becomes Resolved with evidence visible to authorized people.

Privacy and limits

Signature images and data are private. Only people with specific confirmation access, such as requester, assignee, current line, and administrators, can view them. They are not included in public tracking or notifications. A ReportArea handwritten signature is operational evidence; its formal value depends on the rules applicable to your activity.