Adecco
US pageStaffing schema v1
Mapped
20%
Components
8
Public map
How Adecco is built
Layer health
What is known, per layer
- People0/4
- Process4/18
- Software3/10
- Data1/7
- Decisions0/1
Lenses
Business architecture: 4 parts. System architecture: 4 parts.
Interfaces and channels
- 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
- Public audience routingPublic audience routingThe retained homepage has separate job-seeker and hiring-business entry sections. These entry paths do not prove an automated lead-to-operations handoff.
- Evidence
- documented
Demand and commitment
- Assignment recordAssignment recordOnce employed, workers can see assignment dates and locations, paystubs and payroll information.
- Evidence
- documented
- Worker onboardingWorker onboardingThe app supports applying and following application progress.
- Evidence
- documented
Work delivery and recovery
- Operational messagingOperational messagingThe app describes contacting experts through chat or the service team.
- Evidence
- documented
- Scheduling and changesScheduling and changesApp publisher: viewing or choosing work schedules.
- Evidence
- documented
Money and obligations
- Employee payroll administrationEmployee payroll administrationOnce employed, workers can see assignment dates and locations, paystubs and payroll information.
- Evidence
- documented
- Worker earnings and payoutWorker earnings and payoutApp publisher: earnings access or payment options.
- 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.