How to Write a Standard SOP: 15 Steps to Create Standard Operating Procedures for Your Business

According to surveys by many internal management organizations, over 60% of operational errors in small and medium-sized enterprises in Vietnam come from the lack of a clear standard SOP process. Employees work in their own ways, information handover is insufficient, and work depends on individuals instead of the system – and that's when the business starts to "lose control."

If you are looking for how to write a standard SOP, how to build a professional SOP, or want to know how to create a standard workflow from scratch, this article will help you understand quickly and apply it immediately.

In fact, writing SOP (Standard Operating Procedure) is not as complicated as many people think. In essence, it is simply a clear, step-by-step guide that allows anyone to perform a task correctly without relying on previous employees. You can modify existing SOPs or create new ones from scratch – the important thing is to follow the correct structure and systematic thinking.

In this article, you will be guided on how to write a standard SOP that is easy to understand, easy to implement, and suitable for the Vietnamese business environment – helping to save time, reduce errors, and improve work efficiency starting today.

Part 1: How to format a standard SOP for readability and ease of application

Step 1: How to choose an effective SOP writing format

1. Prioritize using existing SOP templates within the company

• Check if the company already has a standard process template.

• Refer to the presentation style: layout, step numbering, safety notes.

• Reusing the old structure helps ensure consistency and easy management of internal documents.

• Consistent formatting helps employees read and apply standard workflows faster, reducing confusion.

If there is no standard template yet, you can choose one of the three common formats below.

2. Simple Steps Format

Suitable when:

• The process is short, under 10 steps.

• Few contingencies arise.

• There are not many decision branches.

Presentation method:

• List each step in order 1–2–3.

• Each step is written concisely, clearly, focusing on action.

• Add safety notes or related documents if necessary.

This is the simplest and easiest way to write an SOP, especially suitable for daily repetitive tasks such as data entry, customer service, and order processing.

3. Hierarchical Steps Format

Suitable when:

• The process is long, over 10 steps.

• There are many decisions or branching conditions.

• Detailed explanations of terms or instructions are needed.

Presentation method:

• Main steps are numbered largely (1, 2, 3...).

• Sub-steps are numbered hierarchically (1.1, 1.2, 1.3...).

• Arranged in mandatory execution order.

This format is often used in business operating procedures, new employee training, or internal control procedures that require high accuracy.

4. Flowchart Format

Suitable when:

• The process has many different possible outcomes.

• Results are not fixed.

• There are many "If... then..." decision points.

Application method:

• Use a diagram with decision nodes.

• Clearly show the direction of each situation.

• Combine with detailed explanatory documents if needed.

This is a suitable choice for incident handling procedures, multi-level approval processes, or customer service scenarios with multiple scripts.

Step 2: How to identify the audience when writing an SOP

1. Reader's education level and background knowledge

• Is the reader familiar with the organization and internal processes?

• Do they understand the specialized terminology being used?

• Are they new hires, long-term employees, or managers?

Practical application:

• If writing for new employees, explain terms clearly and avoid using obscure acronyms.

• If writing for a highly specialized team, internal terminology can be used but still needs to be consistent.

• Always ask: "Can the reader perform the task correctly just by reading this document?"

In my experience implementing SOP development for SMEs, I found that over 40% of SOPs are difficult to apply because they are written from the perspective of the author, not the executor.

2. Language proficiency of SOP users

In manufacturing, logistics, or multinational enterprises, there may be personnel who:

• Are not fluent in Vietnamese

• Have limited reading comprehension

• Prefer to receive information visually

Practical solutions:

• Use short, clear sentences.

• Avoid long, complex sentences.

• Add illustrative images, diagrams, and intuitive annotated photos.

• If necessary, use prominent icons or numbered steps.

A professional SOP template is not just a document, but a guide that can be "looked at and acted upon."

3. Number and roles of participants in the process

If an operating procedure involves only one person, you can write it as a series of continuous steps. But if multiple departments are involved, the presentation needs to be different.

Optimal approach for multiple roles:

• Clearly divide roles: Employee A, Manager B, Department C.

• Present in the chronological order of each person's actions.

• Can be written in a dialogue-like process:

  • Step 1: Sales department receives the request.

  • Step 2: Technical department confirms the information.

  • Step 3: Accounting proceeds to issue the invoice.

This helps each individual clearly see their responsibilities within the entire standard SOP process, avoiding the situation where "it's everyone's job but no one takes responsibility."

