Shifts round the clock, and a clock-in that shows where the shift began and ended
Nights, weekends and public holidays. The shifts must be staffed, the staff must be approved, and the client wants to know somebody was actually there.
A week in a security company
Security is staffing with stricter conditions. Sites must be staffed round the clock, every guard must be approved by the county administrative board, and the collective agreement governs how nights and weekends are paid.
- 01
The assignments
Static guarding, patrols and alarm response, often on contracts that run year to year. The price is per hour or per month and site.
Where it breaksThe site instructions are in binders on the sites and in emails nobody can find.
- 02
The schedule
Shifts must cover the clock, cross midnight and be shared fairly over weekends. Whoever is on leave or lacks the right training cannot be put in.
Where it breaksThe schedule lives in a spreadsheet with a tab per week, and swaps are made by text.
- 03
The shift
The guard clocks in at the site, walks rounds and writes a report. Some sites have no signal, in basements and car parks.
Where it breaksWithout a clock-in on site there is no way to show the client when the shift began.
- 04
Approval
The hours are gone through weekly: late swaps, overtime, shifts that ran long.
Where it breaksChanges are made afterwards with no way of seeing who changed what.
- 05
Invoice and payroll
The client is invoiced monthly. Pay is computed with supplements for nights and weekends under the agreement.
Where it breaksThe hours are typed in twice, and the gaps between invoice and payroll are found at the turn of the year.
Built for Swedish rules
The rules behind a security schedule
Security has licensing requirements few other trades have, and the working-time rules bite harder when the operation runs round the clock.
- Authorisation and approved staff
- A security company must be authorised by the county administrative board before the business starts, and all staff must be approved by the board before they may work — including staff who are not guards.
- Daily and weekly rest
- The Working Hours Act gives at least 11 hours off in every 24 (section 13) and 36 hours in every seven-day period (section 14). Night shifts followed by day shifts are where it breaks.
- The collective agreement
- The Working Hours Act can be replaced by a collective agreement (section 3). Pay for nights, weekends and public holidays is a matter for the agreement, computed in payroll.
- Overtime
- Overtime may, under section 7, be at most 200 hours per calendar year, unless a collective agreement says otherwise.
- Guarding carries no RUT
- Skatteverket explicitly excludes guarding and security services and alarm installation from the RUT deduction. Guarding is invoiced at 25 per cent VAT.
Checked against the authorities’ own pages — Skatteverket, Arbetsmiljöverket and the county administrative boards — in October 2026. This is a summary, not tax advice: in a single case the authority’s text decides, and amounts and rates change.
The same week in Closepact
Every row below is built, and carries the module and tier it needs. What is not built is in the next section.
- Approval as a competenceScheduling & work orders · Start
- The county board’s approval, guard training or a security officer appointment can be recorded as competences on staff and used as a filter while you plan.
- Shifts across midnightScheduling & work orders · Start
- A shift is a start and an end, so a 22.00–06.00 night is one shift and shows on both days on the board. Double booking and employment dates give errors, absence and working hours give warnings.
- Standing guardingScheduling & work orders · Väx
- A site that has to be staffed every night sits as a recurring job, and the jobs are written out ahead to be staffed.
- Clock-in with a positionScheduling & work orders · Väx
- The guard clocks in and out in the field app. The position is taken at the tap and compared on the server with the site’s coordinates. In a car park with no signal the clock-in queues with the phone’s time and is sent when the signal returns; a missing position is stored as unknown.
- Approval and traceabilityScheduling & work orders · Start
- Approval is its own permission. Approved rows cannot be changed without first being rejected with a written reason, and who did what is in the audit log.
- The client invoiceInvoicing & receivables · Väx
- The month’s approved hours per site become invoice lines per person and hourly rate, or a fixed monthly price per job. The client’s reference sits in a field of its own.
Honest about the edges
What Closepact does not do for security companies
This is here because it is cheaper to read now than to discover after the contract is signed.
No checkpoints: no NFC, no QR codes and no trace of the round between clock-in and clock-out. The position is taken at clock-in and clock-out, not during the shift.
No check of daily or weekly rest, and no calculation of supplements, overtime, on-call or standby. Pay is computed in the payroll system, and there is no payroll export today — a payroll file is planned.
The county board’s approval is not checked. A competence is a filter without an expiry date, and the schedule does not warn when somebody without it is put on a shift.
Working-hours rules cannot cross midnight. If a guard has recorded working hours, a night shift therefore always gets a working-hours warning; with no working-hours rules there is no warning at all.
No incident or deviation reporting beyond the checklist, photos and materials on the job, and no alarm-receiving centre.
The field app is a web app without background location, so there is no automatic clock-in when the guard arrives.
What it costs a security company of 31
Twenty-eight guards and three who plan and run the operation. All 31 log in to the schedule; two of the three invoice.
Väx in both: standing guarding and GPS-verified clock-in in the schedule, recurring invoices and reminders in invoicing. Two modules take 15 per cent off the whole amount.
Prices in SEK per month excluding VAT, on an annual agreement. Each module has a 14-day trial, no card. Seats are counted per module, the way the calculator on the pricing page counts them.
Per month, priced the way the pricing page prices it
| Scheduling & work orders · Väx | 2 153 kr |
|---|---|
| 31 users · base fee 619 kr, 5 users included · 26 more at 59 kr | |
| Invoicing & receivables · Väx | 279 kr |
| 2 users · base fee 279 kr, 5 users included | |
| Modules | 2 432 kr |
| Bundle discount 15 % | −365 kr |
| Per month, excl. VAT | 2 067 kr |
Buy one. Buy two. Buy all three.
Each module is whole on its own. Together they stop being three systems exporting files to one another.
Common questions
Questions security companies ask
Can we show the client the guard was on site?
You can show when the shift was clocked in and out and where the phone was at that moment, judged on the server against the site’s coordinates and radius. A missing position is stored as unknown, not as outside. What you cannot show is the round in between: the position is taken only at the clock-ins, and there are no checkpoints with NFC or QR codes. The site’s coordinates and radius are set on the address in the panel, or fetched from the street address through OpenStreetMap.
Does Closepact warn when daily rest is broken?
No. The schedule makes four checks: double booking, employment dates, absence and shifts outside recorded working hours. A night shift followed by a day shift with too little rest in between is not caught by a rest-period check, because there is none. Rest periods, supplements and overtime are computed in your payroll system. We would rather write that here than have it come up after you have signed.
How are shifts across midnight handled?
A shift is a start time and an end time, so 22.00–06.00 is one shift and one time row — not two. The board shows it on both days. One thing to know: working-hours rules cannot cross midnight, so a guard with recorded working hours gets a warning for working outside them on a night shift. With no working-hours rules, no such warning is given.
Can we see that a guard is approved by the county board before we book them?
You can record the approval as a competence and filter on it while you plan, so only those who hold it are shown. But it is a filter, not a check: the competence has no expiry date, and the schedule does not warn if you drag somebody without it onto a shift. The approval itself and its validity you track against the board’s decision, as today.
Does clock-in work in a car park with no signal?
Yes. The clock-in is written first to a queue on the phone, with the time and id set on the phone the moment the button is pressed, and sent when the signal returns — in the order it happened. The server keeps the tap’s time, within limits that catch a wrong clock, and flags a stretch that arrived more than 15 minutes late. If the phone gets no position within eight seconds, the shift starts anyway and the row is stored without one. A clock-out cannot arrive before its clock-in.
What would it cost us?
The worked example above — 28 guards and three in management, Väx in scheduling and invoicing — comes to 2 067 kr a month excluding VAT, after the 15 per cent bundle discount. It is the schedule that grows with every user who logs in. Somebody planned as a resource without an account costs nothing, but a guard who clocks in in the field app needs one. Each module has a 14-day trial with no card.
Want to see it on your own numbers?
Twenty minutes, no slides. We set the module up with one of your own cases before the call.