Scheduling, time clocks, and Team Chat
Give every manager a clean handoff from schedule to approved time.
How to carry a shift from schedule to approved time and team handoff: keep planned coverage, current clock state, worked-time review, eligible approval, and native employee messaging close enough for the next manager to see what happened and what still needs an owner.
One team, one accountable handoff
Give managers one clear handoff from schedule to approved time.
LiftedPOS keeps schedules, current clock state, timesheet review, and native Team Chat close enough for the next manager to see what was planned, what happened, and what still needs an owner. During scoped setup, we help configure the enabled modules, roles, employees, locations, and handoff procedure.
Plan the coverage
Build the selected-location schedule around the employees, times, roles, stations, and notes the manager needs.
See live state
Open the employee record to see Clocked In, On Break, or Off Clock before taking an authorized manager action.
Carry the exception
Reconcile worked time, approve eligible records, and preserve unresolved context for the next manager in Team Chat.
Use the seeded product to explore the operating path, then bring us the locations, roles, devices, records, and exceptions that matter to your business.
The manager rule
Keep plan, live state, worked time, approval, and conversation distinct.
Schedule and Timesheets are separate modules. Team Chat is a third operating surface. Connecting them is a management procedure: messaging does not change the authoritative schedule, clock event, timesheet, or approval record.
Shift record chain of custody
Move evidence forward without collapsing its meaning.
A planned shift is not worked time. A live clock state is not an approved timesheet. A message is context, not a mutation of the record.
- 01 · PLANSchedule coverage
Selected location, employee, date, time, optional role or station, and notes.
- 02 · READObserve live state
Clocked In, On Break, or Off Clock in the employee record.
- 03 · CARRYOwn the exception
Name the employee, time, discrepancy, evidence, decision owner, and next check.
- 04 · REVIEWInspect worked time
Choose the selected period and status; review another employee's eligible entry.
- 05 · HAND OFFApprove or escalate
Approve only supported records; preserve unresolved context for the next manager.
Module and permission readiness
Prove access with the role that will run the shift.
Schedule and Timesheets are separate modules. Team Chat has its own module and membership boundary. Validate the merchant's enabled modules and production roles before turning this checklist into policy.
view_schedule
Opens the selected-location Day, Week, and Month schedule board.
manage_schedule
Creates, edits, moves, resizes, copies, deletes, or accepts proposed shifts.
view_timesheet
Opens the whole-store timesheet review surface available to the manager role.
manage_timesheets
Edits another employee's supported entry and approves eligible completed work.
Module + membership
view_messaging gates reading. Conversation membership determines the history available to that employee.
| Record | Primary owner | Evidence | Handoff rule |
|---|---|---|---|
| Schedule | Coverage manager | Selected location and visible period | Overlap warning is a review point, not prevention |
| Live clock | Manager on duty | Employee identity and current state | Act only from the intended employee record |
| Timesheet | Reviewing manager | Selected period, status, hours, entry detail | You cannot approve your own entry |
| Team Chat context | Named conversation owner | Message, author, time, membership, archive state | Messaging does not change the operating record |
Planned coverage
Read the selected location before changing the week.
The current board supports Day, Week, and Month views; create, edit, move, resize, and delete; optional role / station and notes; current-range CSV; and keyboard as well as pointer controls.
Swipe horizontally to inspect the full product screen, or use the full-resolution link.
Confirm location and range
All schedule reads and changes begin in the selected location and visible period.
Read existing coverage
Compare employee, time, role / station, notes, shift count, and scheduled hours.
Treat automation as a proposal
Auto-schedule uses the selected location's previous 30 days of transaction count by weekday and hour. It proposes narrow busy-window coverage; it does not evaluate availability, skills, wages, time off, or labor targets.
Copy carefully
Copy Last Week appends shifts. Repeating it can duplicate coverage, and a multi-shift copy can produce a partial result if one create fails.
Live clock state
Observe the employee before using the manager action.
The manager-facing Employees surface shows Clocked In, On Break, or Off Clock and exposes the appropriate authorized manager Clock In or Clock Out action.
Swipe horizontally to inspect the full product screen, or use the full-resolution link.
| Visible state | Manager reads | Supported action | Carry forward |
|---|---|---|---|
| Off Clock | Employee identity and current absence of active time | Clock In when authorized and operationally correct | Reason if manager initiated |
| Clocked In | Active state and elapsed context | Clock Out when the employee's work is actually ending | Any discrepancy for review |
| On Break | Break state attached to the active time record | Follow the merchant's supported break procedure | Unresolved break context |
Planned versus worked
Reconcile intent, current state, and completed time separately.
The timesheet surface supports This Week, Last Week, Pay Period, and Custom ranges, employee search, status filters, sortable fields, eligible manager editing and approval, and selected-period CSV.
Swipe horizontally to inspect the full product screen, or use the full-resolution link.
| Question | Read from | Decision | Do not infer |
|---|---|---|---|
| Who was planned? | Selected-location schedule | Coverage and assignment intent | That the hours were worked |
| Who is active now? | Employee manager clock state | Immediate operating response | That the final entry is complete |
| What time was recorded? | Timesheet row in the selected period | Edit another employee where authorized or hold for review | Payroll, legal overtime, or policy compliance |
| Can it be approved? | Status, completeness, actor, and permission | Approve another employee's eligible completed entry | That a bulk run is atomic |
Shift exception tree
Route the discrepancy by record, not by urgency alone.
A message can preserve context, but the owning product record still needs the supported correction, approval, or rollout action.
Return to planned coverage.
Confirm selected location, range, employee, and shift. An overlap warning can be saved anyway, so inspect the actual board. If Copy Last Week was repeated, look for appended duplicates.
Open the employee record.
Confirm identity and current Clocked In, On Break, or Off Clock state. Do not guess from a schedule block or a Team Chat message.
Filter the selected period.
Find the employee and entry, inspect completeness and status, then use the supported manager path for another employee or hold the exception.
Check actor and partial result.
Confirm the row is eligible, completed, and belongs to another employee. After a bulk attempt, refresh because earlier rows may already be approved.
Read membership and connection state.
Normal messages are not guaranteed alerts. Live delivery uses an application connection with a 30-second fallback refresh; direct messages and explicit mentions have narrower notification behavior.
Name the next owner and check.
Record the discrepancy, current evidence, decision authority, deadline, and product record that must be revisited.
Team Chat handoff
Preserve context without pretending chat changed the record.
Current Team Chat supports Direct, Group, public Channel, and Announce conversations; mentions, typing, reactions, edit, tombstone delete, archive and restore, pin, cross-channel search, membership controls, unread state, pagination, and qualified presence.
Swipe horizontally to inspect the full product screen, or use the full-resolution link.
Use one exception packet
Employee · shift/date · observed state · expected state · evidence · manager decision · next owner · due time.
Choose the audience
Direct, Group, public Channel, or Announce according to existing membership. An announcement reaches its configured members, not automatically the entire company.
Use the accepted file boundary
Server-accepted attachments are JPEG, PNG, WEBP, GIF, or PDF up to 10 MB. Keep sensitive employee and payment information out of routine chat.
Return to the record
Unread, typing, presence, reaction, or a message is not proof that the schedule, time, approval, or payroll process changed.
Printable manager close checklist
Close the shift with an auditable handoff.
- 01 · COVERAGEConfirm selected location, visible range, late changes, overlaps saved anyway, copied coverage, and unresolved gaps.
- 02 · LIVE STATEReview every employee still Clocked In or On Break and name the manager who owns each exception.
- 03 · WORKED TIMESet the intended period and filters; inspect incomplete, missing, and pending approval rows.
- 04 · APPROVALApprove only another employee's eligible completed record. Refresh after bulk work and identify any partial result.
- 05 · CONTEXTPut unresolved exceptions in the correct Team Chat audience with evidence, next owner, and next check.
- 06 · ACCEPTANCEReturn to Schedule, Employees, Timesheets, and Team Chat and confirm the displayed state matches the written handoff.
Before you go live
Run one complete shift handoff with both managers.
Run this with the merchant's enabled modules, locations, roles, schedules, clock procedure, approval policy, and Team Chat membership.
| Scenario | Expected evidence | Pass gate | Recovery owner |
|---|---|---|---|
| Planned shift | Correct selected location, employee, time, role / station, and notes | Coverage is readable in the intended view | Schedule manager |
| Overlap | Warning appears before Save anyway | Intentional exception is documented | Coverage manager |
| Copy previous week | New appended shifts are reviewed for duplicates | Partial or duplicate result is resolved | Schedule manager |
| Auto-schedule | Proposal is explained as 30-day transaction count | Human accepts only appropriate suggestions | Store manager |
| Clock state | Correct employee shows Clocked In, On Break, or Off Clock | Manager action matches physical truth | Manager on duty |
| Timesheet approval | Another employee's eligible completed record is approved | Own-row block and status are understood | Reviewing manager |
| Bulk approval failure | Refresh reveals any partial result | Every remaining row has an owner | Reviewing manager |
| Team Chat handoff | Correct membership receives the exception packet | Source record is rechecked separately | Next-shift manager |
Workforce rollout
Price the stations clearly, then configure the team workflow with us.
LiftedPOS software is $100/month for the first station and $50/month for each additional station. A standard station is $499.99 to purchase or $39.99/month to lease. Cancel anytime—there is no long-term software contract. Leased equipment must be returned after cancellation or billed at the full purchase price.
Tenant access uses {company-prefix}.liftedpos.com/login. During scoped setup, we help configure and validate the enabled workforce modules, locations, roles, employee records, scheduling rules, break policy, time approvals, Team Chat membership, and management escalation. Payroll remains the merchant’s separate process unless explicitly included in a written integration scope.