Last updated: · Version 1.0
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.
Agree how evidence can be attributed
Interview evidence is handled according to the permissions and confidentiality arrangements established for the engagement. Outputs may use named, role-level, department-level or anonymised attribution, or keep the source restricted.
A role or department can still identify someone in a small team. Removing a name alone does not make an account anonymous. Any limits to confidentiality need to be explained before an interview.
The sponsor does not automatically see everything
Commissioning Discovery does not give a client sponsor unrestricted access to every raw recording or transcript. The authorised audience, purpose and source restrictions determine what can appear in the findings.
Sensitive employee accounts, restricted departmental material and legally privileged information require particular care. Access must follow applicable legal requirements as well as the agreed permissions.
Quotes add context, not a financial calculation
Approved quotations can explain how work happens. They do not replace quantitative or authoritative evidence when the conclusion requires it.
Illustrative example, not a client quotation: “Every morning I export yesterday’s jobs and compare them manually with the Finance spreadsheet.” That describes a workflow. A claim about its annual cost still needs evidence of frequency, time, volumes and relevant costs.