Create your first site
A site is the place work happens — shifts, patterns, check calls and client billing all hang off one. Creating a site is a wizard: only the details are required, and the client, contact, geofencing, coverage, check calls, staff, forms and client documents can all be set as you go or skipped. It needs a name, an address and a postcode. You then land on the site's own page, with five tabs — Overview, People, Documents, Settings and Performance — where the client, the check-call pattern and everything else are set.
Who can create a site?
An Admin, and in practice only an Admin.
Sites appears in the header under More, for Admin, Manager and Control. Only Admins create sites, so only they see Add Site.
The consequence is worth knowing before you delegate the job: a Manager who follows a link to the wizard is sent back to Sites. The wizard page itself is limited to Admins, and the request that saves a site also needs the sites.create.organization permission, which only Admins hold by default. Blocking it in Settings → Permissions stops an Admin creating sites too; allowing it for a Manager does not open the wizard.
What do you need first?
A name, an address and a UK postcode. Everything else on the wizard, including the contact and the coverage, can be added or changed later on the site's own page. The client is not on the wizard at all; it is set afterwards.
Two things are worth deciding up front because they are awkward to change.
The SIN, or Site Identification Number, is a 1-to-4 digit code unique within your organisation. Leave it blank and the next free number is allocated in sequence, zero-padded to four digits — 0001, 0002, and so on. Type one and it is padded the same way, so 7 is stored as 0007.
Geofencing is easier to set up here than to repair later. See If it goes wrong.
How do you create one?
- Go to More → Sites and press Add Site. On an organisation with no sites yet the empty state offers Create Your First Site instead; both lead to the same wizard, headed New Site.
- Site Details. Fill Site Name and Address. Type the Postcode and press Find: once the lookup recognises it, it shows ticked with its town and county, and its centre is kept for geofencing. Change clears it. If the lookup cannot help — Lookup failed — enter manually — the postcode you typed is used, as long as it is a valid UK postcode. Site Identification Number (SIN) and Site Instructions are optional. Press Continue.
- Client and contact. Choose the Client the site is billed to, if it has one, or leave it on No client. Then Contact Person, Phone Number and Email Address, all optional. The phone and the email are format-checked if you fill them and ignored if you do not. Press Continue.
- Geofencing. Off by default. If you want it, turn on Enable Geofencing. Latitude and Longitude start at the centre of the postcode found on Site Details; Auto-detect from address places them on the address instead. Set the Geofence Radius. Under Enforce Location For, choose which of Check Calls, Book On and Book Off it applies to, and pick the Violation Action — Warn, which logs the violation and allows the action, or Block, which prevents it. Press Continue.
- Coverage. Optionally pick a staffing tier — 84 hours/week, 108 hours/week or 168 hours/week — or take Skip — set up shift patterns later. Nothing is pre-selected, so leaving the step alone is the same as skipping it. Press Continue. After you pick a tier, Staff it now offers the rotations that tier can run: pick one and name the crews, and the shifts are added when the site is created. It is optional. See Rotations.
- Check calls. Leave the Organisation default, or pick another Check-call pattern. The step says what the schedule is. Press Continue. PIN, location and escalation are adjusted afterwards, on the site's Settings tab.
- Staff. Tick the employees based at this site. Anyone already based elsewhere moves here: the step shows their current site, and Review names each move. Press Continue.
- Forms and documents. Tick the published forms this site uses. A form on all sites is already included. A form that is paused gains this site, and stays paused. If you chose a client, and hold the Manage Client Reviews permission, add its assignment instructions or risk assessment here, as PDF, Word or an image up to 20 MB. These are held with the client's documents: the client sees them in their portal and can sign them, and guards do not see them. Press Continue.
- Review. Check the summary, which also lists anything still Not ready. Each part has an Edit link back to its step. Press Create Site.

