A staff augmentation agreement is the contract between a company that needs temporary technical talent and the agency supplying it, and the clauses you write into it decide who owns the code, who carries employment liability, and how either side gets out. The client runs the project work day to day while the vendor stays the employer of record for payroll, taxes, and benefits. That split sounds clean on paper. It falls apart quickly if the contract doesn’t police the boundary.
What follows are the terms that actually matter when something goes wrong, and the drafting choices that keep small problems from becoming expensive ones.
The Two-Document Structure
Most of these relationships run on two layers. A master agreement sets the universal terms: IP ownership, confidentiality, liability caps, insurance, dispute resolution. Individual statements of work attach as exhibits, each covering one engagement with its own roles, rates, timeline, and deliverables. New project, new SOW. You don’t renegotiate the master every time you swap a developer.
Order of precedence matters. When an SOW conflicts with the master, the master usually controls unless the SOW explicitly overrides it. That’s worth stating in the contract, because project managers drafting a quick SOW can accidentally create obligations that contradict terms the lawyers spent weeks negotiating. Name the winner on the page.
Scope, Rates, and Payment
Each SOW should name the exact roles, the required qualifications, and what “done” looks like. “Developer support” is not a scope. “Senior backend engineer, four years of Go, delivering the authentication service described in Appendix A by March 15” is a scope. Vague descriptions invite disputes over whether the vendor delivered what the client expected.
Technical hourly rates often run from $75 to $250 depending on specialization and seniority. Lock in the rate per role, say whether rates can change at renewal, and fix the payment cadence. Net-30 and net-45 are standard, meaning payment within 30 or 45 days of invoice receipt. If the engagement has a hard end date or a budget ceiling, write both into the SOW.
Before the first invoice, the vendor should return a completed IRS Form W-9 with the correct taxpayer identification number, which may be an EIN for a business entity or an SSN for a sole proprietor.1Internal Revenue Service. Form W-9 Request for Taxpayer Identification Number and Certification Getting that on file early avoids year-end reporting trouble.
Travel reimbursement is cleaner when tied to a benchmark instead of individual receipts. Many contracts peg lodging and meals to the federal GSA per diem rates for the destination.2GSA. Per Diem Rates The contract should also say whether travel time is billable and whether expenses above a threshold require pre-approval.
Overtime deserves its own line. Technical contractors often work long hours during a crunch, and the agreement should state who pays for the extra time and whether written pre-approval is required. The federal exemption for computer professionals only applies when the worker earns at least $684 per week on salary or $27.63 per hour and performs qualifying duties like systems analysis, software design, or programming.3U.S. Department of Labor. Fact Sheet 17E – Exemption for Employees in Computer-Related Occupations Under the Fair Labor Standards Act People who just use computers in their job, like an engineer running CAD, don’t qualify.
Keeping the Vendor as Employer of Record
This is where staff augmentation agreements live or die. The whole premise is that the vendor employs the workers and the client avoids taking on employment obligations. The IRS, however, looks at substance over labels. If the client controls how the work gets done rather than just what gets done, the IRS can treat the arrangement as direct employment.4Internal Revenue Service. Employee Common-Law Employee
Three factors drive that analysis: behavioral control (who dictates methods and tools), financial control (who handles expenses and equipment), and the nature of the relationship (do the parties act like employer and employee). A reclassification finding can mean back taxes, penalties, and retroactive benefits.
Draw the operational line in the contract. The vendor runs onboarding, performance reviews, discipline, and payroll. The client defines scope and deliverables, approves work, and accepts output, but doesn’t dictate daily schedules, require attendance at employee-only events, or issue company badges and email addresses that make contractors indistinguishable from internal staff. These distinctions feel like paperwork until an audit, at which point they are the whole case.
Reporting responsibilities depend on the arrangement. When the vendor pays its people as W-2 employees, the vendor handles income and payroll withholding and the client has no direct IRS reporting duty for those workers. When the client engages an independent contractor directly, the client must issue Form 1099-NEC for payments of $600 or more.5Internal Revenue Service. Forms and Associated Taxes for Independent Contractors The agreement should state which arrangement applies.
IP Assignment, Not Just Work Made for Hire
This is the clause most companies get wrong, and the one most likely to cost you control of your own codebase.
Under federal copyright law, when a regular employee creates something within the scope of their job, the employer owns the copyright automatically. Augmented staff are not your employees. For work created by independent contractors or vendor-employed workers, the “work made for hire” doctrine applies only to nine narrow categories: contributions to a collective work, parts of a motion picture, translations, supplementary works, compilations, instructional texts, tests, answer material for tests, and atlases.6Office of the Law Revision Counsel. 17 US Code 101 – Definitions Even inside those categories, both parties have to sign a written agreement calling the work a work made for hire.7U.S. Copyright Office. Circular 30 – Works Made for Hire
Notice what’s not on that list: software, custom code, database schemas, architecture diagrams, almost everything a technical contractor actually builds. A work-for-hire clause by itself will not transfer ownership of code. The contract needs an explicit copyright assignment where the vendor and each of its personnel assign all right, title, and interest in the work product to the client upon creation or payment. Without that language, the vendor or the individual developer could retain ownership of code you paid for and license it to your competitors.
The assignment should cover copyrights, patent rights, and trade secrets developed during billable hours, and it should include a further-assurances commitment: the vendor will sign whatever follow-on documents are needed to perfect those rights if a dispute surfaces later.
Pre-existing IP needs its own paragraph. Vendors often bring tools, libraries, and frameworks they built before the engagement. Those stay with the vendor, but the client should receive a perpetual license to use them as part of the delivered product.8Office of the Law Revision Counsel. 17 US Code 201 – Ownership of Copyright Otherwise you’re paying to build something you can’t fully use.
Confidentiality and Data Handling
Augmented staff sit inside your network, attend internal meetings, and touch systems that permanent employees use. The confidentiality terms have to match that exposure. Define what counts as confidential: pricing strategy, customer data, proprietary source code, internal processes. Then prohibit disclosure outside the engagement.
For ordinary confidential information, survival periods of one or two years after termination are typical. Trade secrets are different. They should be protected for as long as they qualify as trade secrets under applicable law, which can be indefinite. Setting a short expiration on trade secret protection is a trap: once the clock runs out, the former contractor has no contractual duty to keep quiet even if the information still carries competitive value.
When the engagement touches personal data, health records, or payment information, attach a data processing addendum. The addendum should bar the vendor from using client data for anything beyond the engagement, prohibit mixing client data with the vendor’s own data, and set security standards against unauthorized access or accidental disclosure. In regulated industries, name the frameworks that apply, such as HIPAA for healthcare or PCI DSS for cardholder data.
Non-Solicitation and Conversion Fees
Non-solicitation clauses prevent each side from poaching the other’s people. Twelve months after a worker finishes an assignment is a common duration, but enforceability varies by state. Several jurisdictions limit the scope or duration of non-solicits, and a few have barred them for certain worker categories.
Most contracts also include a conversion fee, sometimes called a buyout, that lets the client hire a contractor directly by paying a percentage of expected annual salary. The percentage varies, and you want it negotiated up front rather than discovered when you’ve decided you want to keep someone. Some contracts scale the fee down the longer the contractor has been on assignment, reaching zero after a set period.
Liability, Indemnity, and Insurance
Liability caps ceiling what either side can owe the other. The cap is often tied to fees paid under the agreement during the preceding twelve months. Carve out intentional fraud, gross negligence, and confidentiality breaches, because no party should get the benefit of a cap when it has acted in bad faith.
Indemnification handles third-party risk. If a developer slips stolen or infringing code into your project and a copyright holder sues, the vendor’s indemnity obligation picks up the defense and the damages. Require prompt written notice of any claim and give the indemnifying party the right to control the defense, not just a bill for whatever counsel the other side chose.
Require insurance before any work starts, with certificates on file. Standard coverage includes statutory workers’ compensation, commercial general liability, and professional liability or errors-and-omissions. For engagements involving sensitive data, cyber liability is now expected. Name the client as an additional insured on the vendor’s general liability policy, and require advance notice from the insurer before any cancellation so the coverage can’t disappear mid-engagement without anyone noticing.
A force majeure clause excuses performance for events beyond either party’s control. Require prompt notice, continued performance of any obligations that aren’t actually blocked, and an outer limit, often 60 or 90 days, after which either side can terminate. Without that escape hatch, you can be stuck in a contract where nothing is happening and no one can leave.
Performance Standards
Put measurable targets in the master agreement or the SOW. Useful metrics include time to submit qualified candidates, the share of submissions that advance to interviews, fill rate for open positions, and a retention target for placed contractors, often measured at 90 days.
For larger engagements, metrics live in a formal service level agreement attached as an exhibit. The SLA should name the remedy when a target is missed: service credit on the next invoice, an escalation path, or the right to bring in another provider. A commitment to “provide qualified resources” is unenforceable. Numbers are enforceable.
Termination and Offboarding
Build in clear termination mechanics. Either party should be able to terminate for convenience with 30 to 60 days’ written notice, and immediately for cause after an uncured material breach. Say what happens to in-progress work, whether there’s a wind-down period, and what the client owes for work performed through the termination date.
Offboarding is where companies routinely slip. When an augmented worker rolls off, every form of access should be revoked the same day: SSO and identity provider credentials, VPN, database and server permissions, SaaS accounts, email. Recover company-issued devices. Reset shared passwords the contractor knew. The agreement should require the vendor to cooperate with offboarding and confirm that client data and materials have been returned or destroyed. Skip these steps and you leave zombie credentials in your systems, which is exactly how a breach shows up six months later.
Dispute Resolution
Most of these agreements send disputes to arbitration under the American Arbitration Association’s Commercial Arbitration Rules, with a named venue (often the client’s headquarters city) and a stated number of arbitrators.
Watch one drafting trap. If the contract has a governing law clause naming one state’s law but the arbitration clause doesn’t require the arbitrator to apply that law, the arbitrator isn’t automatically bound by it. “Governed by the laws of Delaware” in a general choice-of-law clause plus a silent arbitration clause means the arbitrator has discretion. Fix it by stating in the arbitration clause itself that the arbitrator must apply the governing law the contract specifies.
Signing and Keeping the Record
Federal law treats electronic signatures as legally equivalent to ink for commercial contracts.9Office of the Law Revision Counsel. 15 US Code 7001 – General Rule of Validity E-signature platforms create an audit trail with timestamps and IP addresses, useful if someone later denies agreeing. Make sure both sides get a fully executed copy right away so billing can confirm rates and project teams can track expiration.
Retention depends on industry. Federal contractors must keep records at least three years after final payment under the FAR.10Acquisition.GOV. FAR Subpart 4.7 – Contractor Records Retention Private companies commonly hold contracts six or seven years to cover breach-of-contract limitations periods in most jurisdictions. Keep executed agreements and every related SOW in a secure document system for at least the longest applicable limitations period, with a buffer.