Building Landscaping Scopes of Work for RFPs

“A SOW is an acronym for a scope of work, and it’s important to have one to avoid contractors making assumptions about what you may or may not want, or what your ownership may or may not want with regards to the level of service and quality of your landscape management. It is important to be clear with your scope of work and what your expectations are, so you’re getting a service that will meet your needs” says John Wetherald, Director of Business Development at Russell Landscape. SOWs are in place to define the expectations or end result of an RFP. RFP stands for request for proposal and is used by property managers and owners to define the scope of work, evaluation standards, pricing, and more. An RFP usually includes an SOW, job requirements and specifications, a pricing matrix, scheduling information, bid form requirements, and more. Having well-defined and detailed SOWs included in RFPs is incredibly helpful towards making expectations and standards clear. Confusion can bring conflict and misunderstandings that hinder progress in projects.

Expectations

Wetherald emphasizes the importance of performance expectations. If performance expectations are explicit in an SOW, there is little room for confusion and miscommunication. Industry standards can differ by state. “Industry standard in Atlanta is typically 51 visits, but in somewhere like Nashville, it’s usually 42 where you visit biweekly” explains Wetherald. Understanding the different industry standards in your city or state help our property make more informed decisions about your expectations. Often, the expectations at properties are aesthetic and outcome based. This is another reason why performance specifications are so important when curating an SOW for a project. “The expectation, in my opinion, is that you do whatever it needs to be done to make sure that the properties look the way that you expect it to” says Wetherald.

Dos and Don’ts of SOWs

Wetherald advises against exclusively using past SOWs to curate RFPs.

“One of the one of the problems that we see a lot is that people take scopes from other previously used documents, and they don’t always apply to the level of expectation that they have on a property” explains Wetherald. Using past SOWs for current RFPs can create miscommunications between property management and contractors because they might not include the level of service that meets the property’s expectations on a specific project. This issue can be avoided by utilizing advice from service providers to guide their curation of an SOW or an RFP. Wetherald advises “property managers or owners should reach out to their service providers to help them write scopes of work for each of their individual and different traits.”

“I am always more than happy to help a customer or friend go through what their expectations are and how to put together a scope of work that their confident will get similar pricing and scopes from their vendors.” “One of the things that I always ask for people to avoid are our