What Is an HR SOP? A Practical Guide to Writing HR SOPs

An HR SOP (Standard Operating Procedure) is a document that clearly sets out how many steps each HR task involves, who handles each step, which forms to use, and when the task must be completed—from onboarding new employees and approving leave requests to closing payroll and processing employee exits. Put simply, if the HR person responsible for a task is away for three days and someone else can pick up the SOP and complete it without having to call and ask questions, the SOP works.

 

 

Why Does an HR Team Need SOPs?

The main reason is not to make documents look polished, but to manage hidden risks  such as:

1. Reduce reliance on one person: Many organizations have only one person who “knows how to close payroll.” If that person leaves, the knowledge leaves with them. An SOP transfers that knowledge from one person’s head onto paper.
2. Reduce errors that lead to penalties: HR work is tied to many government deadlines, such as submitting Social Security contributions by the 15th of the following month or filing P.N.D.1 by the 7th of the following month. Missing a deadline by even one day can result in surcharges or monthly penalties. An SOP with clearly stated dates helps prevent these mistakes.
3. Help new employees become productive faster: New HR staff can read and follow the SOP without waiting for a mentor to become available.
4. Create an audit trail: When a labor dispute arises or evidence is requested under the PDPA, an SOP that specifies who may access which information can be invaluable (see What HR Needs to Know About the PDPA for more information).
5. Lay the foundation for digital HR: If you do not yet understand your own processes, adopting a system will simply move the confusion from paper to a screen.

 

What Should an HR SOP Include?

A good SOP does not have to be long, but it should cover all eight elements below. If any are missing, people will probably still need to ask HR for clarification.

 

 

How to Write an HR SOP in 7 Steps

1. Capture the actual process, not the ideal one: Observe someone completing the task once and note everything they do, including any shortcuts. Shortcuts often reveal where the existing process has problems.

2. Map the flow before writing the instructions: Draw a flow showing who starts the process, who it passes through, and who completes it. Bottlenecks will become immediately visible.

3. Remove steps that add no value: If no one uses the output of a step, remove it before documenting the process. Do not create an SOP for work that should not exist in the first place.

4. Use direct instructions—one step, one action: “HR verifies that all documents are complete within one business day” is better than “Documents are reviewed as appropriate.”

5. Include deadlines and decision conditions: Every step should answer two questions: When must it be completed, and what happens if it does not pass?

6. Test it with someone who has never performed the task: Ask someone outside the team to follow the SOP. If they need to ask more than two questions, the instructions are not yet clear enough.

7. Assign an owner and a review cycle: Name the person responsible and review the SOP at least once a year, or whenever laws or systems change.

 

SOP Example: Leave Request and Approval Process

HR-SOP-002 | Objective: To standardize leave requests and approvals, maintain an audit trail, and deduct leave entitlements correctly before payroll closes.

 

 

For statutory leave entitlements and conditions, refer to the Labour Protection Act B.E. 2541 (1998) issued by the Department of Labour Protection and Welfare. If your organization still keeps records in files, download the Excel Employee Leave Tracking Template to get started.

 

SOP Example: Monthly Payroll Closing

A calendar-based SOP is more suitable for payroll closing than a step-by-step format because every activity is tied to a date.

 

 

The deadlines in the final three rows are the heart of this SOP. They are based on information from the Revenue Department and the Social Security Office and should be reviewed by the team at the start of each year in case new announcements have been issued.

 

For a detailed overview of the payroll-closing process, continue reading >> Complete Monthly Payroll Process

 

Summary: How to Write an HR SOP That Works

An HR SOP turns knowledge held in one person’s head into a process that anyone can follow and achieve the same result. It is not created simply to add another document; it keeps work moving when someone is absent and prevents missed deadlines that could lead to penalties. The best SOP is one that no one has to memorize because the system guides the process automatically—from submitting requests and obtaining approvals to deducting entitlements and calculating payroll.

 

FAQ: Frequently Asked Questions About HR SOPs

Q: What is the difference between an SOP and a Work Instruction?

A: An SOP provides an overview of a process, including the number of steps and who is responsible for each one. A Work Instruction is a more detailed guide explaining which buttons to click and which fields to complete. In practice, small organizations can often combine both in one document by adding screenshots at the end of the SOP.

 

Q: Does a small company with 15 employees need HR SOPs?

A: Yes—and they are often even more important for a small company. Small businesses frequently have just one HR person who knows how everything works. If that person is absent or leaves the company, work may stop immediately. Start with SOPs for three areas: payroll closing, leave approval, and new-employee onboarding.

 

Q: Are HR SOPs legally required?

A: No law directly requires organizations to create SOPs. However, Section 108 of the Labour Protection Act B.E. 2541 (1998) requires employers with 10 or more employees to establish work rules in Thai and make them known to employees.

 

Q: How often should HR SOPs be reviewed?

A: At least once a year, and immediately when any of three events occurs: laws or contribution rates change, the organization changes its system or team structure, or the same process error recurs. Whenever an SOP is revised, always update its version number and date.

 

Q: Should an SOP be stored as a Word file or built into a system?

A: Keep the original file for reference and approval signatures. However, frequently repeated processes such as leave requests and approvals should also be configured as workflows in the HR system. The system can enforce the sequence and retain evidence automatically, reducing reliance on people remembering the SOP.

 

Q: Who should own an HR SOP?

A: Each SOP should name a specific owner rather than simply stating “HR Department.” Generally, the person who performs the task regularly drafts the SOP and maintains its content, while the Head of HR approves it and controls its versions. This makes it clear whom to contact when something changes.

 

Read more related articles 

• A Beginner’s Guide to HR: Essential Formulas Every HR Professional Should Know 
• Free HR Planner Template for Accurate Monthly Work Planning 
• Individual Employee Development Planning Techniques for HR 
• What Does HR Need to Know About the PDPA? A Complete Checklist