Drag jobs onto people, see the clash before it is saved, and let the crew clock in with GPS — with or without coverage — and work through the checklist on site.
From 449 kr/month
Replaces Bokning och Schema
14 days free, per module. No card.
What that means in practice
Four checks across two severities. The system never refuses a booking — it says what is wrong and lets the planner decide, because the planner knows things the system does not.
A shift 08:00–12:00 and one 13:00–17:00 are merged before working hours are judged, so a job in the middle of the day is not flagged as out of hours just because there is a lunch break.
Clock-ins and clock-outs queue on the phone and send when coverage returns, in order, counted from the tap by the phone's clock. The checklist, photos and the customer's signature go when the job is reported done, and that needs a connection.
The week lives in a spreadsheet
Whoever has the file has the truth. The change made at seven in the morning sits in a version somebody else never opened, and two fitters drive to the same address.
The hours arrive as texts on Sunday night
Somebody types them up on Monday. Nobody remembers whether it was three hours or three and a half, and nobody can show where the person was when the shift began.
The basis is a photo of a note
The job is done, the materials are on a scrap of paper in the van, and the invoice waits for somebody to decipher the handwriting. What cannot be read is not billed at all.
Everything below is in the product today. Route optimisation and online booking are not — they are under the limits further down.
Day, week and month, one row per person, and drag in both directions: the job onto the person or the person onto the job. Filter by location, role, team or skill, and copy last week when the week looks the same.
Double booking and employment outside the dates are errors. Absence and working hours are warnings. A job ending at 12:00 does not clash with one starting at 12:00, and somebody with no working-hours rules is never warned for not having them.
Booked, scheduled, in progress, done, invoiced — a lifecycle that is enforced, not a status field. Checklist, materials, photos and the customer's signature on the tablet, and the ROT/RUT flag carries through to the invoice.
Before clocking in, the worker picks work or travel. The position is taken the instant the button is pressed, with accuracy rounded up, and the server compares it with the fence on the service address — coordinates and radius set in the panel, or fetched from the address through OpenStreetMap. A denied permission or a phone indoors never blocks the clock — the shift starts anyway.
It opens with no coverage and shows the coming seven days, a multi-day job on every day it spans, and the access notes for jobs the worker is booked on. Clock-ins and clock-outs queue on the phone and send in order when the signal returns, timed from the tap by the phone's clock — so an hour in a basement is not an hour that begins when the van reached the main road. A stretch that synced more than 15 minutes late is flagged on the timesheet.
Approved hours, materials, fixed prices, travel and ROT/RUT become a basis the moment the job closes. Only approved time is billable, hours are priced at each person's billing rate rather than at what they cost you, labour and materials always sit on separate lines, and nothing is rounded twice.
From an accepted quote or typed in: customer, address and service fill in from the register. The price follows the service.
Drag the job onto the right person. The clash shows before you save, not after.
The field app shows the week's jobs and clocks in with a position, with or without coverage. The checklist is worked through on site.
The manager signs off the week, deviations at the top. The basis is ready to invoice.
Built for Swedish rules
Most of this is detail you only notice when it is missing.
Tiers
The same tiers the billing code charges for. The price below is what the module costs alone; from the second module 15 per cent comes off, from the third 25.
449 kr/month
5 users included, then 45 kr/user
619 kr/month
5 users included, then 59 kr/user
799 kr/month
5 users included, then 79 kr/user
Being activated: built and part of the tier at the price shown, but not yet switched on. It waits on agreements and accounts on Closepact's side, not on more development, and until then the app shows it as unavailable.
Planned, not delivered. It is listed so the tier is honest about where it is going — but none of it is part of what you pay for today.
Together, and apart
With the proposals module on Väx or Pro an accepted quote becomes a job to be planned on its own, with the customer, the service address and the accepted lines on it. With the invoicing module the approved basis becomes an invoice line with no export and nobody retyping it.
On its own the module is the whole operation: schedule, jobs, time, field app and reports. The basis exports as CSV or SIE4 into the finance system you already use — a file, where Bokning och Schema syncs with Fortnox, Visma and Hogia; our own connections to those are planned.
Honest about the edges
This is here because it is cheaper to read now than to discover after the contract is signed.
The app does not clock people in automatically when they arrive. A web app on iOS gets no position in the background — it cannot be done, whatever is promised. We verify the position at the instant the button is pressed, which covers most of the value, and we would rather say so than promise something the phone cannot do.
The field app is a web app installed to the home screen, not an App Store or Google Play app. Clocking in and out works offline, but it is not native.
Route optimisation and online booking do not exist yet. Both are marked "planned" in the tier table and are not part of the price today.
Projects, quoting straight from a job, and finished connections to Fortnox, Visma and Hogia are planned, not built. The basis exports as CSV and SIE4 in the meantime.
Scheduled runs — the overnight generation of recurring jobs — need a scheduler process running in the deployment. That is part of a deployed installation, but it is worth knowing it is a process and not magic.
Only clock-ins and clock-outs queue without coverage. The checklist, photos and the customer's signature are sent when the job is reported done, which needs a connection.
Common questions
No, and we are not going to claim it does. A web app on iOS gets no background position, so automatic clock-in simply cannot be built there — that applies to everyone, not only to us. What we do instead is take the position the second the fitter presses the button and let the server compare it against the job's address. A missing reading is stored as unknown, never as "outside the fence", because "no position" and "probably somewhere else" are not the same thing.
Only the ones who log in. Staff and users are two different things here: a person can sit in the schedule as a resource, with skills and working hours, without having an account. Somebody using the field app has an account and counts as a seat; somebody who is only planned does not.
Partly — the part that matters most. It opens with no network, and clock-ins and clock-outs queue on the phone. The queue drains in the order things actually happened and stops at the first real failure rather than skipping past it — a clock-out depends on the clock-in before it. Each counts from the tap by the phone's clock, within limits that catch a wrong clock (no more than five minutes ahead or a week back); the time it reached the server is kept beside it, and a stretch synced more than 15 minutes late is flagged. The checklist, photos and customer signature go when the job is reported done, and that needs a connection.
You are told before you save, and then you can save anyway. The system reports conflicts but never refuses a booking, because the planner regularly knows something the system does not — that the customer moved the time, that the shift is shorter in practice, that the two addresses are in the same stairwell.
Yes. Entities are built into the core: a company with three branches or three brands can keep staff, jobs and customers apart without three separate accounts. Included on Pro.
Then every completed job becomes an invoice basis that exports — CSV or SIE4 — into the finance system you already have. That is a step back from Bokning och Schema, which syncs invoice drafts with Fortnox, Visma and Hogia from its Standard tier; our connections to those are planned, not built. What you can do here instead is add the invoicing module later and drop the export entirely.
Customers, addresses, services and articles import from CSV, with semicolons or commas, and with quoted fields spanning several lines kept intact. We do not move the schedule history itself — whoever needs it usually needs it in the old system anyway.
Twenty minutes, no slides. We set the module up with one of your own cases before the call.