
Creating a Digital QA System from Zero
Transforming Traditional Paper QA into a Digital Workflow
(Boeing Hangar – Gatwick Airport)**.
01
The Crisis That Exposed the Truth: QA Could No Longer Survive on Paper
![]() | ![]() |
|---|---|
![]() | ![]() |
![]() |
Initial Context
-
QA was entirely analogue: notebooks, loose sheets, paper checklists, and thousands of untagged photos with no location, context, or order.
Project Complexity
-
Dozens of façade and roof zones operating simultaneously.
-
Panels of 9m, 11m, and 14m installed in parallel.
-
Constant defects, damages, deliveries, and remedials.
-
Each observation required precise documentation for traceability.
-
Notebook + simple photos = no longer viable.
Immediate Risks
-
Losing the exact location of photos.
-
Inability to reconstruct defect paths.
-
No clear evidence of who caused damage.
-
No link between deliveries, installation, and events.
-
Weak NCR support.
-
Major financial loss exposure.
-
Loss of control over actual progress.
The Turning Point
-
A new system had to capture exact location, time, comments, and observations in real time.
-
The challenge was also psychological: without instant data capture, critical information would disappear.
-
On a Boeing project, lost information = lost money, lost evidence, lost control.
Conclusion
-
This was the moment I decided to build a new QA system myself — even without any official digital tool available.
02
Building a Digital QA System from Zero — Essential Summary
![]() | ![]() |
|---|---|
![]() | ![]() |
![]() | ![]() |
Light-bulb moment
The project generated too much information to control on paper. I needed a fast way to capture and organise data before QA became unmanageable.
First tools – useful, but not enough
-
Snagging Apps (SitePo / Snagging App): good for quick notes and photos, but no structure, no drawing integration, no complex traceability.
-
SideRise: early-stage, slow, but allowed basic fire-barrier documentation — first sign of order.
-
Bluebeam Revu: powerful for mark-ups, comparing phases, updating drawings, and organising info by gridlines — but still not a full QA solution.
The critical missing link
I still lacked one essential capability:
a tool that captured photos with exact location, timestamp, comments, and export.
Without this, real QA, traceability, and contractual evidence were impossible.
The breakthrough – discovering I-neosyte
I-neosyte provided the missing element:
-
precise photo location
-
automatic timestamp
-
observations & categories
-
clean exports
Then came the key insight:
geo-tagged photos from I-neosyte + Bluebeam mark-ups = the first fully functional digital site diary.
![]() | ![]() |
|---|---|
![]() | ![]() |