The next screen lists what was saved. If a step failed, the site still exists: the line says what went wrong, and Fix takes you to the place to do it. Open site goes to the site's own page — see What is on the site's page?
What do the coverage tiers actually create?
Shift patterns, one row each, all with one person per block and the role Security Guard.
| Tier | Patterns created |
|---|---|
| 84 hours/week | Day 07:00–19:00, every day |
| 108 hours/week | Weekday Day 07:00–19:00 Mon–Fri, Weekend Day 07:00–19:00 Sat–Sun, Weekend Night 19:00–07:00 Sat–Sun |
| 168 hours/week | Day 07:00–19:00 and Night 19:00–07:00, both every day |
They are a starting point, not a commitment — every field is editable afterwards in the pattern builder, covered by Recurring shift patterns.
Creating the patterns is a second request, made after the site already exists. It needs the shifts.edit.pattern_days permission and an active subscription, neither of which site creation itself requires. If it fails, the site is still created and the result screen says so: Add coverage in the pattern builder.
What is on the site's page?
Open a site from More → Sites. A card on the left names the site with its postcode, whether it is Active, its coverage and how many patterns it has. While setup is incomplete it also shows one pill — Setup 1 of 3 · next: … — that goes to the next missing piece: a shift pattern, staff, or a site contact. Staff means an employee based at the site, or a shift assigned to someone. Once all three are done the pill disappears.
Below the card sit five tabs. Admins, Managers and Control can open the page (sites.view.details).
| Tab | What it holds |
|---|---|
| Overview | Four tiles — Coverage, Staffing, Patterns and Operating hours — a This week list, the site's Shift Patterns and its contact |
| People | The employees assigned to the site, and Coverage by pattern |
| Documents | The site's Assignment Instructions and Risk Assessments, with a Staff must sign switch on each. See Site documents your guards sign |
| Settings | Site details and client, check calls, special requirements, geofencing, and the Danger zone |
| Performance | A placeholder — Metrics · coming soon |
The header carries Roster, which opens the roster filtered to this site, and Shift Patterns, which opens the pattern builder.
Overview
Each tile is also a button: Coverage opens the roster, Staffing goes to People (Assign staff), and Patterns to the builder (Manage). This week lists the shifts in the next seven days, each linking to that week of the roster; with none it reads No shifts scheduled in the next 7 days.
Coverage and Staffing count the shifts scheduled at the site over the next four weeks, cancelled ones left out, and how many have someone on them. Operating hours runs from the earliest start to the latest end of the site's shift patterns — 24/7 when day and night patterns join up, (next day) when a night pattern ends the following morning.
The contact card lets you change the Site contact, Phone and Email in place: Saves when you leave a changed field. Control sees it read-only.
People
Assign opens Assign Employee. Search by name, ID or position, and choose from the Assign as picker beside an employee — Permanent, Temporary, Emergency or Cross Training. Choosing assigns them straight away. The settings button on an assigned employee's row opens Employee Settings — Assignment Type, Available for other sites and Notes; the remove button, then Remove, takes them off the site.
Coverage by pattern lists each pattern with the number of people it requires, against the number assigned to the site as a whole. Assignments are to the site, not to a pattern.
Settings
Settings is one long page, editable by Admins and Managers; Control sees it read-only — Only Admins and Managers can change a site's settings. The links across the top — Details, Geofencing, Profile, Instructions, Check-call, Documents, Hours, Managers and Danger zone — jump to each part. Change anything and a bar appears at the bottom: Unsaved changes, with Cancel and Save. One Save covers the whole tab, geofencing included.

| Part | What you set |
|---|---|
| Site details | Site Name, Address, Postcode, Contact Person and Contact Phone |
| Client | Which client the site belongs to — the default reads Unassigned. It saves as soon as you choose it, without the bar, and is what makes the site visible in the client portal. Admins and Managers only. |
| Check-call | The check-call pattern and any site adjustments, including Alarm if not booked on after (0 to 240 minutes, inherited from the organisation unless set here) — see Configure check-call patterns |
| Operating hours | Nothing — it is shown, not set. Manage patterns → opens the builder. |
| Site profile | Site type, Risk level, Access instructions, Key-holding & alarm notes, Site emergency number, Nearest A&E and Nearest police station |
| Site instructions | Duties, patrol routes and anything a guard must know on arrival, kept exactly as typed |
| Geofencing | Enable Geofencing, Site Location (pick it on the map, or Set from Address), Geofence Radius, Enforce On and On Violation |
| Documents | One switch, Guards must sign site documents before booking on. It can only be switched on once a current document is marked Staff must sign on the Documents tab. A guard with an unsigned document cannot book on in the app and is taken to it; a manager booking a guard on is never blocked |
| Site managers | Which Manager and Control users manage the site, ticked from the organisation's list and saved with Save managers (Admins only; everyone else sees the list). They see the site's form submissions, reports and files; an Admin always sees everything. A site with none ticked is seen by Admins only. Adding a manager needs the Professional plan; taking one off works on any plan. |
| Danger zone | Deactivate and Delete |
Saving needs sites.edit — Admins and Managers. Control can open the tab, but a save is refused.
Performance
Not built yet: Live performance metrics are not yet available. It shows the site's Required Staffing, with 7d, 30d and 90d range buttons that change nothing else.
How do you deactivate or delete a site?
On Settings → Danger zone:
- Deactivate hides the site from active lists and calendars, keeping all its data. Activate brings it back. Admins and Managers (
sites.edit). - Delete is for Admins (
sites.delete). The site disappears from your site lists and can no longer be used — Site deleted. Its shifts, requests and history are kept. It cannot be brought back from the screen; to stop using a site for a while, Deactivate it instead.
Both ask you to confirm first.
If it goes wrong
"SIN {n} is already in use". Another site in the organisation holds that number. Pick a different one, or clear the field and let it be allocated.
"Maximum site limit (9999) reached for this organisation". Every number in the SIN range is taken. This is the only hard ceiling on site count — your plan's site limit is displayed on Settings → General but is not enforced when a site is created.
A later save refuses with "Geofence coordinates are required when geofencing is enabled". The wizard lets you finish with geofencing switched on and no coordinates. Set a location on Settings → Geofencing, or switch geofencing off, then Save.
You cannot set a radius above 1 km. The wizard's slider stops at 1000 metres. The Settings tab goes to 30,000 metres, which is also the server's limit, so set a wider radius after creation.
Site Instructions ignores the character counter. The 0/500 characters line under the box is decoration — there is no limit on the field and none on the column behind it.
"Site ID" is not actually checked. The SIN is shown to workers as Site ID, and the check-call settings offer Require Site ID. Neither the web portal nor the mobile app sends the number a worker sees, and no route compares it against anything. Treat the SIN as a reference code, not as a credential — the PIN is the credential.
Related
Last updated 2026-11-17