Staff, supervisors & organizations
DSP Staff & Supervisor Documentation Workspaces
Direct support professionals need fast documentation. Supervisors need visibility. Administrators need secure configuration. Those are different jobs.
Staff: the right recipient and the right task
The intended staff workspace is centered on assigned recipients, relevant programs, upcoming services and permitted documentation actions. A DSP should be able to open the correct person, record a short observation and identify any required follow-up fields.
Configured categories and prompts can make expectations clear before submission rather than forcing staff to guess what information their supervisor will need.
Supervisors: review within the assigned scope
Supervisors may need to examine documentation, recognize missing follow-up, review goals, check incident status and prepare permitted summaries. Their access should be limited to the people and programs they are authorized to oversee.
A supervisor's title is not permission to open every recipient in every program. Access is designed around current recipient and program assignments.
Administrators: configure programs and permissions
A multi-program provider might run adult day, community participation and respite services. Administrators could define required tags, approved questions, staff assignments, access levels and reporting options per program.
The intended rule hierarchy prioritizes system security and mandatory organization requirements over optional personalization.
Questions people ask
Can a DSP see every person in an organization?
The experience is designed around assignment-based access to people and programs.
Can supervisors change documentation?
The intended workflow supports authorized review and attributable amendments according to program permissions.
Related KinNotice guides
Less time documenting. More clarity in care.
Share your workflow challenges and help shape the KinNotice early-access experience.
Request a pilot conversation