If you sign the quote because one line says design and installation coordination included, and the supplier cited ASTM F2970 somewhere up the email thread, you have signed an adjective. Weeks later the crew stands in front of a slab, the anchor layout turns out to be nobody's line item, and the schedule starts burning while two offices trade messages about who was supposed to scope it. The equipment arrived. The responsibility did not.
The failure is rarely a manufacturer refusing to carry responsibility. It is an RFQ that never asked which of the roles named in the standard's public scope this particular quote covers. Buyers compare suppliers on standards mentioned instead of duties accepted, and the distance between those two things is what lands on install day.
Where a Trampoline Park Manufacturer's Design Scope Ends
The handoff is not the shipping date. It is the moment design decisions, construction work, manufacturing, installation and inspection duties move from one participant to another, and each of those moves needs a name attached before it happens. The public scope of ASTM F2970-25 describes a practice that applies to architects, designers, engineers, construction contractors, manufacturers, appropriate inspectors, owners and operators involved with the design, construction, manufacture, installation, operation, maintenance, inspection or major modification of institutional trampoline courts. The manufacturer is one line in that list.
The same document says what it is for: providing consistent criteria, references and operational considerations in the specifications, management and construction of institutional trampoline courts. That is a statement about what the document offers. It is not a statement about which contract party performs which task, and it cannot be, because the audiences named in it sit on opposite sides of a purchase order.
An ordinary equipment purchase order defines two things, the product and the price. A trampoline court project has to define who carries each role on this build. The common mistake is to spot manufacturer in the scope list and read the whole package as turnkey: design, fabrication, install and sign-off from one vendor. The damage is quiet rather than dramatic. Both sides hold a different reading, and nothing surfaces until a crew is standing around waiting. Copy the role list onto one page and ask, role by role, who carries it on this project.
Why 'We Follow ASTM F2970' Settles Nothing
Read the standard's own description literally. It promises consistent criteria, references and operational considerations for specifications, management and construction. Nothing in that sentence assigns a duty to a party. A standard reference and a responsibility allocation are two separate documents, and only one of them is attached to your quote.
The obvious objection is that a supplier who names the standard must be more careful than one who does not, and careful suppliers are the ones worth shortlisting. Fair, but the question here is not diligence. It is coverage. A document addressed to architects, construction contractors, manufacturers, inspectors and owners at the same time cannot tell you which segment this supplier accepted, and a supplier can be entirely diligent while believing the anchor interface belongs to your concrete contractor.
Treating the citation as a responsibility list is the mistake. The consequence lands in the contract as white space, and white space is where install-day arguments live. The fix costs one email: ask the supplier to state, line by line, which roles it accepts, which it expects from you, and which it treats as shared.
The Handoff Mistake That Shows Up on Install Day
Suppose a quote comes back with design and installation coordination included plus a delivery window, and the buyer reads coordination as ownership. On site, the foundation tolerances and the anchor interface have no named owner on either side. No owner. Work stops. Then the day goes into a long exchange in which each party explains, reasonably and in good faith, why the interface nobody discussed belongs to the other one, while the crew idles and the schedule slips with every round of clarification that has to travel back to whoever wrote the original scope.
Assigning responsibility with an adjective is the mistake. Coordination, turnkey, full service: all three describe a mood, not a task. Consequences are a stopped site, standby charges and a relationship that starts on the defensive. The correct move is to rewrite each role named in the public scope as a line item and ask the supplier to mark ours, yours or shared, without pre-filling any answer.
That line-item table is your construction, not something the standard text supplies; the public scope hands you role categories and stops there. No supplier quote, MOQ, lead time or customization authority exists for this project yet, so nobody can promise in advance which rows a given factory will accept. What you can do is make refusal visible early, while switching suppliers is still cheap.
Name the Sign-Off, Not the Install Date Alone
Before work starts, put four questions in the procurement file: who signs acceptance at the handoff, which drawings and submittals travel with it, which inspection records the owner keeps, and what the supplier will and will not commit to in writing. Owners and operators appear in the same scope sentence as appropriate inspectors and manufacturers, which is why who signs has to be written next to who does. A signature with no named role behind it is decoration.
Reading installation included as a complete scope clause is what goes wrong here. At handoff nothing then transfers but keys: no drawing set, no submittal log, no record of who inspected what. Build a single-page handoff sheet with four columns, role, item, signer and date, and fill it from your own project needs rather than presenting it as a standard requirement.
A Standards Reference Is Not an Injury Guarantee
The public text says plainly that the standard does not purport to address all of the hazards associated with institutional trampoline courts, that its existence alone will not prevent injuries, and that use involves the risk of injury, particularly if equipment is used improperly or if users exceed their capabilities, endurance, training or experience. Your acceptance file therefore records coverage, not outcome, and it should be worded that way.
A skeptic would say this is legal boilerplate and buyers should move on to prices. The reverse holds: that paragraph decides whether your handoff file can be relied on years later, when somebody asks what the project actually verified and what it merely referenced. Keep the disclaimer's original wording beside the acceptance record instead of paraphrasing it into something friendlier.
An inspection signature is not an injury-prevention promise, and reading it as one shifts the consequence onto the owner, who then misjudges who carries residual risk. The fix is to keep both halves in one file: what was done on this project, and what the standard states it does not cover.
Put Role Ownership in the RFQ Before Price
Sequence the RFQ this way. First fix the role table. Then ask what object changes hands at each boundary, whether that is a drawing, a submittal, a record or a signature. Only then compare price, MOQ, lead time and sample terms. One shared table is what makes competing quotes comparable, because without it each quote is priced against a different scope.
None of those commercial numbers appear in this article. No valid quotes, MOQ figures, lead times, capacity data, customization permissions or sample test results were obtained here, and inventing them would produce a comparison you cannot defend internally. They come from your own RFQ replies.
Price comparisons made before roles are fixed punish you twice: the cheapest quote looks the most complete because its scope is the vaguest. Put the role table on the front page of every comparison so the numbers are answering the same question.
Run the same project a second time and the buyer from the opening scene attaches one extra page to the RFQ. Negotiation slows, with suppliers pushing back on rows they would rather leave as coordination, but on install day nobody asks whose interface it is, because the answer was marked in a column months earlier. That page does quieter work too: price, MOQ and lead time finally get measured against one scope. If the rows are not all marked, the quote is not ready to sign.