A service request signature request specifies whose signature is required before the request can be marked as completed in the usual way. Adding a request is not itself a signature: the signer must draw and save a signature image. There can be multiple signatures.

Where do signature requests come from?

Signature requests can be configured for a service request category as a whole or separately for an individual service request. If the category has active signature requests, an incomplete service request uses those instead of its own requests. In that case, you cannot add individual signature requests to the service request.

Spotilla User means a specific user account. Only someone logged in with that account can provide the signature assigned to it. The same user account can have only one active signature request on the same category or service request. External User means a person whose name is specified in the request and who signs on the handler's device without logging in to Spotilla themselves.

Add a signature request in the browser

From the menu, open Manage tasks → Service requests → Service requests. Open the relevant request using the pencil icon on its row and select the Signatures tab in the form. Check the request's title and description before configuring signature requests.

  1. On the tab, select Add Signature.
  2. Select User Type. For a Spotilla user, select the account in the Spotilla User field; this fills in the signer's name. For an external user, enter the name in the Signer field.
  3. Confirm with the Add Signature button in the dialog.
  4. Check that the correct person appears in the list and that the signature is awaiting signing.

Adding an individual request requires permission to edit the service request. The add button is not shown if signature requests are inherited from the category or the service request is On hold, Completed, Cancelled or Forwarded.

Shared signature requests for a service request category

Open Manage tasks → Service requests → Service request settings → Service request categories. Open a saved category by selecting its name or the pencil icon on its row, and go to the Signatures section of the form. Select Add Signature, specify the signer, and confirm both the addition and the warning about the change. The addition is saved separately; reopen the category to check the new requirement.

Changing a category requires permission to edit it. The change also affects the requirements for existing incomplete service requests. Read about the deletion effects of category changes below before adding the first shared requirements. Creating categories and configuring other settings are covered in service request categories and additional information fields.

Add an individual request on mobile

Open the Service requests view on Android or iOS and open the relevant request's details. When there are no requirements yet, Add new E-signatures for this item, shown after the expenses, opens the signature list. If requirements already exist, open the list using Sign or VIEW SIGNATURES alongside the completion actions at the bottom of the details page. On iOS, the signing action is SIGN.

Select ADD SIGNATURE at the bottom of the signature list on either Android or iOS. Select Spotilla user and a user account, or External signer and enter a name. Confirm with Save Signature on Android or SAVE SIGNATURE on iOS. This saves only the signature request, not a drawing. Check the new request in the list.

Adding a request requires permission to edit the service request, and individual requests cannot be added alongside requirements inherited from the category. The add action is hidden when the signature list is opened from the combined list of pending signatures; start from the service request's details to add a request.

Permissions for signing

Providing the signature assigned to your own user account requires permission to read the service request, but does not in itself require edit permission. You cannot provide another Spotilla user's signature using your own account.

Saving an external person's signature on mobile requires permission to edit the service request. In the browser, in addition to read permission, you need either edit permission or permission to manage external signatures for the item. Seeing the action does not guarantee that you have permission to save.

Both mobile apps may hide the signing and viewing action on the service request details page if you lack handling permission. In that case, you can open your own signature from the pending signatures view if the service request falls within its scope. Android also hides signature actions on the details page for completed and cancelled requests. Check their saved images in the browser.

The external signer's name and the Spotilla user used to save the signature are separate pieces of information. The browser's Signed by Device column shows the name of the logged-in user used to save it, not the identity of the external person.

Provide a signature in the browser

  1. Open the service request's Signatures tab and check the signer on the relevant row.
  2. Select Sign on the row. For an external person, let them draw their signature on the handler's device.
  3. Draw the signature in the drawing area of the dialog that opens. Clear removes the current drawing so you can draw it again.
  4. Confirm with the dialog's Sign button and wait for the Signature Successful notification.

Provide a signature on Android or iOS

At the bottom of the service request details page, open Sign, or SIGN on iOS. In the signature list, select the signing action for the correct person. Draw the signature and, if necessary, use Clear, or CLEAR on iOS, to correct it.

Confirm the drawing with Save on Android or SAVE on iOS. Wait for saving to finish. The iOS SAVE SIGNATURE button is used to add a new signature request, not to save the drawing.

The external person's name comes from the signature request. Although a name field is shown in the mobile drawing view, editing it does not change the name of the signature being saved. If the name is incorrect, correct the signature request before signing. In the browser, an incorrect individual request can be deleted and added again as described below; a request inherited from a category must be corrected in the category settings.

Clear applies only to the drawing in the currently open drawing view. A saved signature cannot be replaced by drawing over it.

Find pending signatures

