A policy, a procedure and a guideline are three different documents

Three words that are not synonyms

Being told that something is “our policy” covers an enormous range of situations, from a rule that nobody in the organisation may set aside to a suggestion written years ago by a team that no longer exists. The word does a lot of work in conversation and rather less in the document library, where policy, procedure and guideline occupy distinct positions.

The distinction is worth knowing because it predicts flexibility. Some documents describe what must be achieved, some describe exactly how to achieve it, and some describe what usually works. Departing from the third is routine, departing from the second is a decision, and departing from the first is normally not available to anybody you are speaking to.

Policy states a position and rarely says how

A policy is a short statement of what the organisation requires or forbids, and the good ones are deliberately brief. They set out scope, principle and responsibility, and they avoid detail, because detail dates faster than principle and every change to the document costs an approval cycle.

Policies are approved at a senior level, reviewed on a fixed cycle and versioned carefully, which is why the machinery around them looks disproportionate to their length. A two-page document can take months to change. That’s also why a policy statement is so often unhelpfully general when quoted at a counter: generality is the point of the format, and the specifics were never in it.

Procedure is the operational version, and it is where the detail lives

A procedure translates a policy into steps: who does what, in what order, using which system, with which checks. It is the document staff actually work from, it changes far more often than the policy above it, and it is usually owned by the team that performs the work rather than by the executive.

Because procedures encode the how, they can be departed from where the policy is still satisfied — but that departure normally has to be authorised and recorded, since the procedure exists partly to guarantee consistency. This is the layer where most of the answers you actually want live, and it is also the layer least likely to be published, because it is written for people who already know the internal vocabulary.

A guideline is advisory, and the word is chosen carefully

Guidance sits below both. It suggests, illustrates and gives worked examples, and it is written to help somebody exercise judgement rather than to remove the judgement. The choice of the word is deliberate: calling a document a guideline is a statement that departure is permitted where circumstances warrant it.

In practice guidance is quietly treated as more binding than its status implies, because following it is safe and departing from it invites the question of why. That gap between formal status and practical weight is a real feature of how organisations behave, and it explains the answer that something is not compulsory but is nevertheless what will happen.

The hierarchy is what makes exceptions possible

Layering exists so that the organisation can change how it works without renegotiating what it stands for. A procedure can be rewritten in a week when a system changes, and the policy above it remains true. It also means an exception can be considered against the right test: does this depart from the method, or from the requirement?

That question is genuinely the crux of most requests for flexibility. A departure from method is often approvable within the department, because the outcome the policy demands is still achieved by another route. A departure from the requirement itself is a different animal entirely, and it usually has to travel much further up before anybody can say yes.

Asking about the right document

When told that something cannot be done because of policy, the useful and entirely reasonable question is whether that is a policy requirement or the procedure for meeting it. Staff can generally answer, and the answer determines whether an alternative route is even conceivable.

It is also worth asking whether the document is published, since many organisations publish policies while keeping procedures internal, and the published version may show what the requirement actually is rather than how one team implements it. None of this is a substitute for advice where something significant turns on it, and the layering itself varies between organisations. But knowing that the three words are not interchangeable turns a flat refusal into a question with a location.