Step 3: Assess competence before writing SOPs

1. Do you understand the entire process from start to finish?

• Do you know each step of the implementation?

• Do you know where the process usually goes wrong?

• Do you understand the safety risks or potential errors that can occur?

If you do not directly participate in operations or have never handled contingencies, it is highly likely that the SOP process you write will lack practicality.

An inaccurate SOP can lead to:

• Reduced work productivity

• Repeated errors

• Impact on occupational safety

• Damage to the business or working environment

These are risks that should not be underestimated in operational management.

2. If you don't understand enough, delegate or coordinate with the right people

In the practical implementation of SOP development for businesses, the most effective approach is:

• Assign the drafting task to the person directly performing the work

• Or coordinate closely with them during content creation

Daily operators will understand:

• How actual steps may differ from theory

• The most common errors

• How to handle contingencies

This is invaluable information that no document can replace.

3. Interviews and information gathering are mandatory steps

If you are tasked with writing a standard operating procedure, don't try to do it alone.

Please:

• Interview personnel directly involved in the process

• Observe their actual operations

• Note special situations

• Ask clearly: "Which step is most prone to errors? Why?"

Interviewing and data collection are not weaknesses, but a professional part of the professional SOP development process.

Step 4: Choose a short or detailed SOP?

1. When to write a Short-form SOP?

Suitable if:

• The reader is familiar with the process and internal terminology.

• The work is repetitive and changes little.

• No further explanation of context or exception handling is needed.

In this case, a simple SOP in checklist form is the optimal choice.

Effective presentation method:

• Clearly state basic information: purpose, issue date, author, document code.

• List steps in order 1–2–3.

• Each step is concise, focusing on specific actions.

• Avoid verbose explanations when unnecessary.

Examples of common structures in a concise SOP template:

• Step 1: Receive request.

• Step 2: Verify information.

• Step 3: Process and respond.

For experienced teams, this writing style helps to:

• Quick lookup

• Quick execution

• Reduce document reading time

2. When not to use a concise SOP?

Do not choose this format if:

• There are many emerging situations.

• New personnel need to be trained from scratch.

• The process involves safety or high risk.

In these cases, you should develop a more detailed standard operating procedure to avoid misunderstandings and minimize errors.

Step 5: Determine the purpose of writing an SOP

1. Ensure compliance with regulations and standards

• Applies to businesses that must comply with legal regulations, ISO, or internal standards.

• Helps control legal and audit risks.

• Documents processes to demonstrate transparency and compliance.

If the goal is compliance, a professional SOP needs to emphasize mandatory steps, control conditions, and the responsibilities of each department.

2. Optimize productivity and production efficiency

• Standardize operations to reduce repetitive errors.

• Shorten processing time for tasks.

• Reduce reliance on individuals.

In this case, when implementing effective SOP writing, you should focus on clarity, logic, and immediate implementability.

3. Ensure safety and reduce risks

• Applies in manufacturing, engineering, and machine operation environments.

• Emphasizes warnings, protective regulations, and safety inspection steps.

• Reduces the risk of accidents or environmental impact.

If the SOP relates to safety, the content must be specific, unambiguous, and include clear warning sections.

4. Ensure progress and consistency

• Helps departments coordinate in the correct sequence.

• Avoids delays due to lack of information.

• Standardizes processes so everyone follows the same standard.

In business operating procedures, this goal is often associated with clarifying responsibilities and execution times.

5. Prevent errors in production or service delivery

• Identifies points prone to errors.

• Establishes checkpoints.

• Standardizes operations to reduce the error rate.

A well-structured SOP helps reduce the cost of error correction and improve output quality.

6. Use as training material for personnel

• Supports onboarding of new employees.

• Shortens training time.

• Ensures consistent knowledge transfer.

If used for training, the content needs to be easy to understand, with clear explanations of terms and practical examples.

Part 2: Writing a detailed SOP to standardize workflows

Step 1: Mandatory content in a standard SOP

1. Title Page

This page helps identify and control the document. It should include:

• Process name.

• SOP ID.

• Date of issue or update.

• Name of department or section applied.

• Signatures of author and approver.

Standardizing this information helps businesses to:

• Control document versions.

• Avoid using outdated procedures.

• Increase transparency and accountability.

This is an important factor in standard operating procedures, especially as businesses expand.

