Last updated: · Version 1.1
These are the requirements for our Discovery engagements, not a claim that every described software capability is already operational. Scope, permissions, providers and retention must be agreed and checked before client evidence is processed.
What you receive
Your engagement sets out the deliverables and your rights to use them. These may include the written audit, recommendations, roadmap, approved client-safe evidence, calculations, business cases and implementation proposals.
Implementation remains optional. The agreed outputs should let you make a decision and, within the agreed rights, work with your own team or another supplier.
Client information does not become our intellectual property
The underlying Discovery methodology, software, analytical systems, templates and general know-how remain proprietary to their existing rights holders. Using them to analyse your business does not transfer ownership of your confidential information.
The engagement terms must distinguish client materials, project deliverables and pre-existing intellectual property, including any licences needed to use the outputs. This page does not itself assign ownership or grant a licence.
Improvement is not permission to reuse your information
Where legally and contractually permitted, appropriately anonymised, aggregated or generalised operational learning may improve Discovery methods and evaluation. A lesson might be that exception workflows need deeper investigation earlier.
Aggregation, removal of names or generalisation does not automatically make information anonymous or remove commercial confidentiality. Reuse beyond delivery of the engagement needs the applicable legal and contractual permissions.
No permission to train models on client information is granted by an enquiry or engagement description. Any proposed training use would need separate assessment, transparency and the applicable permissions. Provider data-use settings must also be checked before evidence is processed.
A readout you can challenge, with audience-safe evidence
Where the agreed presentation supports it, authorised participants can inspect approved supporting evidence and challenge findings during the readout. That view must not expose every underlying recording, staff account, credential or restricted source.
A material correction should be recorded, with affected findings, calculations and recommendations re-evaluated and reviewed before the revised final audit is released. A live challenge is not a reason to publish an unchecked new answer.