Unbundling Work, Credentials, and Liability

A job title bundles work, authority, trust, evidence, and liability. Open the bundle before deciding what should move and what must stay with a person.

The question

Which parts of consequential work need this person's capability, credential, authority, presence, or liability bearing responsibility?

Active · since 2026 · Unbundling Work

The job title is not the work

A title records an institutional arrangement. It does not show the tasks, decisions, handoffs, evidence, exceptions, or outcomes inside it. Those parts may have been bundled because of regulation, old software, labor scarcity, reimbursement, or habit.

Begin with observed work. Record what happens, how often, what enters, what leaves, who decides, what can go wrong, and who answers for it.

Open the job-title bundleA role branches into tasks, decisions, authority, evidence, credentials, liability, and outcomes.Job titleTaskswhat is doneDecisionsjudgment requiredAuthorityright to actEvidenceproof of workCredentialsknowledge, trust, permissionLiabilitywho answers for failure
Move work only after the bundle is understood.

Credentials carry several things

A professional credential can stand for training, tested competence, legal scope, institutional privilege, trust, supervision, accountability, and liability. These are related, but they are not interchangeable.

A machine may be capable of preparing a recommendation and still lack authority to issue it. A person may hold authority while adding little value to routine preparation. The design must state both facts.

What a credential carriesA credential can bundle tested capability, authority, privilege, supervision, trust, accountability, and liability.CredentialCapabilityAuthorityTrustAccountabilityLiability
Capability, authority, and liability must be examined separately.

Use the minimum necessary exposure

Count credentialed touches and minutes per accepted outcome. Then ask which touch uses judgment or authority and which merely repairs missing information, repeats documentation, or moves a packet.

The objective is not fewer professional minutes at any cost. It is the least credential, authority, and liability exposure consistent with a safe result and clear accountability.

Find where liability lives

For each stage, name who can cause harm, prevent harm, authorize action, execute it, supervise it, communicate it, and pay after failure. Those may be different parties.

Risk creation, risk control, risk ownership, risk transfer, and risk financing need separate fields. Moving work without moving control can leave a person responsible for an outcome they can no longer influence.

Liability follows the workA sound redesign separates the party creating or controlling risk from the party merely financing loss.ControlCreates or prevents harmAuthorizes and supervisesCan detect and contain failureExposureAnswers for the outcomeCarries contractual dutyIndemnifies or insures loss
Moving a task does not settle who controls or carries its risk.

Ask why the work exists

Some work produces the outcome. Some protects safety. Some exists because a payer, regulator, contract, vendor, department, or missing information imposes it. One party may require the work while another pays and a third waits.

Before automating a burden, identify its cause. The right answer may be to retain it, assist it, redesign the exchange, change a rule, renegotiate a contract, consolidate a handoff, or remove the requirement.

Why the work existsA work unit may serve the outcome or arise from safety, law, payment, contract, coordination, information failure, or habit.Work unitOutcomeSafetyPaymentCoordinationObsolete
Do not automate a burden before finding its cause.

Count work wherever it moves

A local labor saving can move effort to another employee, a more expensive professional, a vendor, a patient, or a caregiver. It can also return later as review, exception handling, or correction.

Keep a transfer ledger. A redesign is not better when it saves twenty staff minutes by adding forty minutes of phone calls, forms, portal work, or record gathering for a family.

Know when the bundle should remain

Keep work bundled when the judgment is tacit, the physical act and decision are inseparable, law requires one accountable professional, trust depends on direct participation, or decomposition creates more ambiguity and risk than it removes.

Technical separability is not enough. The legal, clinical, operating, economic, and human case must also hold.

Disposition review

Choose the disposition from evidence, not enthusiasm for automation.

DispositionUse whenEvidence needed
Retain with a personJudgment, authority, trust, presence, or learning changes the resultOutcome and capability evidence
AssistPreparation can move while a person keeps the decisionReview burden and error record
AutomateWork is bounded, observable, reversible, and testableAccepted outcomes under live conditions
Redesign or removeThe burden comes from an avoidable rule or broken exchangeCause, authority, and system effect
Keep bundledSeparation creates legal, safety, or accountability gapsQualified review and failure analysis
Work disposition and proof

Put this to work

Credential and liability map

Separate capability, authority, credential need, control, accountability, and liability before work moves.

For
Operators, professional leaders, risk owners, and workforce designers.
What you keep
A credential and liability map you can review, revise, and send.
What counts as sound
  • Starts with observed work
  • Separates authority from capability
  • Counts burden transfer
  • Names unresolved legal questions
  • Ends with a disposition

Qualified legal and professional review is required before changing regulated authority or responsibility.

Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.

Review the prompt

You can leave any field blank. The prompt will mark it as not provided.

If the record survives your review, send the question, evidence, unknowns, and requested next step.

Notes under this pillar

Design Patterns

  • An AI credential

    Represent trust as evidence about a narrow capability, approved sources, authority, incidents, and recertification.

    September 2026

  • Credential Exposure profile

    Count where credentialed time, authority, supervision, and liability enter one accepted outcome.

    September 2026

  • Liability Decomposition map

    Separate who creates, controls, authorizes, owns, transfers, and finances risk at each stage.

    September 2026

  • Work Origin and Incentive map

    Find whether work serves the outcome or was created by a rule, incentive, boundary, or information failure.

    September 2026

  • Burden Payer and Burden Imposer matrix

    Show who requires work, who performs it, who pays, who benefits, who waits, and who can change it.

    September 2026

Operating Theorys

  • Credentials as insurance

    Training, credential, licence, supervision, and liability cover exist as a stack because each layer is insufficient alone. An AI worker arrives with none of them.

    September 2026

  • The title trap

    A role name hides the scope, authority, evidence, exceptions, and outcomes that determine whether work can move.

    September 2026

Related records