Ownership of results: code, designs and data: situations

This page lists the situation notes in ownership of results: code, designs and data — each one answers a specific moment when something has gone wrong or a decision is due, with the first step, who decides, and what it costs to be wrong. Pick the one that matches your position.

All situations in this practice (22)

• When a contractor claims ownership: what it costs to be wrong
• When a contractor claims ownership: what to do first
• When a data set was assembled by an intern: what to do first
• When a designer reuses a template: what to do first
• When a development partner claims joint: what to do first
• When a former employee launches a similar: what to do first
• When a founder leaves with the prototype: what to do first
• When a group restructuring moves the team: what to do first
• When a subsidiary paid for work the parent: what to do first
• When an acquired team brings prior work: what to do first
• When an agency keeps the design: what it costs to be wrong
• When an agency keeps the design files: what to do first
• When freelancers signed nothing: what to do first
• When open source is found inside: what to do first
• When source code sits on a personal account: what to do first
• When the assignment is unsigned but: what to do first
• When the client wants the design files: what to do first
• When the contract says work for hire: what to do first
• When the database was built by a supplier: what to do first
• When the deliverable was accepted but never: what to do first
• When the team is spread across three: what to do first
• When the training corpus has no provenance: what to do first

Back to the practice overview: Ownership of results: code, designs and data.