Home / AI for HR / Policy Writing

Policy Writing: How to Write a Clear Workplace Policy, With the 8 Components and 6 Steps

Updated October 11, 2026.

What does policy writing mean?

Policy writing means deciding an organization's rule on a topic and putting it in a document people can follow and managers can enforce. The policy says what the rule is and why it exists. It should be broad enough that it does not need rewriting every time a form or system changes. That is why university policy offices such as Weill Cornell Medicine's and Boise State University's separate the policy from the procedure that carries it out.

Four kinds of document get called a policy, and policy writing goes faster once you know which one you are writing:

Definitions follow the distinctions drawn by Weill Cornell Medicine's Policy Writing 101 and The Write Direction's policy writing guidelines, listed under sources below.

Policy writing is not the same as a policy brief. A policy brief is a short paper that argues for a public policy choice to a government or advocacy audience, the kind of assignment the UNC Writing Center's handout covers. This HRStak guide is about the internal rules a company or institution writes for its own people.

The 8 main components of a policy document

Most policy templates use the same eight components, in this order, and this HRStak guide follows that core set; some templates, The Write Direction's among them, split the last row into three sections (related documents, revision history, approval authority) and count ten. The example lines come from a short remote work policy.

Bracketed values are placeholders to replace with your own. Leave out the definitions section only if no term in the policy could be read two ways.

Policy writing in 6 steps

The policy writing process below combines the draft to rollout sequences published by The Write Direction and PowerDMS into six steps that fit an HR team without a dedicated policy office. HRStak's policy tools help most at step 4; the other five steps are judgment work for people.

1. Name the problem and the owner. Write down why the company needs this policy now: a legal requirement, a risk, a recurring question, or a practice that differs from team to team. Name one owner who will answer questions and keep it current.
2. Research the rules and what you already have. List the laws and regulations that apply in every state or country where affected employees work, and collect any existing policies, emails, or habits that already set the rule. Summarize the legal requirement in your own words rather than pasting statute text.
3. Talk to the people who will follow it. Ask managers and a few employees how the work actually happens today. A policy that does not match practice gets ignored or enforced unevenly.
4. Draft from a standard template in plain language. Use the same eight components for every policy. Keep the policy to the rules and move step by step instructions into a separate procedure.
5. Review and approve. Send the draft to subject matter experts, to employment counsel for anything touching leave, pay, discipline, accommodation, or protected characteristics, and then to the leader with authority to approve it.
6. Publish, train, and schedule the review. Announce the policy, explain what changed, collect acknowledgments where needed, and set a review date at least once a year and whenever a law, an incident, or a practice changes.

Writing a procedure follows the same six steps with one addition PowerDMS recommends: after the first draft, ask a few employees to follow the steps exactly as written, and fix every place they get stuck or skip ahead.

Policy writing rules: the words that make a policy enforceable

Policy writing lives or dies on a handful of words. Boise State University's guidance and The Write Direction both set the same scale, and HRStak recommends adopting it across every policy you write:

• Must for an obligation. "Employees must report an injury the same day."
• Must not for a prohibition. "Employees must not share login credentials."
• May for a permission. "Employees may carry over up to [40] hours of PTO."
• Should for a recommendation. "Employees should request PTO two weeks ahead when they can."

Both sources advise replacing shall with one of those more precise words. Weill Cornell Medicine's guide still uses shall for an obligation. Either choice works if you define it once and never mix the two.

The rest of the policy writing rules that published policy guides agree on, in one list:

• Use active voice and present tense, and name who acts. "The department head must approve" beats "approval is required".
• Write in plain language for a reader with no policy expertise. Cut jargon, qualifiers, and phrases such as "in order to".
• Use gender-neutral wording: "they" or "the employee", "chair" rather than "chairman".
• Use one term for one thing across every policy. If it is "PTO" in the leave policy, it is not "vacation" in the remote work policy.
• Summarize the legal requirement in your own words and cite it. Do not paste statute text into the policy.
• Spell out an acronym the first time it appears.
• Avoid escape hatches such as "as appropriate" and "where reasonable". If a manager has discretion, say which manager and within what limits.

