01
Shift Planning
Create dated shifts with assigned staff, homes, members and service codes.
Products / Staffing operations
Active
Build schedules around authorized staff, homes and service delivery
Coordinate assignments, service codes and workforce coverage while keeping users within their approved agency and home scope.
SchedulersHome managersWorkforce leads
NVASIKI workspace
Scheduling and Workforce Management
01
Staff
02
Home
03
Member
Verified agency and role scope
Availability
Active
Product overview
Purpose-built around controlled access and reviewable work
NVASIKI scheduling connects staff, homes, members, service codes and planned shifts. Published shifts support the downstream EVV and service-documentation workflow.
Verified tenant
Role and scope
Review trail
Core functionality
Tools that follow the complete working process
Each capability is presented according to its current product status and implementation limits.
02
Publishing Controls
Keep incomplete drafts from entering the active workforce schedule.
03
Home Scope
Restrict managers to homes assigned through verified access records.
04
Staff Assignment
Connect direct-care users to the people and services they are expected to support.
05
Workforce Status
Review active coverage, scheduled work and current shift status.
06
EVV Connection
Carry approved schedule information into the clock-in workflow.
How it works
A connected, reviewable workflow
Every step remains subject to the user’s verified agency, role, functional permissions and record scope.
Designed for clear handoffs
01
Staff
02
Home
03
Member
04
Service code
05
Published shift
06
EVV
Practical value
Support for authorized teams
Clarify coverage
Give authorized teams one view of planned staffing.
Reduce incomplete shifts
Require key service information before publishing.
Support downstream checks
Provide the schedule context required for EVV and billing validation.
Access follows responsibility
The workspace changes according to verified role, permissions and scope.
Security and permissions
A page never grants authority
Selecting a product page, portal or login card never grants access. Protected NVASIKI requests verify the authenticated user’s current UserAccess record, agency, role and scope. Sensitive modules require their own access grants.
Agency separation
Home and member scope
Separate functional permissions
Audit and lifecycle records
Frequently asked questions
Clear answers before implementation
Can managers schedule another agency?
No. Backend scope checks restrict agency and home access.
Does a published shift grant clinical access?
No. Clinical authority remains separately permissioned.
Can staff clock in without a valid schedule?
The controlled workflow requires an eligible scheduled shift and server verification.
Related products