2. Table of Contents

Only necessary when:

• The SOP is long and has many sections.

• There are many sections, subsections, and appendices.

A table of contents helps to:

• Quick lookup.

• Save time finding information.

• Increase the professionalism of the document.

If you are writing a simple SOP under 3–4 pages, a table of contents may not be necessary.

3. Quality Assurance / Quality Control

This is a section that many Vietnamese businesses often overlook.

An effective SOP must answer the question: “How do we know the process is being performed correctly?”

Content should include:

• Criteria for evaluating results.

• Checkpoints within the process.

• Related forms or documents for verification.

• Instructions for handling when results do not meet requirements.

This section is especially important in manufacturing, engineering, internal control, or processes affecting service quality.

4. Reference

If the SOP refers to:

• Legal regulations.

• Internal standards.

• Related SOPs.

You need to list them clearly and, if necessary, attach appendices.

This helps to:

• Ensure consistency between processes.

• Avoid information conflicts.

• Support auditing and internal review.

5. Comply with internal regulations before adopting a new structure

In management practice, many businesses already have their own standard SOP templates.

If one already exists:

• Use the existing structure to ensure consistency.

• Do not arbitrarily change the document framework without approval.

Consistency is more important than adopting an external "common standard" template.

Step 2: How to write the main content section of a standard SOP

1. Scope and Applicability

This section answers the question: What is this process for and who does it apply to?

Clearly state:

• The objective of the process.

• Scope of application (which departments, which situations).

• Relevant standards or regulations.

• Roles and responsibilities of each position.

• Inputs and outputs of the process.

In the actual SOP development for businesses, if this section is vaguely written, personnel will easily misunderstand the scope of work.

2. Methodology and Procedures

This is the "backbone" of the standard workflow.

Should present:

• Steps in sequential order.

• Equipment and tools to be used at each step.

• Decision conditions (if... then...).

• Potential contingencies that may occur.

• Influencing factors or potential risks.

Should:

• Clearly number each step.

• Write short sentences, focusing on specific actions.

• Avoid ambiguous phrasing like "handle appropriately."

An effective SOP must enable the reader to perform the task immediately without further questions.

3. Clarification of Terminology

If there are:

• Abbreviations.

• Technical terms.

• Uncommon internal phrases.

List and explain them clearly.

This is especially important when using SOPs as training materials or applying them across multiple departments.

4. Health and Safety Warnings

Do not casually embed them within the content.

Standard practice:

• Create a separate section for safety warnings.

• Reiterate them at steps where risks are present.

• Clearly state mandatory protective gear or safety conditions.

In technical operating procedures, this is a mandatory section to minimize accident risks and legal liabilities.

5. Equipment and Supplies

It should specify:

• A complete list of required equipment.

• Equipment standards or technical requirements.

• Storage location or access method.

• Time of use within the procedure.

This section helps prevent the lack of tools during execution.

6. Cautions and Troubleshooting

A professional SOP not only tells "what to do" but also "what to do if there's a problem."

Should include:

• Common errors that may occur.

• Signs of errors.

• Specific troubleshooting methods.

• Factors that may affect the final outcome.

This section helps reduce error correction costs and improve output quality.

7. Clearly divide into sections for easy reference

To avoid confusion and verbosity:

• Each content should have its own section.

• Use clear numbering or symbols.

• Maintain consistent structure throughout the document.

This makes the document easy to read, update, and control versions.

Step 3: How to write a concise, easy-to-read, and applicable SOP

1. Keep sentences short and direct

• Each sentence should convey only one action.

• Avoid long, complex sentences with multiple clauses.

• Eliminate unnecessary words.

For example:

Do not write:
"Ensure that all dust in the air duct is cleaned before beginning use."

Write:
"Vacuum dust from the air duct before use."

This writing style makes the standardized work procedure easier to understand and execute.

2. Use imperative sentences and active voice

Instead of circumlocution, you should:

• Start sentences with action verbs.

• Avoid passive writing that creates ambiguity about responsibility.

• Do not use pronouns "you" or "he/she".

For example:

Do not write:
"Equipment inspection needs to be performed before operation."

Write:
"Inspect equipment before operation."

In building SOPs for businesses, active voice helps clearly define actions and reduce confusion.

3. Focus on implementability

Ask yourself:

• Can the reader perform it immediately after reading?

• Are there any steps that would make them ask again?

