Agentic AIForecastingSchedulingComplianceTimekeepingTime ClockReportingPeopleSettingsMobile
Health

A decision engine that runs your day before you need it to

This is the real Day Health screen — click a score to see what's behind it.

Inside the product

One score that tells you where to look first

The Agentic AI watches every store’s day as it trades — one Day Health score per store, the five pillars behind it, and priced recommendations staged before the problem reaches the floor.

One lens on every store you run

The Agentic AI opens on the whole district — every location, every day, scored. Flip between the grid and a dashboard, week and day, and switch the driver you score by.

  1. Jump to any location with the full store selector — no logging in and out of stores.
  2. Score by Overall Health or drill into a single pillar across the estate.
  3. The same view scales from one district to hundreds of stores.

The morning question stops being “what happened?” and becomes “where do I look first?”

The week as a heat map, not a spreadsheet

Every cell is one store’s day, scored 0–100 and colored by risk. Wheaton’s 63 jumps out of a wall of healthy 80s before anyone has opened a report.

  1. Today’s column runs live; future days are projected from forecast and schedule.
  2. Each score is built from sub-scores — profit, workforce, compliance, service, wellbeing.
  3. Click any cell to open that store’s day — the score is a door, not a verdict.

Five pillars behind every score

The district rolls up to one number — 84 today — but the gauges underneath tell you which discipline is dragging it.

  1. Profit & Throughput at 75 is the weakest tier — slightly below target and flagged amber.
  2. Workforce Reliability, Compliance, Service Delivery and Team Wellbeing each score independently.
  3. A “Next 8 hours” timeline flags the day parts where risk is building — before they arrive.

Cause attached to every score

Stores requiring attention come with the reason, not just the number — so the first phone call is already an informed one.

  1. Addison at 60: +3 crew, 33% labour — an overstaffing problem, named.
  2. Bolingbrook at 67: sales −8% with two extra crew — demand, not discipline.
  3. Insights call the most urgent store and the highest-leverage move today.

“Wheaton (63) is the most urgent. Site visit there is the highest-leverage move today.”

The live day, priced in dollars

Open a store and the day is running math, not vibes: sales-to-time against forecast, SPLH against target, labour % against plan — live to 2:45pm.

  1. Daily Pacing tracks same-day sales-to-time against forecast as the day trades.
  2. The narrative names the problem: “lunch came in 30% short — a demand problem, not a staffing one.”
  3. Day view drills to 1-hour or 15-minute intervals with color-coded role requirements.

Every fix arrives priced, staged and reversible

The Agentic AI doesn’t stop at telling you the storm is coming — it stages the response and prices it before you commit.

  1. Storm response reshuffles 4 crew across channels to protect ~$4,800 in throughput.
  2. Crew re-allocation finds the one cross-trained person and moves her at zero extra labour.
  3. A no-show is patched by pulling the next scheduled start 30 minutes forward — one tap.
  4. Every action is logged and attributed, like every forecast adjustment in History.

It doesn’t report your day. It runs alongside it.

Demand

Stop staffing on last week’s guess

This is the real forecasting screen — drag the labour target and watch the week reprice itself.

Inside the product

Stop staffing on last week’s guess

A forecast that lands three weeks out, sharpens daily, and turns straight into a labour target your managers can trust. Review it, add what only you know, approve it — and the roster builds itself against real demand.

Know the week before you staff it

Labour is your largest controllable cost, and every hour of it is a bet on demand. LIFELENZ takes the guesswork out three to four weeks ahead — and sharpens the number every single day until the doors open.

  1. Forecasts built from your own trading history, plus weather, local events and holidays.
  2. Regenerated daily — the closer the date, the tighter the number.
  3. 20–50% more accurate than the legacy forecasting it replaces.

Get this right and everything downstream — labour, coverage, service — falls into place.

One forecast, from the week to the quarter-hour

