Skip to content

Template management

Overview

Templates are the master registers and documents that super admins keep for the whole platform. You deploy them to clients to give each one the same starting set of compliance records.

When you deploy a template, Fisher Portal makes a copy for the client. The client fills in its own copy. Changes to the copy do not affect the template or any other client.

How templates work

Template (belongs to no client)
|
+-- Copy deployed to Client A
+-- Copy deployed to Client B
+-- Copy deployed to Client C

There are two kinds of template.

Template registers

A register template sets the structure of a register: its fields, their types and their order. Each register template has:

  • a Code, such as HSF02, and a Name
  • a Category, such as Health & Safety
  • a Description of what the register records
  • fields that set what each entry records

When you deploy a register, Fisher Portal copies the register and all its fields to the client.

Template documents

Document templates are policies, procedures and forms, kept in folders. When you deploy documents, Fisher Portal keeps the folder structure. If you tick a file, its folders are deployed with it.

Word documents can be personalised. Fisher Portal fills in the client’s company details, such as the registered name and managing director, when it deploys them.

Open the template registers

  1. In the side nav, under Platform, select Template Registers.

The Registers page lists template registers and every client register. The Type column shows which is which. You can search, and filter by category.

The Registers page, with template registers and client registers

Open the template documents

  1. In the side nav, under Platform, select Template Documents.

The Template documents page shows the folders and files you can deploy. Changes here reach clients the next time you deploy templates.

The Template documents page

Create a register template

  1. On the Registers page, select New register.
  2. Complete the form:
FieldRequiredNotes
NameYesThe full name of the register.
CodeYesA short reference, such as HSF02. Each template code must be different. You cannot change the code once the register has entries.
DescriptionNoA sentence or two on what the register records.
OrganisationNoLeave it as Template register to make a template. Choose a client to make a register for that client only.
CategoryYes, for a templateFor example, Health & Safety, Incident & Security, Quality & Management or Business Continuity.
  1. Select Create register.
  2. On the register page, under Register structure, select Add Field.
  3. Complete the field form and select Add field.
  4. Repeat for each field.

To change the order of fields, use the Move up and Move down buttons in Register structure.

Field form

FieldRequiredNotes
Field labelYesThe label people see on the entry form.
Field nameNoUsed behind the scenes. Leave it blank to make one from the label.
Field typeYesThe kind of information the field holds. See the table below.
ChoicesFor choice fieldsPut each choice on its own line.
Currency symbol and Decimal placesNoShown for some number types.
Help textNoShown under the field on the entry form.
Required fieldNoTick it if every entry must fill in this field.
PositionNoLeave it as the next free position unless you need a set order.

Field types

Field typeUse it for
Text (single line)Short text, such as a name
Text (multi-line)Longer text, such as a description
Number (whole number)Counts
Number (decimal)Measurements
CurrencyAmounts of money
PercentageRates and scores
DateDates
Yes or noA single tick box
Choose one (dropdown)One choice from a list
Choose several (checkboxes)Several choices from a list
Email addressEmail addresses
Phone numberTelephone numbers
Web addressLinks
File uploadAttached files
PersonA user of the portal

The Add field form, with the field types

Deploy templates to a client

  1. In the side nav, under Platform, select Clients.
  2. Find the client, open More actions and select Deploy. You can also select Deploy Templates on the client profile.
  3. Read the message at the top of the page:
    • Personalisation details ready shows the registered name, phone number and managing director that Word templates will use.
    • Complete details before deploying Word templates lists the missing details. Select Complete client details to add them.
  4. Choose the templates:
    • Register templates lists each template with its code, name, description and number of fields.
    • Document templates lists the folders and files, with the number of each.
    • Templates the client already has show Already deployed and are not ticked.
    • Use Select all to tick every item in a list.
  5. Select Deploy selected templates.

To deploy the approved starting set of templates, select Deploy approved baseline instead.

When the deployment finishes, the client profile opens. A message shows how many registers and documents were created, and how many the client already had.

The Deploy templates page, with register and document templates to choose from

How deployment works

Registers:

  1. Fisher Portal checks whether the client already has a register with the same code.
  2. If it does, Fisher Portal keeps the client’s register and does not copy the template again.
  3. If it does not, Fisher Portal copies the register and all its fields, in the same order.

Documents:

  1. Fisher Portal adds the folders of each ticked file, so the folder structure stays complete.
  2. It copies each folder and file into the right place.
  3. It copies each attached file. Word templates are filled in with the client’s details.
  4. If a document belongs to a register, it is linked to the client’s register with the same code.

All or nothing: Fisher Portal checks every ticked template before it starts. If a file is missing, or the client details for Word templates are not complete, nothing is deployed. The message lists the problems.

You can deploy more than once. Templates the client already has are not copied again.

Check what you deployed

Deployed templates

  1. On the client profile, select Deployed templates.

The page shows the number of documents Deployed, Current and Stale. A document is stale when the client’s company details have changed since it was deployed.

The table shows each Document, the Method used, when it was Deployed and its Status.

  • To update one stale document, select Re-deploy in its row.
  • To update every stale document, select Re-deploy all stale. The button shows how many there are.
  • To deploy more templates, select Deploy more templates.

The Deployed templates page, with current and stale documents

Baseline status

  1. On the client profile, select Baseline status.

The page compares the client with the approved starting set of templates. It shows Matches when the client has every required folder, document and register. It shows Drift when something is different, and lists the differences.

The Deploy approved baseline button on this page opens the Deploy templates page.

Check as a user

After you deploy, you can impersonate a user from the client to check that the registers and documents appear for them.

Tips

  • Plan your template library before you deploy to clients. Clear register codes and folders make it easier to manage.
  • Use the same pattern for register codes, such as HSF for health and safety.
  • Complete the client’s company details and key personnel before you deploy Word templates.
  • Deploy templates soon after you add a client, so that they have a working set of records from the start.
  • Changes to a register template do not reach clients that already have it. Update each client’s register yourself.
  • After you change a client’s company details, use Re-deploy all stale to update their Word documents.

Troubleshooting

ProblemWhat to do
Every template shows Already deployedThe client already has every template. Deploy again only after you add new templates.
”Complete the client details required for personalised documents”Edit the client and add the missing details, then deploy again.
”Selected template content is unavailable”A ticked file has no attached file, or the file cannot be read. Fix the template document, then deploy again.
”Deployment failed and no changes were saved”Read the reason in the message, fix it, then deploy again.
A register template will not saveEnter a Category. Every register template needs one.
Template changes do not reach a clientClients keep their own copies. Update the client’s register, or re-deploy stale documents.