Claude Chat

Everyone has access. Almost nobody has guidance.

Broad Claude access without a usage policy is how sensitive material ends up somewhere nobody intended. This track fixes the guidance and the governance at the same time.

Where you are

If any of this sounds familiar.

Licences went out organization-wide and adoption is uneven and unmeasured.

Nobody has told people plainly what they may and may not put into it.

Compliance has questions that a vendor datasheet does not answer.

Who it’s for

Built for the people who do the work.

Organizations rolling Claude out beyond a pilot group
Compliance and risk teams who need a defensible usage position
Team leads who want their people productive without creating an incident

What you get

What your team keeps afterwards.

Role-based guidance, so a clinician, a recruiter and an analyst each get what applies to them

A written usage policy covering what may be entered, by whom, and what is retained

The governance module every Kriv engagement includes: who owns which automated action, what gets logged, and what an auditor sees.

Practical patterns for everyday work, taught in your own context

How it runs

Scoped to your week, not ours.

Discovery workshopHalf day, virtualAssess readiness and current shadow usage honestly.

Organization rolloutMulti-session, hybridRole-based cohorts with the policy work alongside.

Training pricing

Straight answers

The questions that actually come up.

Do you write the usage policy, or just advise on it?

We draft it with you and hand it over as a document you own. It covers what may be entered, by which roles, what is retained, and how exceptions get approved. Your legal and compliance teams review it; we make sure it is specific enough to actually follow.

What if people are already using AI tools we have not approved?

Assume they are, and that is a finding rather than a failure. The discovery workshop surfaces it without turning it into a disciplinary exercise, because a policy written as if shadow usage does not exist gets ignored.

Is this HIPAA-aligned?

Kriv delivers HIPAA-aligned engagements and a BAA is available. For this track that means the usage policy, role guidance and retention position are built around PHI handling from the start rather than added afterwards.