What this page is for
Once a budget owner has agreed an engagement in principle, procurement, legal and security teams need facts: who the supplier is, what insurance is held, how data will be handled, who owns what is produced, whether anyone else will do the work, and on what contractual basis. This page sets out what I provide and, just as importantly, what your organisation has to assess for itself.
The distinction matters. Business terms are things I can state for every engagement. Contract-specific assessments, such as an IR35 status determination or a data protection assessment, depend on the particular contract and are made by you or your advisers. Mixing the two produces either false assurance or delay.
The supplier information pack
Provided on request once an engagement is agreed in principle:
- Business details. The contracting entity’s legal name, address, registration and tax details, and bank details on letterhead for your vendor set-up.
- Insurance. Details of any cover held, with current certificates. Specific levels are confirmed against your contract’s requirements rather than published here.
- Data-handling and security practices. How I access your systems, which devices are used, how credentials and data are protected, what happens to data and access at the end of the engagement, and how a suspected incident is reported to you.
- IP and confidentiality position. The starting position on ownership of deliverables created for you, and on pre-existing tools, libraries and know-how. The contract settles the final position.
- Working practices. How work is directed, the working pattern, location, equipment and how the engagement ends. These are the facts your status determination needs.
- Subcontracting policy. The work is done by me personally; no subcontracting or substitution happens without your written approval.
The pack does not include certification badges or audit reports that I do not hold. If your process requires a particular certification, ask early and you will get a plain answer.
Data access and security in practice
I work inside your environment wherever possible: your repositories, your cloud accounts, your collaboration tools, under your identity and access controls, with the least access the work needs. Where you require it, I use a device you provide. I do not copy your data to personal storage or unapproved services. Where AI providers are involved, only those you have approved are used, configured for your data location and retention requirements. At the end of the engagement, access is removed through your leaver process and any working copies are deleted, confirmed in writing.
Contract basis
Engagements can be contracted directly with my contracting entity, through your preferred recruitment agency or contract desk, or through a partner that holds the client relationship. The engagement models page explains each commercial model, and the partners overview explains how agency, MSP and vendor routes are contracted.
For UK contracts, your organisation makes the IR35 status determination where the off-payroll rules place it with you. I give you the working-practice facts, honestly described, and do not give tax advice. Equivalent rules in other jurisdictions are handled the same way: the facts from me, the assessment from you or your advisers. Delivery location (remote, on site or a mix) and where data may be processed are written into each contract.
Scope and acceptance
Procurement often receives a statement of work that promises vague AI outcomes. Every engagement here has a written scope with deliverables, acceptance tests, the data and access the work depends on, exclusions and a change process. The project scope and acceptance template shows the structure and can be used as a starting point for your own.
Requesting the pack
Use the form below with the engagement reference or the name of the budget owner you are working with, and the questionnaires or standard terms you need completed.