Operators think in weeks. Shifts happen in fifteen-minute blocks. The same forecast answers both without switching tools.

  1. W for the shape of the trading week at a glance.
  2. D to drill into a single day, hour by hour.
  3. Labour broken down by role, filtered however you need it.
  4. Compare against the same week one or two weeks back.

The number gets better while you sleep

Forecasts behave like weather forecasts — they sharpen as the date approaches. Every version is kept, so you always work from the best available read.

  1. Pick the latest so your judgement sits on the freshest data.
  2. Older versions stay available for comparison and audit.
  3. No usable history for a day? Replace Forecast borrows a comparable one.

“LIFELENZ forecasts become more accurate as the date approaches.”

See the peak inside the peak

An hourly view tells you lunch is busy. A fifteen-minute view tells you the twenty minutes that decide whether the queue holds.

  1. 1 hr for the shape of the day; 15 min for the pinch points.
  2. Express demand in whichever driver runs your business.
  3. Labour redistributes underneath whichever view you choose.

Every day part, priced in labour

Sales forecast and the labour hours it implies, side by side, before a single shift exists. This is where the cost of the week is decided.

  1. Forecast and labour hours for every day part.
  2. The afternoon trough is where labour percentage quietly leaks.
  3. Change a day part and the hours recalculate on the spot.

Demand and people on the same picture

The line is what your guests are about to do. The bars are the people it takes to serve them. When those two shapes disagree, you are either losing sales or paying for idle time.

  1. Roles colour-coded, with employee counts on every interval.
  2. Store hours along the bottom — coverage legible at a glance.
  3. Hide a role from the graph without touching the labour totals.

You still know things the model doesn't

Road works outside. A school playoff down the road. A competitor closed for refit. Type it straight onto the day part and the whole plan follows — logged, attributed and reversible.

  1. Adjust a day part or the whole day; it saves as you type.
  2. The note records why; the bin puts it back.
  3. Labour hours re-allocate automatically across roles.
  4. History shows who changed what, when, and by how much.

The discipline that makes it work: only adjust for something the model could not have known.

Approve once, and the roster builds itself

Approval locks the number and freezes the labour target — so scheduling starts from ground that will not shift underneath it.

  1. Submit for Approval with a comment; retract any time.
  2. Above-store approval, or clear a whole estate in one pass.
  3. AOS only runs on an approved forecast — the two are joined at the hip.
  4. Afterwards, accuracy is measured against actuals and flagged in red past your threshold.

This is the handshake between forecasting and scheduling — and the reason 91% of schedules ran automated at McDonald's UK&I.

The roster

Build the week in minutes, not evenings

Try the actual Auto Schedule flow — swap shifts, approve the week, and watch cost update live.

Scheduling

Build the week in minutes, not evenings

Auto-Optimised Scheduling turns your forecast into a costed, compliant roster for every location — so your managers stop rebuilding the same schedule and start running the shift. Explore the screen they work in.

One screen for every store you run

Schedules opens on the week your GM needs, for whichever location they're standing in. No spreadsheet, no version control, no Sunday night rebuild.

  1. Week view first — the view a trading week actually runs on.
  2. Every location a manager owns, from the same login.
  3. Above-store visibility without commissioning another report.

Plan a trading day or a trading quarter

Day parts, weeks, months — the same roster at whatever range the decision needs.

  1. Day view for a promo, a rush or a new store opening.
  2. Week view for the rota your crew plans their life around.
  3. Month view for holiday cover and seasonal peaks.
  4. Print for the crew room — paper still wins back of house.

Operators who build four weeks ahead give crew the notice that keeps them.

See the roster the way you think about labour

Group and colour the week by role, cost or approval state. Coverage gaps and cost creep show up on screen, not in next month's P&L.

  1. Group by role, job category, employee type or post status.
  2. Colour by shift status or by role.
  3. Sort by start or end time to see how the day actually stacks.
  4. Hide earnings detail when the screen sits somewhere public.

