eduKate Singapore

How to Categorise Roles | Function, Authority, Responsibility, Capability, Scope and Accountability

A role is a defined pattern of responsibility, authority and expected behaviour attached to a person, team, system or institution.

Teacher, reviewer, owner, operator, approver, custodian, parent, regulator, supplier and learner are all roles. The same person can hold several roles, and the same role can be held by several people. Good categorisation therefore separates role from identity.

Quick answer: how should roles be categorised?

  • Function: what job does the role perform?
  • Authority: what can the role decide, approve or change?
  • Responsibility: what outcomes or tasks must it deliver?
  • Capability: what knowledge, skill or access is required?
  • Scope: where does the role apply?
  • Accountability: who reviews the role’s performance?
  • Duration: permanent, temporary, acting or event-specific?
  • Relationships: who does the role supervise, serve, depend on or report to?
  • Handoffs: what work enters and leaves the role?
  • Conflict: which roles should remain separate?

This article extends How to Categorise Organisations and How to Categorise Relationships by treating roles as first-class structures inside systems.

Role is not identity

A person may be a teacher, parent, manager and reviewer in different contexts. The person persists while roles can begin, end or overlap.

Role is not title

Titles are labels. Roles are defined by actual function, authority, responsibility and relationships. Two people with the same title may perform different roles in practice.

Role is not task

A task is a unit of work. A role is the durable responsibility pattern that determines which tasks a holder is expected or authorised to perform.

Functional roles describe contribution

Designer, analyst, teacher, operator and maintainer are primarily distinguished by what they contribute to a system or process.

Decision roles describe authority

Approver, signatory, regulator and owner can accept, reject, allocate or change something within a defined scope.

Custodial roles preserve assets or records

Custodians, archivists and data stewards may not own what they protect. Custody, ownership and control should remain distinct.

Advisory roles influence without final authority

Experts, consultants and reviewers may provide evidence or recommendations while leaving the final decision to another role.

Execution roles perform authorised action

Operators and implementers may have permission to execute a decision without holding authority to redefine the policy or objective.

Oversight roles monitor other roles

Auditors, examiners, boards and supervisors exist partly to check whether another actor is meeting a standard, rule or obligation.

Service roles face recipients

Teachers, clinicians, support staff and public-service officers may be defined partly by the users or communities they serve.

Authority should be explicit

A role can read, recommend, create, approve, publish, allocate, revoke or delete. These permissions should not be inferred from title alone.

Responsibility should be outcome-linked

“Responsible for quality” is vague. Better role definitions specify which outputs, thresholds or outcomes the holder must protect.

Accountability is the return path

Responsibility states what must be done. Accountability identifies who must answer for whether it was done appropriately.

Capability requirements should travel with the role

Credentials, experience, training, system access and judgement may be prerequisites for competent role performance.

Scope limits authority

An approver for one project may have no authority over another. Geographic, organisational, financial and temporal boundaries should be explicit.

Temporary roles need expiry

Acting, emergency and project-specific roles should state when authority begins and ends so temporary power does not become permanent by accident.

Role combinations can create conflict

The same person may be able to create and review work, but in high-stakes settings independent review can be stronger when producer and approver are separate.

Segregation of duties is a role-design tool

Separating creation, approval, payment, audit or deletion reduces the chance that one unchecked actor can create and conceal a harmful action.

Role overlap can be useful

Small teams often combine roles for efficiency. The key is to make the overlap visible and add stronger checks where consequences justify them.

Handoffs define interfaces between roles

A role should know what inputs it receives, what evidence accompanies them, what output it produces and who receives that output next.

Role dependencies reveal bottlenecks

If many workflows depend on one specialist role, that role may become a capacity constraint or single point of failure.

Substitution matters

A role can be unique, pooled, delegated or backed up. This affects continuity when the primary holder is unavailable.

Delegation transfers action, not always accountability

A manager may delegate a task while remaining accountable for the outcome. Role classification should therefore distinguish delegated authority from retained accountability.

Human and machine roles can coexist

Automated systems may classify, route or monitor, while humans retain approval, exception handling or accountability. Treat tool capability and governance authority as separate dimensions.

Role drift creates hidden risk

Over time, people often take on informal duties that are absent from formal role descriptions. Periodic review should compare actual work with intended authority and responsibility.

A practical role record

  • role ID and name;
  • function;
  • responsibilities;
  • authority and permissions;
  • required capabilities;
  • scope;
  • accountability route;
  • relationships and dependencies;
  • handoffs;
  • conflicts of interest;
  • delegation rules;
  • backup or substitute roles;
  • effective dates;
  • version.

The deeper idea

Roles turn organisations from collections of people into structures of responsibility and authority. They explain who may act, who must act, and who answers when action succeeds or fails.

To categorise a role well is to preserve what function it serves, what authority it holds, what responsibility it carries, where that authority stops and who remains accountable for the result.

Final answer

Categorise roles by function, authority, responsibility, capability, scope, accountability, duration, relationships and handoffs. Keep role separate from identity and title, make conflicts and delegation explicit, and design backup or review structures where one role would otherwise become a single point of failure.

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.