Systems

Scheduling & time clock

Schedules, timecards and forecasts decide most of what a store costs to run. Poros Ops reads them for every store, every day, and flags problems while there's still time to do something about them, not after the week has closed.

What Poros Ops reads

  • Schedules, posted and draft
  • Timecards and punches
  • Forecasts by store
  • Labor posting, which stores have posted and which haven't
  • Inventory counts from the back office

What it checks

  • Midday labor pulse. Trim suggestions when a store runs over its labor target.
  • Overtime watch. Who is about to cross into overtime, before they do.
  • Break compliance. Missing or short breaks, every shift.
  • Schedule publish check. Stores that haven't posted next week's schedule on time.
  • Missed clock-outs and bad punches. Found the same night, not on payroll day. See how to catch missed clock-outs across every store.
  • Count review. Inventory counts that don't look right, flagged before they're used.
  • Week close. Which stores are posted and clean before payroll. See the payroll week-close checklist.

The full list is on the automations page.

What it can write, and only when you say so

  • Schedule pre-draft. Next week's schedule drafted from your forecast, with re-trims suggested. Schedule changes apply only on your OK.
  • Timecard fixes. Missed clock-outs and bad punches fixed once the manager OKs the correction.
  • Count corrections. Miscounts and unposted counts fixed with the manager's OK.

Labor automations text managers and owners only. Hourly crew are never texted by them.

Nothing on this list writes until you switch it on, and each one climbs the same ladder on its own:

  • Shadow. It runs on its real schedule and logs what it would have done. Nothing is sent and nothing changes.
  • Ask-first. It proposes each change with the evidence. A person approves, edits or rejects it.
  • Autonomous. Only where you decide it has earned it, and only inside limits you set. Each automation has its own off switch, and it can be stepped back down at any time.

"Done" means Poros Ops re-read the timecard, schedule or count and saw the new value. No read-back, no success message. Every write is logged: who asked, what changed, and what the system read back. More on the ladder in Shadow mode: how to trust automation with your stores.

How access works

  • Agreement first. We ask for access only after a written agreement is signed.
  • Your account, your user. You create a read-only user for Poros Ops inside your own scheduling and back-office account. You own that user and can remove it at any time.
  • Writes are approved one at a time. If you later switch on an automation that writes, the access it needs is set up with you then, for that automation only. Approving one does not approve the rest.
  • Never passwords by email. Don't send passwords or account numbers through email or our forms. Access is set up with you, inside your account.

Systems we connect today

Compatible with CrunchTime Net-Chef.

Using something else? Tell us on the walkthrough.

See it on your stores

If you'd like to see how the labor, break and clock-out checks would run across your locations, we're happy to show you.

Book a walkthrough

CrunchTime and Net-Chef are trademarks of their respective owners. They are used here only to identify compatibility. No partnership, sponsorship or endorsement is implied.