Time off, swaps and drops — handled between rushes

Requests arrive in one queue with the coverage impact already worked out, so a GM answers in seconds instead of after close.

  1. One queue for time off, swaps and shift drops.
  2. The impact on coverage shown before you decide.
  3. Potential replacements ranked with the cost of each.
  4. Every approval available in the Manager Mobile App.

Your best week, reusable forever

Turn the roster that actually works into a template. New managers and new stores inherit a proven pattern instead of guessing at one.

  1. Week and shift templates built from any week you've already run.
  2. The same operating pattern across every location in the group.
  3. A new GM onboards into a schedule that already works.
  4. Drag, copy and right-click to adjust in seconds.

Managers are scheduled four to five weeks ahead, so the leadership rota is never the bottleneck.

The roster writes itself

AOS builds a full, compliant week from your approved forecast, availability, contracts and skills — optimising cost, coverage and fairness at the same time.

  1. Built from the approved forecast, not last week's copy.
  2. Balances labour cost against coverage, day part by day part.
  3. Keeps the shifts your managers placed and fills the rest.
  4. Auto-publish releases each week at the legal notice period.

Assign LZ_AOS and the engine decides where that person is needed, using only roles they're cleared to work.

Know where the week stands in one look

Colour carries the state of every shift, so a manager scans the week and sees only what still needs them.

  1. Grey unposted, green accepted, yellow pending, red declined.
  2. Light blue where AOS still has a shift to place.
  3. Black where a shift falls outside someone's availability.
  4. Drag, copy or reassign without opening a single dialogue.

Compliance priced in before you post

The rules engine checks breaks, young-worker limits and skill levels while the shift is still a draft — the cheapest possible place to catch a breach.

  1. Break, minor and skill-level rules applied as you build.
  2. Auto-break spaces breaks away from your busiest trading.
  3. Every alert resolved before the schedule is allowed to post.
  4. Post once — everyone assigned is notified.
Exposure

Labour law, priced in dollars, before you publish

This is the real Compliance screen — see what a breach costs before you publish.

Inside the product

The law, running inside the schedule

Rulesets built from federal, state and local law — local inherits state, state inherits federal, and the most restrictive rule wins. Warnings are priced, pinned to the shift that caused them, and enforced all the way to the time clock.

Timekeeping: enforced at the clock — and self-paying

When a break is genuinely missed, LIFELENZ doesn’t just log it: the premium the law requires is calculated and applied to the punch automatically as Compliance Pay.

  1. At clock-out the Time Clock detects untaken breaks and prompts the employee to attest — offered-but-declined breaks generate no premium.
  2. Missed-break premiums are added as worked time and count toward weekly overtime.
  3. Dismissing a warning removes the premium — but requires a reason, a comment, and lands in History with the manager’s name.

The Break Audit report then proves every break was Clocked, Attested or Waived — 15 months back.

Timekeeping: consent, captured — not assumed

The second tab exists because compliance isn’t only about hours: when a manager edits a punch, the employee is asked to consent — and unanswered requests surface at payroll as unresolved.

  1. Punch edits trigger a Consent Request to the employee’s app, with before and after times.
  2. Meal-break waivers are captured electronically at the clock, date-stamped for 12 months, with renewal prompts at 11.
  3. Chicago Fair Workweek employees can Accept or Reject late-notice shifts from their phone.

Every consent, waiver and dismissal is a record — built for the day someone asks you to prove it.

Scheduling: exposure is priced before the week posts

Over on the Schedule screen, the same rules run against the draft. The red button carries a running count of warnings — and the estimated cost of every premium they would trigger.

  1. Rulesets stack federal → state → local; the most restrictive rule wins, per location.
  2. Click any warning to jump straight to the shift that caused it — each shift chip carries its own ⚠ count.
  3. Publishing a non-compliant week lists every issue in the confirmation dialog first.

