Requirements and presets

Choose what each kind of provider must hold before they count as compliant at your school.

3 min readLast updated

Applies to: Core (every organisation) · School admin, School staff

On this page

Requirements are the documents each category of provider must hold: for example public liability insurance, a trade licence or a Working with Children Check. Each category starts with the iComply preset. Presets are a starting point, not legal advice: check them against your own policies, contracts and safety advice.

Everyone on your team can read the requirements. Only school admins can change them. Clubs, charities and peak bodies find Requirements in the menu next to their Provider register.

How to change a category

  1. Step 1: Open Requirements in the menu.
  2. Step 2: Find the category. Its tag says iComply preset or Customised for your school.
  3. Step 3: Change a requirement's name, tick or untick Has an expiry date, or remove it with the bin button.
  4. Step 4: Select Add a requirement to type in a new one, or a quick-add button for a requirement met inside iComply (for example Site induction, or a policy people must sign).
  5. Step 5: Select Save changes.

Every provider in that category is re-checked against the new list straight away, and their status on the register changes to match. The category is now tagged Customised for your school.

How to add your own category

  1. Step 1: At the bottom of Requirements, find Add a category.
  2. Step 2: Type a Category name.
  3. Step 3: Add each requirement, ticking Has an expiry date where the document runs out.
  4. Step 4: Select Create category.

The new category appears in the Category list when you invite a provider, and as a view on the register.

Go back to the preset

A customised category that has an iComply preset shows Reset to preset. Select it to replace your list with iComply's version. Your other categories don't change.

Requirements for one site

If your school uses Sites, each site can add its own requirements on top of these (for example a client's police check or a site induction). Set them on the site's page under Sites. A provider on that site needs both lists, and their status on the site is shown on the site's page and on their file.

Builders and other businesses: where requirements come from

Under each category you also see where a requirement usually comes from (for example a regulator or a national code), with the date iComply checked it. When you first set up, and once a year after that, someone signs off a review of your requirements: see Review and sign off your requirements.

Common questions

  • What does Has an expiry date do? The provider must enter an expiry date when they upload. A document without one stays Non-compliant, even after you approve it.
  • Can a requirement be a policy to sign? Yes. Add the policy as a requirement and the provider stays non-compliant until they sign it. See Policies and acknowledgements.
  • Does changing requirements email anyone? No. Status changes straight away, and the usual reminders and alerts follow.
  • Why can't I change anything? Only school admins can. Everyone else sees a read-only list.
Presets and the sources shown with them are starting points, not legal advice. iComply records and checks what people supply against the list you set; it doesn't certify anyone.
Was this helpful?

Related articles