Ownership assumed from payment
Developers, designers and agencies are engaged, invoiced and paid. No agreement assigns what they produced, so the business holds no more than an implied licence to use material it believes it owns outright.
Paying for something is not the same as owning it, and the gap between those two usually surfaces at the worst possible moment.
Ownership of work product is determined by what the agreement says, not by who paid for it. An express present assignment, a further assurances obligation and a licence carve-out for the creator’s pre-existing material are what make the chain hold.

Most businesses assume they own what they paid someone to make. The default rule runs the other way, and the assumption holds right up until somebody traces the chain.
That tracing happens during diligence on a financing, an acquisition or a significant customer’s security review, when the buyer’s counsel asks who assigned the rights in each material component and the answer for one of them turns out to be nobody.
For a business in Meridian or elsewhere in Ada County, this page covers who owns what by default, what an assignment has to say to work, and how the chain breaks in the places it usually does.
A clause transferring ownership at the moment of creation, as distinct from a promise to assign in future, which requires a further document that may never be signed.
Developers, designers and agencies are engaged, invoiced and paid. No agreement assigns what they produced, so the business holds no more than an implied licence to use material it believes it owns outright.
Every engagement carries a present assignment with further assurances, pre-existing material is licensed rather than assigned, and the obligation reaches whoever the counterparty engages in turn.
For each material component the business can point to the person who created it and the document by which they assigned it, which is the question diligence asks and the one that is expensive to answer late.
The starting position differs depending on who created the work, and that difference is the source of most of the confusion.
Work created by an employee within the scope of employment generally belongs to the employer as a work made for hire. That is the reassuring case and it covers a good deal of what a company produces internally.
Work created by anyone else — a contractor, a freelancer, an agency, a consultant — generally belongs to the creator absent a written agreement transferring it. Payment does not transfer ownership. The business has, at most, an implied licence to use the work for the purpose it was commissioned for, which is considerably less than ownership and is not something a buyer’s counsel accepts quietly.
The work made for hire doctrine does not rescue the position for most commissioned material. It applies to employee work within the scope of employment and to a short, closed list of specially commissioned categories, agreed in writing. Software written by a contractor, a brand identity produced by an agency, engineering drawings from a consultant and written content from a freelancer generally fall outside that list.
The consequence is that an agreement reciting that the work is a work made for hire, and stopping there, can leave ownership with the creator. The recital is worth including because it may apply; it is not worth relying on alone.
Patentable inventions follow their own rules, with inventorship attaching to the individuals who actually conceived the invention. A company whose product rests on an invention conceived by a contractor needs an assignment from that individual, and the time to obtain it is while they are engaged.
A clause that works has four elements, and the absence of any one of them is a common finding.
The first is a present assignment. The clause should assign all right, title and interest in the work product as it is created, rather than promising to assign it at some future point. An agreement to assign requires a further document, and the further document gets signed only if somebody chases it, which at the relevant moment nobody does.
The second is scope that matches reality. The assignment should cover everything created in connection with the engagement — not only the final deliverable but the intermediate material, source files, drafts, specifications and documentation. A business that owns a compiled output and not the source has bought something it cannot maintain.
The third is further assurances: an obligation to execute whatever documents are reasonably required to perfect the assignment and to register rights, continuing after the engagement ends. A power of attorney permitting the business to execute such documents if the creator cannot be located is a sensible backstop, and costs nothing to include.
The fourth is the background material carve-out. Most contractors bring their own libraries, templates, tools and methods, and a clause assigning everything they touch is either renegotiated or ignored. The workable structure leaves those with the contractor and grants the business a perpetual, irrevocable, worldwide, royalty-free, non-exclusive licence to use, modify and sublicense them to the extent they are embedded in the deliverable. That gives the business what it actually needs — the ability to use and develop the work without returning to the contractor — without demanding something no established contractor will give.
Moral rights and similar personal rights should be waived to the extent permitted, which is a line of drafting rather than a negotiation.
An agency assigns to the business. The agency engaged a freelancer who never assigned to the agency. The chain breaks at the person who actually did the work, and the agency cannot assign what it does not own.
The fix is a flow-down obligation: the counterparty must obtain equivalent assignments from anyone it engages, and must be able to evidence them on request.
Ownership and confidentiality are distinct and both are needed, because owning the deliverable does not stop the creator using what they learned on the next engagement.
Idaho Code section 48-801 subsection (5) defines a trade secret as information deriving independent economic value, actual or potential, from not being generally known to and not being readily ascertainable by proper means by other persons who can obtain economic value from its disclosure or use, and that is the subject of efforts that are reasonable under the circumstances to maintain its secrecy. Subsection (1) defines improper means to include breach or inducement of a breach of a duty to maintain secrecy.
The duty whose breach constitutes improper means is the one the confidentiality clause creates, which is why the clause carries statutory weight rather than being belt-and-braces. A business that engages creators without confidentiality obligations has weakened both limbs: no duty exists to be breached, and the absence of the obligation is itself evidence against reasonable efforts.
Restrictive covenants are the third element and operate on a defined statutory footing here. Idaho Code section 44-2701 provides that a key employee or key independent contractor may enter into a written agreement or covenant protecting the employer’s legitimate business interests, and that such an agreement is enforceable if it is reasonable as to its duration, geographical area, type of employment or line of business, and does not impose a greater restraint than is reasonably necessary to protect those legitimate business interests. The section was added by Stats. 2008, ch. 295, sec. 1, p. 824.
For creators, the legitimate interest being protected is usually the information and the relationships rather than the general ability to practise a trade, which points toward a covenant scoped to specific confidential material and specific customers rather than a broad bar on similar work. A covenant the business can explain in one sentence is on firmer ground than one drafted to the outer edge.
Most businesses discover the problem partway through, with several years of engagements behind them and no realistic prospect of papering all of them.
The sensible approach is triage rather than completeness. Map the components the business actually depends on — the product, the platform, the brand, the material it licenses to customers — and trace only those. A gap in a marketing graphic from four years ago is not the same problem as a gap in a core module.
For each gap, the question is whether the person can be reached and whether the relationship is live. Someone currently engaged will usually sign a confirmatory assignment as a matter of course, and that is the cheapest fix available. Someone who left on good terms will often sign if asked plainly. Someone who left badly, or who has since gone to work for a competitor, is a negotiation.
That ordering is the argument for acting early. The cost of an assignment rises steadily as the relationship cools, and it rises very sharply at the moment the business is known to need it. A contractor asked for a signature during a live acquisition understands exactly what the signature is worth.
Where a gap cannot be closed, it should be documented honestly: what the component is, who created it, what rights the business can establish, and what the practical exposure is. A known and quantified gap disclosed in diligence is a negotiating point. The same gap discovered by the other side is a finding.
Going forward, the fix is procedural. Every engagement of anyone who creates anything goes out on a form carrying the assignment, the further assurances, the carve-out and the flow-down. That is a one-time drafting exercise and a standing instruction to whoever issues engagements.
Clark Meyers advises Idaho businesses on work product ownership and assignment chains from the firm’s Nampa office at 4865 E. Franklin Rd. The firm has no Meridian office; Meridian clients are served from Nampa. Lee Clark is licensed in Idaho and California.
Can your Meridian business point to the document assigning each thing it depends on?
Absent a written agreement transferring it, generally the contractor. Payment does not transfer ownership, leaving the business with no more than an implied licence for the commissioned purpose.
The doctrine covers employee work within the scope of employment and a short closed list of specially commissioned categories, so most commissioned software, design and written work falls outside it.
It transfers ownership as the work is created. A promise to assign in future requires a further document that only gets signed if somebody chases it, which at the relevant moment nobody does.
Everything created in connection with the engagement, including intermediate material, source files, drafts, specifications and documentation — not only the final compiled or delivered output.
They stay with the contractor, with the business taking a perpetual, irrevocable, royalty-free, non-exclusive licence to use, modify and sublicense them to the extent embedded in the deliverable.
The chain usually breaks at a subcontractor. An agency assigns to the business but never obtained an assignment from the freelancer who did the work, and it cannot assign rights it does not itself hold.
Section 48-801(1) makes breach of a duty to maintain secrecy an improper means, and the clause is what creates that duty. Its absence also undercuts the reasonable efforts element.
Section 44-2701 permits a written covenant with a key employee or key independent contractor, enforceable if reasonable in duration, area and scope and no broader than necessary to protect legitimate interests.
Triage by importance, close what can be closed while relationships are live, and document honestly what cannot — a quantified gap disclosed in diligence is a negotiating point rather than a finding.
Fill out the form below and we'll get back to you within 24 hours.
We've received your request and will be in touch within 24 hours.