1. Objective

This SOP defines how a Virtual Assistant (VA) builds, maintains, and deploys reusable e-signature templates — the base documents an agent uses over and over (listing agreement, buyer representation agreement, offer package, disclosure request, contingency removal). Templates cut minutes off every send and eliminate the most common source of e-signature errors: missing fields, wrong signer assignment, outdated forms.

The VA's role is template authoring and maintenance, not legal review. You build templates from the current state- or board-issued forms the agent has approved, place every required field in the correct spot, and assign each field to the correct signer. When a transaction starts, you don't start from a blank PDF — you start from the template.

Where this SOP starts: The agent identifies a document they sign frequently and wants templatized.
Where this SOP ends: The template is saved in the e-signature platform, tested with a dry run, documented in the template index, and available for immediate use on any transaction.

Success looks like: Every high-volume document is a one-click send. No signer ever receives an envelope with missing fields, wrong recipients, or outdated language. Template maintenance is on a calendar — forms get updated within 30 days of a state or board release.

---

2. Your Role & Boundaries

2a. What you handle independently

• Building e-signature templates from agent-approved base documents
• Placing signature, initial, date, text, and checkbox fields in the correct positions
• Assigning each field to the correct signer role (Seller 1, Seller 2, Buyer, Agent, Broker, etc.)
• Naming and filing templates per the naming convention in Section 5
• Running dry-run tests on every new template before it goes into active use
• Maintaining the template index in the operations file
• Running the annual and form-release template review process per Section 6
• Sending envelopes from templates for individual transactions once the agent has approved the specific send

2b. What requires agent approval before acting

• Any new base document being added to the template library
• Any change to a template's fields, language, or signer assignments
• Any deletion or retirement of a template
• Any non-standard signer order on a specific send (e.g., broker signs first instead of last)
• Any expiration setting outside the standard (most platforms default to 7 or 14 days)
• Sending an envelope to parties the agent has not specifically authorized for that transaction

2c. What you never do

• You never negotiate on the agent's behalf under any circumstances.
• You never provide pricing, legal, or strategic opinions to any party.
• You never sign or initial any document on behalf of the agent, client, or any party.
• You never communicate directly with the other party's client.
• You never modify the language or substance of a legal form — you use the forms the agent has approved, unchanged, and only update templates when the state, board, or brokerage releases a new version of the form itself.
• You never send an e-signature envelope with a party's email that has not been verified with the agent for that specific transaction.
• You never pre-sign, pre-initial, or pre-fill any substantive terms on behalf of any party.
• You never store or share login credentials for the e-signature platform outside the agent's designated secure storage.

When in doubt: Ask the agent before creating or modifying a template. A template mistake propagates to every transaction that uses it.

---

3. Schedule & Trigger

This SOP runs on three triggers.

New template trigger: Agent identifies a document they want templatized. Could happen at any time — commonly during initial onboarding (CRM Setup & Configuration (New Agent) may flag documents that need templates) or when a new form is adopted by the state/board.

Template update trigger: A form is updated by the state, board, brokerage, or the agent. Update the template within 30 days of release.

Annual review trigger: Once per year, review every active template for form currency, field accuracy, and signer-role correctness. Typical cadence: January of each year.

Expected turnaround:

• New template build: 1–2 business days including dry-run
• Form update on existing template: within 30 days of release, sooner if closings are imminent
• Annual review: complete within the month of January

Sequence context: This SOP is a foundational operations SOP — its outputs are used by every transaction-related SOP that involves signed documents: pre-listing, listing agreement review, seller disclosures, buyer representation agreement, offer package, and the TC series for contingency removals and amendments. If a template isn't ready, transactions either run slower or run off of ad-hoc PDFs.

---

4. Platform

Confirm the e-signature platform during onboarding. Common platforms in real estate:

Platform	Notes
DocuSign	Widely used; strong template engine; integrates with most transaction management systems
DotLoop	Real-estate-specific; combines e-signature with transaction management
Authentisign (part of Lone Wolf Transactions / zipForm)	Common in boards that use zipForm; tightly integrated with form library
Skyslope (DigiSign)	Common in brokerages that use Skyslope as the TMS

The template-building mechanics differ per platform, but the underlying workflow is similar: upload base document → place fields → assign signers → save. Follow the platform's current documentation for exact clicks; the standards below apply regardless of platform.

---

5. Templates to Create

The standard template library includes the documents below. Not every agent will use all of these — confirm with the agent during onboarding which apply.

Core templates

Template	Used by SOPs	Notes
Buyer Representation Agreement	Buyer Intake & Onboarding	Binds the agent–buyer relationship; state-specific
Listing Agreement	Pre-Listing Appointment Prep, Listing Agreement Review & Filing	Listing engagement; state- or board-specific
Seller Disclosure Request Packet	Seller Disclosure Request & Document Collection	Multi-document: Seller's Property Condition Disclosure, Lead-based paint (if pre-1978), HOA docs, state disclosures
Offer Package (Purchase Agreement + Addenda)	Offer Preparation Checklist	Combines purchase agreement with common addenda (FHA, VA, inspection, financing)
Counter Offer	Multiple Offer Situation Protocol	Used in negotiation back-and-forth
Contingency Removal Forms	Contingency Removal Management	Inspection, appraisal, loan removals
Repair Request / Response	Repair Request & Negotiation Documentation	Repair request, repair response, credit addendum
Mutual Release / Cancellation	Final Walkthrough Coordination	For deals that fall through
Addendum — Generic	Various	Blank addendum for miscellaneous amendments
Amendment to Listing Agreement	Price Reduction Process	Price changes, term extensions

Optional / situational templates

• Pre-Marketing Agreement (coming soon / office-exclusive)
• Extension of Closing Date
• Seller's Notice to Perform
• Buyer's Notice to Perform
• Agency Disclosure / Transfer Disclosure (state-specific)

Build the templates the agent uses most often first. Expand the library as demand surfaces.

---

6. How to Build a Template

6a. Gather the base document

