How English Works | The Policy

A policy is what an organisation writes when it does not want an important decision to depend entirely on whoever happens to be in the room.

Should staff retain student records?

Who may approve expenses?

What counts as acceptable conduct?

What information may be shared?

Which principles govern recruitment?

When must a conflict be declared?

Without policy, people answer these questions from memory, custom, preference or power.

With policy, the organisation attempts to make the decision boundary durable.

A policy is English that tries to make an organisational intention survive individual judgement.

That does not remove judgement.

It gives judgement a frame.

Quick Read

One-sentence answer: a policy works when it states an organisation’s durable intent, scope, principles, requirements, responsibilities and exceptions clearly enough that different people can make consistent decisions across time without needing the original policy-maker in the room.

The UK Green Book 2026 defines policy as a statement of intent implemented through a procedure or protocol and as a deliberate system of principles that guides decisions and achieves rational outcomes. It describes policy as providing enduring parameters for directing and controlling change.

A current 2026 Registers of Scotland disciplinary policy and procedure shows the common architecture in practice: purpose and scope, guiding principles, formal process, possible outcomes, support, roles and responsibilities, approval and review.

Those examples reveal the policy’s central components:

• purpose: why the policy exists;
• scope: who and what it applies to;
• principles: the values or standards guiding decisions;
• requirements: what must, must not or should happen;
• roles: who holds responsibility or authority;
• exceptions: when the normal rule does not apply and who may approve deviation;
• governance: approval, effective date, review and replacement.

Policy does not describe every move.
It defines the field inside which legitimate moves can occur.

The Policy Is Not the Procedure

Policy:

All assessment records must be stored in the approved central system and retained according to the organisation’s retention schedule.

Procedure:

1. Open the central assessment system.
2. Select the current class.
3. Upload the verified result file.
4. Confirm the import summary.
5. Record any rejected entries for correction.

The policy states what must be true.

The procedure explains how to make it true.

policy = enduring decision boundary
procedure = executable route inside that boundary

Conflating them creates brittle documents. If every click sequence is inside the policy, a software update may force the policy itself to be rewritten even though the underlying rule has not changed.

The Policy Is Not the Memo

A memo may announce that the policy changed.

The policy should remain the canonical source of the durable rule.

Memo:

The revised Data Retention Policy takes effect on 1 October.

Policy:

Assessment records must be retained for the periods defined in Schedule A and disposed of through the approved deletion process.

One communicates change.

One owns the rule.

Purpose Should Explain the Problem the Policy Exists to Control

Weak:

The purpose of this policy is to set out the policy.

Stronger:

This policy establishes how the organisation protects student assessment records from unauthorised access, inconsistent storage and premature deletion.

The reader now knows what failure the policy is designed to prevent.

Purpose is not ceremonial preface.

It is the policy’s reason for existing.

Scope Is the Boundary of the Rule

A policy can be perfectly clear and still fail if nobody knows whether it applies to them.

Scope answers:

• Which people?
• Which locations?
• Which systems?
• Which activities?
• Which records?
• Which time period?

Registers of Scotland’s 2026 policy documents begin with purpose and scope for exactly this reason.

Weak:

This policy applies to staff.

Which staff?

Permanent employees?

Contractors?

Volunteers?

External tutors?

Stronger:

This policy applies to employees, contracted teaching staff and temporary staff who create, access or manage student assessment records on behalf of the organisation.

Scope turns a general rule into a defined jurisdiction.

Definitions Prevent Policy from Splitting into Private Meanings

A policy may depend on words such as:

• record;
• confidential;
• authorised user;
• serious incident;
• working day;
• personal device.

If these terms are interpreted differently by different readers, the policy fragments.

Useful definition:

Assessment record: any digital or physical record that identifies a student and contains marks, grades, written feedback or assessment outcomes.

The definition is not there to make the policy sound formal.

It creates a shared local meaning boundary.

This connects directly to the Glossary article: policy language often needs a controlled vocabulary because enforcement becomes unstable when key terms drift.

“Must”, “Should” and “May” Are Different Governance Verbs

Policy English often relies on modal verbs.

Must normally signals a mandatory requirement.

Should often signals a strong expectation that can admit justified exceptions.

May can signal permission or discretion.

Example:

