1
Sections
Home, Chat, Calendar, Profile, and any configured mobile areas.
Concept overviewFindLiveLogSubmitEngage
Concept deep dive
Mobile app experience
The mobile app is where frontline workers see the actions and information relevant to their work. What they see depends on access group settings, policy rules, location access, shift eligibility, and mobile section configuration.
Practical rule
Use mobile for worker actions that should become structured operational data: claims, clock-ins, tasks, reimbursements, callbacks, time off, content acknowledgements, and communication.
Use this page when you need to decide:
what to configure, where the data lives, who should see it, and what the next operational action should be.
Operational visualization
Mobile turns frontline activity into structured operations data.
Today
Worker app
Available shifts
Policy filtered
Clock in
Attendance signal
Tasks
Work completed
Reimbursements
Structured request
Chat
Operational comms
Worker surface
What should a worker be able to see, submit, confirm, or complete from the field?
Mobile should expose only the actions that are relevant to the worker’s role, location, policy state, and shift status.
Definition
The parts operators need to understand
This is the vocabulary to use when explaining the concept to a scheduler, payroll lead, client manager, or implementation owner.
2
Shift actions
View, claim, request, release, clock in, clock out, and receive recommendations.
3
Task actions
Complete service tasks, care logs, onboarding tasks, forms, or acknowledgements.
4
Submission actions
Time off, reimbursements, callbacks, surveys, or custom forms.
5
Visibility rules
Access groups and policies decide what the worker can see and do.
1
Shift visibility and actions
Workers can view available shifts, request or claim shifts, see active and upcoming shifts, clock in or out, release a shift, select a replacement where required, and receive shift notifications or recommendations.
Use access groups to decide whether workers can claim, request, release, or clock in.
Use policies to block shifts that violate overtime, location, credential, or tier rules.
Use notifications and broadcasts to bring workers back into the workflow.
Always test the shift list from a real worker account.
2
Tasks, activity logs, and submissions
Mobile actions should produce structured records admins can use. A completed task, reimbursement, callback, survey, or time-off request should not disappear into a message thread.
Tasks can support care logs, service work, compliance, quality, and billing.
Reimbursements should capture amount, description, receipt, status, and approver.
Callbacks should link to the worker and shift.
Time-off requests can route to manual approval or auto-approval.
3
Self-serve information and communication
Teambridge can expose facility instructions, policies, training content, process guides, and other reference material directly in the app. Workers can also receive messages through chat, SMS, MMS, email, voice, or broadcasts depending on Engage setup.
Put instructions where workers need them, not only in admin docs.
Scope information by role, location, client, or access group.
Use broadcasts for urgent shift outreach and reminders.
Keep self-serve pages current as operations change.
Example: Mobile reimbursement request
How this shows up in a real Teambridge workflow
Use this as the implementation checklist: each step should produce a visible record, permission, view, or automation.
1
Worker opens the mobile reimbursement action.
2
They enter amount, description, and receipt details.
3
Teambridge creates a reimbursement request record.
4
Admin reviews the request in a workspace.
5
Approved requests become available to payroll or billing processes.