Skip to main content
Cayley | Independent Technology Assurance & Advisory

Methodology

How we establish technical facts

Every engagement follows the same method. It is designed to produce a result that holds up in front of a client, counsel, an investment committee or a court.

The method has five steps

We use five steps because the work needs them. We do not force a matter into a shorter shape to look tidy.

  1. Define the question

    We agree the decision the work must support and the scope boundary. A narrow, answerable question produces a defensible result. An open brief does not.

  2. Preserve and collect evidence

    We secure the repositories, accounts, records and systems the review depends on before anything changes. Where evidence is at risk, preservation comes first.

  3. Test the technical position

    We examine the evidence against the claim being made. We separate what the records show from what has been asserted.

  4. Rate risk and confidence

    We classify each finding by materiality and by the strength of the evidence, using a fixed confidence scale so the reader can weigh each point.

  5. State the next action

    We set out the practical step, the owner and the timing where possible, so the finding leads to a decision rather than a discussion.

How we rate confidence

Each finding carries a confidence level in both text and colour, so no conclusion rests on certainty it does not have.

Confirmed
The evidence reviewed directly supports the finding.
Supported
The available evidence supports the finding, with minor gaps.
Indicative
The evidence points to the finding but is incomplete.
Unknown
The evidence needed to reach a view was not available.

What a finding looks like

Findings follow one structure across the report and the briefing. The example below is illustrative and composite, not a real matter.

F-014Material risk

Production repositories contain unassigned contractor code

Evidence
Repository history, contributor email addresses and the agreements supplied for review.
Impact
The seller may be unable to demonstrate clean title to all production source code.
Confidence
Confirmed
Limitation
The review did not include records held by two former contractors.
Recommendation
Obtain executed assignments or address the ownership gap in the transaction documents before completion.

What you receive

  • An executive summary written for the decision-maker
  • Findings rated for risk and confidence
  • An evidence appendix that traces each finding to the records reviewed
  • An action plan with owners and timing where possible
  • A verbal briefing on request

A named expert accepts the conclusion

Research and comparison may be assisted by software. A named human expert reviews and accepts responsibility for every published technical conclusion.

Discuss a matter

If you have a decision, transaction or dispute that turns on a technical question, outline it and we will review the scope.