Project Participation Terms

A private Network opportunity invitation, and a response such as "open to a conversation" or a request for more information, sit before project contracting. They do not by themselves create an assignment, a fee entitlement, an employment or worker relationship, or any obligation on LYNR or a client. Scope, commercials, confidentiality, data protection, security, intellectual property and delivery terms must be confirmed separately before any work starts.

Network membership alone creates no obligation to perform client work and no right to payment. Before work begins, LYNR and the participating person or organisation must agree a written assignment identifying at least the scope, accountable delivery party, dates or delivery period, fees/payment mechanics, Definition of Done or acceptance basis, and any client-specific requirements that are material to the work.

Unless a signed assignment expressly creates a different lawful relationship, the parties intend a business-to-business or independent-services arrangement. The participant is not authorised to bind LYNR or the client.

Employment, worker, agency, tax and off-payroll status depend on applicable law and the actual working arrangements, not merely the label used in a contract. The parties must not operate an assignment in a way that knowingly contradicts the written responsibilities or an applicable status determination. Where UK off-payroll working rules, agency rules or similar requirements may apply, the relevant parties must identify and address them before or during the assignment as required by law.

Nothing in these baseline terms is intended to transfer a statutory responsibility that the law places on a client, fee-payer, intermediary or other party.

• Perform the work with the reasonable skill, care and professional diligence expected from the senior capability represented to LYNR.
• Work to the agreed scope, Definition of Done, acceptance criteria and timetable.
• Raise blockers, material scope changes, dependencies, conflicts and delivery risks promptly rather than hiding them.
• Use the client's and LYNR's approved tools, workflows and access methods where the assignment requires them.
• Produce the working artefacts, documentation, ownership model and handover material required by the assignment.
• Do not represent work as complete where a material agreed acceptance condition remains unmet without disclosure.

If an assignment is awarded because of a named senior lead, specialist capability or stated delivery team, material substitutions must be disclosed before they affect delivery and approved where the assignment requires approval.

A partner organisation remains responsible for its employees, contractors and subcontractors and for ensuring they are bound by confidentiality, data, security and intellectual-property obligations appropriate to the assignment. Use of a subcontractor does not reduce the partner's responsibility for its contracted deliverables.

• Use confidential client, LYNR, member and opportunity information only for the assignment and only to the extent needed.
• Request and retain the minimum systems, personal data and access required for the work.
• Protect credentials, devices and data and follow agreed security, location, access and acceptable-use requirements.
• Do not copy production data into personal tools or unapproved services merely for convenience.
• Report suspected confidentiality, privacy or security incidents to LYNR promptly and provide reasonable information/cooperation needed for investigation and notification duties.
• Return, delete or stop using assignment information and access when the need or assignment ends, subject to a lawful or expressly agreed retention requirement.

The written assignment must identify any material data-protection role where the participant will process personal data for LYNR or a client. Where the participant acts as a processor or sub-processor, an appropriate data-processing agreement or equivalent contractual terms must be in place before restricted processing begins.

A participant must not appoint a sub-processor, change agreed processing locations, or use personal data for its own incompatible purpose where the assignment or applicable data-protection terms prohibit that activity.

AI and automation may be used where they are appropriate to the assignment, but no participant may place confidential client, LYNR or member information into an unrestricted public AI service or use it to train or improve a model for an unrelated purpose without express authorisation and an appropriate legal/security basis.

Where AI materially affects a deliverable or decision, the participant must comply with agreed requirements for approved providers, data handling, evaluation, human review, auditability, disclosure, intellectual property and security. AI-generated output does not reduce the participant's responsibility to check the work before it is relied on.

If a proposed automated process could make or materially influence high-risk decisions about individuals, the participant must escalate it before deployment so that LYNR/client can assess legal, governance and human-intervention requirements.

For an EU-facing AI workstream, the written assignment must identify the relevant regulatory roles and allocate responsibility for any applicable EU AI Act obligations, including transparency, human oversight, input-data quality, monitoring, logging, worker/affected-person information, incident handling or impact assessment requirements. No party should be treated as having accepted a provider, deployer, importer, distributor or other regulated role merely by joining Lynr Network.

Disclose any actual or reasonably foreseeable conflict that could materially affect independence, client trust, confidentiality or ability to perform. LYNR may require safeguards, recusal, restricted information access, a different team or a decision not to proceed.

Ownership and permitted use of deliverables must be stated in the written assignment. Pre-existing tools, methods, templates, code, software, products, know-how and other background intellectual property remain with their existing owner unless expressly transferred.

A participant must identify material third-party material, open-source software, datasets, model/provider terms or licences incorporated into a deliverable where they could affect the client's permitted use, ownership, confidentiality or obligations.

No client product licence, software licence, trademark licence or transfer of copyright should be inferred merely from Network membership or participation. Where a technology/product partner is involved, the written assignment must identify relevant licensing, implementation, support, data-processing and integration responsibilities.

Material statements about credentials, certifications, insurance, team, security capability, product functionality, references, delivery history or outcomes must remain materially accurate. A participant must notify LYNR if a representation relied on for the assignment becomes materially inaccurate.

Fees, currency, invoicing, payment timing, applicable taxes and any approved expenses are governed by the written assignment. Expenses are reimbursable only where the assignment permits them or LYNR approves them in writing. Each party remains responsible for taxes and statutory obligations allocated to it by law or the signed agreement.

Where an assignment requires professional indemnity, cyber, public liability or another insurance, screening, certification or client onboarding requirement, the participant must maintain and evidence the required cover/condition for the period stated in the assignment and notify LYNR of a material lapse that affects eligibility to perform.

Any exclusivity, non-solicitation, non-circumvention or similar restriction applies only where expressly set out in a written assignment or other signed commercial agreement, and only to the extent lawful and enforceable. Network membership alone creates no such restriction.

Material scope, team, timeline or commercial changes must be handled through the change-control mechanism in the written assignment or otherwise agreed in writing by the authorised parties.

The written assignment will state termination rights and the consequences for work in progress, access, confidential information, handover and payment. On termination or expiry, the participant must cooperate with a reasonable transition and comply with continuing confidentiality, data, IP and security obligations.

Liability caps, exclusions, indemnities, warranties, insurance allocation and any client flow-down obligations are deliberately not standardised by Network membership. They must be stated in the signed assignment or relevant client/subcontract agreement because they depend on the work, risk and contracting structure. Nothing in these baseline terms excludes liability that cannot lawfully be excluded.

Unless the written assignment specifies otherwise, these baseline terms are governed by the laws of England and Wales and the courts of England and Wales have jurisdiction, subject to mandatory rules that apply. If a signed assignment expressly conflicts with these baseline terms, the assignment prevails for that work.