AMS / EXPERTISE
Know what still needs to be shown.
Separate support in a specification from evidence of behaviour in a product or network.
What the scope can include
- Observable and non-observable elements
- Proposed test scenarios and configuration assumptions
- Log, product and laboratory evidence requirements
Deliverables, availability, fees and timing are agreed in a proposal before work begins. An initial enquiry does not create an engagement or an NDA.
The decision this supports
Determine what evidence is worth seeking before commissioning product investigation.
What to prepare
- The claim elements or mapping assumptions requiring implementation evidence.
- Named product categories and any lawfully available public technical information.
What you receive
The following is a proposed scope, confirmed in writing before engagement.
- An evidence-gap matrix identifying what still needs to be observed.
- Candidate observable behaviours and questions for a qualified testing partner.
- A staged investigation plan with dependencies and limits.
Proposed handover: a PDF evidence plan and editable question/evidence matrix.
Where the scope stops
Laboratory testing, reverse engineering, device acquisition and access to third-party proprietary material are not included unless independently arranged and explicitly agreed.
Review and handover
Agree the source set and acceptance criteria first. The handover should identify assumptions and unresolved points, and distinguish findings from recommendations. Any revisions, walkthrough or follow-on work are specified in the proposal.
Inspect the illustrative report ↗How we begin
Share your objective and, if useful, a public publication number. We clarify the scope and confidentiality requirements before requesting sensitive documents.
Discuss this service ↗Technical findings support a decision; they do not establish validity, infringement or a legal outcome.