Incident reconstruction
A forensic sitting after a failure involving handlers — double submit, a frozen page, a modal that would not close — written up for the people who have to explain it.
- Format
- Reconstruction from traces and a short report
- Duration
- Three to ten days, depending on the record you already keep
- Where
- Melbourne or video; on-site when the failure still reproduces
- Fee basis
- From AUD 4,200
Incident reconstruction starts from a moment: a form that posted twice on a Thursday afternoon, a checkout that ignored the first tap, a status-page widget that kept listening after it was removed from the page. We read whatever traces, screen recordings, and builds you still have, and we write the sequence of listener activity that made that moment possible.
This sitting is narrower than the flagship analysis. We do not catalogue every attach point in the application. We follow the incident, name the handlers that participated, and say what we cannot know because the record is thin.
If the failure no longer reproduces, say so in the brief. A reconstruction from a partial log is still a reconstruction; it will carry the gaps on the page rather than filling them with guesses.