Lanyard

What it does

• Add staff and invite them to sign in, or import a staff list from a CSV
• Collect staff availability and leave requests, and let managers decide leave
• Publish a conflict-free weekly roster that staff see and confirm
• Let staff clock in and out on a phone, with a retry if the connection drops
• Let managers prepare missed time, approve hours and correct approved records with history kept
• Export approved hours as a payroll CSV once per revision, and record your provider's acknowledgement
• Let an assistant prepare rosters, timesheets and payroll drafts for people to approve
• Back up and restore, and remove staff or assistant access

What it promises

• Lanyard never calculates award pay or pays wages; it exports hours only, and there is no automatic submission to a payroll provider.
• Publishing a roster is refused if a shift falls outside availability, approved leave or overlaps another shift.
• A retried clock-in or clock-out never duplicates time.
• A correction keeps the earlier record and needs a fresh approval, and a manager's own hours need another manager or the owner to approve.
• Each payroll revision is exported once, re-downloads return identical bytes, and later corrections export only the difference in hours.
• An assistant can only prepare work; a person alone publishes, approves and exports, and decisions are recorded.
• Deactivating staff cuts off their access at once, and only staff who were never invited, imported or used in work can be erased.

Move in from

• Staff list (Staff CSV v1, Lanyard's documented format)

Run it yourself

Install the command once, then clone a product and start it.

$ npx -y @runeditrun/rer cli install
$ git clone https://github.com/just-every/run-lanyard
$ cd run-lanyard && rer dev

No npm? curl -fsSL https://runeditrun.com/install.sh | sh installs the same command.