No manager needs to know which ordinance applies where — the location does.

Scheduling: four different laws, one list

Meal breaks, minor curfews, daily overtime and right-to-rest each fire from their own ruleset — and land in the same list, with the rule text spelled out.

  1. Meal Breaks: a 30-minute break must start between the 2nd and 5th hour — missed means premium pay owed.
  2. Minors: 16–17s cannot work 10:00pm–7:00am before a school day — a hard stop, not a warning.
  3. Overtime: hours over 8 in a day owed at 1.5× — flagged before they are worked.
  4. Right to rest: under 10 hours between a close and the next open pays 1.5× on the encroaching hours.

Planner: draft weeks are checked like posted ones

Manager Planner runs the same rules across a whole planning period — the school-night curfew problem on August 11 is visible while it is still five weeks away and the week is still a draft.

  1. Severity at a glance: hard-stop breaches in red, advisories in yellow, right on the grid.
  2. Minor-labor breaches are a hard stop — the shift cannot be saved until it is legal.
  3. The scheduler filters out anyone a shift would put in breach, so you cannot assign them.

Compliance isn’t a publish-time surprise — it follows the plan from the first draft.

Planner: warnings, from above the store

The Warnings panel gives an area manager the whole period’s compliance picture without opening a single store week.

  1. Warnings grouped by date or by category, filterable across the period.
  2. Each entry names the person, the rule, and the day — one click from the fix.
  3. The same list, priced, follows the schedule into Payroll as a final compliance step.

Timekeeping, Scheduling, Planner — one rules engine, three places it defends you.

The pay period

Pay for the hours you actually rostered

Step through a real pay period — resolve exceptions and see premium pay caught before it posts.

Timekeeping

Pay for the hours you actually rostered

Punch drift, missed clock-outs and avoidable premium pay erode franchise margin a few minutes at a time. Timekeeping surfaces all three while the pay period is still open.

Worked hours, against the hours you rostered

The gap between what you planned and what you paid is where franchise margin quietly goes. Here it's one number, per person, per day.

  1. Worked hours in bold, the scheduled hours beneath them.
  2. Punch drift visible per shift — not discovered in the pay run.
  3. Shifts worked with no roster behind them surface immediately.

The week's labour position, before payroll sees it

Your KPIs sit across the top of the screen, so the cost of the week is obvious before anyone edits a single punch.

  1. Labour percentage of sales, actual against forecast.
  2. Scheduled against punched — the variance in one glance.
  3. Regular and overtime hours split out.
  4. Compliance warnings with the premium pay already attached.

Premium pay, caught while it's still avoidable

Compliance warnings show the money at stake and who it belongs to, with time left to do something about it.

  1. Total cost and issue count for the week, up front.
  2. Every warning priced, by employee.
  3. Jump straight to the punch behind the number.
  4. The same warnings appear on the schedule and at payroll.

Skip the clean punches

A trading week is thousands of punches. Quick filters cut it down to the handful that genuinely need a manager — each with a count.

  1. Open — someone forgot to clock out.
  2. Needs Review — flagged for a decision.
  3. Minor — young-worker hours checked separately.
  4. Absent, Time Off, Shared and Terminated for the rest.

Fix it in seconds, on the record

Corrections take a moment and leave an audit trail — with the crew member told exactly what changed.

  1. Add or correct a punch without leaving the grid.
  2. Mark as Absent on a no-show and strip the premium with it.
  3. Employees notified through the mobile app.
  4. Edits can require the employee's consent to take effect.

Read a week of attendance at a glance

The tile tells the story. No-shows, over-runs and missing punches surface without opening anything.

  1. Solid line — clocked in and out as expected.
  2. Dotted line — no clock data; they didn't show.
  3. Line past the tile — worked longer than rostered.
  4. Red dashes — a rostered shift with no punches at all.
  5. Diagonals — marked absent.

Every disputed punch has a paper trail

