A task template brings together the shared information and settings for frequently repeated work. A task form defines the information to fill in during the work. You can attach a form to a task template. Saving a template alone does not create a task.
Before you start
Create and edit shared task templates in the browser. You need permission to create task templates to set up a new template, and edit permission to change an existing template. View permission alone is not enough.
If you use an existing task form, work order or category tags, they must be available for selection in the service. A form attached to tasks must be active. You can also create a template without these selections. Creating a form is covered in creating a task form.
Create a template and fill in the basic information
- Open Manage tasks → Tasks → Task templates.
- Select the Create new task template button on the page.
- Fill in Basic info in the form that opens, and open the settings sections you need by selecting their headings.
- Save using the Create new task template button at the bottom of the form. Resolve any errors and make sure the template appears in the list.
Task template name helps you select the right template. Task template description explains what kind of work it is used for. Task name and Task description are the information that will appear on tasks: use them to describe the work itself and the instructions for carrying it out.
Both names are required and can contain up to 512 characters each. Descriptions are optional and can contain up to 4096 characters each. Multiple templates can have the same name, so choose a distinctive name.
Task form adds the sections to fill in on the task. Work order links the task to the selected set of work. Category Tags classify tasks to help you find and filter them.
Enter Estimated working time in the Hours and Minutes fields. Use whole numbers, with minutes between 0 and 59. For example, 1 hour and 30 minutes are saved as a planned duration of 90 minutes. The initial value on the creation form is 00:00. Planned time does not replace the employee's actual logged work hours.
Estimated cost is an optional planning value that must be zero or positive. It is not the actual cost. Billable sets the task's billable flag; the cost estimate and billable status are separate pieces of information.
Select the work requirements
The requirements are in the Basic info section. Select only the requirements needed for the work, and make sure the people carrying it out know what they need to record.
- The task must be reviewed before completion: when the person carrying out the work marks it as done, it moves to review. The work is finally completed after the review. See reviewing a task.
- Enforce logging of work hours: completion requires work time logged on the task with a total greater than zero. Estimated working time does not meet this requirement.
- Require input of machine hours: marking the work as done requires the device's machine hour meter reading, which must not be negative. This is the device's accumulated machine hours, not the time the employee spent on this work.
Configure the other settings
Repetition and scheduling settings
Open Repetition and scheduling settings. Select the recurrence interval, time unit, recurrence method and allowed weekdays if the work needs to recur. By default, a new template does not recur, all weekdays are selected, and the recurrence method retains the original schedule.
A recurring template needs a positive interval and at least one allowed weekday. Recurrence that retains the original schedule calculates the next due date from the previous due date; recurrence that adjusts to completion uses the completion time. The next task is created when the previous task is completed, not simply when its due date is reached.
You can limit the total number of occurrences in the Recurrence ends after X tasks field. A count of 1–9999 includes the original task. Leaving the field empty sets no limit on the count. In the same section, Default resourcing defines the responsibilities and resourcing provided by the template; still check the responsibilities and schedule of the first task. Counting and ending recurrences are covered in setting up a recurring maintenance task.
Signatures
Open Signatures and select Add Signature. Select User Type: for a Spotilla user, select the person in the Spotilla User field; for an external user, enter a name in the Signer field. Confirm by selecting Add Signature. Repeat for other signers as needed.
Requests for a new template are saved when the template is created. When editing an existing template, adding a request saves that change separately and may display an update confirmation before you save the main form.
The template's active signature requests are applied to tasks that use it. Their signatures are checked when the task is marked as completed. A signature alone does not mark the task as completed. See signing a task.
Product Settings and Maintenance route
Open Product Settings and select Add new product under Products. Specify the product to add to the task, its quantity, and the required warehouse and warehouse location selections. These are the tasks' product rows. Also check the quantity used and warehouse selections on the task before completion. For detailed instructions, see using a spare part in a task.
In the Maintenance route section, you can define multiple inspection points and their checks within the same task. Maintenance route checks and task form sections are separate; if you use both, you must fill in the required information for both. See setting up maintenance route inspection points.
Mobile resourcing permissions
Open Mobile resourcing permissions. These options control editing your own resourcing, editing everyone's resourcing, changing the due date, adding new responsible parties and removing your own responsibility. A check mark on an option row allows the action, and a cross blocks it.
The form initially shows selections based on the service's general settings. If the entire group of options matches the general settings, the template inherits them. If you change the group so that it differs from the general settings, all visible options in the group are saved as the template's own settings. To restore inheritance, set the entire group to match the service's current general settings and save.
When determining a task's permission, the task's own setting is used first, then the template's setting, and finally the service's general setting. An explicit block does not inherit an allowing default. When a template has its own mobile permission settings, the task's own settings are cleared when the task is saved, so the template's settings take effect.
Allow editing of due date is not a general due date lock for all tasks: the service's check for this restriction applies to recurring tasks.
Use the template when creating a task
In the browser, open Manage tasks → Tasks → Tasks and select Create new task. Select a task template on the creation form. On Android and iOS, select the template under Task Template on the new task form. The selection fills in the task name, description, form and work order; on mobile, the task form selection is locked after you select a template.
Always check the Spot, responsible parties and due date. A regular task requires this information; a draft in planning can be saved without it. Saving a template and saving a task are separate actions. See creating a task and a draft.
Not all template information consists of defaults that can be freely overridden. The service takes the requirements, billable status and recurrence settings from the template even when the task is saved later. The template's work order overrides the task's own work order selection if a work order is defined on the template. The template's planned duration is applied if the template has a value for it. The name, description, form and cost estimate fill in missing information; a later template update may still replace them as described below.
Edit a template that is in use
In the Task templates list, open the template by selecting its name or the pencil icon on its row. Change the settings and select Save at the bottom of the form. If the service displays the confirmation Do you want to update the task template?, assess the effects before confirming.
Changing an editable table cell also saves a change to the shared template. Editing in the table does not use the same update confirmation. A template update does not affect only the task for which you opened the template.
Which information changes, and in which statuses?
The background update of basic information applies to the template's tasks with the statuses Open, Overdue and Planning. It replaces the task name, description, form, work order, planned duration, review and logging requirements, billable status, recurrence settings and allowed weekdays. This also replaces information manually changed on the task.
The cost estimate is an exception: it is updated only if the task's estimate is empty or matches the template's previous estimate. For example, when the template's estimate changes from €100 to €120, a task estimate of €100 changes to €120, but an estimate of €150 entered separately on the task is retained.
This background update does not apply to tasks that are in progress, in review, on hold or completed. However, it does not detach them from the template: for example, signature requests and mobile permissions read from the template, and settings applied when the task is next saved, may still affect them. The update confirmation's reference to all tasks does not accurately describe these differences between fields.
- Form: changing the form removes the previous sections from the tasks being updated, along with the information recorded in them and their section attachments. The new form does not transfer old answers into new fields. Removing the form entirely may be blocked if the task has a completed section.
- Products: changing the template's product rows replaces the old product rows on open, overdue and planning tasks with the template's rows. Rows added separately to the task may also be removed.
- Maintenance route: changing the route replaces the routes on tasks in the same set of statuses. Previous check values and additional information are not transferred to the new rows.
- Category Tags: changing the template's category tags replaces the category tags on all tasks using the template that are not completed. This also applies to tasks that are in progress, in review or on hold.
- Signatures: adding the first active signature requests to the template starts the background removal of the individual signature requests on tasks that are not completed. Signatures saved through those requests are removed at the same time. The template's requests replace the individual requests.
If you remove a template signature request that has signatures on completed tasks, the request is removed from active use, but its saved signatures are retained. Otherwise, removing the request also removes its associated signatures.
If the template is used in a maintenance rule based on machine hours, you cannot remove its machine hour logging requirement or enable calendar-based recurrence. Maintenance based on machine hours is configured separately using an hour-based maintenance template.
If the structure of the new work differs substantially from the previous work, create a separate template for it. This lets you select the new template for the intended work without accidentally changing the shared template.
Check the result
Reopen the saved template and check its information. If needed, create a test draft in planning and make sure the template provides the intended content. Also check the Spot, responsibilities and due date on a regular task before starting work.
After editing a template that is in use, wait for background processing and reopen tasks that use it. Pay particular attention to the form and its information, product rows, maintenance route, category tags, signature requests, work order and cost estimate. Successfully saving the template alone does not prove that all tasks have been updated: a task-specific check may prevent a change, such as removing the form.