• Confirm which form the agent uses — state-association form, local board form, brokerage-branded version, or custom
• Download or export the current version of the form as a clean PDF with no pre-filled data
• Verify it is the most current version (check the form's effective date or revision code)

6b. Upload to the e-signature platform

• In the platform's template builder, upload the base PDF
• Confirm the upload renders cleanly (all pages visible, no rendering artifacts, orientation correct)

6c. Place signature, initial, date, and text fields

• Walk through the document page-by-page
• Place a signature field on every signer's signature line
• Place initial fields on every initial line (some forms have initial fields on every page — include all)
• Place date fields next to every signature or initial line that has a date requirement
• Place text fields for any field the VA needs to fill in per-transaction (property address, sale price, client name, dates)
• Place checkbox fields for any choice the signer needs to make (e.g., inspection contingency yes/no)

Field assignment rules:

• Every field gets assigned to a specific signer role, not left unassigned
• Signer roles use generic labels: Seller 1, Seller 2, Buyer 1, Buyer 2, Agent, Broker, VA (for any field the VA will fill before sending)
• For fields the VA fills before sending (like property address), mark as "VA complete before sending" or the platform equivalent
• For fields the signer must complete (like their name, initials, signature), mark as "Required" — never optional on a signature or initial

6d. Assign signer routing and order

• Set the signer order per the document's requirements (typically all sellers sign before the agent, or buyers sign before the seller for offers)
• If a broker signature is required, place it last in the order
• If the document has optional signers (e.g., a co-broker on the other side), mark them as optional; the platform will handle their inclusion or exclusion per envelope

6e. Save with the correct name (Section 7 convention)

6f. Dry-run test

Before the template goes into active use:

1. Create a test envelope from the template
2. Send to a test email you control (or a team member's test account)
3. Walk through the signer experience as if you were the client
4. Confirm every field is in the right place, assigned to the right role, and required where it should be
5. Sign, complete, and return the envelope
6. Confirm the completed envelope looks correct and all required fields were collected

Do not put a template into active use without a dry-run. A template error caught on a live transaction costs the agent time, credibility, and sometimes the deal.

---

7. Template Naming Convention

[Document Name] — [State or Board if applicable] — [Version Date]

Examples:

Listing Agreement — CA — 2026-03
Buyer Representation Agreement — WA — 2026-01
Purchase Agreement — NVAR — 2025-11
Seller Property Disclosure — OR — 2026-02
Contingency Removal — CA — 2025-09

Use the month of the form's effective date (not today's date) so that any template's name reflects the version of the underlying form.

Folder / category structure (if platform supports)

Group templates by category:
- Listings (Listing Agreement, Seller Disclosures, Listing Amendments)
- Buyers (Buyer Representation, Offer Package, Counter Offers)
- Transaction Coordination (Contingency Removals, Repair Requests, Amendments, Release)
- Administrative (Agency Disclosures, Transfer Disclosures, misc)

---

8. Template Maintenance

8a. Form updates

When the state, board, or brokerage releases a new version of any form:

1. Compare the new form side-by-side with the current template's base document
2. Identify every difference — new fields, removed fields, reordered fields, language changes
3. Decide whether to update the existing template or create a new one:
   - Minor field-position changes: update the existing template
   - Substantive form-structure changes (new required fields, removed fields, legal-language updates): retire the existing template and create a new one with the updated version date
4. Build the updated template following the Section 6 process
5. Run the dry-run test
6. Update the template index to reflect the change
7. Notify the agent of the update: which template changed, what changed, and when it becomes active

8b. Annual review

Once per year (typically January), review every active template for:

• Form currency: Is the underlying form still the most current version? Check state-association, local-board, and brokerage sources
• Field accuracy: Do all placed fields still make sense? Did any form section move or get reformatted?
• Signer role correctness: Do the signer roles still reflect how the agent's team operates (solo agent, team, broker involvement)?
• Usage data: Which templates are being used? Which aren't? Retire unused templates to reduce clutter

Create a short annual template review memo (1–2 pages) documenting what was reviewed, what was updated, and any templates retired. File in the operations folder.

8c. Retired template handling

• Move retired templates to an "Archived" folder, don't delete them (they may be needed for historical reference)
• Update the template index to mark them retired with the retirement date and reason

Forms that expire have real consequences. Using an outdated form can invalidate a signature, expose the agent to E&O claims, or create problems at closing. The 30-day update window is not optional.

---

9. Sending for Signature

9a. Start from a template

• Navigate to the template in the platform
• Start a new envelope from the template
• The platform pre-populates all fields, signer roles, and routing

9b. Complete the VA-fill fields

• Property address, sale price, names, dates, checkbox selections — whatever the VA needs to fill before sending
• Double-check against the transaction file; any data error here propagates into a signed document

9c. Add signers with correct contact info

• Add each signer's name and email to the template's placeholder roles
• Cross-check every email against the transaction file — a typo sends the envelope to the wrong person, potentially with personally identifiable information
• If the agent has a preferred internal review step before sending, route to the agent first

9d. Set signing order

• For most real estate documents, the standard order is: Clients first (Seller 1, Seller 2 OR Buyer 1, Buyer 2), then Agent, then Broker (if required)
• For counter offers and negotiations, the order follows the negotiation (the party making the offer signs first, the other party signs in response)
• Confirm the order in the envelope preview before sending

9e. Set expiration

Default expiration for most platforms is 7–14 days. Adjust for the specific transaction:
- Urgent closings or time-sensitive offers: 24–72 hours
- Standard contracts: 7 days
- Documents waiting on third-party input: 14 days

9f. Send and monitor

• Send the envelope
• Confirm the system shows "Sent" with all intended recipients
• Track the envelope's status (typically: sent → viewed → completed → completed, fully executed)
• Send a brief heads-up to signers if they've not viewed within 4 hours: "Quick note — I sent the [document] a few hours ago. Let me know if you need help accessing it or if it landed in spam."

9g. Post-signature handling

• Download the completed envelope as a PDF with the certificate of completion
• File in the transaction folder using the agent's standard naming convention
• Update the transaction status in the TMS
• If the document is the listing agreement, disclose, or offer, trigger the appropriate downstream SOP

---

10. Escalation — When to Escalate Immediately

Template issues that require immediate agent contact:

• Dry-run test fails on a new template and you cannot diagnose the issue
• Form update discovered post-signing — a signed document used an outdated form
• Template accidentally sent to an unintended recipient (email typo or wrong client selection)
• Platform outage during critical send window
• Missing or mis-routed field discovered after an envelope is in flight

Use this escalation template:

Hi [Agent Name] — e-signature issue:

Issue: [One sentence — e.g., "Template 'Listing Agreement — CA — 2026-03' is missing the initial field on page 5. I caught it on the dry-run before sending."]
Impact: [Specific — e.g., "Template not yet used on a live transaction; no signed documents affected."]
What I need from you: [Specific — e.g., "Please review the corrected template. Can send for your sign-off in 10 min."]

[VA Name]

If an envelope was sent in error to a wrong recipient:
1. Immediately void the envelope in the platform
2. Notify the agent within 5 minutes
3. Document the incident (to whom, what was visible, when voided) — file in the operations folder
4. If personally identifiable information or contract terms were visible in what the wrong recipient could see, flag the compliance implication to the agent

If the agent is unreachable: Void any in-flight envelope sent in error immediately — do not wait for agent approval to void a misdirected send. For all other escalation items, hold pending action and document. Attempt the secondary contact channel. For platform outages during a critical send window, note the timestamp and document which transaction is affected so no deadline is missed.

---

11. Completion Checklist

New template build
- ☐ Agent confirmed the base document to use
- ☐ Base document uploaded, renders cleanly
- ☐ All signature, initial, date, text, and checkbox fields placed
- ☐ Every field assigned to the correct signer role
- ☐ Signer order set correctly
- ☐ Template named per convention (Section 7)
- ☐ Dry-run test passed
- ☐ Template index updated

Template update
- ☐ New form version compared to current template
- ☐ Differences documented
- ☐ Updated template built and dry-run tested
- ☐ Prior template archived with retirement date and reason
- ☐ Template index updated
- ☐ Agent notified of the change

Annual review
- ☐ Every active template reviewed for form currency
- ☐ Every active template reviewed for field accuracy
- ☐ Signer roles reviewed against current team structure
- ☐ Usage data reviewed; unused templates retired
- ☐ Annual template review memo filed

Per-transaction send
- ☐ Envelope started from correct template
- ☐ VA-fill fields completed and cross-checked against transaction file
- ☐ Signer names and emails cross-checked against transaction file
- ☐ Signing order confirmed correct
- ☐ Expiration set appropriately
- ☐ Envelope sent
- ☐ Completion downloaded and filed after signing

---

12. Tools & Access

Item	Details
E-signature platform	[Confirm during onboarding — DocuSign, DotLoop, Authentisign, Skyslope DigiSign, other]
Platform account tier	[Confirm during onboarding — impacts template count and features]
VA access level	[Confirm during onboarding — typically "User" or "Sender" on the agent's account]
State-association form library	[Confirm during onboarding — e.g., CAR for California, NVAR, TREC, etc.]
Local-board form library (if applicable)	[Confirm during onboarding]
Brokerage form library (if applicable)	[Confirm during onboarding]
Operations folder (template index)	[Confirm during onboarding — Google Drive or other]
Transaction management system	[Confirm during onboarding — for post-signature filing]
Test email address for dry runs	[Confirm during onboarding]