Does work-for-hire language take my reusable methods?

It can, if the agreement assigns everything without a carve-out. List your frameworks and templates as pre-existing materials, license them for the deliverable, and keep a dated snapshot outside the client’s systems.

Can a client non-solicit follow me into contract work?

Yes. Non-solicits are enforced more often than non-competes, and contractor versions are common. The scope list, the clock start date, and the carve-out wording decide what you may do.

What records prove my work was pre-existing?

Dated repository history, a snapshot taken before the engagement, prior-client deliverables, and your invoice timeline. Export them before portal access ends, because a summary page is not evidence.

Should I disclose a signed clause to a new client?

Before the engagement starts, yes. A written disclosure with the scope you can work in protects the new relationship and puts the boundary on the record before anyone disputes it.

Contract Work Mobility: IP, Clients, Portability

Contract mobility is IP mobility: work-for-hire language transfers your deliverables, the reusable methods carve-out keeps your toolkit, and client relationships follow the non-solicit lines (see the mobility guide).

The Paper Lines

Assignment: work product ownership transfers on payment, not on delivery; keep license language for your frameworks, templates, and methods (see the contract terms guide).
Client portability: clients you built stay yours only when the agreement allows it; assignment + non-solicit lines decide the lane.
1099 records: invoices, deliverables, and payment trails prove your pre-existing methods at disputes (see the 1099 guide and the records guide).

The fee rules in the fee guide, venue in the fee-shifting guide, and the state map in the non-compete map. The conversion math to W-2 is in the 1099-to-W-2 guide.

Put the rule into action

Write the letter with the free Contract Engagement Termination Notice generator. The state pages carry the local payout and notice windows, and the application tracker keeps the follow-up date in writing.

Before you sign, get these in writing

The rule text, not a summary: the sentence in the handbook, plan document, or offer letter that states the payout, eligibility, or notice duty.
The dates: the notice date, the last day worked, the effective date of any change, and the date the decision was made.
The name and channel of the decision maker: who approved it, and the email or portal the confirmation was sent through.
Your own copy, dated: save the request you sent and the answer you received, with the timestamp. A record built after access is cut is much weaker.

Prove what you brought with you

Pre-existing IP is proved with dates, not memory. Before the first milestone, put your toolkit in evidence: a dated repository with commit history, a portfolio of prior deliverables, and a written schedule of pre-existing materials attached to the agreement.

Name the toolkit in the contract: frameworks, templates, code libraries, testing harnesses, and decks.
License those items to the client for the deliverable. Do not assign them.
Snapshot the starting state outside client systems: a dated archive or repository tag.
Keep invoices and deliverable submissions in one folder. They are the timeline proving which work came first.

If the assignment clause transfers everything you touch, the snapshot is your only defense. The contract termination notice generator puts the handover list and the pre-existing materials list in one dated letter.

Three outcomes for client portability

Whether a client you built stays yours depends on clause states, not on the relationship:

Assignment plus client non-solicit. You keep the work and lose the contact for the stated period. Check the clock start date and whether the list is named or written as any client.
Non-solicit with a carve-out. General outreach, inbound interest, and publicly posted roles are allowed. Direct solicitation of named accounts is not.
No clause. The lane is open, and the only limits are confidentiality and any trade-secret duty.

Read the non-solicitation entry and the non-compete entry, then check the state rules on the state map. Disclose what you signed to the next client in writing with the non-compete disclosure letter before the engagement starts.

Closing an engagement without losing the next one

The last week of a contract is where mobility is won or lost. Five things:

Serve written notice that cites the notice clause and names the final day.
Deliver a handover document: where things live, open items, credentials, and who owns each.
Invoice the milestone in progress and attach the acceptance evidence.
Ask for written confirmation of what the client keeps and what you retain.
Get a reference line you can quote: scope, dates, and one measurable outcome.

Then pull the records before portals lock. Export invoices, deliverables, and approval emails; a dispute two months later is decided by what you saved on your side. Collect the reference with the reference letter draft generator so the person signing has a page they can defend.

Clause state	You can do	You cannot do
Assignment plus client non-solicit	Keep your licensed toolkit	Contact named accounts during the period
Carve-out non-solicit	Respond to inbound and public postings	Direct outreach to listed clients
No restrictive clause	Work with anyone	Use confidential client information

Before you rely on a date or an amount on this page, check it against the California job exit rules page and the New York job exit rules page, along with the Release of Claims definition and the hiring references non competes guide hub. Rules move, and those pages carry the current text.

Frequently Asked Questions

Does work-for-hire language take my reusable methods?: It can, if the agreement assigns everything without a carve-out. List your frameworks and templates as pre-existing materials, license them for the deliverable, and keep a dated snapshot outside the client’s systems.
Can a client non-solicit follow me into contract work?: Yes. Non-solicits are enforced more often than non-competes, and contractor versions are common. The scope list, the clock start date, and the carve-out wording decide what you may do.
What records prove my work was pre-existing?: Dated repository history, a snapshot taken before the engagement, prior-client deliverables, and your invoice timeline. Export them before portal access ends, because a summary page is not evidence.
Should I disclose a signed clause to a new client?: Before the engagement starts, yes. A written disclosure with the scope you can work in protects the new relationship and puts the boundary on the record before anyone disputes it.