On Android, open the Signature card in the Browse view. On iOS, open the SIGNATURES button in the browse view. On either platform, select the Service requests tab. The All tab also includes tasks, while Task on Android and Tasks on iOS show only tasks. Select Sign on an item row to open the signature list, or View Item to open the service request details; on iOS, these actions are SIGN and VIEW ITEM.

Open the filter icon at the top, on the right side of the top bar on iOS, and select a filter:

  • Only my signatures shows items with missing signatures assigned to you. This is the default filter; iOS remembers your previous selection.
  • All Signatures also includes items with missing signatures from external people. It does not mean signature requests for all other Spotilla users.

On Android, confirm the filter with the Apply button in the filter dialog. On iOS, use the confirmation button at the bottom of the filter dialog.

The service requests retrieved are those you have access to with an Open or In progress status; the latter is labelled In progress in the mobile status queue. Requests that are on hold, completed, cancelled or forwarded are not included in this list. The list is a current worklist, not a report for a particular period.

Pending counts represent distinct items, not missing signatures. For example, one service request missing two signatures covered by the filter counts as one service request. The count on the All tab also includes tasks. A request may remain on the list after you have signed if the selected filter still includes a missing external signature.

The browser's name search and signature columns are covered in finding and assigning service requests. If you cannot find a request in the pending list, open the service request itself and check its status, your permissions and its signature list.

Check that the signature was saved and resolve an interrupted attempt

Reopen the signature list after saving. Check the signer, the signed status or save date, and the image. In the browser, open the image using the eye icon in the Preview column. On Android, use View on the signed row; on iOS, use the eye icon on the row. Once all applicable signatures have been provided, the action on the mobile details page changes to VIEW SIGNATURES, provided the viewing action is otherwise available.

The drawing dialog closing or the name of the user who saved it is not enough: a signature is provided only when its image is saved. If saving is interrupted or appears to fail, check the network connection and any error message. Open the incomplete service request's signature list directly from its details, and check the status and image before trying again.

An interrupted image save for a signature request added individually to a service request can leave a record that causes the service request to disappear from the pending list. Absence from the list therefore does not prove that signing succeeded. If the image is missing and the signature is still awaiting signing, open Sign for the same person and draw it again. The new attempt replaces the incomplete save record. If the image is already visible, do not sign again. If the status and image conflict or the action is missing, ask an administrator to investigate.

Signatures and service request completion

Marking a request as completed in the usual way requires all applicable signatures. Signing does not itself mark the service request or its related tasks as completed. Other completion conditions must be checked separately; see completing a service request.

Immediate completion through the service request category's After transferring to tasks setting and automatic completion based on all related tasks being completed bypass the service request's signature check. The condition requiring all tasks to be completed is also affected by a shared setting that accepts tasks in the In Review status as completed. A completed service request therefore does not prove that all signatures were provided.

The signature list for a completed service request shows the signature records created for it and no longer lists missing requirements. A record from an interrupted image save may also appear in the list. Check the required signatures before automatic completion and verify the saved images afterwards. A completed, cancelled or forwarded request cannot be returned to an incomplete state by changing its status.

Deletion and the effects of category changes

In the browser, you can delete an individual signature request from a service request using the trash icon on its row in the Signatures tab and confirming deletion. This requires edit permission and is not available for inherited requests or service requests that are on hold, completed, cancelled or forwarded. Deletion removes the entire requirement and its associated signature and image. It does not clear the drawing or return the signature to a pending state.

To delete a request inherited from a category, use the trash icon on its row in the Signatures section of the category form and confirm the change. If the requirement has at least one associated signature record on a completed service request in that category, the requirement is made inactive and its associated signature records and images are retained. A record whose image failed to save is also sufficient to meet this retention condition. An inactive requirement no longer applies to incomplete requests, but making it inactive does not reset retained signatures. Otherwise, the requirement and its associated signatures and images are deleted.

When the first shared signature requests are added to a category with no active shared requirements, the system deletes, in the background, the individual requirements and their signatures and images from all service requests in that category except completed ones. This also applies to requests that are on hold, cancelled or forwarded. Before making the change, ensure that the data to be deleted contains nothing that needs to be retained. After background processing, reopen the category and some of its service requests and check the applicable requirements and retained signatures.

The dashboard's change history shows service request creation and status changes. It is not an archive of signature images and does not replace checking or retaining images before changes that delete data.

Service request and task signatures are separate

A service request signature does not replace the signature for a related task or automatically appear in the task's PDF report. The task PDF shows the task's own signatures when Include signatures is selected in the task form's PDF settings. See signing a task and task form PDF settings.