eduKate SG

Three learners review open books together at a classroom table, with stacks of textbooks, stationery and a whiteboard in the bright room.

How to Categorise Obligations | Source, Subject, Action, Deadline, Condition, Enforcement and Discharge

An obligation is a recognised duty requiring a person, role, organisation or system to act, refrain from acting, deliver something or maintain a condition.

Obligations can come from law, contract, role, promise, policy, ownership, professional standards or accepted responsibility. They differ in who owes the duty, to whom, what must be done, when it must be done, what evidence proves fulfilment, and what happens if the duty is not met.

Quick answer: how should obligations be categorised?

  • Source: law, contract, role, promise, policy, ownership or professional duty?
  • Subject: who owes the obligation?
  • Beneficiary: to whom or what is the duty owed?
  • Action: perform, deliver, pay, disclose, protect, refrain or maintain?
  • Condition: unconditional or triggered by an event?
  • Deadline: immediate, periodic, dated or open-ended?
  • Priority: which obligations take precedence when duties conflict?
  • Enforcement: legal, contractual, organisational, professional or social?
  • Evidence: what demonstrates fulfilment?
  • Discharge: completion, expiry, waiver, transfer, impossibility or supersession?

This page complements How to Categorise Rules, How to Categorise Roles and How to Categorise Requirements. Rules and roles can generate obligations; requirements describe conditions an acceptable solution must satisfy.

Obligation is not permission

A permission says an action is allowed. An obligation says an action or restraint is required.

Obligation is not goal

A goal is desired. An obligation binds whether or not the subject personally prefers the outcome.

Obligation is not responsibility

Responsibility is a broader role relation. An obligation is a specific duty within that responsibility structure.

Legal obligations derive from law

Statutes, regulations, court orders and licences can create duties that apply within a jurisdiction.

Contractual obligations derive from agreement

Payment, delivery, confidentiality and service commitments may be binding because parties agreed to them.

Role obligations derive from office

Teachers, directors, custodians and reviewers can inherit duties because they occupy a recognised role.

Professional obligations arise from standards of practice

Competence, confidentiality, disclosure and duty of care may attach to professional roles even when every detail is not written into one contract.

Ownership obligations accompany rights

Maintenance, conservation, safety, privacy and tax duties can accompany ownership of assets or information.

Positive obligations require action

Deliver, pay, report, maintain and provide are positive duties.

Negative obligations require restraint

Do not disclose, do not discriminate, do not exceed a safety limit and do not alter a protected record are obligations to refrain.

Continuous obligations remain active

Confidentiality, monitoring and maintenance may persist over a period rather than being completed by one event.

Periodic obligations recur

Annual reporting, monthly payment and scheduled inspection require repeated fulfilment.

Conditional obligations activate on triggers

Notification after an incident, payment after delivery and review after a threshold crossing depend on defined events.

Time-critical obligations need exact deadlines

“Promptly” and “as soon as possible” may be inadequate when consequence matters. Precise deadlines improve accountability.

Priority matters when obligations conflict

Safety, law, privacy, contractual duty and operational continuity can pull in different directions. Precedence should come from governing authority, not convenience.

Non-delegable obligations stay with the original subject

Some duties may be performed with help but accountability remains with the original holder.

Delegable obligations require transfer rules

Assignment should state whether both performance and accountability transfer, or only execution.

Joint obligations require coordination

Several parties can owe the same duty together, separately, or in defined shares. Classification should preserve that structure.

Evidence of fulfilment should be defined

Receipt, signed approval, test result, delivered output, audit log or completed inspection can provide proof that the duty was met.

Attempted performance is not always discharge

An attempted payment, notification or repair may fail. The obligation remains until the required state is actually achieved or another valid discharge condition applies.

Waiver can remove an obligation

Only an authority entitled to waive the duty should do so, and the scope and duration of the waiver should be explicit.

Expiry can end an obligation

Some duties end after a date, role termination, contract completion or statutory period.

Supersession replaces an obligation

A new rule, contract or requirement can replace an earlier duty. Preserve lineage so historical compliance remains interpretable.

Impossibility should not be assumed casually

An obligation can become difficult without becoming discharged. Where impossibility matters, classification should preserve the governing rule and evidence.

Breach is a state, not an obligation type

An obligation can be pending, fulfilled, overdue, breached, waived, expired or disputed. Lifecycle state should be tracked separately from source and content.

AI agents can create operational obligations

When an automated system accepts a task, triggers a workflow or sends a commitment on behalf of an organisation, responsibility for fulfilment should remain traceable to authorised human or institutional ownership.

A practical obligation record

  • obligation ID;
  • source and authority;
  • subject owing the duty;
  • beneficiary;
  • required action or restraint;
  • conditions and triggers;
  • deadline or recurrence;
  • priority and precedence;
  • delegation rules;
  • evidence required;
  • enforcement route;
  • status;
  • discharge condition;
  • review or dispute state;
  • version.

The deeper idea

Obligations turn rules, roles and promises into accountable future action. Their value depends on knowing exactly who owes what, to whom, by when and what counts as done.

To categorise an obligation well is to preserve its source, subject, beneficiary, required action, deadline, evidence of fulfilment and the conditions under which the duty ends.

Final answer

Categorise obligations by source, subject, beneficiary, action, condition, deadline, priority, enforcement, evidence and discharge. Keep obligations separate from permissions and goals, track lifecycle state explicitly, and do not treat attempted performance as completed duty without evidence of the required outcome.

Continue through the series

Explore the connected learning guides

Choose the question that brought you here. Open one useful guide, try a small task, and stop when you have what you need.

Take one question further

The same learning habit can travel across subjects, while each subject keeps its own methods. These routes help you notice a difficulty, understand one part of it, and return to something you can do.

A word is familiar, but using it is difficult.

Move from recognising a word to retrieving it in a new context. Understand vocabulary plateaus.

Try it without the guide: Choose one word you already know. Close the guide and use it in a new sentence. Explain why it fits; try another context tomorrow.

A piece of writing has ideas, but the reader loses the thread.

Make the order of events and the links between sentences clear. Explore composition writing.

Try it without the guide: Choose one short paragraph. Read the relevant explanation, close it, and revise the paragraph. Ask someone to tell you what happened and why.

The Mathematics seems familiar, but marks still disappear.

Find the first point where the working stops being reliable. Find Secondary 4 A-Math mark leakage.

Try it without the guide: For a Secondary 4 A-Math question you have attempted, locate the first uncertain line. Repair that step, then try a comparable question without the worked answer.

A Science fact is remembered, but the explanation is incomplete.

Connect the evidence to a scientific idea and the resulting change. Follow the Primary Science learning route.

Try it without the guide: Choose a familiar Primary Science example. Explain the evidence, the idea and the result without notes. Then change one condition and explain your prediction.

Two accounts of the world seem to disagree.

Check the question, source, date and evidence before combining claims. Explore the World Knowledge research library.

Try it without the guide: Take one claim. Find the source best placed to support it, note its date, and state what remains uncertain. Return to your original question.

There is plenty of help, but independence is hard to see.

Check what the learner can understand and do after support is removed. Understand how education works.

Try it without the guide: Choose one small task the child has practised. Agree on a calm, brief attempt without prompts. Use what happens to choose one next step, then stop.

For the structure behind these connections, read the eduKateSingapore runtime manifest and the eduKate ecosystem boot contract. The reader map describes public navigation; those manifests preserve the wider ownership and return rules.