NC-01Non-conformance
No standardized capture
Every engineer structured their own checklist, so report quality and depth varied by whoever ran the audit.
Texas SoluTech Co. Ltd
Electrical safety consultancy
From clipboard to platform: 1,000 audit reports a week
Texas SoluTech's field engineers produced electrical safety audits on paper — 2 to 5 days per report. We built a mobile-to-cloud audit platform that now carries over 1,000 reports a week across eight audit types.
2–5 days
seconds
The time it takes Texas SoluTech to turn a completed site audit into a finished, client-ready report.
- Reports per week
- 1,000+Reports per week
- Audit types live
- 8Audit types live
- Standardized output
- 100%Standardized output
- Hazard notification
- Real-timeHazard notification
- Client
- Texas SoluTech Co. Ltd
- Industry
- Electrical Safety & Compliance
- Scope
- Mobile app · REST API · Web dashboard
- Audit types
- 8
Texas SoluTech Co. Ltd is online at www.texas-solutech.com(opens in a new tab)
The problem
A reporting process running on paper
Texas SoluTech's field engineers were running a paper-based audit process. Checklists on clipboards, photos on personal phones, reports manually assembled in Word or Excel after returning from site.
A single audit report took two to five days to produce. With a growing client base and multiple facility types to cover at once, that model had hit its ceiling — the business had scale ambitions the process could not meet.
5 findings
NC-02Non-conformance
No central record
Findings, photos, and report status lived in inboxes and local files. Nobody could answer what was outstanding without asking around.
NC-03Non-conformance
Untraceable QC review
Quality control happened over email. There was no record of who reviewed what, when, or what changed between drafts.
NC-04Non-conformance
No compliance history for clients
Clients received a PDF attachment and nothing else. Tracking their own compliance over time meant digging through old email.
NC-05Non-conformance
Fragile photo evidence
Evidence sat on personal devices with no archive and no integrity guarantee — the weakest link in a compliance document.
What we built
One record, from the site visit to the client portal
A cloud-native platform in three layers: engineers capture on mobile, a NestJS API holds the record, and administrators and clients work from a web dashboard.
Mobile app
Capture that cannot be filled in wrong
For Field engineers
Engineers pick an audit type on site and get the exact structured checklist for it. Every checkpoint has a defined response — compliance status, observation notes, and a photo attached directly to that checkpoint.
Completeness enforced at submission
An audit cannot be submitted with gaps. Every section is validated before the record leaves the device.
Photos go straight to S3
Evidence uploads at the moment of capture, keyed to the checkpoint and audit record. No camera roll, no manual labelling, no lost files.
Drafts survive bad connectivity
Audits save locally and sync when there is signal, so a single audit can span several sessions and several site visits.
Web dashboard
Review, approve, publish — on the record
For QC managers & client companies
QC managers see submissions arrive in real time over Socket.io. They open a submission, read every checkpoint response and photo, leave inline comments, and either approve it or return it for revision.
Every review action is logged
The full cycle carries timestamps and actor identity, which is what turns a report into an audit trail.
PDF generated on approval
Approval triggers a formatted, complete, consistent report — produced in seconds rather than assembled by hand.
Client portal instead of attachments
Client companies log in to see their own reports, thermographic results, lux surveys, danger notifications, and downloadable PDFs. No email threads, no version confusion.
The results
9 faults, cleared
Every constraint the old process imposed, and what replaced it.
CircuitBeforeAfter
- Time to produce one reportBefore2–5 daysFaultFaultAfterSeconds
- Weekly report capacityBeforeManual bottleneckFaultFaultAfter1,000+
- Photo evidence integrityBeforePersonal devicesFaultFaultAfterUUID-keyed S3
- QC review cycleBeforeEmail, daysFaultFaultAfterDashboard, hours
- Client deliveryBeforeEmail attachmentFaultFaultAfterSelf-service portal
- Concurrent audit typesBefore1, manualFaultFaultAfter8
- Danger notificationBeforePhone callFaultFaultAfterInstant, on record
- Report consistencyBeforeEngineer-dependentFaultFaultAfter100% standardized
- Compliance audit trailBeforeNoneFaultFaultAfterFully timestamped
9 circuits · all clear
The outcome
Reporting stopped being the constraint
Adding clients no longer means adding report-writing headcount. The platform handles the assembly; the engineers handle the judgment.
Texas SoluTech turned a manual reporting bottleneck into a platform. Reporting capacity now scales without hiring against it.
The platform has become part of how they sell. Clients get real-time compliance visibility, immediate hazard notification, and a self-service audit history — not a PDF in their inbox.
The stack
What it runs on
Mobile
React Native
API
NestJS, TypeORM, PostgreSQL
Web
Next.js 16 (App Router), React 19, Tailwind CSS
Auth
Passport.js (JWT), NextAuth.js, Google OAuth
Storage
AWS S3 — pre-signed URLs, UUID keys
Puppeteer + pdf-lib
Real-time
Socket.io
Deployment
Render.com (Docker), managed PostgreSQL
Your bottleneck is somebody's platform
If your team is assembling the same document by hand every week, there is a version of this build for you. Let's scope it.
