Working Arrangements: Responsibilities, Access & Onboarding

These are the topics to agree before an engagement begins. Items marked “In my current role” are practices I run in my current job; items marked “Agreed per engagement” are set with each client. This is a working checklist, not a certification or an audit report.

01Technical ownership

Identify who approves architecture, reviews code, and accepts technical work.

02Accounts and tools

Agree on account ownership, approved repositories and tools, and who grants access.

• In my current roleCode lives only in client-owned repositories and accounts; the client grants and revokes access.
• In my current roleSingle sign-on with multi-factor authentication, on least-privilege access.
• Agreed per engagementAudit logs and a regular access review schedule.

03Data and environments

Define which environments and data the team may access, and any masking or separation required.

• In my current roleNo production data, or masked data only.
• Agreed per engagementStaged access, and which core modules stay in-house.

04Devices and offboarding

Assign device responsibilities and document access removal and handover steps.

• In my current roleCompany-provided, centrally managed computers; no personal devices.
• In my current rolePersonal account deleted and computer returned on the engineer's last day.

05Employment and IP

Establish the contractual parties and responsibilities, including appropriate documentation and specialist review where needed.

• In my current roleLabour contracts with work-product ownership and confidentiality clauses; non-compete terms where appropriate.
• Agreed per engagementContract chain and IP assignment to the client, with specialist legal review.

Your technical leadership approves the standards. Implementation and specialist responsibilities are defined in the agreed engagement.