WeavrCRM

Field guide / Scheduling & operations

A Detailing Subcontractor Work Order That Prevents Guesswork

When you send a subcontractor to a customer's vehicle, two separate agreements exist: what the customer approved and what you promised the vendor. A work order is the document that covers the vendor's side. Without one, your sub may upsell unauthorized services, skip steps, or dispute payout at the end of the job. This template gives you a single-page document you can copy, fill in, and send before every subcontracted appointment.

By WeavrCRM Editorial ·

Why a Work Order Is Different from Your Customer Quote

Your customer quote or invoice shows what the customer agreed to pay your business. The subcontractor work order shows what your vendor is authorized to do, where to go, and what you will pay them. These are two distinct documents. Mixing the numbers creates real problems: a vendor who sees your full customer price may pressure the customer for a tip on the markup, or learn your margin and start undercutting you directly.

Keep the documents separate. The work order references the job without revealing what the customer paid. List only the vendor payout, the defined scope, and the conditions for approval. Everything else stays internal. This is an operational practice, not a legal employment determination. How your vendor is classified for tax and labor purposes is a separate question for a qualified professional.

The Eight Fields Every Work Order Needs

A work order does not need to be long. It needs to be unambiguous. Eight fields cover the facts a vendor needs to show up, do the right work, and get paid. Anything beyond that is clutter that gets ignored.

Missing even one of these fields creates a gap the vendor will fill with their own judgment. That is where scope creep, access problems, and payout disputes come from. Fill in every field before you send it, even if some answers are obvious to you.

  • Work order number and issue date
  • Job date, start window, and expected duration
  • Service location address and any access notes (gate code, parking, who to contact on arrival)
  • Authorized services with specific descriptions, not just package names
  • Any services explicitly excluded or requiring your approval before performing
  • Completion evidence required (photos, checklist sign-off, timer stop)
  • Vendor payout amount and payment trigger (completion approval, not invoice submission)
  • Your contact number for questions during the job

Related resource: Detailing Team Handoffs: What the Next Person Needs

Copyable Work Order Template

Copy this into a plain document, fill in every bracketed field, and send it to your vendor before the appointment. Do not leave any field blank. If a field does not apply, write N/A so the vendor knows you considered it.

This template is an operational starting point, not a legal contract. Have a qualified professional review any agreement you intend to be legally binding, especially if it addresses worker classification, liability, or payment disputes.

DETAILING SUBCONTRACTOR WORK ORDER

Work Order #: [WO-XXXX]
Issue Date: [MM/DD/YYYY]
Issuing Business: [Your Business Name]
Your Contact: [Your Phone Number]

--- JOB DETAILS ---
Job Date: [MM/DD/YYYY]
Arrival Window: [Start Time] to [Latest Arrival Time]
Expected Duration: [X hours]

--- LOCATION AND ACCESS ---
Address: [Full street address]
Parking / Setup Notes: [Where to park water tank, generator, etc.]
Site Access: [Gate code, keypad, contact name, key pickup, etc.]
On-Site Contact (if any): [Name and phone]

--- AUTHORIZED SCOPE ---
You are authorized to perform the following services only:
  1. [Specific service, e.g., Full interior vacuum and wipe-down, all surfaces]
  2. [Specific service, e.g., Exterior hand wash and clay bar]
  3. [Specific service, e.g., Single-stage paint sealant application]

Excluded or Requires Approval Before Performing:
  - [e.g., Engine bay cleaning — call before starting]
  - [e.g., Stain treatment beyond standard extraction — call for approval]
  - [e.g., Any service not listed above]

Do not perform any service not listed without contacting [Your Name] at [Your Phone].

--- COMPLETION EVIDENCE REQUIRED ---
Before leaving the vehicle, you must submit:
  [ ] Before and after photos of each authorized service area
  [ ] Completed checklist (attached or linked separately)
  [ ] Job end time noted (photo of clock, timer screenshot, or CRM stop)

Evidence sent to: [Your email or messaging method]

--- PAYOUT ---
Vendor Payout for This Job: $[Amount] USD (hypothetical example)
Payment Trigger: Evidence reviewed and job approved by [Your Name]
Expected Payment Date: [e.g., Friday of the week the job is completed]
Payment Method: [Check / ACH / etc.]

Note: Payout is for authorized scope only. Unapproved services performed without prior approval may not be compensated.

