Approach
Work is structured to be robust and reviewable: clear scope, documented assumptions and reproducible results. Method and deliverables are adapted to the assignment's risk level and requirement profile.
Assignments are always scoped with confidentiality and conflict-of-interest considerations.
Principles
- Traceability: inputs, assumptions, method and versions are documented.
- Reproducibility: results can be repeated with the same inputs and tools.
- Consistency checks: unit/consistency checks, sensitivity and sanity checks.
- Review readiness: report/appendix structure designed for technical review.
Typical delivery flow
- Scoping – objective, scope, data availability, assumptions and delivery format.
- Baseline – reference case + verification of data/configuration.
- Analysis – calculations, comparisons, parameter studies and interpretation.
- Quality assurance – consistency checks, sensitivity, peer-check when needed.
- Delivery – report + appendices + optional reproducible calculation package.
Quality assurance
Quality assurance is adapted to the nature of the assignment. When needed, checklists are used for assumptions, unit checks, run/calculation logging and versioning of delivered artefacts.
- Version identifier on delivery
- Change log (Release Notes) for iterative deliveries
- Structured file and evidence handling when required
FAQ
What information is needed to start?
Ideally: objective/question, system/process description, available inputs and the desired delivery format. Incomplete material is fine – a practical scope is proposed in step 1.
Can you work under NDA/confidentiality?
Yes. When needed, examples and presentations are anonymised, and deliveries are structured so that sensitive data is separated from general methodology.
What do I receive at the end?
Typically a report (PDF/DOCX) with assumptions, method and results plus appendices (tables/figures). When relevant, a reproducible calculation package (e.g., scripts/notebooks) can be included.
How do you ensure the results are reasonable?
Through baseline checks, unit/consistency checks, sensitivity analysis and explicit assumptions. For higher requirements, peer-check and extended verification can be included.