Skip to main content

Features

Everything a case touches, in one plugin

Six modules, fourteen record types, and one capability map they all register against.

Module 01

Referrals & intake

A referral is a record from the second it arrives — source, funding source, referring contact, and the consumer it is about. The welcome-contact clock starts at creation, and the 24-hour compliance window is measured, not remembered.

When intake is ready, the referral bridges into a consumer case without re-keying anything. Discovery calls and pathway assessments hang off that same consumer record.

  • csw_referral, csw_welcome_contact, csw_discovery_call and csw_pathway_assessment record types
  • 24-hour welcome-contact compliance measured per referral and rolled up per team
  • Funding source carried from referral through to billing readiness
  • Gravity Forms bridge for public or partner-facing intake forms
Intake specialist meeting with a new client
Team reviewing a case board on a laptop

Module 02

The case pipeline

One lane per case stage, one card per consumer. Dragging a card runs Csw_Consumer_Status::advance() — the same state machine the admin screens and the REST API use — so a skipped step is rejected on the board exactly as it would be anywhere else.

Every move is authorized twice: the REST route requires manager tier, and the state machine re-checks the mover’s per-consumer edit capability.

  • Drag-and-drop board scoped to team or org by role
  • Barrier plans with dated follow-up tasks and notifications
  • Billing-readiness gate before a case can be billed
  • Case closure with outcome capture and a final report record

Module 03

Visits & documentation

Visits are dated records with field-completeness scoring, so “documentation completion” is a number you can chart rather than a feeling. A visit can be attached to a timecard entry as proof of service.

The AI documentation assistant drafts a visit note from the structured fields using Claude. It drafts; the staff member edits and files. Nothing is auto-filed, and no consumer identifier is sent without the sensitive-field protections in place.

  • csw_visit records with completeness scoring
  • Proof-of-service linkage between visits and timecard entries
  • AI-assisted note drafting (optional, key-gated, never auto-files)
  • Revision log on the records that matter
Case worker talking with an older adult at home
Trainer presenting to a room of staff

Module 04

Training & credentialing

A configurable training catalog plus per-staff training records bucketed into completed, due, expired and upcoming — including catalog items nobody has taken yet, which is the bucket that usually bites during an audit.

Credentials carry expiration dates, and a scheduled job sends expiration notices ahead of time to the staff member and their supervisor.

  • Training catalog with completion matrix by training and by staff
  • Department and role filters on the org-wide training dashboard
  • Credential expiration cron with templated notifications
  • Certificate generation for completed programs

Module 05

Time & billing

Staff pick a pay period, add line entries against their own documented visits, and submit. On submit the card locks and an hours-only PDF becomes available. Ownership is re-checked server-side on every add, delete and submit — a forged POST against someone else’s card is rejected even though the UI never offered the control.

No rate and no dollar figure appears on the staff screen or its PDF. The with-dollars view lives in wp-admin behind csw_view_billing_math.

  • Semi-monthly pay periods by default, filterable
  • Owner approval queue with edit-request workflow
  • Hours-only staff PDF; billing math strictly capability-gated
  • Billing rates per funding source, resolved by the calculator
Reviewing hours on a laptop screen
Two colleagues talking in a care setting

Module 06

Roles, security & privacy

Eight roles ship with the plugin, each mapped through one central capability table that every record type registers against. An owner headcount cap keeps the top tier small, with a CLI escape hatch so nobody can lock themselves out.

Sensitive identifiers are encrypted at rest with a last-four hint for matching; revealing one requires a capability, a reason, and leaves a PII access-log entry. Two-factor enforcement is policy-driven for the roles that need it.

  • 8 roles: CHW, Instructor, Supervisor, Program Coordinator, Intake Specialist, Referral Coordinator, Org Admin, Owner
  • Encrypted sensitive identifiers with logged, reason-required reveals
  • Protected file storage — sensitive uploads never sit in the open uploads folder
  • WP 2FA policy enforcement per role

See the modules actually running

Every front-end screen described above is placed on this demo site as a real page.