Policies set the rules, SOPs define the repeatable process that enforces those rules, and work instructions detail the exact steps an individual follows to execute that process. In private lending, all three documents serve distinct purposes — and confusing them produces compliance gaps, audit failures, and inconsistent loan servicing outcomes.
Key Takeaways
- A policy states what must happen and why — it does not describe how to do it.
- A standard operating procedure (SOP) translates a policy into a repeatable, role-assigned workflow.
- A work instruction is a task-level reference that a single operator follows step by step at the point of execution.
- All three documents form a hierarchy: policy governs the SOP, the SOP governs the work instruction — break the chain and your audit trail breaks too.
- Private lenders who treat these terms as interchangeable expose themselves to regulatory findings and loan-level errors that third-party auditors will flag.
Why the Distinction Matters in Private Lending
Private mortgage lending operates under a patchwork of federal statutes — RESPA (12 U.S.C. §2605), Regulation X (12 CFR §1024.17), TILA/Regulation Z (12 CFR Part 1026), and SCRA (50 U.S.C. App §501+) — alongside state-specific licensing and servicing requirements. Each of those frameworks assumes an organization with documented controls. When an examiner asks for your “loss mitigation policy,” they want a policy document — not your SOP binder and not a checklist your team uses during a forbearance call.
Using the wrong document in the wrong context signals to auditors that your operation lacks governance structure. A well-run private lending shop treats these three document types as distinct layers of a control framework — not synonyms. Lenders who need a structured SOP foundation to anchor this framework should start with the strategic SOPs for private mortgage servicing success pillar, which covers the full governance model for servicers.
The Comparison: Policy vs. SOP vs. Work Instruction
| Dimension | Policy | SOP | Work Instruction |
|---|---|---|---|
| Purpose | States the rule and the intent behind it | Defines the repeatable process that fulfills the rule | Provides step-by-step task guidance at execution |
| Scope | Organization-wide; applies to all applicable roles | Function- or process-level; assigned to a team or role | Individual task; single operator or station |
| Authoring Role | Executive leadership, compliance officer, or board | Department head or operations manager | Team lead or subject-matter expert on the floor |
| Approval Authority | Senior leadership or governance committee | Operations or compliance manager | Immediate supervisor or team lead |
| Change Frequency | Infrequent; driven by regulatory changes or strategic shifts | Moderate; updated when workflow or system changes | Frequent; updated when tools, screens, or task steps change |
| Audit Use | Demonstrates intent and governance posture to examiners | Shows that a process exists and is assigned to a role | Proves that operators have task-level guidance at execution |
| Private Lending Examples | Escrow administration policy, loss mitigation policy, SCRA hardship policy | Loan boarding SOP, monthly escrow analysis SOP, payment processing SOP | Screen-by-screen boarding checklist, escrow disbursement input guide, reinstatement letter mail-merge steps |
What a Policy Does — and Does Not Do
A policy answers two questions: what is required, and why. In private mortgage servicing, your escrow administration policy tells readers that the organization follows 12 CFR §1024.17, conducts annual escrow analyses, and handles shortages and surpluses according to Regulation X requirements. The policy does not tell anyone which software screen to open, who runs the analysis on the third Tuesday of each month, or what to do when the system returns an error.
Policies sit at the top of the governance hierarchy. They require senior leadership approval because they bind the entire organization. A change to policy signals a change in how the organization positions itself relative to regulation or risk. Examiners reviewing your compliance posture under RESPA Section 6 (12 U.S.C. §2605) want to see a written policy that demonstrates your organization’s commitment to the rule — not a process document. Conflating the two is the fastest way to trigger a request for additional documentation during an audit.
One other discipline: policies require a review cycle with documented approval. If your policy binder has no revision date and no approval signature, it functions as a draft — not a control — in the eyes of an auditor.
What an SOP Does — and Where It Belongs
An SOP translates the policy into an executable, role-assigned workflow. Where the policy says “the organization conducts annual escrow analyses,” the SOP says: the loan operations team runs the analysis in the servicing platform during a fixed annual window — then the results route to the escrow manager for review, and all shortage letters generate from the approved template. The SOP names roles, identifies handoff points, and specifies decision branches — but it does not drop to the level of “click the Escrow Analysis tab, enter the current balance in field 3.”
SOPs work at the function level. They exist to make a process repeatable regardless of which qualified team member executes it. Lenders building out their first SOP library should review the 7 SOPs every private mortgage servicer needs as a starting point for identifying which workflows require formal documentation first.
The critical discipline with SOPs is version control. An unversioned SOP is operationally indistinguishable from no SOP — if a borrower dispute lands in court or before a regulator, an undated SOP proves nothing. Every SOP needs a version number, an effective date, and a named approver. Consult qualified legal counsel before relying on any SOP as a legal defense in a dispute.
What a Work Instruction Does — and Who Uses It
A work instruction is the street-level document. It gives a single operator the exact steps to complete a specific task — field names, screen sequences, file paths, error handling steps, and submission confirmations. In a private mortgage servicing operation, work instructions cover things like: how to enter a new loan into the servicing platform, how to generate a payoff quote from the system, or how to process a wire receipt and post it to the correct loan account.
Work instructions change more frequently than SOPs because they reflect the current state of your tools. When your servicing software updates its interface, the SOP does not change — the process is still “post the payment and send the confirmation” — but the work instruction updates to reflect the new screen layout. This is why authoring authority for work instructions sits at the team lead or subject-matter expert level: the person closest to the task documents the task.
Private lenders who skip work instructions and rely entirely on SOPs produce inconsistent output. Two operators reading the same SOP will execute a task differently if neither has a step-by-step reference. Work instructions eliminate that variance. The how-to guide for building a servicing SOP covers the layered approach to documentation — including when to stop at the SOP level and when a work instruction is warranted.
Expert Take: The Document Stack in Practice
How the Three Documents Reference Each Other
The power of the three-tier system is in the linkage. Every SOP should cite the policy it implements — by document name and version number. Every work instruction should cite the SOP step it supports. This chain of reference does two things: it keeps your documentation coherent as rules evolve, and it gives auditors a traceable path from the regulatory requirement down to the operator’s desk.
When a policy changes — because a regulation changes or because leadership updates the organization’s risk posture — the change cascades down. The compliance team identifies which SOPs reference the changed policy, those SOPs get reviewed and updated, and the work instructions that reference the affected SOP steps update to reflect the new execution path. Organizations that maintain the chain handle regulatory changes without operational disruption. Organizations that lack it scramble to update disconnected documents that no one is sure are current.
Private mortgage servicers operating across multiple states benefit especially from this structure because state-specific requirements layer on top of federal baselines. A single payment processing policy references RESPA — but the payment processing SOP for Texas borrowers references the Texas Finance Code requirements that sit on top of that federal baseline. Work instructions for a Texas loan differ in specific steps from work instructions for a California loan. The hierarchy makes that variance manageable.
Frequently Asked Questions
Is a loan servicing agreement the same as a policy?
No. A loan servicing agreement is a contract between the lender and the servicer that defines obligations, compensation, and performance standards. A policy is an internal governance document that defines how the organization operates to meet those contractual and regulatory obligations. The two documents reference each other but serve entirely different legal and operational functions.
Who approves SOPs in a private lending operation?
The operations manager or compliance manager holds approval authority for SOPs in most private lending shops. If the SOP touches regulatory requirements — escrow, loss mitigation, SCRA hardship — the compliance officer reviews before approval. The approval signature and date must appear on the document; an unapproved SOP is an informal procedure, not a control.
How do work instructions need updating?
Work instructions update whenever the tools, screens, or task steps they describe change. There is no fixed schedule — the trigger is a change in the execution environment. Assign ownership of each work instruction to the team lead responsible for that task. When they flag a change, the update happens immediately, not at the next scheduled review cycle.
What happens when a private lender has SOPs but no policies?
The SOP describes a process with no documented justification for why the process exists in its current form. When an auditor asks why your loss mitigation process is structured the way it is, the SOP alone cannot answer that question — the policy provides the governing rationale. Without it, every SOP decision looks discretionary rather than principled, which is a governance finding waiting to happen.
Can one document serve as both a policy and an SOP?
In very small operations, a combined policy-and-procedure document is an accepted starting point — and regulators recognize this for small servicers. The document must clearly separate the policy statement (the “what and why”) from the procedure section (the “how and who”). As the operation scales, the combined format becomes unwieldy and separation into distinct documents is the standard approach. The split also allows each document type to follow its own approval and revision cycle.
Do private lenders need to share these documents with borrowers?
Policies and SOPs are internal governance documents — borrowers do not receive them. However, certain regulatory requirements under RESPA and TILA require written disclosures to borrowers that reference your policies. For example, your escrow administration policy drives the content of the annual escrow account statement the borrower receives. The policy is internal; the disclosure is external. Consult qualified legal counsel before determining which disclosures apply to your loan portfolio.
Sources & Further Reading
- CFPB Regulation X (12 CFR Part 1024) — CFPB official regulation text covering RESPA servicing requirements including escrow and loss mitigation
- CFPB Regulation Z (12 CFR Part 1026) — CFPB official regulation text covering TILA disclosure and credit requirements
- ISO 9001:2015 Quality Management Systems — International standard defining the document hierarchy for quality management, including the policy-procedure-work instruction framework
Next Steps: Work with Note Servicing Center
Note Servicing Center manages the full documentation stack — policies, SOPs, and work instructions — as part of its private mortgage servicing practice. If your operation needs a servicer that runs on documented, auditable processes rather than tribal knowledge, contact Note Servicing Center to discuss your portfolio.