--- ACKNOWLEDGMENT ---
By accepting this work order, you confirm you have read the authorized scope, understand the exclusions, and will submit required evidence before leaving the job site.

Vendor Name: ______________________________
Signature: ________________________________  Date: ____________

Worked Scenario: A Ceramic Coating Referral Job

Hypothetical example: You book a ceramic coating prep and base coat application for a customer's SUV. You charge the customer $480 for the full service. You have agreed to pay your ceramic-certified subcontractor $210 for labor, which covers paint decontamination, a light single-pass polish, and one coat of ceramic. You issue work order WO-0041.

The work order lists those three steps, explicitly excludes a second coat and any interior work, and requires ten photos submitted to your phone before the vendor leaves. Your vendor texts you the photos at 3:40 PM. You review them, confirm the panels look uniform, and approve payout. Payment goes out that Friday for $210. The customer pays you $480 through your usual invoicing process. The vendor never sees either of those numbers except their own $210 payout line. The customer never sees that you used a subcontractor or what they were paid. No guesswork on either side.

Setting the Payout Trigger Correctly

The single most common payout dispute happens when a vendor considers the job done when they leave the driveway, but you consider it done when you verify the evidence. Spell out the trigger before the job, not after. The trigger should be your approval of submitted evidence, not the vendor's own declaration of completion.

This does not mean you drag out payment to save cash. Set a clear, reasonable review window, such as same day or next business morning, and stick to it. Vendors who trust you will pay on time as agreed are far more reliable than vendors who have been slow-rolled before. Predictable payment is one of the cheapest ways to keep a good subcontractor loyal.

Related resource: Verify Subcontractor Booking Requests Before Promising a Slot

Handling Scope Changes Mid-Job

Sometimes a vendor finds something unexpected: a headliner with mold, a pet-hair situation the customer did not mention, or a scratch the customer asks to have addressed on the spot. Without a clear process, vendors either do it and expect payment, or refuse and create a bad customer experience.

The work order's excluded-services line handles this. If it requires approval before performing, the vendor calls you, you decide whether to authorize it and at what add-on payout, and you give verbal approval they can reference. Follow up with a written addendum or text confirmation the same day. If the vendor performs an unapproved service without calling, you have a documented basis to discuss whether you compensate it. No promises about legal enforceability, but clear documentation makes the conversation far less ambiguous.

Failure Cases to Know Before You Use This

A work order reduces guesswork but does not eliminate every risk. A vendor who ignores the exclusions list and performs extra services anyway still creates a problem. A customer who directly tips or rehires your vendor is a business risk no document prevents. If your vendor is not reliable, the work order shows you where the breakdown occurred, but it does not fix the relationship.

The other failure case is your own: sending an incomplete work order, leaving the payout field blank, or forgetting to include access codes. Vendors filling in blanks with assumptions is exactly the problem a work order is supposed to prevent. Build a quick pre-send check into your process so you never issue one with empty fields.

  • Incomplete access notes lead to vendors waiting or leaving without starting
  • Vague scope descriptions like 'full detail' invite vendors to interpret broadly
  • No photo requirement means you cannot verify quality before approving payout
  • Forgetting to separate customer price from vendor payout risks exposing your margin
  • No addendum process means mid-job changes become informal and unprovable

Organizing Work Orders in Your Workflow

A work order only works if it is issued before the job and filed somewhere you can retrieve it when payment is due. Attach a PDF or text copy to the appointment record in whatever tool you use to manage jobs. If you use Weavr, the linked task and notes area on a scheduled appointment gives you a place to log the work order number and flag the job for payout review once evidence comes in. That way the job record, the vendor payout, and the evidence log are connected rather than spread across your inbox.

After the job, keep the issued work order and the submitted evidence together for at least long enough to clear any payment dispute. If you reconcile vendor payouts weekly, a folder by week works fine. The goal is that if a vendor questions their payment three weeks later, you can pull the original authorized scope, the evidence photos, and the payout approval in under two minutes.

Related resource: Reconcile Completed Vendor Jobs Before Approving Payouts

The practical takeaway

Fill in every field of the work order before sending it, keep the vendor payout separate from the customer price, and tie payout to your approval of submitted evidence rather than the vendor's own say-so. A blank field is an invitation for a dispute.

Explore the relevant WeavrCRM workflow · Review integrations and requirements

Continue reading