Open, overlapping and adjusted punches all resolve in one panel — alongside the reason the crew member gave at the clock.

  1. Close open punches; deactivate anything that shouldn't be paid.
  2. Overlapping punches numbered and handled separately.
  3. The reason captured at the clock: late, forgot, or manager asked.
  4. Manager Authorization logged against the shift.

Close the period with confidence

When the week reconciles, approval is one click. So is reopening it, if something surfaces late.

  1. Post and Approve — status moves through to Processed.
  2. Miscellaneous pay and compliance pay reviewed separately.
  3. Dismiss or reinstate a premium before it's ever paid.
  4. Reopen a posted period the moment something changes.
Time Clock

The kiosk that runs the floor's punches

This is the real LIFELENZ Time Clock — walk the live punch board, a late clock-in, break enforcement and a manager authorization.

Inside the product

The time clock, running the floor

The real LIFELENZ Time Clock — a live punch board on the tablets you already own, with compliance enforced at the moment of the punch.

The floor, counted live

The header answers the shift-runner's first question at a glance: who's on, who's late, who's missing, who's on break — live counters, each one a tappable tab.

  1. Tap Missing and every no-show appears as a red card, with the scheduled shift it's missing from.
  2. Runs on the tablets you already own — no new hardware to buy or install.
  3. Offline mode keeps taking punches with no internet — the connectivity bars strike through, and punches sync to Timekeeping when the connection returns.

Every punch, color-coded by exception

Four columns — Shift Start, Breaks, Shift End, Compliance & OT — and every card carries the person, the punch window, and a countdown.

  1. A yellow border appears at 5 minutes overdue; red means missing, late, or a break gone over.
  2. Shift End tiles surface when someone is 15 minutes from the end of their shift — before overtime starts.
  3. The Compliance & OT column counts down to due meal and rest breaks (“MB in 1 min”) so the rule never sneaks up on the manager.

Late punches explain themselves

Crew clock in with a 6-digit PIN or biometrics. Arrive 14 minutes late, and the clock asks why before the shift starts.

  1. Three reasons: I was late, I forgot to clock in, or my manager asked me to start late.
  2. Manager-initiated reasons can qualify for premium pay under your labor rules — employee-initiated ones don't.
  3. Depending on your Time Clock thresholds in business settings, the reason may or may not require manager authorization.

Marked absent? The employee is always notified — with the reason attached.

Breaks enforced at the clock, not after payroll

Meal and rest breaks are separate, counted actions — the board shows exactly when each break ends, per person.

  1. “Break Ends in 5 Mins” and “Break Overdue” countdowns keep the floor honest in real time.
  2. Coming back early? Manager approval is required to return from a break before it legally completes.
  3. Missed or short breaks flow straight into the Compliance & OT column — and into premium pay if your jurisdiction demands it.

Compliance pay, priced before it's approved

When an authorization would trigger compliance pay, the manager sees the exact warnings and premiums before saying yes.

  1. Each line shows the rule (“1×10 minute rest break is missing”) and the cost (“one additional hour at regular rate”).
  2. Nothing is silently waived — the premium is applied automatically and lands on the pay record.
  3. The same engine that prices covers in Scheduling prices punches here: one rule set, 130+ jurisdictions.

Manager PIN, full audit trail

Authorizations are personal: the manager enters their own PIN, and the decision is stamped to them — not to a shared login.

  1. Managers cannot create or edit their own punches — a superior has to do it on their behalf.
  2. Punch edits go to the employee as a consent request in their app — accept or reject before payroll runs.
  3. Best practice: filter Timekeeping to pending consent before every pay run, so no edit ships unacknowledged.

Every punch, edit, reason and authorization — one auditable trail from the clock to the pay run.

Evidence

Every number you argue about, in one place

This is the real Reporting screen — the seven reports a wage claim actually asks for.

Inside the product

The report a wage claim asks for, live to the minute

