How can I document the contributions of employees, freelancers and research partners?

Describe the work each person actually did

A project team list shows who was involved, but rarely explains their contributions. Record the particular work: who proposed a solution, produced a drawing, wrote a software component, designed an experiment or interpreted its results.

For each substantial contribution, keep:

• The person’s name, organisation and role at the time.
• A description of what they created, changed or decided.
• The dates or period of the work, identifying any estimates.
• References to the relevant files and versions.
• Supporting messages, meeting notes, laboratory records or task discussions.

For example, a prototype record might distinguish the employee who proposed a new mechanism, the freelancer who prepared its detailed drawings and the research partner who tested it. Link each description to the material that supports it. If several people developed something together, describe their interaction and any uncertainty about individual contributions.

Separate existing material from new work

At the start of a collaboration, identify the designs, code, data or methods each participant brings. As work proceeds, record what was added or changed and which earlier material it builds on. Include the source and relevant permissions for third-party material.

For confidential know-how, WIPO’s guidance on collaborative innovation distinguishes information brought into a project from results developed during it, and explains why their treatment should be addressed in the collaboration agreement.

Keep the agreements connected to the contributions

Retain the signed documents that apply to the work and identify the relevant project, period or deliverables. Depending on the relationship, these may include employment terms, a freelancer’s commission, a research agreement, a licence or an assignment of rights. Preserve amendments as well as the original agreement.

Do not infer ownership simply from payment, a job title or a name on a file. For example, the UK Intellectual Property Office’s copyright guidance distinguishes work made in the course of employment from commissioned work and recommends keeping records of creators and contracts. That is a UK copyright example, not a rule for every country or IP right.

The contribution record supplies facts for an ownership review. It does not itself transfer rights or settle who legally qualifies as an author or inventor.

Check the account with the people involved

At a milestone or handover, ask contributors to review the description of their work and the supporting references. Keep their replies, record corrections and mark unresolved points explicitly. Silence should not be recorded as confirmation.

Date later corrections and preserve the earlier account so changes remain traceable. If you reconstruct events after the project, distinguish recollections from records made at the time.

Preserve the record and its supporting files

Keep the contribution notes with the exact file versions they describe, in storage the responsible organisation can maintain after a contributor leaves. Restrict access to confidential material and retain only the personal information needed to explain the work.

An independently verifiable timestamp can strengthen the chronology of the preserved material. RFC 3161 describes evidence of data existence: timestamping a note that names a contributor does not establish that the attribution is true. The underlying work, correspondence and contributor confirmations give that statement its support.