• Staff must store assessment records in the approved system.
• Managers should review access permissions each term.
• Department heads may approve temporary access for a defined project.

If writers use these words casually as synonyms, the policy loses its force map.

Modal verbs are tiny words carrying organisational authority.

Principles Explain How to Decide When the Rule Does Not Cover Every Case

Policies cannot predict every future circumstance.

That is why many policies include guiding principles.

For example:

• collect only what is necessary;
• limit access to legitimate operational need;
• retain records no longer than required;
• make decisions consistently and fairly;
• document material exceptions.

The principle gives decision-makers a compass when the exact case was not anticipated by the policy writer.

rule handles known cases
principle guides judgement at the edge

Roles and Responsibilities Prevent Everyone from Owning Nothing

Policies frequently fail through diffuse responsibility.

The organisation will ensure records are reviewed regularly.

Who inside the organisation?

Stronger:

• Policy owner: Head of Academic Operations
• System owner: IT Manager
• Local compliance: Level Coordinators
• Individual responsibility: Staff who create or access records

Registers of Scotland’s current policy architecture explicitly includes roles and responsibilities.

A role section turns an abstract organisational promise into distributed accountability.

Exceptions Need Authority, Reason and Trace

Weak exception language:

Exceptions may be allowed where appropriate.

Appropriate according to whom?

Stronger:

The Head of Academic Operations may approve a time-limited exception where the standard rule would prevent essential service delivery. The reason, duration and compensating controls must be recorded.

The exception now has:

• authority;
• condition;
• time limit;
• documentation.

Without these boundaries, “exception” can become a quiet route for the policy to stop meaning anything.

Compliance Language Should Say What Happens When the Policy Meets Reality

Some policies contain strong requirements but no explanation of how compliance is supported, observed or reviewed.

Useful governance language can explain:

• training requirements;
• periodic review;
• monitoring;
• audit;
• reporting of non-compliance;
• escalation;
• corrective action.

The policy does not need to reproduce every enforcement procedure.

It should make clear that the rule connects to an operating system rather than existing only as a PDF.

Approval, Effective Date and Review Make Policy Temporal

A policy is durable.

It is not timeless.

Useful document control can identify:

• policy owner;
• approving authority;
• approval date;
• effective date;
• version number;
• next review date;
• superseded version.

Registers of Scotland’s current policy architecture includes approval and review sections. This matters because organisational rules can become stale while continuing to look official.

Current policy is not merely the policy document you found. It is the version that still has authority now.

This connects policy directly to timestamp, filename and version discipline.

Review Dates Are Not Expiry Dates by Default

A policy saying:

Review date: September 2026

does not automatically mean:

This policy becomes invalid on 1 October.

Review and expiry are different states unless the governance model says otherwise.

Clear document-control language should distinguish:

• effective date;
• scheduled review;
• expiry;
• withdrawal;
• replacement.

Ambiguous lifecycle language can produce a dangerous state where some staff treat a policy as expired while others continue enforcing it.

Policy Hierarchy Prevents Two Rules from Being True at Once

Organisations can accumulate:

• laws and regulations;
• board-approved policies;
• department policies;
• procedures;
• memos;
• local working practices.

What happens when they conflict?

A department memo should not quietly override a higher-authority policy unless the governance system allows it.

A local procedure should not contradict a statutory requirement.

Good policy estates make the authority hierarchy visible.

higher authority → policy boundary → procedure → local execution

This helps readers know which document wins when instructions disagree.

A Policy Can Be Too Broad to Operate

Policy statement:

We are committed to excellence, fairness and safety in everything we do.

That may express values.

Can a manager use it to decide a difficult case?

Maybe not.

Operationally useful policy translates values into decision-relevant principles and requirements.

value → principle → requirement → procedure → observed behaviour

The policy should not become a motivational poster with a version number.

A Policy Can Also Be Too Detailed to Survive

The opposite failure is procedural overload.

A policy states:

Click the blue button in the upper-right corner, choose “Archive,” then select folder 2026-A.

Next month the interface changes.

The policy is now wrong even though the underlying rule still makes sense.

Durable policy should sit above volatile implementation detail where possible.

The more frequently a detail changes, the more carefully we should ask whether it belongs in policy at all.

Policy Must Be Findable at the Moment of Decision

A policy nobody can locate has weak practical authority.

Staff should be able to identify:

