Schedule staff against the workload you already have booked.
Garmenly builds rosters per site, records hours from the counter station staff already use, and reads labour cost back against revenue by site and by trade.
Why rostering sits inside the POS
A standalone scheduling tool asks you to maintain a second copy of information the POS already holds: who works at which site, which days are busy, and how much work next week has already promised. Keeping the roster next to the workload means you are scheduling against real committed jobs rather than last month’s pattern.
It also means one fewer subscription. For the multi-site operator Garmenly was built in, this module replaced a separate rostering and timesheet product that had been costing $300 a month.
Build a roster for a site
Rosters are built per site and per week. The booked workload for that week is visible alongside the roster, so you can see the days that are already committed before deciding who is on.
Choose the site and the week
Each location has its own roster. A store-and-factory setup rosters each separately, because the work arriving at each is different.
Check the committed workload first
Look at the due dates already promised and the alteration bench minutes those jobs carry before you decide the shape of the week.
Place shifts against that demand
Cover the counter for trading hours, and cover the bench for the minutes the week actually owes. These are not the same shape.
Publish the roster to staff
Once published, staff can see their shifts. Changes made after publishing are visible as changes rather than quietly overwriting the original.
Clock on and clock off
Staff clock on and off at the counter station they already use, so there is no second device and no separate app to maintain. Each entry is recorded against the site the station belongs to.
- Clock on and off at the store terminal, no extra hardware
- Entries recorded against the correct site automatically
- Breaks recorded so paid and unpaid time can be separated
- Missed clock-offs flagged rather than silently rounded
Review timesheets against the roster
Timesheets accrue as staff clock on and off, and are shown against the roster that was published. Where actual hours differ from rostered hours, the variance is flagged so you can look at it while somebody still remembers the day.
| What you see | What it usually means | What to do |
|---|---|---|
| Actual hours consistently above roster | The roster is under-scheduling the real demand at that site. | Compare against booked workload for those weeks and adjust the pattern. |
| A missing clock-off | Somebody left without clocking off, or the station was closed first. | Correct the entry with a note before the pay period is exported. |
| Hours at an unexpected site | Staff covered another location, which is normal in a multi-site group. | Confirm it is genuine so the labour cost lands against the right site. |
Corrections are recorded as corrections. An edited timesheet keeps its history so a later payroll question can be answered rather than argued.
Export hours for payroll
Approved hours go straight through to Xero or MYOB, so the tedious part — re-keying a timesheet into your accounting package at the end of every pay run — disappears. Garmenly records, approves and hands over hours; it does not calculate pay, award interpretation or entitlements.
Close the pay period
Resolve flagged variances and missing clock-offs first. Exporting an unresolved period only moves the problem downstream.
Approve the timesheets
Approval is the point at which hours are treated as final for that period.
Send to Xero or MYOB
Connect the accounting package once and approved hours push across for the pay period and site range you choose. A CSV export is available as well if you would rather handle it manually.
Measure productivity, then roster to it
The roster is only as good as your understanding of how much work actually gets done per hour. Because every garment scans and every operation carries an estimated bench time, Garmenly can report throughput per person and per site against the hours that were worked — not as a performance-management exercise, but so the roster is built on a real number.
- Garments and priced operations completed, per person and per site
- Bench minutes produced against hours clocked
- Read against the workload already committed for the week ahead
- Spot the shift that is consistently overstaffed and the one that is consistently short
Read labour against revenue
Because hours are recorded per site and revenue is already reported by site and by trade, the two can be read together. That is the number most garment-care operators never get to see: what the alterations bench costs to staff against what it actually brings in.
- Labour hours by site for a chosen period
- Read alongside revenue by site and by trade
- Compare rostered against actual to find where the estimate is wrong
- Use it before adding a shift, not after the quarter closes
Common questions
Does this replace my payroll software?
No. It replaces the scheduling and timesheet layer — the part that tells you who is on and how many hours they worked. Those hours are then exported to whatever you use to actually pay people.
Can staff see their own roster?
Yes. Once a roster is published, staff can see their shifts. What they can see beyond their own shifts is controlled by their role.
What happens if somebody forgets to clock off?
The entry is flagged as incomplete rather than rounded or guessed. Somebody with the right permission corrects it, and the correction is recorded with its history.
Can I roster somebody across two sites in a week?
Yes. Multi-site cover is normal, and the hours land against the site actually worked so labour cost stays accurate per location.
Is this an extra charge?
It is included in your Garmenly quote rather than sold as a separate product. Talk to us about your specific setup on a walkthrough.
Related articles
Still need a hand?
Email support with the site and pay period you are looking at and we can help you work through it.