A before and after rewrite. Before: "It is the responsibility of all staff to ensure leave requests are submitted in a timely manner as appropriate." After: "Employees must request planned leave in [system] at least [10] working days before the first day off. Managers must approve or decline within [2] working days." The second version names who acts, what they do, and by when, so it can be followed and enforced.

Example of a business policy: a short remote work policy

Here is the remote work policy from the components table written out in full. HRStak's Remote or Hybrid Work Policy Writer drafts the same ground (eligibility, arrangements, equipment, security, expectations, exceptions) for an HR team to edit. It is an example to adapt, not legal advice; expense reimbursement and some notice rules depend on where the employee works.

Company policy examples come in five families, according to The Write Direction's list: HR and workplace (code of conduct, anti-harassment, attendance, leave, remote work), IT and security (acceptable use, bring your own device, passwords, data protection), finance and operations (travel and expense, procurement), health and safety (injury reporting, emergency response), and governance and ethics (conflicts of interest, whistleblowing, privacy). A small company usually writes the HR and workplace family first; HRStak's employee handbook template lists the 15 sections those policies usually sit in.

Common policy writing mistakes

The policy writing mistakes that published policy guides warn about are worth checking for in every draft, whether a person or a tool such as HRStak wrote it. Each comes with its fix:

• Mixing the rule with the steps. Move the steps into a procedure and link to it, so a new form does not force a policy rewrite.
• Copying legal text verbatim. Summarize the requirement and cite the source.
• Skipping definitions. If two managers could read a term differently, define it.
• Writing for lawyers instead of employees. Long, dense policies do not get read. Plain language does.
• Leaving out the people who follow it. A policy drafted without the teams it governs rarely matches how the work is done.
• No owner and no review date. Policies drift out of date quietly. Name an owner and set a date.
• Poor version control. Keep one live version, mark superseded copies clearly, and record each change.
• Enforcing it unevenly. A rule that applies to some teams and not others undermines every other policy.

Who should write company policies? Four options

Policy writing can be handed off in four ways. PowerDMS describes the first three; the fourth, an AI drafting tool such as HRStak, is the newer option and still depends on the reviewers named in the other three.

• An outside consultant. Brings specialist knowledge and finishes faster, at a higher cost.
• Leadership with legal counsel. Keeps the knowledge in house, but only works if the people who actually do the work are consulted.
• Accreditation or licensing body templates. Common in healthcare and law enforcement, where an accrediting body already publishes standards.
• An AI draft with human review. Fast for the first draft, but the tool does not know your locations, headcount, or practices, so HR checks every clause and counsel reviews anything touching leave, pay, discipline, or accommodation.

Can AI help with policy writing? Where HRStak fits

AI helps with the drafting part of policy writing, which is step 4 of the six. HRStak is an AI workspace for HR teams that assists with that step. It does not decide which laws apply to you, and it does not replace HR judgment or legal review. For the wider picture of which AI tools suit which HR jobs, see HRStak's overview of AI for HR teams.

• AI Usage Policy Generator (Essentials, $249 a month): drafts purpose, scope, acceptable and restricted use, data handling, approvals, and enforcement.
• Remote or Hybrid Work Policy Writer (Essentials, $249 a month): drafts eligibility, work arrangements, equipment, security, performance expectations, and exceptions.
• Employee Handbook Section Writer (Workspace, $599 a month): drafts one policy section at a time, such as PTO and leave, anti-harassment, dress code, social media, or drug policy, from the topic, state, and company size you choose, organized into purpose, scope and eligibility, policy details, procedures, exceptions, and state specific notes.
• Policy approval queue: saved handbook, AI usage, and remote work policy drafts can be submitted to a team admin, who approves or rejects them with a decision note before rollout.
• Internal Knowledge Base (Workspace, $599 a month): once a policy is approved and uploaded, answers questions from it and names the source file, so three people stop giving three different answers.

HRStak drafts in 7 languages and exports PDF and DOCX. All 81 tools are listed by category on the HRStak HR AI tools page, and HRStak's brand facts page summarizes what the product is and is not. If you are still choosing between a general chatbot and an HR-specific tool for policy drafts, HRStak's comparison of the best writing assistants for HR teams covers ChatGPT, Claude, Copilot, and five others. There is no free trial of the HRStak workspace.

Frequently asked questions