LaborWorks
USStaffing schema v1
Mapped
25%
Components
10
Public map
How LaborWorks is built
Layer health
What is known, per layer
- People1/4
- Process5/18
- Software4/10
- Data0/7
- Decisions0/1
Lenses
Business architecture: 6 parts. System architecture: 4 parts.
People and relationships
- Supplied or external workforceSupplied or external workforceThe portal is offered within a staffing service.
- Evidence
- documented
Interfaces and channels
- Approver interfaceApprover interfaceThe customer portal supports adding/editing punches and approving hours.
- Evidence
- documented
- Client web portalClient web portalThe service links separate customer and employee portals to Zenople.
- Evidence
- documented
- Native worker appNative worker appA published worker app is retained in the catalog; listing metadata establishes the channel, not a completed login or the rest of the workflow.
- Evidence
- documented
- Worker web or PWAWorker web or PWAThe service links separate customer and employee portals to Zenople.
- Evidence
- documented
Work delivery and recovery
- Scheduling and changesScheduling and changesApp publisher: viewing or choosing work schedules.
- Evidence
- documented
- Time captureTime captureThe customer portal supports adding/editing punches and approving hours.
- Evidence
- documented
- Work-time review and approvalWork-time review and approvalThe customer portal supports adding/editing punches and approving hours.
- Evidence
- documented
Money and obligations
- Client billing and invoicesClient billing and invoicesClient invoices and employee pay history are described in the portal features.
- Evidence
- documented
- Worker earnings and payoutWorker earnings and payoutClient invoices and employee pay history are described in the portal features.
- Evidence
- documented
Is this your company?
Claim the profile, correct it, decide what shows
Everything here is public research, labelled as inferred. Create an account to add your own detail in private and choose, value by value, what the registry shows.