Order of precedence when vendor terms conflict with yours

Reference article · 5 min read

A technology purchase rarely lives in one document. By the time an agency signs, the deal may include a base contract, the solicitation and the vendor's response, a statement of work, an order form, and a set of online policies the order form points to by web address. Each says something about scope, availability, data handling, liability, and termination, and they do not say the same things. The order of precedence clause tells a reader, months or years later, which sentence controls.

Agencies that treat precedence as boilerplate tend to discover the problem during a dispute, when a vendor points to a line in an online policy that quietly reverses a negotiated protection. The work is not complicated, but it has to happen before signature. Decide the stack, write it down, and make sure every document allowed into it is one your contract file actually contains.

Inventory the stack before you rank it

Ask the vendor for a written list of every document it intends to make part of the agreement, including anything referenced inside those documents:

• The negotiated agreement. Base terms and conditions, plus any rider, addendum, or amendment.
• Solicitation and response. The RFP or IFB with attachments, and the vendor's proposal, including clarifications and best and final offers.
• Statement of work. Deliverables, milestones, acceptance criteria, and the implementation plan.
• Order form or quote. Products, quantities, subscription term, and price.
• Referenced online terms. License or subscription terms, a data processing addendum, an acceptable use policy, a service level agreement, support policies, and third party or open source notices.

Then apply one rule: if a document is not on that list, nothing else may reference it into the agreement.

Write the precedence clause so it reaches everything

State the hierarchy explicitly rather than relying on a general rule that the more specific document wins. An agency-favorable order usually runs: signed amendments, later ones over earlier; the negotiated agreement; the solicitation; the statement of work; the vendor's proposal; the order form, limited to products, quantities, term, and price; and last, referenced vendor policies.

Three drafting points do most of the work. Apply the clause to conflicts, inconsistencies, and ambiguities across all listed documents. State that no preprinted or click-accepted terms presented during ordering, installation, login, or support have any effect, regardless of who at the agency clicked. And state that the clause survives renewals, change orders, and later orders under the same agreement.

Pin referenced terms to a dated copy

Terms incorporated by web address are the least stable part of the stack, because the vendor controls the page. Convert them into fixed documents.

• Capture and attach. Save each referenced policy as a dated file, attach it as a numbered exhibit, and replace the web address with a reference to the exhibit.
• Date the reference if capture is refused. At minimum, incorporate the version in effect on the effective date, not the version in effect from time to time.
• Flatten nested references. Many online policies incorporate further policies. Require that any sub-reference not listed and attached is excluded.
• Read the data terms against your own rules. Data location, subprocessors, breach notice timing, retention, and export at termination are where vendor policies most often conflict with state requirements.

Strike unilateral amendment rights

Look for phrases such as we may update these terms from time to time, the current version posted at, and continued use constitutes acceptance. These are ordinary in commercial software and difficult for public buyers, because agency contract changes generally must be executed by an authorized officer, and because funding and records obligations do not bend to a posted update online.

Replace them with a written amendment requirement signed by both parties. If the vendor needs flexibility, negotiate narrow carve outs: changes required by law, and security improvements that do not reduce agency rights or raise cost. For feature removal or platform migration, ask for advance notice, continued support for a defined period, and a termination right with a refund of prepaid unused fees.

When the vendor says its paper is standard

Standard describes a vendor's default, not a legal limit. Ask which clause cannot change and why. Some answers are real, such as a flow down from a third party license. Most are habit.

• Ask whether a public sector addendum exists. Many vendors maintain one.
• Ask whether the product is available on a cooperative or statewide contract whose terms a public entity negotiated.
• Sort clauses into three piles: genuinely fixed, movable with escalation, and merely untested.
• If a term truly cannot move, exclude that section by number rather than accept the whole document, and manage the risk another way, such as a shorter term or a termination for convenience right.

Say early, in writing, which of your terms are set by statute or policy rather than preference. Provisions on immunity, indemnification, choice of law and venue, payment timing, automatic renewal, and public records disclosure are often constrained by state or local law, and those rules vary. Confirm current requirements with counsel rather than assuming last year's language still applies.

Keep the stack intact after award

Most precedence failures happen after signature, when a new module, renewal, or change order arrives on a fresh vendor form carrying fresh terms. Require every future order to reference the base agreement by name and date, state that no other terms apply, and route through the same review as the original. Keep the dated exhibits with the executed contract so the next reader can see which version governs.

HQT is a technology and software company focused on state and local government systems. Technical staff are often asked to review the operational terms buried in these documents, and that review is most useful before award.

Frequently asked questions