The Scope Behind the Price: Why Fleet Service Proposals Are Not Always Comparable

Scope gaps do not remain paperwork problems.

They become change requests, schedule conflicts, additional preparation, disputed expectations, incomplete documentation, and vehicles that remain unavailable longer than planned. A proposal can be accurate according to the provider’s assumptions and still fail to match what the fleet believed it requested.

Formal procurement systems address this problem by defining the need before evaluating the price. The Georgia Procurement Manual distinguishes between purchases that can be described through clear specifications and those that require technical and cost factors to determine best value. It also directs state procurement professionals to use cost worksheets that identify the same items and units of measure so supplier pricing can be compared consistently. [1]

The Georgia Procurement Manual governs state entities subject to the Georgia Department of Administrative Services. Its requirements should not be assumed to govern a school district, municipality, or private fleet. Each organization must follow its own applicable policies, law, and funding conditions. The underlying management principle is still useful: first establish what is being purchased, then determine whether each proposal meets that requirement, and only then compare price.

A service name is a category. It is not a complete scope.

Fleet washing can describe anything from a defined exterior wash on regularly maintained vehicles to a more involved reset of heavily contaminated units. The vehicle count may be identical while the buildup, surface types, access, water-management responsibilities, and acceptance standard are not.

Ceramic coating can refer to different protected surfaces, different levels of decontamination or correction, different coating systems, and different cure, documentation, warranty, and aftercare requirements.

Roof preservation can include different assumptions about existing coating condition, seams and penetrations, corrective preparation, primer, finish layers, access, weather windows, inspection, and repair limits.

None of those differences proves that one provider is more responsible than another. It proves only that the same service name can describe different work.

A useful comparison begins with one common baseline.

The fleet should identify the exact units involved, the surfaces included, the known condition of those surfaces, the desired result, the expected work window, and any operating constraints that every provider must address. When condition varies across the fleet, the scope should say how that variation will be handled rather than assuming every unit requires identical effort.

The requested outcome also needs definition. “Clean,” “protected,” and “preserved” can sound specific while leaving room for very different interpretations. A better scope explains what the fleet expects to be complete, what condition is acceptable at handoff, what documentation should be provided, and what work is outside the assignment.

Federal procurement standards for purchases made under a federal award use the same basic discipline. Solicitations must provide a clear and accurate description of technical requirements and identify the factors that will be used to evaluate offers. [2] That rule applies within its federal funding context, but the comparison principle is broader: suppliers cannot price the same requirement when the requirement has not been made clear.

Surface work is especially sensitive to starting condition.

Two buses of the same model year can require different preparation because they have been washed differently, stored differently, repaired differently, or exposed to different operating environments. One finish may be serviceable with routine preparation. Another may require additional decontamination, correction, sealing, or repair before the proposed service can begin.

A proposal should therefore explain the preparation included in the price and the condition assumptions behind it. That may include cleaning, bonded-contamination removal, masking, test areas, correction limits, correctable seam work, drying, or other service-specific steps. The fleet does not need to prescribe a contractor’s entire technical method. It does need enough detail to understand the promised result and the work used to reach it.

If additional preparation is discovered after work begins, the proposal should explain how it will be handled. The provider may include a defined allowance, identify unit prices, require written authorization, or exclude the condition entirely. Any of those approaches can be reasonable when it is stated clearly.

Unstated preparation is where price comparisons begin to drift.

A product name may identify the material without describing the entire installation.

The proposal should make clear which system will be used, where it will be applied, which surfaces are excluded, and what preparation and application requirements are included. Where layers, coverage, recoat windows, curing conditions, or manufacturer procedures matter, those expectations should be visible enough for the fleet to understand what constitutes completion.

Documentation belongs in the same conversation. Depending on the service and value of the project, the fleet may need a vehicle list, starting-condition photographs, completion photographs, product or system identification, application dates, noted exclusions, aftercare instructions, and warranty documents.

Warranty length alone is not a complete comparison. The fleet should understand who provides the warranty, what surfaces or failures it covers, what maintenance or inspection it requires, what conditions are excluded, and what remedy is available. A longer term may be valuable, but only when the fleet understands the obligations and protection behind it.

The work may also depend on vehicle staging, safe access, moving units, work-area availability, electricity, water, weather, surface temperature, washwater management, drying, cure time, and return-to-service coordination. The fleet or the provider may carry those responsibilities. Either arrangement can work when both parties understand it.

These details can create legitimate differences between proposals. The U.S. Environmental Protection Agency’s municipal vehicle-washing guidance, for example, identifies school buses among the vehicles covered by its best-practice discussion and notes that washwater controls and site practices can vary with the facility and applicable local requirements. [3] One washing proposal may therefore include site-protection or water-management responsibilities that another assigns to the fleet.

Mobilization and schedule assumptions matter as well. A proposal based on ten vehicles available together is not necessarily pricing the same operating plan as one that expects ten separate visits. A service window that allows uninterrupted work is different from one divided around routes, shifts, or daily vehicle release.

The comparison should identify the arrangement the fleet actually needs and which party has agreed to provide it.

Every proposal contains assumptions, whether they are written or not.

A provider may assume that the listed vehicles will be available on arrival, that surfaces are free from active failure, that repairs have already been completed, or that adequate work space will remain available. The fleet may assume that preparation, travel, protective masking, touch-up work, documentation, or a return visit is included.

When those assumptions differ, the original price can stop describing the final cost. Before offers are received, the solicitation or proposed contract should identify which conditions trigger a scope change, who can authorize additional work, how the price will be calculated, and how the schedule will be adjusted.

Although it applies to FTA recipients and FTA-assisted procurements rather than ordinary school-district purchasing, the Federal Transit Administration’s August 2026 guidance offers two useful comparison points. Evaluation factors should reflect the elements that matter to the buyer and should be disclosed in the solicitation. An unusually low offer can sometimes indicate a mistake or misunderstanding of the work, while a higher-priced best-value selection requires documented benefit sufficient to justify the premium. [4]

The appropriate response to an apparent gap must follow the applicable procurement process. Limited clarification may be permitted, but it cannot be used to negotiate or allow an offer to be revised or improved. A material mismatch may require rejection or another remedy allowed by the published rules. [1]

Once proposals arrive, the fleet should compare each one against the published requirement.

That means placing the material differences side by side: included vehicles and surfaces, condition assumptions, preparation, materials and application, site responsibilities, schedule, exclusions, documentation, warranty terms, aftercare, acceptance, and change authorization.

Some differences may be resolved through clarification where the published process permits it. Clarification cannot be used to change a material term, add criteria, or let a supplier revise or improve an offer. Other differences show genuinely different approaches or a failure to meet a material requirement. [1]

Price may properly dominate when the requirement is clear, performance risk is limited, and each offer meets the same standard. A lower responsive and responsible proposal can be the right decision. When the published evaluation method permits a best-value tradeoff, technical approach, experience, documentation, schedule, and accountability may also be considered, with the rationale for any higher-priced selection documented.

The purpose is to make price comparison meaningful and defensible.

A fleet should know how the work will be accepted before the work begins. Depending on the scope, handoff may include verifying completed units and documented exceptions, receiving required product and warranty information, resolving a punch list, and recording aftercare or return-to-service instructions.

For the state entities it governs, the Georgia Procurement Manual carries contract management through inspection, acceptance, warranties, performance tracking, and payment for accepted goods and services. [1] The proposal therefore becomes a reference for managing and verifying the result, not merely the initial price.

An invoice should not be the first place the fleet discovers what was included.