Writing a Clear Vendor Scope for Mobile Home Park Repairs

A vendor scope is the bridge between what a park operator sees and what a contractor is authorized to do. “Fix the porch” or “make the home ready” may feel clear to the person who wrote it, but those phrases can produce different interpretations, change orders, and incomplete handoffs. A useful scope describes the observed condition, the intended result, and the boundaries of the work without pretending to replace a licensed professional’s judgment.

Start with the observation

Describe what was seen, where it was seen, and when. “The rear entry landing has a loose tread reported during the August 25 inspection” is more useful than “unsafe porch.” Add the home identifier, location, photos if permitted, and the person who recorded the observation. If the finding came from a resident report, distinguish the report from an independently verified condition.

Avoid declaring a technical cause when it has not been assessed. Moisture staining may indicate several possible problems. A cracked surface may be cosmetic, structural, or part of a larger issue. The scope can request inspection and a written recommendation before repair, with an escalation requirement if the vendor finds a condition outside the authorized work.

Define the outcome in observable terms

The scope should say what completion looks like. For a damaged step, that may include a stable walking surface, secure attachment, appropriate disposal of removed material, and a completion photo. For a plumbing repair, it may include the identified connection repaired by the qualified person, a leak check, and documentation of any remaining limitation.

Do not specify a result the park cannot verify. “Guaranteed to last ten years” is not an acceptance check. “No visible leak at the repaired connection during the agreed test” is an observable condition, subject to the limits of the test and the vendor’s professional requirements.

Put assumptions and exclusions in plain language

Every scope has assumptions. Access may depend on a resident, utilities may need to remain on, or concealed damage may be unknown. List those assumptions and describe what happens if one is false. Exclusions are equally important: interior painting may be excluded from an exterior repair; appliance replacement may be excluded from a cleaning scope; code interpretation may require a qualified reviewer.

An exclusion is not a way to avoid a safety issue. If the vendor observes an immediate hazard, the scope should require the vendor to stop or secure the area according to their professional obligations and notify the park’s designated contact. The park then decides the next authorized step.

Use a small acceptance checklist

Before issuing the scope, identify three to seven checks. Confirm the correct home and work area. Confirm the authorized work was performed. Check that debris and temporary protection were handled. Capture photos or documents required by policy. Record any punch-list item with an owner and date.

The person accepting work does not need to duplicate a licensed inspection. Their role is to confirm the contracted work appears complete and to flag discrepancies. If the work requires a permit, certification, or specialist signoff, identify that evidence explicitly and route it to the correct reviewer.

Control change requests

Change requests should not arrive only as a surprise on an invoice. Ask the vendor to pause and provide the new condition, why it is outside scope, proposed work, urgency, and any effect on the sequence. The authorized decision-maker records approval, rejection, or a request for more information.

For emergency conditions, the process may allow limited immediate action. Even then, capture the reason, time, person notified, and work performed afterward. Good records distinguish an urgent response from a broad, unreviewed expansion of the job.

Match the scope to the handoff

Send the vendor the information needed to work safely and identify the home, but avoid unnecessary resident personal information. Include access instructions, known utility constraints, scheduling windows, site rules, and the contact for questions. When work closes, return the same record with completion evidence and unresolved items.

Review scopes that repeatedly generate changes or callbacks. Patterns may indicate unclear observations, missing acceptance criteria, poor sequencing, or a maintenance issue that needs a different intervention. Clear vendor scopes help mobile home park teams spend attention on decisions rather than translating vague notes after the fact.

Make the invoice understandable

Close the scope only after the acceptance checks are recorded. If a recommendation is outside scope, create a new review item rather than burying it in the completion note. This preserves the distinction between contracted work and a future decision.

Use the scope as a handoff record. Send only the access information, site rules, utility constraints, schedule window, and contact needed for safe authorized work. At completion, return the same record with evidence, a punch-list, and any recommendation outside scope. A recurring pattern of changes may show that the initial observation was too vague or that the work belongs in a different project. Reviewing those patterns helps the park improve future scopes without blaming a vendor or promising a result no one can verify.

Use the home identifier, work area, authorized task, assumptions, and required completion evidence so the later invoice can be matched to the scope. If inspection and repair require separate approvals, say so. For recurring work, define the visit boundary and what the vendor must report when the normal condition is absent. When a scope changes, link the original, request, decision, and resulting instruction. A later reviewer can then distinguish a concealed condition, access issue, authorized improvement, or vendor error instead of treating every difference as an unexplained charge.