Writing FE Policies That People Actually Use

Too many provider policies are lengthy, complex documents that sit unread on a server. While created with good intentions, they fail their primary purpose: to guide practice. When policies are not used, you create risks of inconsistency, non-compliance, and confusion. This undermines the very quality you aim to assure.

The alternative is to treat policies not as static rules, but as live, practical tools that empower your colleagues. A well-written policy makes the right way of working the easiest way. Here is how to create policies that your teams will actually use.

Start with 'Why' and 'Who'

Before writing a single sentence, be clear on the policy's purpose and its audience. A policy that tries to be for everyone often ends up being useful to no one. Grounding it in a clear purpose makes it relevant and easier to understand.

• State the core purpose: Begin with a simple statement explaining what the policy is for. What problem does it solve, or what core principle does it uphold? For example, "This policy ensures all learners and apprentices receive fair, valid, and reliable assessment."
• Define your audience: Is this policy primarily for tutors, assessors, support staff, or managers? Write in language they understand, addressing their specific roles and responsibilities.
• Use plain English: Avoid overly formal or legalistic language unless absolutely necessary. The goal is clarity, not to prove your command of jargon. A clear policy is a strong policy.

Focus on Actions, Not Just Rules

Effective policies translate principles into expected behaviours. Staff should be able to read a policy and know exactly what they are expected to do. This shifts the document from a theoretical statement to a practical guide for daily work.

• Use active verbs and assign roles: Instead of passive phrases like, "Consideration should be given to...", be direct: "The assessor must..." or "The curriculum lead is responsible for...". This removes ambiguity.
• Structure processes as steps: For multi-stage processes like handling a learner complaint or an assessment appeal, use a simple, numbered list. This makes the process easy to follow and audit.
• Use visuals for complexity: A flowchart can explain a complex decision-making path - such as your procedure for investigating academic malpractice - far more clearly than a dense paragraph of text.

Separate Policy from Procedure

A common mistake is to merge the high-level rules with the detailed, step-by-step instructions. This makes policies long and difficult to navigate. Separating them makes your entire framework more agile and user-friendly.

• Policy = What and Why: The policy document itself should be concise. It should state the guiding principles, mandatory rules, and key responsibilities.
• Procedure = How: The detailed, step-by-step instructions for carrying out the policy should live in a separate document, such as a standard operating procedure (SOP), user guide, or checklist.
• Link, don't embed: In the main policy document, simply link out to the relevant procedures, forms, and guidance. This makes the policy easier to digest and allows you to update a specific procedure without needing to put the entire policy through a full re-approval process.

Build in Review and Feedback

Policies should not be 'fire and forget' documents. They are part of your continuous improvement cycle and must be tested against the reality of day-to-day operations. An effective review process ensures they remain fit for purpose.

• Assign ownership and a review date: Every policy must have a named owner and a scheduled review date. This ensures accountability.
• Consult the users: When reviewing a policy, don't just check it against regulations. Talk to the staff who use it. Ask them: Is this clear? Is it practical? Where does it cause problems? Their feedback is essential for improvement.
• Use your QA findings: Your quality assurance activities - such as thematic reviews, work scrutiny, or internal audits - will reveal where practice differs from policy. Use these findings to identify where a policy may be unclear, impractical, or simply wrong.

Where this fits in QualityHero

Well-defined policies form the bedrock of a robust quality system. The QualityHero Toolkit Areas module allows you to store, version-control, and link your policies directly to the relevant quality standards, procedures, and evidence. This creates a single source of truth, ensuring your team can always access the definitive, up-to-date guidance for their practice.