• Are there any vague words like "appropriate," "adequate," "necessary" that haven't been clearly explained?

An effective SOP doesn't need to be flowery. The important thing is:

• Easy to read quickly.

• Easy to reference.

• Easy to do correctly.

4. Avoid making the document "intimidating"

If the document is too long and dense with text:

• Personnel will ignore it or follow old habits.

• SOPs will only exist on paper, not in actual operation.

Therefore, when applying the SOP standardization writing method, prioritize:

• Short sentences.

• Clear verbs.

• Coherent structure.

A concise, clear, and practical SOP is always more valuable than a long but difficult-to-apply document.

Step 4: Interview the right people to write accurate SOPs

1. Directly communicate with the people performing the work

Prioritize:

• Personnel who work with that process daily.

• Those who handle the most emergent situations.

• Those with many years of experience in the department.

Questions should focus on:

• The actual steps they are currently performing.

• Common errors.

• "Out-of-the-book" situations.

• Steps often overlooked but still affecting the results.

In reality, SOPs built for businesses often differ significantly from how personnel actually operate. If not verified, the document will quickly be disregarded.

2. Gather information from multiple sources

Don't just ask one person.

• Each position will view the process from a different angle.

• Some participate in the entire process.

• Some are only responsible for a small part.

To build a professional SOP, you should:

• Interview representatives from each relevant role.

• Compare information between sources.

• Confirm differences before including them in the document.

This approach helps avoid situations such as:

• Writing based on personal habits.

• Standardizing the process incorrectly.

• Missing important steps.

3. Respect existing processes

If there's an existing, stable operating process:

• Do not arbitrarily change it without thorough analysis.

• Do not rewrite it just to "standardize the format."

An effective SOP must reflect reality and be improved based on data, not on intuition.

Step 5: Use diagrams and flowcharts to make SOPs easier to understand

1. Add flowcharts when the process has multiple decision branches

You should use a flowchart if:

• There are many "If... then..." situations.

• The process changes based on specific conditions.

• Multiple departments are involved.

For example, in a standard operating procedure related to handling customer complaints:

• If the complaint is valid → transfer to the technical department.

• If not valid → respond and file.

• If a refund is needed → transfer to accounting for approval.

A flowchart helps the reader see the overall picture instead of reading many continuous text blocks.

2. Use charts or tables when execution steps are complex

Consider adding charts when:

• There are many technical parameters to cross-reference.

• There is a need to compare before-and-after conditions.

• There is a multi-level sequence.

This approach is especially useful in technical SOPs, manufacturing, or quality control.

3. Do not add images just "for aesthetics"

A professional SOP does not need too many diagrams if the content is already clear.

Only add when:

• It simplifies complex steps.

• It helps readers with language limitations.

• It genuinely increases understanding and implementability.

If added merely to increase page count or create a sense of "completeness," the document will become cluttered and distracting.

4. Combine text and visuals appropriately

Effective principles in standard work procedures:

• Text is used for detailed descriptions.

• Diagrams are used for overall illustration.

• Do not let images completely replace mandatory content.

In summary, in how to write a standard SOP, diagrams and flowcharts are powerful support tools if used correctly. The ultimate goal is still to help readers understand quickly, perform accurately, and reduce errors in the operating process.

Step 6: Document control notes in SOP

1. Why is document control notation needed?

In a business, there are often:

• Many different SOPs.

• Many updated versions over time.

• Internal storage systems by document code.

Without identification codes and version information, the following will occur:

• Using old SOPs by mistake.

• Inability to identify the latest version.

• Difficult to check in case of incidents or internal audits.

This is a crucial factor in the standard operating procedure, especially in companies with multiple departments.

2. Information required on each SOP page

Typically (depending on internal regulations), the top right corner of each page should include:

• Short name of the procedure or SOP code.

• Revision number.

• Issue date or update date.

• "Page X/Y" format (e.g., Page 2/10).

Example display:

• SOP-OPS-01 | Rev 02 | 12/02/2026 | Page 3/8

This helps to:

• Quick lookup in the system.

• Easy control during printing.

• Detect missing pages or confusion.

3. Is it necessary to place information in the footer?

Depending on the company's regulations:

• Some units place control information in the header.

• Others place it in the footer.

The important thing is not the position, but consistency throughout the entire SOP template system.

4. Adhere to the internal management system

If the company already has:

• Document coding system.

