Coverage first
The schedule surface shows assigned employees, requirement counts, event status, and underfilled work so admins can act before the day starts.
Scheduling
Create events, assign employees, apply rotating templates, review maker requirements, handle open-shift coverage requests, and import schedule files through review-first workflows.
Launch posture
Core launch surface
Scheduling, coverage review, and import review are part of the controlled launch workflow.
Admin Schedule with coverage counters and assignment review
Capture desktop and mobile schedule views after seeded coverage examples are final.
These points describe shipped product behavior or explicitly scoped setup readiness. Final screenshots and recordings will be captured from the product after demo data is frozen.
The schedule surface shows assigned employees, requirement counts, event status, and underfilled work so admins can act before the day starts.
Auto-fill proposals, schedule imports, time-off approvals, and coverage offers stay reviewable. Ready-draft autopublish only confirms shifts that meet coverage rules.
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
These answers keep trial, support, export, provider, AI, mobile, and trust expectations consistent across the public site.
The current path supports controlled trial activation. No-card demo tenants remain support-approved so capacity, provider setup, sensitive uploads, and data-retention expectations stay bounded.
Paid access normally ends at the end of the billing period, then the workspace enters a 30-day export/reactivation window unless a verified deletion request is completed earlier.
No. Yrka supports timekeeping, payroll-prep exports, review, and provider handoff. Customers remain responsible for payroll processing, tax filing, legal, HR, and compliance decisions.
Launch mobile support is responsive web/PWA-oriented. Employees get scoped offline read context and supported queued writes with visible sync states; native app-store apps and broad offline admin operation are not part of launch scope.
Yrka uses optional analytics on the public site to understand page interest. The authenticated app does not load GA4.