Temper
NetherlandsStaffing schema v1
Mapped
18%
Components
7
Public map
How Temper is built
Layer health
What is known, per layer
- People0/4
- Process5/18
- Software1/10
- Data1/7
- Decisions0/1
Lenses
Business architecture: 5 parts. System architecture: 2 parts.
People and relationships
- Worker profileWorker profileThe worker app describes signing up and completing a profile before selecting work.
- Evidence
- documented
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
Demand and commitment
- Offer and acceptanceOffer and acceptanceWorkers choose shifts and set their own hourly rate under the described freelance route.
- Evidence
- documented
Work delivery and recovery
- Time captureTime captureThe app describes checkout and approved hours as conditions for DirectPay; payment claims are not independently verified.
- Evidence
- documented
- Work-time review and approvalWork-time review and approvalThe app describes checkout and approved hours as conditions for DirectPay; payment claims are not independently verified.
- Evidence
- documented
Money and obligations
- Pay and bill termsPay and bill termsWorkers choose shifts and set their own hourly rate under the described freelance route.
- Evidence
- documented
- Worker earnings and payoutWorker earnings and payoutThe app describes checkout and approved hours as conditions for DirectPay; payment claims are not independently verified.
- 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.