A prime with a specialist partner it uses repeatedly has a choice about where the friction lives. Negotiate a fresh subcontract for every task order and the friction lands on the program manager who needs engineers next month, which is why that manager keeps using whatever instrument is already in place. Negotiate once, thoroughly, and issue task orders underneath it, and the friction moves to a single hard conversation that happens one time. The second arrangement is a master subcontract, and setting one up well is among the highest-return things a subcontracts organization can do with a quarter's attention.
This is written for the subcontracts manager doing that work: what the agreement should carry, what belongs in a task order instead, the clauses where the two sides genuinely disagree, and the positions each usually takes. The subject is technology work: software, AI, data platforms, cloud. Those pursuits have specific problems around intellectual property, data rights, security and acceptance that a generic services template handles badly.
The split: what goes in the master, what goes in the task order
Get this boundary right and everything else follows. The master carries everything that is true of the relationship. The task order carries everything that is true of one piece of work.
In the master: the parties and the term. Order of precedence. Flow-down clauses. Rate structure or pricing method and how rates adjust. Intellectual property and license grants. Data rights and marking obligations. Confidentiality and handling of government data. Security requirements, incident reporting and subcontractor personnel screening. Insurance. Invoicing and payment. Changes, disputes and termination. Key personnel and substitution. Non-solicitation. Records and audit. Export control and representations. Warranty and acceptance mechanics. Publicity and past performance use.
In the task order: the statement of work. Deliverables and the acceptance criteria for each. Period of performance and milestones. Price, or the labor mix and ceiling. The named individuals and their allocation. The specific contract the work supports, so the correct flow-downs attach. Government-furnished items and access dates. The point of contact on each side authorized to approve a change.
The failure mode is a master that is so general it settles nothing, so every task order reopens intellectual property, rates and acceptance. If a topic will be argued about on every order, it belongs in the master with a stated position and a narrow mechanism for variation.
Clauses ranked by how often they stall a technology subcontract negotiation
Editorial weighting, illustrative rather than measured. The last row is low because it is argued about loudly and settled quickly.
Flow-downs: scope them, do not paste them
The reflex is to attach every clause from the prime contract and let the subcontractor sort it out. It saves an hour and costs a quarter, because the specialist firm's counsel now has to read clauses that have nothing to do with the work, and some of them cannot be accepted by a firm that does not hold that kind of contract.
The better construction has three parts. A short list of clauses that flow down by law or by the prime contract's own terms regardless of scope. A scoped set that attaches based on what the task order actually involves, referenced from the task order rather than the master. And an express statement that clauses referencing the government's rights against the prime are read, in the subcontract, as running between the parties, with named exceptions where that substitution does not work.
Then handle the ones that genuinely require action rather than acknowledgment. Safeguarding and incident reporting obligations for covered defense information flow to subcontractors handling that information, and they carry real requirements about what the firm's environment must do and how fast an incident must be reported. Prohibited-telecommunications representations require the firm to actually check its own supply chain, not to sign a paragraph. Where a clause requires an act, say so in the master and put a date on it.
The subcontractor's reasonable positions here: flow only what applies to the scope; give the firm the prime contract number and the applicable clause list per task order rather than a blanket incorporation; and do not flow clauses that presuppose a contract type the subcontract is not. A prime that accommodates those three gets agreements signed in weeks rather than months, and gives up nothing.
Intellectual property and data rights: the clause that decides the ending
This is where most technology subcontracts are quietly broken, and where the two sides have legitimate interests that have to be stated rather than assumed.
Assignment, not just work-for-hire language. Under 17 U.S.C. § 101, a commissioned work qualifies as a work made for hire only if there is a written agreement and the work falls within one of nine enumerated categories. Software is a literary work and is not among the nine. A recital that the work is made for hire, standing alone, can leave the prime holding an implied license rather than title. The clause needs a present assignment of copyright in the deliverables, with the work-for-hire language kept as a belt-and-braces alternative.
Background technology named and carved out, with a license back. Any specialist firm worth engaging arrives with existing tooling, libraries, scaffolding and internal frameworks. Assigning that is not a position a competent firm will accept, and a prime should not want it: buying a firm's toolkit means buying the obligation to maintain it. The workable construction names the background technology in an exhibit, excludes it from assignment, and takes a perpetual, irrevocable, sublicensable license to use, modify and distribute it as part of the delivered system, including onward to the government. Update the exhibit per task order rather than once.
Data rights and markings settled up front. On defense work especially, what the government receives in delivered software and technical data depends on where development funding came from, and on assertions being made and markings being applied correctly and on time. Put in the master: who prepares the assertions table, when it is delivered relative to the offer, what marking convention applies, and who reviews markings before delivery. Put in the task order: the actual assertions for that scope. A prime that leaves this to closeout gets a delivery it cannot lawfully hand onward and an argument with a partner who thought the position was obvious.
Government data is not the subcontractor's data. State where it may live, who may touch production, whether any of it may be used to train or tune a model, whether it may be used in aggregate for anything, what retention applies, and what is destroyed at the end and how that is evidenced. Silence on the model-training question is the fastest route to a legal review that stops a program.
Acceptance: tests, not adjectives
The master should require, and the task order should contain, acceptance criteria that a third party could evaluate without either party's opinion. "Accurate," "scalable," "production-ready" and "high quality" are not criteria; they are the setup for a dispute in which the prime withholds payment and the subcontractor insists the work is fine.
Workable criteria for technology deliverables look like this. A measured threshold on a named dataset with a stated split and a stated baseline. A latency figure at a stated concurrency on stated infrastructure. A deployment that runs from a clean checkout following written steps, performed by someone other than the author. A test suite that runs automatically with a stated pass condition. An accessibility conformance result against the applicable standard for the interfaces in scope. Documentation delivered as named artifacts rather than as a general obligation.
Then the mechanics, in the master. How many days the prime has to accept or reject. That a rejection must be in writing and must identify the specific criterion not met. A cure period and what happens after it. Deemed acceptance if the window passes in silence, which is the clause that protects a partner from a program office that goes quiet in December. And that acceptance of a deliverable does not waive the warranty.
Rates, pricing and payment
Pre-negotiating price is what makes days-not-weeks possible, so the master should carry a method rather than deferring everything.
Carry a rate schedule by labor category with definitions of each category, and an annual adjustment mechanism tied to a stated index or a stated percentage cap with a notice period. Carry the treatment of travel and other direct costs, including whether they are burdened. Carry the two pricing shapes the relationship will use, typically firm-fixed-price against milestones for definable scope, and a time-and-materials or committed-team structure with a ceiling for sustained capacity, with a note that the task order names which applies.
On payment, the two sides have a real conflict and it is worth naming. Primes prefer pay-when-paid; specialist firms cannot finance a large program's cash cycle, and a firm that has to will either price it in or fail mid-delivery. The common landing is a defined number of days after receipt of a proper invoice, independent of the government's payment to the prime, with the prime protected by clear invoice requirements and a defined dispute mechanism for contested amounts. State what makes an invoice proper, in detail, so nothing is rejected on a technicality three weeks after submission.
| Clause | Prime's usual opening | Specialist firm's usual position | Where it commonly lands |
|---|---|---|---|
| IP in deliverables | All work product assigned, broadly defined | Deliverables assigned; background tools excluded | Present assignment of deliverables, background named in an exhibit with a perpetual license back |
| Flow-downs | Blanket incorporation of the prime contract | Only clauses applicable to the scope | Mandatory set in the master, scoped set attached per task order |
| Payment | Pay when paid by the government | Fixed days after a proper invoice | Fixed days, with detailed invoice requirements and a dispute path |
| Liability | Uncapped, with broad indemnity | Capped at fees paid, carve-outs for the usual exceptions | A multiple of fees under the task order, uncapped for confidentiality, IP infringement and willful acts |
| Key personnel | Named, no substitution without consent | Named, substitution with equivalent qualifications | Consent not unreasonably withheld, with a qualifications standard and notice |
| Non-solicitation | One-way, covering all employees | Mutual, narrow, limited to people who worked on the engagement | Mutual, engagement-scoped, with a general-advertisement exception |
| Exclusivity | Broad, across the agency or market | Narrow, tied to a named pursuit and a date | Pursuit-specific, time-limited, with a defined release if the prime does not bid |
Security, personnel and the things that must be true before day one
A master subcontract for technology work should state the security posture as an obligation with evidence, not as an aspiration.
Name what the firm's environment must satisfy for the categories of data it will handle, and require that the position be evidenced rather than asserted: a current self-assessment, the plan behind it, and a date by which any gap closes. Require notification when the posture materially changes. Set the incident reporting path and the timeline, and name the person at the prime who receives it, because an incident process that routes to a general mailbox is not a process.
On personnel, state the screening the prime requires and who performs it, the onboarding steps and who owns each one, and the offboarding obligations including access removal and evidence of it. Access provisioning is the single most common cause of a subcontractor's first month being wasted, so put the government-furnished access items and their dates in the task order and make a missed date a schedule-relief event rather than a silent problem.
Add an obligation that neither party will introduce third-party code or services into a deliverable without the license terms being disclosed, and a mechanism for approving them. Open source is not a problem; an undisclosed license with terms the government contract cannot accommodate is.
The rest of the master, briefly
- Order of precedence. Task order, then master, then exhibits, with a statement that a task order may not modify the master unless it says so expressly and both signature authorities sign.
- Changes. A written mechanism with a stated response time for pricing a change, and an express statement that the subcontractor is not obliged to perform out-of-scope work before a change is executed.
- Termination. For convenience with payment for work performed and commitments incurred, for cause with a cure period, and what happens to work in progress and deliverables in either case.
- Exit as a deliverable. Source, build pipeline, infrastructure as code, environment configuration, credential rotation and runbooks, delivered as a condition of final payment. Add a handover rehearsal in which the receiving team deploys while the original engineers observe.
- Records and audit. Retention periods, what may be examined, notice, and reasonable limits on frequency and scope.
- Publicity and past performance. Usually no public reference without written consent. Worth adding: that the subcontractor may describe the work in a past performance submission in general terms with the prime's review, since a partner who can never cite the work has less reason to invest in the relationship.
- Insurance. Types and limits including technology errors and omissions and cyber coverage, certificates naming the correct entity, and notice of cancellation.
- Representations. Prohibited telecommunications, export control, no exclusions, and a duty to notify on any change.
What a well-drafted master actually buys the prime
Editorial weighting, illustrative rather than measured. The last row is low because a master is a speed instrument, not a discount instrument.
The task order template
Keep it to two or three pages and make it mostly fill-in-the-blank, because the point of the master is that a task order requires no legal review.
Header: task order number, effective date, the master it is issued under, the prime contract it supports, and the applicable scoped flow-down list. Scope: the statement of work, written by the engineers who will do it. Deliverables: each one with its acceptance criteria stated as a test. Schedule: period of performance, milestones, and the government-furnished access items with dates. Price: firm-fixed-price by milestone, or labor mix, rates and ceiling. People: named individuals with allocation, and the substitution standard by reference. Administration: the authorized representative on each side for technical direction and for changes, invoicing address and cadence. Signatures: two.
A prime that can produce that document, filled, in a day, has removed the reason its program managers reach for the wrong instrument.
How we work under a master subcontract
Precision Federal is a small business engineering firm. We build AI systems, data platforms, cloud infrastructure and full-stack web and mobile software, and we deliver them into production inside federal agencies. We work as a specialist subcontractor, teaming partner, protégé and nontraditional partner on other transaction agreements. We take a scope and answer for it rather than supplying hours, which is why acceptance criteria matter to us as much as they do to a prime.
Our positions on the clauses above are the ones this article describes as the usual landing, and we will state them in writing at the start rather than discovering them in redlines. We assign the deliverables. We name our background technology in an exhibit and license it back perpetually so nothing is stranded. We produce the assertions table for a scope before delivery, not at closeout. We will accept scoped flow-downs and will tell a prime plainly which ones require an act on our side and when it will be done. We ask for payment on a fixed number of days after a proper invoice, and we will accept detailed invoice requirements to get it.
What a prime gets in the first weeks of a task order is concrete. Week one: a written technical position on the scope, with the risks named and the questions we need answered. Weeks two and three: a scoped, priced statement of work with acceptance criteria written as tests, ready to drop into the task order template. Where a pursuit is live, draft technical volume text a proposal manager can edit rather than rewrite. Where the work has started, the first increment lands in the prime's environment, on the prime's pipeline, in the prime's deliverable format.
What the prime keeps is everything a prime should keep. The customer relationship is the prime's and we do not go around it. Code, models, pipelines and documentation are delivered under the assignment terms. On a proposal we are named and stand behind our resumes where that strengthens the technical volume, and we work behind a single face to the customer where the capture strategy calls for it.
Pricing takes one of two shapes: fixed-price milestones against written acceptance criteria where the scope is definable, or a committed team at an agreed allocation for a stated period where the program needs sustained capacity. Both are quoted against a rate structure that supports the flow-downs the prime's contract carries.
The first step is one email with a one-page brief: the program or pursuit, the technical scope, the environment the result must live in, the security destination, the date that matters, and the contract instrument. We return a scoped, priced statement of work. If the fit is not there, we say so in the same reply.
Bottom line
A master subcontract earns its keep by moving every argument to the front, once. Put in it what is true of the relationship: scoped flow-downs, a present assignment of deliverables with background technology named and licensed back, data rights and marking responsibilities, acceptance mechanics with deemed acceptance, a rate schedule with an adjustment method, payment on fixed days after a proper invoice, a security posture backed by evidence, a mutual and narrow non-solicit, and an exit that is a deliverable. Leave in the task order what is true of one job: scope, acceptance criteria written as tests, schedule with access dates, price, named people, and two signatures. Do that and a program manager who needs specialist engineers next month has a path that takes days, which is the only reliable way to stop the organization from reaching for an instrument that was never meant to carry engineering.
Frequently asked questions
It is an agreement negotiated once with a partner, carrying everything true of the relationship, with task orders issued underneath it for individual jobs. Use one whenever the same partner will be issued work more than once or twice. The purpose is to move the negotiation to the front so a program manager who needs specialist engineers can have a signed task order in days, rather than reaching for whatever instrument is already in place because a new subcontract takes months.
Whoever the assignment clause names, and the language matters. Under 17 U.S.C. § 101 a commissioned work qualifies as a work made for hire only if there is a written agreement and the work falls in one of nine enumerated categories, and software is not among them. The clause needs a present assignment of copyright in the deliverables. Pair it with the partner's background technology named in an exhibit, excluded from assignment, and licensed back perpetually so the delivered system can be maintained and passed onward.
The set that applies by law or by the prime contract's own terms regardless of scope, plus a scoped set attached per task order based on what the work involves. Blanket incorporation of the whole prime contract is what stalls negotiations for a quarter, because counsel must read clauses irrelevant to the work and some cannot be accepted by a firm holding a different contract type. Where a clause requires an act rather than an acknowledgment, say so and put a date on it.
As tests a third party could evaluate. A measured threshold on a named dataset with a stated split and baseline. A latency figure at a stated concurrency on stated infrastructure. A deployment that runs from a clean checkout by someone other than the author. An automated test suite with a stated pass condition. An accessibility result against the applicable standard. Then the mechanics: a rejection window, written rejections identifying the specific criterion, a cure period, and deemed acceptance if the window passes in silence.
It is a common opening and a poor landing for technology work. A specialist firm cannot finance a large program's cash cycle, and one that has to will either price the risk in or run into trouble mid-delivery. The workable position is payment a fixed number of days after receipt of a proper invoice, independent of the government's payment to the prime, with the prime protected by detailed invoice requirements and a defined dispute path for contested amounts.