The Scope Split Document — The Page That Decides a Modular Purchase
The Short Version
Every modular project has a scope split; the only question is whether it is written before production or discovered at set day. This guide draws the document line by line — and names the orphan lines that sink schedules.
What the document is
A line-by-line assignment of every element of the finished building to a named engineer: the box to the plant's team under the program; the foundation, anchorage, laterals, seams, and site-built elements to the site side's licensees. Each line carries an owner, a deliverable, and a date. It is agreed before production starts, because after the first unit rolls, every unowned line is a change order looking for a signature.
The orphan lines
Certain lines go unowned so reliably they have a pattern: the crossover points where in-box plumbing meets site laterals; the anchorage pattern when the plant's loads arrive after the footings are poured; the fire continuity where a rated wall ships in two halves; the stairs, ramps, and canopies that are 'site-built' in every contract and designed in none. Read any split document for these four lines first — their ownership is the document's honesty test.
How to use it in negotiation
Send the split request with the request for pricing, not after it. A company's response sorts the field faster than any reference call: the serious ones return a document with names; the rest return enthusiasm. Price the offers only after the splits are on the table — a cheaper offer with three orphan lines is not cheaper; it is deferred.
