Your wholeteam’s week,in one app.
Squady is the staff app for teams that work in shifts across many locations. The recurring schedule, clocking in, time off, swaps and approvals — for the people on the floor and the people who plan it.
- On every phone
- In the browser
- At the counter
How Squady works
1The network
Every location, one team.
Six shops on one map. The thin lines are the people who work at two of them: one account, one app, both recurring schedules.
2One shop
Each shop runs its own recurring schedule.
Northgate’s Monday: who is on and when, and who leads the shift. Planned for this location, in the same app as every other.
3One phone
…and every person clocks in from their pocket.
At 05:59 Ines slides up on her own phone, and Northgate has her on the clock.
Built for teams spread across many locations.
One recurring schedule for the whole business, and every shop still running by its own rules — its own pins, hours, staff requirements and holidays.
One sign-in, every location
Somebody who works at two shops has one account and one app. Their shifts, hours and requests from both arrive in one place.
Approvals that follow your org chart
Each role decides for its own locations, and only for the people it outranks. Nobody approves their own request.
Phone, browser or counter tablet
Staff clock in from their own phone, or at a shared tablet by face or a six-digit code — whichever each location runs.
A record you can stand behind
Every punch, approval and change is kept with who made it and when. A closed pay period is locked, and re-opening one goes on the record too.
For employees
A shift, start to finish, on the phone in their pocket.
No app-store account to create, no photo of the recurring schedule in the group chat. Squady runs in the phone’s browser and installs to the home screen.
The week is already in her pocket.
Before she leaves home, Ines checks her shifts. What she sees is the recurring schedule as it will actually run — this week’s swaps, cover and time off already folded in.
Slide up to clock in.
One deliberate gesture and one confirm, so nobody clocks in by accident. Her company’s name sits above the slider, the line under it says she is clocked in, and the day’s hours start counting.
Open the forecourt, tick by tick.
The opening checklist arrives on her phone because her role is on it. The lead can see it done without walking the shop.
Breaks count themselves.
On a break, the break timer runs in plain sight and her worked hours stop counting. Sliding back ends it.
“Staying late?”
Just before the end of her shift Squady asks, instead of guessing. She stays; the extra time goes to her manager for approval and she keeps working.
Time off, from the bus stop.
She asks for three days in October and offers Friday’s early to Tomas. Every request shows where it stands — and her overtime is already approved.
For managers
The week, planned, approved and closed.
The administrator panel runs on the web, on a proper screen. Every location, every person, one week at a time.
Mon 07:00
Who is on, and what needs you.
One screen across every location: the requests waiting on a decision, kind by kind — shifts, time off, clock corrections — the checklists still open, and who is on the clock right now.
Tue 10:00
Let Squady propose the people.
Set the minimum staff each location needs, then press Propose people. It fills the gaps by score, keeps people inside their hours, shows the overtime it would create — and tells you when you need one more barista.
Wed 14:00
An approval writes the recurring schedule.
Approving time off is not a note in a list. The leave is charged from the schedule and the recurring schedule changes in the same step, so the week never disagrees with itself.
Fri 18:00
Close the week. It stays closed.
Check the punches, then close the pay period through the last day you want. Every punch in it is locked, and the period goes out to payroll as a CSV or Excel file.
Any day
Decide who can decide.
Roles carry their own permissions, rank and reach — one location, a list, or all of them. A supervisor approves for their own shop, for the people they outrank.
Everything in one app
The whole shift floor, not just the recurring schedule.
The week, as it will run
Everyone sees their own schedule — the recurring schedule with this week’s changes already folded in.
Clock in and out
A slide on the phone or a face at the counter. Locations can require a GPS fix inside their radius.
Timesheets that explain themselves
Worked against scheduled, day by day. A wrong punch is fixed by a clock correction request, not a spreadsheet.
Time off and sick days
Leave is charged from the schedule the moment it is approved. Calling in sick records the absence.
Swaps and shift changes
Ask to change or drop a shift, or offer it to a colleague — they accept, then a supervisor approves.
Checklists
Opening and closing routines assigned to people or roles, ticked on the clock and tracked by the lead.
Equipment and uniforms
Lend kit to people and see who has what. Staff report a missing item from their phone.
Notices and documents
Post a notice to a location. Share a policy or a handbook and see exactly who has acknowledged it.
Certificates
Record what each person is qualified to do, with a reminder before a certificate lapses.
Shift reports
Staff write up their shift in the app. A report is locked the moment it is filed.
Scoring
A score built from what actually happened on each shift — and the planner can use it to pick people.
Payroll close and export
Close the pay period through any day, locking every punch in it, and take it out as a file.
Also in the box: Push notificationsPublic holidaysStaff requirements per locationA Bin that restores anything deletedYour own colours and logoA help center behind the ? in the header, in your own words
Security and trust
The payroll record, treated like one.
Hours become pay. Squady is built on the assumption that every punch will one day be questioned — so it keeps the answer.
Two-factor for every administrator
An authenticator code is required at every administrator sign-in — it cannot be skipped or switched off. Recovery codes are issued once, and the most sensitive actions ask for a fresh code again.
Scoped by location and by rank
Roles carry their own permissions and a reach: themselves, their own location, a list of locations, or all of them. A decision is only ever made about somebody the role outranks.
Closed periods stay closed
Closing a pay period locks every punch inside it. Re-opening one is possible, and it is recorded.
An audit trail, and a Bin
Changes are logged with who made them. Anything an administrator deletes goes to the Bin, where it can be restored.
Faces handled with care
Face clock-in is switched on per location. It stores an encrypted template, not a photo library, and records the consent each person gave.
People can take their records
Staff sign in with a code sent by text or email and can lock the app with a PIN. Anyone can download a copy of their own data from the app, whenever they like.
At the counter
A tablet by the till becomes the time clock.
For locations where phones stay in lockers: staff clock in at a shared tablet with their face, or with a code from their own phone. Each tablet is its own special account, tied to its location.
Slide up
The tablet waits at the counter.
One slide up starts a clock-in: the same deliberate gesture as the clock on the phone.
Look
A second at the camera.
Hold still while it looks. Nothing is recorded until the person confirms.
Confirm
“Hi Ines.”
Squady says who it thinks it is, and which shift they are here for. Not them? Start again.
Recorded
Clocked in, then cleared.
The punch is kept with its location and a photo, and the tablet clears itself for the next person.
Type a code
No face clock? Six digits.
Where a location does not use the face clock, the person types the six digits shown on their own phone.
Works with AiSolver HR Module
Your HR module feeds Squady.
Link Squady to AiSolver HR Module and the employee record lives in one place. Squady keeps its people, locations, departments, job titles and holidays in step with it on its own, and those screens become read-only here. The HR module holds each person’s leave balance; Squady tells it what every absence costs.
No HR module? Squady keeps every record itself — the link is optional, company by company.