Who writes the Scope of Work?

Looks good to me. What's the issue?

You may be wondering  why am I only using images showing construction deficiencies? What about using pretty staged photos of completed projects?

Well, it's because stuff like this happens day-in and day-out on-site, especially when there are no rules governing the build.  The real question is, why wasn't the work governed by a Scope of Work (SOW) in the first place?

If there is no SOW, correcting deficiencies requires a great deal of effort to convince everyone involved the work fails to meet expectations, has been damaged by others or is incomplete.

OK, so who writes the SOW?

The SOW is prepared by the architectural firm/designer and outlines the responsibilities of all the parties involved - client, contractor and all of the different trades too. This way expectations are described clearly and openly before the work begins, allowing a dialogue about the work performed to be judged against the rules governing the work.  No more "that's just the way it is" stuff or "you know nothing of construction!" rants either.

If a contractor rips out or damages previous work, alters existing work or somehow does something creatively and inexplicably incomprehensible, the SOW describes what the remedy is and the process used to fix the issue. Long winded time wasting discussions about what celestial event influenced the decision making at that point in time are avoided.

The SOW defines the roles, responsibilities of all involved, the work to be performed, storage of materials, how the work will be done and the process used to fix things. This SOW is the firm hand on the rudder preventing the energy of the project from drifting sideways towards the abyss of chaos.

---

The framer pulled the air conditioner's lineset down before framing the dropped ceiling - because the lineset was in the way?