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 Commitments | Promise, Contract, Plan, Deadline, Dependency, Evidence and Status

A commitment is a declared future obligation or intention that creates an expectation of follow-through.

Promises, contracts, delivery dates, public pledges, project milestones, service-level commitments and personal undertakings all create expectations about future action. They differ in how binding they are, who relies on them, what evidence supports them and what happens when they change.

Quick answer: how should commitments be categorised?

  • Source: promise, contract, policy, plan, role or public statement?
  • Subject: who is making the commitment?
  • Beneficiary: who relies on it?
  • Content: what action, outcome or resource is promised?
  • Deadline: when is fulfilment due?
  • Dependency: what must happen first?
  • Evidence: what proves the commitment exists and is fulfilled?
  • Reversibility: can it be withdrawn, renegotiated or deferred?
  • Status: proposed, accepted, active, fulfilled, overdue, changed, cancelled or breached?
  • Consequence: what happens if it is not met?

This page complements How to Categorise Obligations, How to Categorise Goals and How to Categorise Tasks. A commitment can generate obligations, support a goal and be discharged through tasks, but those are different objects.

Commitment is not intention

An intention can remain private and tentative. A commitment creates a stronger expectation because it has been declared, accepted or relied upon.

Commitment is not goal

A goal describes a desired future. A commitment specifies what someone or something has undertaken to do about that future.

Commitment is not task

Tasks are units of work. A commitment may require many tasks and can remain active even when one task is completed.

Personal commitments are self-declared

They may be morally or socially significant even without formal enforcement.

Contractual commitments are formally binding

Delivery, payment, confidentiality and service levels can become enforceable because parties agree to defined terms.

Organisational commitments create institutional expectations

Budgets, roadmaps, launch dates, public targets and service promises can create reliance across teams and stakeholders.

Public commitments create reputational stakes

When a commitment is announced publicly, failure can affect trust even when formal legal enforcement is limited.

Conditional commitments depend on stated events

“We will proceed if funding is approved” is materially different from an unconditional promise.

Unconditional commitments imply stronger obligation

They should be made only when the subject is prepared to bear the consequences of non-performance or renegotiation.

Time-bounded commitments need deadlines

A delivery promise without a date can remain perpetually ambiguous. Exact timing improves accountability and coordination.

Recurring commitments repeat

Monthly reporting, annual reviews and continuing service obligations should be represented as recurring rather than repeatedly recreated.

Milestone commitments divide long work

Intermediate checkpoints can make progress measurable and reveal delay earlier than one distant final deadline.

Dependencies change commitment risk

A promise relying on several external approvals, suppliers or technical conditions is more fragile than one controlled entirely by the committing party.

Capacity should be checked before commitment

Overcommitment occurs when promises exceed time, money, capability or attention. Classification should preserve resource assumptions where they are material.

Evidence of commitment matters

Signed contracts, approved plans, emails, meeting records, public statements and system receipts provide different strengths of evidence that a commitment was actually made.

Acceptance can change status

A proposed commitment becomes stronger when another party accepts, relies on or acts upon it.

Commitments can be amended

Scope, deadline, quantity or conditions may change through governed renegotiation. Preserve the original version and the reason for change.

Commitments can be deferred

Deferral moves timing without necessarily cancelling the obligation. The new date and approval should be explicit.

Commitments can be cancelled

Cancellation should identify authority, notification, residual obligations and consequences for parties that relied on the commitment.

Fulfilment requires evidence of outcome

Sending a task or initiating a process does not necessarily prove the promised result was delivered.

Partial fulfilment needs its own state

Delivering part of a promised quantity or only some required conditions should not be collapsed into fulfilled or failed.

Overdue is not the same as breached

A commitment can pass a target date while remaining recoverable under grace periods, extensions or revised agreements. Breach depends on the governing terms.

Broken commitments create downstream effects

Others may have scheduled work, spent money or made promises of their own based on the original commitment. Dependency chains therefore matter.

Commitment portfolios expose overload

One promise may look feasible in isolation while the full set of active commitments exceeds capacity. Aggregate review prevents local optimism from becoming systemic failure.

Priority should influence renegotiation

When capacity falls, commitments should not be changed arbitrarily. Safety, legal duties, dependency impact and strategic value can guide which promises must be preserved first.

Commitment histories should remain auditable

Do not overwrite old dates or scopes. Preserve who committed to what, which assumptions existed and how the commitment changed.

AI agents need authority before making commitments

A system that can send or publish text should not automatically be allowed to promise delivery, spend money or bind an organisation. Commitment-making authority should be explicit.

A practical commitment record

  • commitment ID;
  • source and type;
  • committing subject;
  • beneficiary or relying parties;
  • promised action or outcome;
  • conditions;
  • deadline or recurrence;
  • dependencies;
  • resource assumptions;
  • evidence of acceptance;
  • status;
  • fulfilment evidence;
  • amendment or cancellation authority;
  • consequences of non-performance;
  • version history.

The deeper idea

Commitments are promises projected into the future. They coordinate action by giving other people and systems something stable enough to plan around.

To categorise a commitment well is to preserve who promised what, to whom, by when, under which conditions, what the promise depends on, and what evidence proves that it was fulfilled or changed.

Final answer

Categorise commitments by source, subject, beneficiary, promised outcome, deadline, conditions, dependencies, evidence, reversibility, status and consequence. Keep commitments separate from goals and tasks, version amendments honestly, and require evidence of the promised outcome before marking fulfilment complete.

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.