• the current title;
• the current version;
• the owner;
• the effective date;
• related procedures;
• where questions or exceptions go.

This is why a policy estate needs indexing, search, stable links and retirement of obsolete copies.

Policy quality includes retrieval quality.

Primary School: Turn a Value into a Rule

Young learners can practise policy thinking with a classroom value.

Value:

We respect shared books.

Policy-like rule:

Class library books must be returned to their labelled baskets after use. Damaged books should be given to the class librarian rather than returned to the shelf.

Ask:

• What value is the rule protecting?
• Who does it apply to?
• What must happen?
• What happens in the unusual case?

This teaches how broad values become stable group expectations.

Lower Secondary: Separate Policy from Procedure

Give students mixed statements:

• All laboratory visitors must wear approved eye protection.
• Collect goggles from the cabinet beside the entrance.
• Visitors may not enter restricted areas without a staff escort.
• Sign the visitor register before entering the laboratory.

Ask which statements are policy-like rules and which are procedure-like steps.

The exercise teaches level of abstraction.

Upper Secondary: Audit a Policy as a Decision System

• What problem is the policy designed to control?
• Who and what are in scope?
• Are important terms defined?
• Can I distinguish must, should and may?
• Do principles guide edge cases?
• Are responsibilities allocated?
• Are exceptions governed?
• Is the authority hierarchy clear?
• Is the current version identifiable?
• Does the policy contain volatile procedural detail that belongs elsewhere?

This turns policy reading into a lesson in modal language, classification, authority and institutional design.

Ten Failure Modes of Policy English

1. Purpose circularity. The policy exists “to set out the policy” without naming the problem it controls.
2. Scope ambiguity. People cannot tell whether the rule applies to them or their activity.
3. Definition drift. Key words such as “record,” “confidential” or “manager” mean different things to different readers.
4. Modal confusion. Must, should and may are used interchangeably.
5. Responsibility fog. “The organisation” is responsible but no role owns the work.
6. Exception loophole. Exceptions are allowed without authority, conditions, time limits or records.
7. Value-only policy. Broad aspirations never become decision-relevant requirements.
8. Procedure overload. Fast-changing operational steps are embedded in the durable policy layer.
9. Lifecycle ambiguity. Readers cannot tell which version is current, approved or due for review.
10. Policy-practice gap. The document states rules but no training, monitoring, escalation or linked procedure makes them operable.

How to Write a Better Policy

Start with the organisational decision problem.

1. Why does this policy need to exist?
2. Who and what are in scope?
3. Which terms need controlled definitions?
4. Which principles should guide judgement?
5. What is mandatory, recommended or permitted?
6. Who owns each responsibility?
7. How are exceptions authorised and recorded?
8. What procedure or protocol implements the policy?
9. Who approves the policy and when is it reviewed?

Then remove volatile operational detail that belongs in procedures. Make modal force consistent. Make hierarchy and lifecycle visible. Link the policy to the procedures, forms, standards or legislation it depends on.

Finally, perform the absent-manager test:

If the person who wrote this policy left tomorrow, could two competent readers still use the document to make broadly consistent decisions about the same difficult case?

The Deeper Idea: Policy Is Organisational Memory Written as a Boundary

People leave.

Teams reorganise.

Systems change.

New cases appear.

A policy attempts to preserve the organisation’s durable intent through that movement.

values → principles → policy boundary → procedures → decisions → behaviour

That is why policy writing belongs to how English works.

It is language used to make collective judgement less dependent on private memory and individual power.

Reader Checklist

• Why does this policy exist?
• Who and what are in scope?
• Which terms control meaning?
• Which statements are mandatory?
• Who owns responsibility?
• How are exceptions governed?
• What higher authority constrains the policy?
• Which procedures implement it?
• Is the version current and approved?
• Could different readers use it to make consistent decisions?

Related eduKateSG Reading

• How English Works | The Memo
• How English Works | The Brief
• How English Works | The Procedure
• How English Works | The Disclaimer
• How English Works | The Glossary

Research and Further Reading

• HM Treasury — The Green Book 2026
• Registers of Scotland — Disciplinary Policy and Procedure

Final idea: a policy is good when it remains stable enough to guide tomorrow’s unfamiliar case without becoming so vague that every reader can make it mean whatever they already wanted.