• Version control regulations.

• SOP storage database.

Strictly adhere to it instead of designing your own codes.

Part 3: Tips for accurate SOP review to ensure effective implementation

Step 1: Review and finalize the SOP before implementation

1. Test the SOP with less experienced individuals

Choose:

• Personnel who have never performed that procedure.

• Or a person who represents the correct target audience for the document.

Ask them to:

• Follow the instructions in the SOP exactly.

• Do not ask for additional information beyond the document.

• Note down points they find unclear or lacking information.

If they encounter difficulties, it's a sign that the standard operating procedure is not clear enough.

2. Collect feedback from multiple people

It is recommended to test with:

• At least 2–3 people in different roles.

• New hires and those with average experience.

Each person will:

• Identify different errors.

• Have different interpretations.

• Discover ambiguities that the author overlooked.

In practice, building SOPs for businesses, this step significantly reduces revision costs after widespread deployment.

3. Do not test with individuals who are overly familiar with the process

If you ask someone who has been working for many years to test it:

• They will rely on personal experience.

• They will overlook missing points in the document.

• The test results will not reflect the true quality of the SOP.

The goal of testing is to see if the SOP is clear enough to operate independently, not to test the competency of the performer.

4. Update and improve before official issuance

After receiving feedback:

• Revise unclear wording.

• Add missing steps.

• Clarify decision conditions.

• Add warnings if there are risks.

A professional SOP always undergoes at least one round of testing before full implementation.

Step 2: Obtain feedback from direct implementers before approval

1. Prioritize feedback from direct workers

Before submitting for approval, please:

• Send the draft to the personnel currently executing the procedure.

• Ask them to read and provide specific feedback.

• Ask clearly: "Are there any unrealistic steps?"

• Also ask: "Are there any situations not covered?"

In practice, when building SOPs for businesses, the operating team will discover:

• Unnecessary cumbersome steps.

• Illogical execution order.

• Common issues that have not been recorded.

2. Create a sense of ownership in the process

When personnel are involved in contributing:

• They feel their opinions are respected.

• They understand the goals of the standard operating procedure.

• They tend to adhere to the SOP more strictly.

Conversely, if an SOP is imposed from above without consulting the implementers, it is highly likely that the document will be "forgotten" in practice.

3. Balance reality and management requirements

After receiving feedback:

• Adjust content to align with operational reality.

• Ensure compliance with management requirements and internal standards.

• Eliminate unnecessary steps while retaining critical control points.

An effective SOP is a combination of management perspective and the team's practical experience.

Step 3: Review with consultants and quality control department

1. Send SOP to consultants and QA department

After making edits based on feedback from implementers:

• Forward the SOP to specialized consultants (if any).

• Send it to the Quality Assurance (QA) or quality control department.

Typically, they will:

• Check compliance with internal regulations.

• Cross-reference with relevant standards or legal regulations.

• Review layout, document codes, versions, and formatting.

They may not make in-depth changes to the operational content, but they will ensure that the standard operating procedure meets system requirements.

2. Check formal requirements and issuance procedures

A professional SOP needs to:

• Adhere to the internal format template.

• Follow the correct version control process.

• Be officially registered with a document code.

The department responsible for documents will guide on:

• How to update it in the document management system.

• How to officially publish it throughout the enterprise.

• Regulations on storage and access.

This is an important step in building SOPs for businesses, especially for organizations with well-structured management systems.

3. Implement approval via the document management system

To ensure transparency and audit trails:

• Use the internal document management system.

• Record all approval steps fully.

• Save the history of edits and updates.

This helps to:

• Easily check during internal or external audits.

• Avoid disputes over the applicable version.

• Increase the legal validity of the document.

The approval process may vary between organizations, but the common goal is to ensure transparency and compliance.

4. Finalize approval signatures

Before official issuance:

• Signatures of the author are required.

• Signature of the approver.

• Signatures of relevant department heads may be added.

Currently, many businesses accept electronic signatures, making the process of issuing SOP templates faster and more flexible.

Step 4: Deploy and maintain SOP after approval

1. Officially implement the SOP in practice

After approval:

• Officially notify relevant departments.

• Organize training if needed (in-person or online).

• Provide instructions on how to access documents in the system.

• Clearly explain application responsibilities.

Depending on the importance of the standard operating procedure, you can:

• Conduct centralized training for personnel.

• Send emails with implementation guidelines.