The Daily Activity Report — every hour’s sales, transactions and labor on one screen, refreshed while the shift is still running, and out the door as a CSV or PDF the moment somebody asks for it.

Every number, one report screen

The Daily Activity Report lives on the Dashboard, one click from the schedule it measures — the same screen for Business Owners, Regional Directors and store managers.

  1. Hour-by-hour Product Net, transactions, punched hours, SPLH and labor % of sales.
  2. Differential columns show sales vs. forecast and labor vs. forecast at a glance.
  3. Same report on web or the Manager Mobile App — mid-rush, from the floor.

One screen everyone argues from — so nobody argues about whose spreadsheet is right.

Live to the last punch, not a nightly batch

The DAR refreshes while the shift is still running, with a visible “last updated” timestamp — not a number that shows up tomorrow morning when it’s too late to act on.

  1. Flip any day with the date picker; today updates live through close.
  2. View the day hourly or in quarter-hour blocks — same data, sharper lens.
  3. The shift lead checks it mid-shift; the regional checks the same number at close.

The day rolls up while it’s still running

The Total row keeps a running verdict on the whole day — sales, transactions, labor hours and labor % — so you know where you stand before the dinner rush, not after it.

  1. Running totals for every KPI column, recomputed on each refresh.
  2. Compare against forecast and target without leaving the screen.
  3. Labor % of sales at the top is the number that decides whether to flex the floor.

Hour by hour, where the day was won or lost

Each row is one trading hour: what sold, how many transactions, what the kitchen prepped and who was on the clock. The 12 o’clock spike and the 3 o’clock trough stop being anecdotes.

  1. Sandwich counts and KVS prep sit beside the sales they served.
  2. Drive-thru and front-window transactions split out per hour.
  3. Spot the exact hour service slipped — then open the schedule for that hour.

Labor sits beside the sales it served

Punched hours and labor % ride in the same rows as revenue — so the question “were we overstaffed at 2pm?” takes five seconds, not a data pull.

  1. Punched hours per hour block, straight from the time clock.
  2. Labor % of sales calculated live against actual revenue.
  3. Disputes go to the Time Punch Change Approval report: original punch, method (biometric, PIN, manual), who changed it, who approved it, and the employee’s acknowledgment.

Built for the moment an auditor, a franchisor or a wage claim asks you to prove it.

Out of the platform in one click

Export surfaces CSV and PDF right on the report — and the same two formats power a whole evidence library under Reports › Download Reports.

  1. Break Audit: every break per shift marked Clocked, Attested or Waived — 15 months back, terminated employees included.
  2. Pay Period: regular and overtime hours per shift, compliance payouts, terminated staff flagged with a “T”.
  3. Outstanding Payment: open earnings itemized so a final check can be cut within 24 hours where the law demands it.
  4. Pay Details, Labor Exception and Work Pattern reports reach back 15 months.

CSV to crunch the numbers. PDF to end the argument.

Constraints

The record that decides who can work that shift

This is the real People record — one profile the schedule actually reads.

Inside the product

One record that decides who can work that shift

The People List is not an address book — it is the record scheduling, payroll and compliance all read from. Skills, availability, leave and employment history on one profile, for every person in every store.

Find anyone in a 178-person roster in seconds

Search by name or GEID, then stack filters until the list is exactly the people you mean — by role, employment type or status.

  1. The Role Filter shows only employees who hold the role you are scheduling.
  2. Only schedulable people with an active home or shared store appear — no ghosts.
  3. A dedicated Terminated screen keeps leavers out of your working list, with date, reason and last shift.

The list a manager opens first thing — and it is never out of date, because it is the system of record.

Skills and certifications, readable at a glance

Every station qualification is a colored chip on the row — who is trained, who is mid-training, who is about to expire. No clicking into twelve profiles to build a mental map.

  1. Three skill tiers: L1 novice (in training), L2 competent (works independently), L3 expert.
  2. Skill level gates what the auto-scheduler will offer them.
  3. Pay rates ride the same rows — permission-gated, so a shift lead never sees a wage they should not.

