Intellectual Frontiers

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 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 bundle

A role branches into tasks, decisions, authority, evidence, credentials, liability, and outcomes.

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 carries

A credential can bundle tested capability, authority, privilege, supervision, trust, accountability, and liability.

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 work

A sound redesign separates the party creating or controlling risk from the party merely financing loss.

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 exists

A work unit may serve the outcome or arise from safety, law, payment, contract, coordination, information failure, or habit.

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.

Table 1. Work disposition and proof
Disposition Use when Evidence needed

Retain with a person

Judgment, authority, trust, presence, or learning changes the result

Outcome and capability evidence

Assist

Preparation can move while a person keeps the decision

Review burden and error record

Automate

Work is bounded, observable, reversible, and testable

Accepted outcomes under live conditions

Redesign or remove

The burden comes from an avoidable rule or broken exchange

Cause, authority, and system effect

Keep bundled

Separation creates legal, safety, or accountability gaps

Qualified review and failure analysis