Stale handbooks no one reads
PDFs in shared drives go out of date the moment a policy changes.
Resources
Company knowledge that asks for acknowledgement.
Operational knowledge with acknowledgements and source boundaries. Publish what your team needs, target who needs it, and prepare what AI is allowed to answer over.
Evaluation focus
employee handbook software
- company knowledge base for hourly workers
- policy acknowledgement tracker
- employee training resources platform
- compliance acknowledgements software
- Acknowledgements tied to page versions
- Bundles target jobs, teams, roles, employees, and status
- Sources are prepared before chat can read them
Resources handbook
Resources · Operations handbook
Safety
Yard procedures
PTO policy
Customer service
Inventory
Yard opening procedure (v3.2)
Ack required · 23/28Source: prepared
Generated layout — synthetic demo data.
Who it is for
- Ops admins maintaining policies and procedures
- HR/people leads tracking acknowledgements by team or role
- Employees searching the handbook during a shift
Built for these realities
The pain we hear from operators
Each pain point reflects real conversations with SMB operators evaluating workforce tools today. Yrka is shaped around these realities, not generic feature checklists.
Acknowledgements that do not stick
Required reading sign-offs disappear into forms with no audit trail.
AI chat over content nobody approved
Generic doc-chat tools answer from drafts, deprecated pages, and unapproved imports.
How teams use it
Use cases we ship for today
These are the moments this surface is built around. They map to shipped product behavior and the launch scope for this area.
Handbook + directories
Resources sections support policies, procedures, directories, and reference content employees need mid-shift.
Targeted acknowledgements
Required acknowledgements can target company jobs, departments, teams, job roles, explicit employees, and employment status.
Source-ready chat
Imported or edited content is not chat-ready until an admin approves and prepares the source.
Why Yrka here
What makes this different
Differentiators map to shipped product behavior. They are the reasons buyers pick this surface after comparing alternatives.
Version-tied acknowledgements
Required acknowledgements are tied to specific page versions so re-read prompts are accurate.
Admin/employee boundary
Published employee Resources stay separate from admin-only content surfaces.
Retrieval that fails safely
Prepared sources back Resources chat; optional vector retrieval falls back to lexical search when embeddings are not ready.
How it flows
A workflow that mirrors how operators actually run the day
Three steps, three responsibilities.
- 01
Author
Write or import pages into Resources. Stage drafts and revisions before publishing.
- 02
Target
Send the right Resources to the right people with role, team, and employment-status bundles.
- 03
Acknowledge
Require version-aware acknowledgements, then review who has and hasn't completed them.
What's inside
Resources highlights
Acknowledgements
Version-aware ack tracking with full audit trail and renewal reminders.
Collections
Group Resources by team, location, or purpose without losing structure.
Compliance bundles
Job, department, team, role, employee, and employment-status targeting.
Approved sources for chat
Resources chat reads only the records you've reviewed and prepared.
Notion and Drive sync
Reviewed source paths with optional live OAuth into Resources review.
Cited answers
Answers always cite the source pages they came from.
Operational knowledge
Resources are built for policies, procedures, directories, and reference material your team actually opens during the workday — not a sprawling wiki.
Sources before chat
Imported or edited content isn't chat-ready until an admin approves and prepares the source, so answers cite material your team has signed off on.
Scope
What's included, what's intentionally out of scope
Yrka maps every feature to its product claim so commercial conversations stay honest.
Included
- Published Resources
- Collections
- Acknowledgements
- Source approval
- Prepared text records
- Reviewed Notion and Google Drive source export staging
- Live Google Drive, SharePoint/OneDrive, and Notion source staging with Resources review
- Company job, department, team, job-role, explicit employee, and employment-status compliance bundle targeting where configured
Boundaries
- Guaranteed legal policy correctness
- Unapproved source chat
- Compliance knowledge base claim
Related
Where this fits in the platform
Training
Training where employees already read your handbook.
Resource-linked modules, video links, quiz questions, passing scores, assignments, and completion review — designed for real team enablement.
ExploreResources chat
Ask over the company knowledge that's been approved.
Employee and admin Resources chat use organization AI settings and approved prepared source records, with access-scoped retrieval and citations.
ExploreCommunications
Messages, boards, and follow-up that match the workflow.
Direct messages, board announcements, app notifications, and review-required inbox work — each distinct, all connected to the operations they belong to.
ExploreQuestions
Common buyer questions
We surface the questions buyers actually ask — trial, support, export, mobile, payroll, provider, AI, and trust scope — in plain language.
How does the trial work?
Start with a 30-day card-required trial. Cancel anytime from the Stripe customer portal. Workspaces stay available for export or reactivation for 30 days after paid access ends.
Does Yrka process payroll or file taxes?
No. Yrka covers time tracking, scheduling, payroll-prep exports, and provider handoff. Customers stay in charge of payroll processing, tax filing, legal, and HR decisions.
What does mobile look like?
Responsive web and an installable PWA cover employee time entry, scheduling, resources, tasks, messages, and profile review. Employees see scoped offline read context plus queued supported writes with clear sync states.
Can we export our data?
Yes. Payroll-prep exports, schedule and time reports, and employee data exports are part of the core product. Customer data remains exportable for 30 days after paid access ends unless an earlier deletion is requested.
Ready to run the day on Yrka?
Start a 30-day trial in minutes, or book a working session to walk through the rollout with someone who has done this before.