• Update on the internal document management system.

Most importantly, ensure relevant personnel know the SOP exists and understand how to apply it.

2. Monitor the actual application rate

After deployment, it is necessary to:

• Periodically check compliance.

• Record feedback from staff.

• Evaluate operational effectiveness after application.

An effective SOP should help:

• Reduce errors.

• Increase productivity.

• Standardize work methods among individuals.

If the document is not being used, review the communication method or if the content is too complex.

3. Update when processes change

In a business environment, processes are constantly changing due to:

• New technologies.

• Organizational structure.

• Legal requirements.

• Adjustments to operating strategy.

Therefore, in building SOPs for businesses, it is necessary to:

• Review periodically (e.g., every 6–12 months).

• Update when there are actual changes.

• Re-approve the new version.

• Record revision history.

• Redistribute the document to all relevant personnel.

An outdated standard operating procedure can pose a greater risk than having no procedure at all.

4. Maintain long-term validity

To ensure SOPs always deliver value:

• Link SOP compliance to performance evaluations.

• Integrate SOPs into new employee training programs.

• Periodically review during internal meetings.

In summary, in how to write standard SOPs, the ultimate goal is not to complete a document, but to create a system that helps the team work safely, efficiently, and consistently. A well-implemented and regularly updated SOP is the foundation for the sustainable development of the business.

Finalizing and controlling SOPs before issuance

1. Record the change history of each version

Each time an edit is made, it is necessary to:

• Update the revision number.

• Record the date of change.

• Briefly describe the content of the adjustment.

• Record the person who made the change.

This helps to:

• Trace issues when they arise.

• Compare between old and new versions.

• Ensure transparency in the standard operating procedure system.

Not recording change history is a common mistake in building SOPs for businesses.

2. Check old SOPs before writing new ones

Before drafting:

• Verify if there is an old version.

• Assess whether it can be updated instead of rewritten from scratch.

• Retain sections that are still relevant.

This helps to:

• Save time.

• Avoid creating two overlapping procedures.

• Maintain consistency within the system.

If only minor edits are made, the version must still be updated and changes recorded.

3. Use simple, easy-to-understand language

An effective SOP does not require complex terminology.

You should:

• Use short sentences.

• Avoid jargon unless necessary.

• Clearly explain terms that must be used.

The purpose of a standard operating procedure is to be executed, not to impress.

4. Check for clarity and avoid ambiguity

Before submitting for approval:

• Have someone who has never done the process read the document.

• Ask them how they understand the content.

• Identify points that could be misinterpreted.

If a step can be interpreted in two ways, it needs to be rewritten immediately.

In actual implementation of how to write standard SOPs, many errors stem from ambiguous wording rather than missing steps.

5. Ask multiple people to review before signing

Before submitting for approval:

• Ask colleagues or department heads to reread it.

• Check for spelling errors, formatting, and number of steps.

• Ensure the document code and version information are accurate.

Thorough internal review helps to:

• Increase the chance of approval on the first try.

• Reduce time spent on subsequent revisions.

• Enhance the professionalism of the document.

In summary, in standard SOPs, carefulness in the final step will help the document operate stably long-term. Version control, ensuring clarity, and thorough review before approval are the foundations for SOPs to truly be effective in a business.

References

1. Bizmanualz. (n.d.). What are policies and procedures (SOP)? Retrieved from https://www.bizmanualz.com/save-time-writing-procedures/what-are-policies-and-procedures-sop.html
2. Collaboris. (n.d.). Standard operating procedures: A complete guide review and update. Retrieved from https://www.collaboris.com/standard-operating-procedures-a-complete-guide-review-update/
3. Labowitz, D. (n.d.). Business coach: Expert interview.
4. Merriam-Webster. (n.d.). Standard operating procedure. Retrieved from https://www.merriam-webster.com/dictionary/standard%20operating%20procedure
5. Pennsylvania State University Extension. (n.d.). Standard operating procedures: A writing guide. Retrieved from https://extension.psu.edu/standard-operating-procedures-a-writing-guide
6. Process Street. (n.d.). Writing standard operating procedures. Retrieved from https://www.process.st/writing-standard-operating-procedures/
7. Saint Mary’s University. (n.d.). SOP guidance document. Retrieved from https://smu.ca/webfiles/SOPGuidanceDocument.pdf

Translator: Sidney Bailey Hoang.