About ScopeRecord
ScopeRecord builds report software for camera scope inspections. The first product is Sewer Scope Report: field notes in, a coded, signed-off sewer lateral report out. This page is the short version of who we are and what we will not claim.
Who builds this
ScopeRecord is a small, independent software shop. This is a deliberately small operation: no sales team, no support queue, no outsourced first line. Replies to support@scoperecord.com come from the person who writes the code, usually the same day.
That has a practical consequence, and it is deliberate: features get built because an inspector asked for them, not because a roadmap said so. If something is missing from the report you have to hand a client, write in — that is the most useful feedback we get.
Why the wording is generated by fixed rules
A report is a document somebody may act on with a five-figure repair bill, so the parts that carry consequence are computed, not improvised:
- Defect codes come from a fixed list of 20 (M- operation & maintenance, S- structural, C- condition), so the same observation always gets the same code — see the code list.
- Severity follows published thresholds (loss of cross-section, timing), and the pipe's 1–5 condition grade is derived from the worst finding.
- Scope and limitations is a required field, not an afterthought: what was inspected, what was not, and with what equipment. A report that hides its own limits is worse than no report.
- Every page carries a report number, the client address, the date, and the inspector's name and license number.
Language generation drafts the prose around those facts. It does not decide the findings, the severity, or the grade.
What we will not claim
- We are not PACP certification. The codes are PACP-style shorthand. A formal PACP deliverable for a municipality still requires a certified inspector, and the app will not pretend otherwise.
- We are not the inspector of record. The licensed inspector who signs the report is responsible for its content. The report says so, on the page, in the signature block.
- We do not tell you what a defect is. You observed it; the software writes it up consistently and completely.
- We do not put our name on your deliverable. Reports go out under your company name, with your branding on Pro. ScopeRecord appears on this website and in email to you — not on the client's report.
Your data, plainly
Your field notes are sent to our AI provider so the wording can be drafted. Evidence photos are stored with your report so they can be embedded in the PDF. The original video stays on your device. We do not sell your data, and we do not use your reports to train models. The full detail is in the privacy policy.
One request: do not paste Social Security numbers, card numbers or other identifiers into the notes field. Reports do not need them, and we would rather never hold them.
Why one brand for several scope disciplines
Every scope discipline has the same shape: a camera goes down something, you record distances and clock positions, and somebody has to be told what it means and what to do next. The rules that make a report defensible do not change when the pipe becomes a duct or a chimney — the codes, templates and vocabulary do. So the engine is shared and the discipline is pluggable; sewer laterals are simply the first one shipped. More on that at ScopeRecord.
Get in touch
Questions before you pay, a bug, a wording you would never use in a report, or a discipline you want covered: support@scoperecord.com.