Policies are one of the most important—and most frequently underestimated—tools in a midwifery business.
Many midwives start writing policies only when they are required to do so for accreditation, credentialing, licensing, employment, insurance, or another external requirement.
But policies can do much more than satisfy a requirement.
Well-written policies help define how your practice operates, what your team can expect, how decisions are handled, and what standards your organization is committed to maintaining.
They can create consistency, support delegation, improve onboarding, strengthen accountability, and reduce the number of decisions that have to be made from scratch every day.
Poorly written policies, however, can create the opposite effect.
A policy that is vague, unrealistic, outdated, copied from another organization, or inconsistent with actual practice can create confusion and potentially increase risk.
At Midwifery Business Consultation, we encourage midwives to think of policies as part of the infrastructure of the business.
Your policies should not simply fill a binder.
They should help your business function.
Here are some practical tips for creating policies that are useful, realistic, and appropriate for your midwifery practice.
1. Start With the Purpose
Before writing a policy, ask:
Why do we need this policy?
Every policy should have a reason for existing.
Perhaps you are trying to:
- Standardize a process
- Establish an expectation
- Reduce confusion
- Improve communication
- Address a recurring problem
- Support safety
- Define responsibilities
- Meet a regulatory requirement
- Support employees
- Improve consistency
- Prepare for growth
If you cannot explain why the policy exists, you may not need the policy—or you may not have clearly identified the problem it is supposed to solve.
Start with the problem.
Then build the policy.
2. Write for Your Actual Practice
One of the biggest mistakes midwifery businesses make is writing policies for the practice they wish they had instead of the practice they actually operate.
Your policies should reflect:
- Your staffing model
- Your clinical model
- Your location
- Your services
- Your technology
- Your facility
- Your workflow
- Your business structure
- Your scope of practice
- Your client population
A solo home birth practice does not need the exact same policies as a large birth center.
A five-midwife practice does not need the exact same procedures as a solo clinician.
Start with your actual organization.
3. Don’t Copy Another Practice’s Policy Manual
It can be tempting to find another practice’s policies online and use them as a template.
Be careful.
A policy that works for another organization may not be appropriate for yours.
Different practices may have different:
- State requirements
- Licensure requirements
- Scope of practice
- Staffing
- Facilities
- Equipment
- Clinical protocols
- Insurance
- Business structures
- Documentation systems
Use outside materials for education and inspiration when appropriate.
But your final policies should be specific to your organization.
4. Make Sure Your Policies Are Consistent With Applicable Requirements
Midwifery businesses operate within a regulatory environment.
Depending on your practice and location, this may include:
- State law
- Licensing requirements
- Professional standards
- Facility requirements
- Privacy requirements
- Employment law
- Independent contractor requirements
- Insurance requirements
- Accreditation standards
- Scope-of-practice requirements
Policies should not be written in isolation from those requirements.
For clinical policies especially, appropriate professional and legal review may be important.
A policy is not a substitute for knowing the law.
5. Use Plain Language
A policy does not need to sound complicated to be professional.
In fact, overly complicated language can make policies harder to follow.
Instead of:
“All personnel shall endeavor to facilitate timely completion of documentation within an appropriately reasonable period of time.”
Consider:
“Team members must complete required documentation within the timeframe established by the practice.”
Clear.
Direct.
Understandable.
Your team should not need a lawyer to understand an ordinary workplace procedure.
6. Be Specific About Expectations
Vague policies create inconsistent behavior.
Consider:
“Staff should respond to messages promptly.”
What does “promptly” mean?
An hour?
Four hours?
One business day?
Instead, define the expectation where appropriate.
For example:
“Non-urgent client messages should be addressed within the timeframe established by the practice.”
Or, where the practice has determined a specific timeframe:
“Administrative messages received during business hours will generally be addressed within one business day.”
The more important the expectation, the more important clarity becomes.
7. Separate Policies From Procedures
Remember:
Policy = What is expected.
Procedure = How it is done.
For example:
Policy
The practice maintains a consistent process for responding to urgent client communications.
Procedure
- Receive the communication.
- Determine whether the concern requires immediate escalation.
- Follow the appropriate clinical escalation pathway.
- Notify the appropriate clinician.
- Document the communication.
- Complete follow-up as indicated.
Separating the two makes policies easier to understand and update.
8. Identify Who the Policy Applies To
Every policy should clarify its scope.
Does it apply to:
- Midwives?
- Nurses?
- Administrative staff?
- Employees?
- Contractors?
- Students?
- Volunteers?
- All members of the organization?
This is especially important when your practice uses a combination of employees, independent contractors, students, and other professionals.
Do not assume everyone is subject to every policy in exactly the same way.
9. Define Responsibilities
A policy should answer:
Who is responsible for this?
For example:
Practice owner: Maintains the policy.
Clinical director: Provides clinical oversight.
Midwives: Follow the procedure and document appropriately.
Administrative staff: Complete designated administrative steps.
Clear responsibility reduces the chance that everyone assumes someone else is handling the task.
10. Avoid Writing Policies That Are Impossible to Follow
This is one of the most important rules.
Do not create a policy simply because it sounds good.
Create a policy your organization can actually implement.
For example, if your policy requires every phone call to be returned within 15 minutes, but your clinicians are frequently attending births, that may not be realistic.
Instead, create a system that accounts for real-world circumstances.
A policy should support your workflow.
It should not require your team to constantly violate the policy just to get through the day.
11. Consider What Happens When the Normal Process Doesn’t Work
Real life is messy.
A good procedure should account for exceptions.
Ask:
What happens if the person responsible is unavailable?
What happens if the technology fails?
What happens if the client cannot follow the usual process?
What happens if the situation becomes urgent?
What happens if the usual resource is unavailable?
You do not have to write an enormous policy covering every imaginable scenario.
But important exceptions should have an escalation pathway.
12. Build Policies Around Common Problems
Look at the recurring questions your team asks.
If you repeatedly hear:
“What should I do when…?”
you may have a policy opportunity.
For example:
- What happens when a client cancels?
- What happens when a payment is late?
- What happens when a team member calls out?
- What happens when a client requests records?
- What happens when a birth team member is unavailable?
- What happens when equipment is missing?
- What happens when an urgent message is received?
Repeated questions often reveal missing systems.
13. Start With High-Priority Policies
You do not need to create 100 policies at once.
Start with the areas where clear guidance is most important.
For many midwifery businesses, priorities may include:
Clinical
- Emergency response
- Transfer of care
- Documentation
- Medication management
- Infection prevention
- Equipment management
- Client communication
Administrative
- Scheduling
- Cancellations
- Billing
- Records
- Privacy
- Communication
Human Resources
- Attendance
- Professional conduct
- Performance
- Reporting concerns
- Leave
- Workplace expectations
Business Operations
- Purchasing
- Financial approvals
- Technology
- Business continuity
- Incident reporting
Your specific priorities should reflect your organization.
14. Think About the “Why”
Policies are easier to follow when people understand their purpose.
For example, instead of simply stating:
“All incident reports must be completed.”
your training can explain that incident reporting helps the organization identify patterns, improve systems, and address potential safety concerns.
People are more likely to follow processes they understand.
15. Don’t Use Policies to Micromanage
A policy should create structure without unnecessarily controlling every small decision.
If you attempt to write a policy for every possible action, your organization can become rigid.
Not every situation requires a 10-step procedure.
Some situations require professional judgment.
Good policies provide a framework while allowing appropriately qualified professionals to exercise judgment within their responsibilities.
16. Be Careful With Clinical Policies
Clinical policies deserve particular attention.
They should be developed and reviewed by appropriately qualified professionals and should be consistent with applicable:
- Laws
- Regulations
- Scope-of-practice requirements
- Professional standards
- Evidence
- Organizational resources
Avoid treating a generic internet policy as a substitute for clinical expertise.
A policy that looks professional can still be clinically inappropriate for your setting.
17. Make Emergency Policies Easy to Use
Emergency procedures should not be written like a 20-page essay if the team needs to find the critical information quickly.
Consider creating concise emergency guides, checklists, or quick-reference tools where appropriate.
Important information should be easy to locate.
Ask:
If someone is under stress, can they find the information they need?
That is a very different standard from:
Does the policy look comprehensive?
Usability matters.
18. Use Consistent Formatting
Create a standard format for your policies.
For example:
Policy Title
Policy Number
Effective Date
Review Date
Purpose
Scope
Policy Statement
Responsibilities
Procedure
Documentation
References
Revision History
You do not necessarily need every section for every policy.
But consistent formatting makes your policy system easier to manage.
19. Give Policies Version Numbers
Policies change.
When they do, you should be able to tell which version is current.
Include:
- Version number
- Effective date
- Revision date
- Approved date
- Review date
This helps prevent people from accidentally using outdated versions.
20. Assign Someone to Own Each Policy
Every policy should have an owner.
That person may be responsible for:
- Reviewing it
- Updating it
- Coordinating revisions
- Training staff
- Monitoring implementation
If nobody owns a policy, it can quickly become outdated.
21. Establish a Review Schedule
Policies should be reviewed periodically.
The appropriate frequency will depend on the type of policy and your organization’s requirements.
Review when:
- Laws change
- Regulations change
- Clinical standards change
- Technology changes
- Your workflow changes
- Your staffing changes
- An incident occurs
- A problem is identified
- A service is added
- Your business model changes
A policy should never be considered permanently finished.
22. Update Policies After Problems
A mistake or incident can reveal a weakness in the system.
Instead of asking only:
“Who made the mistake?”
also ask:
“What allowed this to happen?”
Maybe the policy was unclear.
Maybe training was inadequate.
Maybe responsibilities were ambiguous.
Maybe the workflow was unrealistic.
Maybe there was no policy at all.
Use problems as opportunities to improve the system.
23. Train People on Policies
Sending someone a PDF does not equal training.
When appropriate, explain:
- What the policy says
- Why it exists
- What changed
- What the employee needs to do
- Who to contact with questions
For important policies, consider scenario-based training.
Ask:
“What would you do if this happened?”
That can reveal misunderstandings much faster than simply asking someone to sign a form.
24. Make Policies Easy to Access
Your team should know where policies live.
Whether you use:
- A secure shared drive
- An employee portal
- Practice management software
- A policy management system
- A controlled digital folder
the system should be organized.
Avoid having one version on someone’s computer, another in a binder, and a third version in email.
One current source of truth is ideal.
25. Protect Confidential Information
Policy documents may contain operational information, employee information, or other sensitive material.
Use appropriate access controls.
Not every team member necessarily needs access to every policy.
Human resources information, financial information, and other restricted materials may require different access than general operational policies.
26. Don’t Let Policies Contradict Each Other
This can happen as a business grows.
One policy says one thing.
Another policy says something different.
A procedure has been updated, but an older policy still references the previous process.
Periodically review related policies together.
Consistency matters.
27. Make Sure the Policy Matches Your Contracts
Your policies should not unintentionally contradict:
- Employment agreements
- Contractor agreements
- Client agreements
- Facility agreements
- Vendor agreements
If there is a conflict, the organization may face unnecessary complications.
Important contractual language should be reviewed appropriately.
28. Think About Client-Facing Policies Separately
Not every internal policy should be handed to clients.
Some policies are internal operational documents.
Others may need to be communicated directly to clients.
Examples may include:
- Cancellation policies
- Financial policies
- Communication expectations
- Privacy notices
- Client responsibilities
- Attendance expectations
Client-facing policies should be written for clients—not for employees.
29. Avoid Punitive Language When It Isn’t Necessary
Policies should establish expectations without making the organization sound hostile.
Compare:
“Failure to comply will result in immediate disciplinary action.”
with:
“Team members are expected to follow established practice policies and procedures. Concerns about compliance will be addressed through the practice’s performance management process.”
The second communicates accountability without making every policy sound like a threat.
30. Don’t Promise More Than You Can Deliver
This is particularly important in client-facing policies.
Be careful with absolute promises.
For example:
“All messages will be answered immediately.”
may create an expectation the practice cannot always meet.
Instead, establish realistic expectations.
Policies should help manage expectations—not create impossible commitments.
31. Consider the Client Experience
When developing a policy, ask:
What will this feel like from the client’s perspective?
A policy can be operationally convenient but unnecessarily difficult for clients.
The best systems balance:
Business needs + clinical needs + client needs.
32. Use Policies to Support Boundaries
Midwifery is relationship-centered.
That is one of its greatest strengths.
But relationships also require boundaries.
Policies can help establish expectations around:
- After-hours communication
- Social media
- Personal phone numbers
- Gifts
- Professional relationships
- Home visits
- Communication methods
- Staff-client boundaries
Clear boundaries protect both the client and the clinician.
33. Ask Your Team for Feedback
The people using the policy every day may identify problems you missed.
Ask:
“Does this procedure make sense?”
“Where does this process break down?”
“Is anything unclear?”
“What would make this easier to follow?”
This does not mean every suggestion must be adopted.
It means the policy should be informed by the people who actually use it.
34. Test the Policy Before Finalizing It
Walk through a realistic scenario.
Imagine a client calls at 8 p.m.
What happens?
Who receives the message?
Who determines urgency?
Who responds?
What gets documented?
What happens if the usual person is unavailable?
If you cannot answer those questions, the procedure may need work.
35. Ask Whether the Policy Actually Solves the Problem
This is the ultimate test.
After writing the policy, ask:
If everyone followed this policy exactly, would the original problem be solved?
If the answer is no, rewrite it.
A policy is not successful because it is detailed.
It is successful because it works.
A Simple Policy-Writing Checklist
Before finalizing a policy, ask:
Purpose
- Why does this policy exist?
Scope
- Who does it apply to?
Clarity
- Is it easy to understand?
Specificity
- Are expectations clear?
Responsibility
- Who does what?
Procedure
- Does the team know how to implement it?
Exceptions
- What happens when the normal process cannot be followed?
Compliance
- Is it consistent with applicable requirements?
Reality
- Can the practice actually follow it?
Training
- Does the team know it exists?
Accessibility
- Can people easily find it?
Review
- Who maintains it and when will it be reviewed?
If you can answer these questions, you are well on your way to creating a useful policy.
The Goal Isn’t to Have the Biggest Policy Manual
It is easy to fall into the trap of thinking:
“The more policies we have, the more professional we are.”
That is not necessarily true.
A 300-page policy manual that nobody reads or follows is less useful than a smaller, well-designed system that your team understands and actually uses.
The goal is not more policies.
The goal is better systems.
Final Thoughts
Writing policies is not just an administrative exercise.
It is an opportunity to decide:
How do we want this business to operate?
What do we expect from our team?
How do we want clients to experience our practice?
How do we respond when things don’t go as planned?
How do we protect the organization while continuing to provide excellent care?
Good policies create clarity.
Good procedures create consistency.
Good training creates competence.
Good leadership creates accountability.
And together, those elements create a stronger business.
Your policies should not exist simply because someone told you that your midwifery practice needs them.
They should exist because your business deserves systems that support the people who operate it.
At Midwifery Business Consultation, we help midwives and midwifery business owners develop the operational foundation needed to move from an owner-dependent practice to a structured, sustainable organization.
Because your policies are more than documents.
They are the written framework for how your business works.
Great resources available – Shop