The whole roster, out the door in one click

Download Report exports the full Employee Roster to CSV in Simple or Detailed form — and bulk actions do the reverse, changing many records at once.

  1. Bulk-edit job skills, titles & rates, AOS groups and store share/transfer in one pass.
  2. Bulk terminations with reasons, instead of twelve one-at-a-time goodbyes.
  3. Every bulk change is still attributed per record in Employment History.

One employment record, and everything obeys it

Open a name and the Employment Details tab holds the organization start date, MFID, seniority and promotion dates — the exact record scheduling and payroll both read.

  1. Company seniority and probation windows tracked by the system, not a side spreadsheet.
  2. Personal Details carries school calendars and minor types — so minors physically cannot be scheduled illegally.
  3. Change it here and scheduling, payroll and compliance see it immediately.

A people list is only worth having if the schedule actually reads it. This one does.

Availability, leave and history on the same profile

Two availability types — Permanent, and Temporary with a required end date — so Spring Break never silently becomes the new normal.

  1. Employees propose changes from the mobile app; managers Approve & Notify with a comment.
  2. Start a Leave of Absence and shifts after the start date auto-unassign; notifications stop.
  3. Employment History logs every change — filter by type, action, date or editor, export to CSV or PDF.

Exactly what the schedule is allowed to read

Schedule Slots on the profile define which jobs this person can be rostered into — the handshake between one person’s record and the whole store’s schedule.

  1. Slots map to schedule jobs; outstanding qualifications are flagged before they bite.
  2. Share a trained crew member with the store next door instead of rehiring one — skills and history travel with them.
  3. Sharing rules (approval, minimum age) are governed centrally in People Configuration.

Nothing here is decorative — every field feeds the scheduler, the clock or payroll.

Estate

Set it once for the estate. Bend it where the store needs it.

This is the real Settings screen — one standard, with room to bend.

Inside the product

Set it once for the estate. Bend it where the store needs it.

Every rule your stores run on — posting windows, break law, roles and permissions — lives on one screen, inherited from the business down to each location, and guarded so nobody can quietly change what matters.

Every control in one place — and it inherits

Settings, roles, scheduling, break types, payroll and time clock configuration share one tab bar. Set a rule at business level and every location inherits it.

  1. Location settings inherit from the business; a feature disabled above becomes read-only below.
  2. One Configuration Checklist covers waiver language, school calendars and app settings before Go-Live.
  3. Sessions time out after 10 minutes — an unattended office PC is not a security hole.

One standard for the estate, with room to bend where a store genuinely differs.

Schedules that post themselves — legally

Auto Post publishes the schedule a set number of days before the week starts, at the minute you choose. Fourteen days out at midnight, every week, without a manager remembering.

  1. Posting window is checked against the legal requirement minimum for the jurisdiction.
  2. Predictive-scheduling and Fair Workweek notice periods stop being a memory exercise.
  3. Turn it off for a location that needs manual control — the business default stays intact.

Your org chart, mirrored in the platform

Every schedule belongs to a group, and groups nest the way your business actually runs — region, area, district, store.

  1. Build multi-level hierarchy with sub-folders: Florida › Miami › District 1 › stores.
  2. Day-part templates drag-and-drop onto whole groups of locations at once.
  3. JTC group rules stop anyone editing HR records or punches for peers or higher groups — and no one can edit their own record.

Break rules arrive pre-built to the law

Break Types come configured to the jurisdiction’s legal requirements out of the box — meal and rest durations, paid thresholds, the lot.

  1. Only owner-operators can edit or add company-policy breaks; managers cannot soften the law.
  2. Meal-break waiver consent is captured at the Time Clock in English and Spanish, date-stamped for 12 months.
  3. Renewal alerts fire 30 days before a waiver expires — before it becomes a violation.

