LoggerIQ
Sign inStart free trial

How it works

One week, from the roster to the payroll file

Six steps across one real week in July: who does what, on which day and what LoggerIQ does for them. Every screen below is drawn from the product, with the rules it actually runs.

Start free trial See pricing

US$5 per user per month, tax included. 30-day free trial.

  1. Build the roster against the budget

    Thursday 2 July · Manager

  2. Publish and everyone knows

    Friday 3 July · Manager

  1. 01Thursday 2 JulyManager

    Build the roster against the budget

    Drag shifts onto the week. The labour cost updates as you go, priced at award rates with Sunday, night and public holiday penalties where the award sets them, against the budget you set for the week.

    • Fatigue flags as you build: under 10 hours rest between shifts, a day over 12 hours, a week over 50 hours or more than 6 days in a row
    • A flag when someone is rostered without a qualification the shift needs
    • Managers see the total. Per-person cost stays with admins.
    Rostering
    The roster for the week of 6 July: labour cost fills to 95% of the week's budget, then a fatigue flag appears on Mia R.'s Saturday open after a Friday close.
  2. 02Friday 3 JulyManager

    Publish and everyone knows

    Until you publish, the week is a draft only you can see. Publishing sends each person their shifts by push notification, by push and email or quietly, as you choose.

    • People only ever see published shifts
    • Swaps and open shifts come back to you to approve
    app.loggeriq.io/roster

    Friday 3 July

    Publish the week of 6 July

    46 people · 168 shifts
    • Notify by pushEach person gets a notification. Their own settings still apply. Chosen
    • Push and emailFor a week with big changes. Reaches people who rarely open the app.
    • Publish quietlyShifts appear, nobody is pinged.
    Fatigue flags cleared. Mia R. now opens on Sunday instead of Saturday.
    Publish week
  3. 03Monday 6 JulyTeam

    Clock in at the site, a kiosk or the door

    On a phone, a clock entry is checked against the site boundary as it is made and kept with its distance from the centre. Outside the boundary it waits for an approved off-site request, so the hour on the timesheet is an hour on site.

    • A shared kiosk tablet with a code and PIN for each person. An optional face check too.
    • Card readers at a fixed door, through your access-control system
    • No signal? The entry is kept on the phone and sent when it reconnects
    Verified clock in
    6:525G

    Today, Monday 6 July

    7:00 to 15:30

    Parramatta, front of house

    Inside the site boundary. 38 m from the centre.
    Clock in

    This week

    Rostered30h 30m
    Last week Approved
    Annual leave left9.4 days
  4. 04Monday 13 JulyManager

    Clean weeks approve themselves. The rest wait in Needs you.

    Switch on auto-approval and set a tolerance, 10 minutes to start. Once a day, every week inside it with nothing flagged and nothing edited is approved and marked as approved automatically. What is left lands in Needs you, each with the reason it was held.

    • Held back for overtime not yet approved, an entry outside your tolerance, a flagged or disputed clock entry or a clock-out answer that asks for you
    • Leave, expenses, swaps and trip flags in the same inbox
    • Leave, expenses and overtime can be decided from the email, without signing in
    Needs you
    app.loggeriq.io/needs-you

    Monday 13 July

    Needs you

    4 to decide
    42 of 46 timesheets approved themselves. Inside your 10 minute tolerance, nothing flagged and nothing edited.
    • Sam L.: Overtime not approved yet1h 15m past the rostered finish on SundayReview
    • Ana P.: Off scheduleClocked in 24 min before the roster on Thursday. Your tolerance is 10 min.Review
    • Mia R.: Disputes a clock out“Stayed to count the till on Friday and forgot to clock out.”Review
    • Lee T.: Clock-out answer asks for youSaid they did not get a meal break on Wednesday.Review
  5. 05Monday 13 JulyPayroll

    Award pay, line by line, with the clause

    Each approved shift is priced by the award engine. Every line names the band, the hours, the percentage, the hourly rate and the clause it came from. The engine refuses to price a figure it cannot trace to a clause.

    • 11 modern awards today: Hospitality, Retail, Fast Food, Cleaning, Security, Restaurant, Clubs, SCHADS, Hair and Beauty, Aged Care and Nurses
    • Bangladesh: overtime on the statutory base, holiday and compensatory leave, wage register and wage slip
    Try an award calculator
    app.loggeriq.io/timesheets/josh-k

    Josh K. · Retail employee level 2 · Casual

    Saturday 11 July 2026, 17:00 to 02:00

    MA000004 General Retail Industry Award 2020 · base $28.45/h, clause 17.1, Table 4

    BandHoursRatePay
    Saturdayclause 22.1, Table 123h 00mSat 17:00 to 20:00150%$42.68/h$128.04
    Saturdayclause 22.1, Table 123h 30mSat 20:30 to 24:00150%$42.68/h$149.38
    Sundayclause 22.1, Table 122h 00mSun 00:00 to 02:00175%$49.79/h$99.58
    Total for the shift9h 00m attended, 8h 30m paid$377.00
  6. 06Tuesday 21 JulyPayroll

    Approved hours out to payroll, typed once

    Send the period to Xero as draft timesheets or to QuickBooks Online as time activities. Or download a payroll file. Only approved weeks go. Nothing is approved on the other side for you.

    • Each person is matched to an employee you confirm, once
    • Someone not matched yet holds only their own rows
    • Payroll files for MYOB and Employment Hero Payroll. A plain CSV for anything else.
    Integrations
    app.loggeriq.io/settings/accounting

    Tuesday 21 July · approved weeks only

    Send hours for 6 to 19 July

    Xero connected
    People
    46
    Approved hours
    2,914.5 h
    Goes to Xero as
    Draft timesheets, one per person
    2 people not matched to a Xero employee yet. Their rows wait until you confirm a match. Everyone else’s go now.
    Payroll file insteadSend 44 as drafts

Under every step

Four rules the week runs on

They are how the product is built, not settings someone can forget, so they hold on a busy week too.

What the employee sees
  • A clock entry counts at the siteInside the boundary or with an approved off-site request. Nowhere else.
  • Nothing is approved past your toleranceAuto-approval is off until you switch it on. It never overrides a decision you made.
  • No pay figure without a clauseIf the engine cannot trace a rate to the award, it says so instead of guessing.
  • Both sides see the same recordThe employee sees the week, its status and every change the manager sees.

Questions

Questions this week raises

Is payroll included?

Not yet. Bangladesh payroll is priced separately once its running costs are known, and Australian payroll is not available yet. Until then, approved hours go to Xero, QuickBooks or your payroll provider as a file.

Can we move from Deputy or a spreadsheet?

Yes. Import sites, people, pay rates, leave balances and shifts from a spreadsheet or from Deputy's own export files. A dry run names every problem row by row before anything is saved, and an import can be undone.

Is my team tracked all day?

No. Location is read at clock in and clock out. During a shift, presence checks confirm someone is still on site, and a precise position is kept only for people who agree to share it. Nothing is collected off the clock, and coordinates are encrypted and cleared after 90 days.

Do we need to install an app?

No. LoggerIQ runs in the browser and installs to a phone home screen, and it keeps clock entries safe offline until the phone reconnects. A native iOS and Android app is built and in testing.

Put your next roster on LoggerIQ

Free for up to 5 people and 1 site. Pro is US$5 per user per month, tax included, with every feature except payroll and a 30-day free trial.

  • 30 days with every feature
  • Import your people, rates and rosters
  • Cancel any month
Start free trial See pricing