GoTu
USStaffing schema v1
Mapped
23%
Components
9
Public map
How GoTu is built
Layer health
What is known, per layer
- People1/4
- Process5/18
- Software3/10
- Data0/7
- Decisions0/1
Lenses
Business architecture: 6 parts. System architecture: 3 parts.
People and relationships
- Supplied or external workforceSupplied or external workforceOffices access a pre-screened dental-professional network.
- Evidence
- documented
Interfaces and channels
- Native client appNative client appThe published app expressly serves both dental professionals and dental offices.
- 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
- Public audience routingPublic audience routingThe retained site separately addresses professionals choosing work and dental practices filling schedule gaps. These entry paths do not prove an automated lead-to-operations handoff.
- Evidence
- documented
Demand and commitment
- Credentials and eligibilityCredentials and eligibilityOffices access a pre-screened dental-professional network.
- Evidence
- documented
- Offer and acceptanceOffer and acceptanceProfessionals browse and apply for work and communicate directly with the dental office.
- Evidence
- documented
- Staffing demand intakeStaffing demand intakeThe office side can post shifts and manage bookings.
- Evidence
- documented
Work delivery and recovery
- Operational messagingOperational messagingProfessionals browse and apply for work and communicate directly with the dental office.
- Evidence
- documented
- Scheduling and changesScheduling and changesThe office side can post shifts and manage bookings.
- 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.