The Break Audit report then proves every break was Clocked, Attested or Waived — 15 months back.

Five security tiers, and nobody edits themselves

Access runs Employee → Schedule Manager → Group Administrator → Employee Manager → Business Owner, each tier adding rights — and the screen shows exactly who can do what, per store.

  1. Roles set system-level access; permissions grant granular view/edit per location.
  2. The Schedulable flag keeps non-floor staff out of the scheduler entirely.
  3. Running SSO? Permissions auto-map and this screen steps out of the way.

Guardrails, not hopes

The rules that keep a schedule defensible are settings here, not habits you hope managers keep.

  1. Max Shift Duration caps what any schedule can ask of one person.
  2. Scheduling over unavailability is a choice: soft warning or hard stop — set at business and location level independently.
  3. People Configuration governs sharing approval, minimum sharing age, and auto-responses to time-off requests X days out.

Every one of these settings has a compliance report on the other end proving it held.

Pocket

The app that goes where the shift does

This is the real crew app — try the notification, the clock-in, and the roster.

Inside the product

The schedule, in every pocket

The real LIFELENZ apps — crew see their next shift, pick up offers, swap and set availability from their phone; managers carry the day’s numbers and approvals from the line.

The next shift, front and center

The crew app opens on the one thing that matters: your next confirmed shift — store, time, and anything that needs your answer.

  1. Action Required surfaces offers, swaps and consent requests as a badge, not an email.
  2. Confirmed shifts roll up with total hours for the period — pending vs completed.
  3. Shift conversations keep manager–crew messages next to the shift they are about.

No printed schedule on a wall. The wall is in 178 pockets, and it is always current.

Open shifts, offered fairly — accepted in a tap

An unfilled shift becomes an offer: to everyone at once, or one person at a time in sequence. The calendar dots the days with pending decisions.

  1. Filter your month by All / Pending / Accepted / Unassigned in one tap.
  2. “Offered to all” shifts show the job, hours and length before you commit.
  3. Chicago Fair Workweek crews can Accept or Reject late-notice shifts from the phone — with the premium handled automatically.

Every cover, priced before you approve it

When someone drops a shift, the app collects willing replacements — and prices each one against the schedule before the manager picks.

  1. Each candidate shows their answer and the cost delta: Dusty covers it for $2.76 less; Na costs $4.38 more.
  2. Swaps run compliance pre-checks — a cover that would breach overtime or minor rules never gets offered.
  3. The drop reason, every response and the approval live in one auditable thread.

Self-service that cannot break the law — or quietly blow the labor budget.

Availability set from the couch, approved from the office

Crew propose a start date and set their week — all-day or exact time ranges per day, with a running total of available hours.

  1. Bulk Update sets a repeating pattern in seconds; single days can differ.
  2. Submitted with comments, it lands with the manager to Approve & Notify.
  3. Temporary availability carries a required end date — Spring Break never becomes permanent.

Approved availability feeds the scheduler instantly — there is no spreadsheet in between.

The manager’s day, carried on the line

The Manager App’s Day at a Glance answers the three questions that matter mid-shift: are we selling to forecast, are the hours landing, and what is labor running?

  1. Sales vs Forecast, Hours vs Scheduled, Labor % vs Scheduled — with the gap quantified.
  2. The full hourly Daily Activity Report is one scroll away, on the phone.
  3. Daily Pacing tracks same-day sales-to-time against forecast as the day trades.

The week, rolled up — and every shift accounted for

Flip to Week and the phone shows actuals against forecast, plus the state of every scheduled shift across the store.

  1. Shift status rolls up Pending, Rejected, Swap/Drop, Unassigned and Accepted in one strip.
  2. Sales vs Labor Hours charted side by side — the week’s shape without opening a laptop.
  3. The full store selector jumps between locations without logging in and out.

Crew and managers see the same live state — the walkie-talkie is now optional.

← Back to Platform