Exposed pipework at kitchen base-unit line
For leak-detection & Trace and Access firms
One contractor case record.
Capture the finding. Generate the contractor report.
TraceRecord helps contractors keep supplied evidence, methods, readings, the engineer-approved finding and its limitations connected through to a reviewed report. The engineer finds the leak; TraceRecord structures the record and assembles the report.
Try the workflow · See the output
Public beta · Free while in beta · No account, upload or paymentUse fictional or properly redacted demonstration data only. Records are held in this browser.
From site evidence to contractor report
Recorded evidence P-04, M-02 and T-02 converge on engineer-approved finding F-01. Limitation L-01 stays attached to that finding, and both are carried into the fictional contractor report TR-FX-26-042.
Recorded evidence
22.4% WME · kitchen skirting
Pressure test held for 12 minutes
Engineer finding
Leakage strongly indicated around concealed heating pipe beneath the kitchen floor.
Exact failed section not observed actively leaking before access.
Report output
Alder & Vine Leak Detection
Trace & Access Investigation Report
Findings · Kitchen
F-01 Leakage strongly indicated around concealed heating pipe beneath the kitchen floor.
Evidence relied upon
P-04 · Plate 4 M-02 T-02
Limitation
L-01 Exact failed section not observed actively leaking before access.
Engineer review · approved v1
Fictional sample · not for issue
Demonstrated on Trace & Access. Also structured for Leak Investigation · Moisture Evidence · Escape of Water.
The reporting problem
Reports get rebuilt in the evening, from material that scattered during the day
Investigation material reaches the reporting stage as job sheets, messages, photographs, readings and brief engineer notes. TraceRecord keeps the visit in one reviewed record so the contractor document does not have to be reconstructed later.
The record scatters before it is written up
- Photographs spread across phones and messages.
- Readings stored separately from the job they belong to.
- Site notes incomplete by the time they are read.
- Limitations missing from an otherwise confident finding.
- Questions returned to the engineer days later.
- The visit reconstructed in the evening.
One record, captured while it is fresh
Methods, readings, photographs, work status and limitations are captured as named parts of the same record, reviewed by the engineer, and carried into the contractor document with evidence and approval still attached.
Operational benefit
Less reconstruction
The visit is recorded once, on site, in the structure the report already expects.
Operational benefit
Fewer clarification loops
Missing information is visible while the engineer is still on the record, not after the report is drafted.
Operational benefit
Faster handover
Report staff start from approved inputs instead of interpreting scattered notes.
For leak-detection engineers, Trace & Access specialists, investigative plumbers, moisture technicians and other firms that turn site evidence into technical contractor reports.
How the connected record works
Origin, evidence, limitation and approval stay attached
The investigating engineer owns the technical judgement, certainty, limitations and wording. TraceRecord structures the record, links the supplied evidence and assembles the report. It does not diagnose leaks, validate conclusions or decide insurance matters.
Information origin
Reported, observed, measured and interpreted stay separate
An account does not silently become an observation, and a reading does not become a conclusion. Each entry carries its origin through the record.
“The damp appeared after the radiator work.”
Staining across a 600 mm base-unit run.
1.4 to 0.8 bar over 30 minutes, circuit isolated.
Results are consistent with one concealed circuit.
The origin label stays visible wherever the information is used. TraceRecord organises the distinction; it cannot decide whether an account is reliable.
Evidence and judgement
The engineer decides what the evidence supports
Evidence keeps its factual description. The engineer records whether it is primary, supporting, contextual, conflicting, inconclusive or not relied upon.
Heating circuit fell from 1.4 bar to 0.8 bar with the circuit isolated.
J-01 · engineer judgement
Relied upon as the principal support for J-01.
EV-04 is listed under “Evidence relied upon” in J-01.
Changing an evidence role changes the record relationship, not the measurement. Removing relied-upon evidence is a material change and returns the approved version to pending engineer review.
Limitations and bounded findings
State what was established—and what was not
The test result and its boundary travel together. A linked limitation prevents a short finding from becoming broader than the recorded investigation.
No active leakage was directly observed during the accessible inspection.
This does not exclude intermittent, concealed or out-of-scope leakage.
LIM-02 · linked to J-01 / F-01 Access was limited to the agreed removable plinth and service-void area. The full floor void and communal riser were not opened.
The limitation stays attached to the finding it qualifies, so no reader view can present the position without its access boundary.
Readiness and approval
Check the record before the engineer approves it
Readiness reports missing information and internal consistency. It does not validate the technical position or claim insurer readiness.
Which single evidence item most supports this position?
The engineer answers; TraceRecord records the link.- Needs attention Method missing on EV-02
- Complete LIM-02 linked to J-01
- Approval Engineer approved · Version 1.2
- Material finding change Approval returns to pending
Readiness says whether the record contains the expected fields and links. It does not decide whether the method was adequate, whether the conclusion is correct or whether an insurer should accept a claim.
Contractor Case Record
One shared record core. Four specialist questions.
Instruction → evidence → judgement → limitation → approval → output. Each pathway changes the prompts and principal document, not the engineer-ownership boundary.
Public demo
Trace & Access
What was opened, what did it reveal and what was left outstanding?
Keep access, exposed condition, repair and reinstatement separate.
- Principal output
- Trace & Access Record
- Release state
- Public demo available
Report output
One structured contractor report. Four guided reader views.
Choose the intended reader. The selected view changes the starting emphasis and navigation. The approved technical record remains unchanged.
This view starts at
04 Findings · 05 Evidence relied upon · 08 Evidence appendix
Checks the record reads as intended before approval — evidence, method, finding, limitation.
Findings are consistent with a likely concealed heating-pipe leak affecting the kitchen lower wall/floor zone. The exact failed section was not directly exposed during this attendance.
The approved technical record remains unchanged. Reader views help different audiences reach the sections most relevant to them.
Where the reader is invited to enter the document, and how much annotation the contents page carries.
The nine sections, their order, the engineer-approved finding wording and every linked limitation.
TraceRecord assembles the reviewed record into a structured contractor report, ready to inspect and save as PDF through the browser print dialogue.
Free public beta · future pilot
Free while in beta. Paid report generation is a pilot proposition.
The public beta demonstrates structured capture and report assembly. Contractor-branded generation and firm setup are not live self-serve services.
Capture and assemble
- Guided capture in the browser
- Missing-information prompts
- Evidence numbering and limitation links
- Watermarked report preview and four reader views
- Five Investigation Tools, three of them reading the record
Useful for testing whether structured capture improves reporting discipline.
Contractor-branded generation and firm setup
- Contractor-branded output and firm templates
- Methods and wording configuration
- Marked clarity and missing-information comments
- No independent rewriting of the technical conclusion
Pricing is under review. Checkout, subscriptions and self-serve paid export are not live.
Data and professional boundaries
Reporting support without taking over the investigation
Technical findings remain authored and approved by the investigating engineer. TraceRecord structures the record and assembles the report.
TraceRecord supports
- Guided capture
- Evidence organisation
- Missing-information and limitation prompts
- Approval state and version history
- Contractor-report assembly
Your firm remains responsible for
- Investigation and testing
- Interpretation and technical judgement
- Certainty and technical wording
- Approval and issue
- Insurance, liability and specialist advice
Public-beta data boundary
- Records are held in your browser on this device. There are no accounts, uploads, cloud storage or payments.
- Use fictional or properly redacted demonstration data only.
- Do not enter identifiable customer, property, insurer or claim information.
- Secure pilot transfer and retention must be agreed separately.
Investigation Tools
Instruments that read the record
The Photo Desk, Finding Evidence Board and Record Readiness read the Contractor Case Record held in your browser and return their work to it only when you choose “Apply to record” and confirm the exact changes. Job Margin and the Invoice & Quote Builder stay commercially separate and touch no technical content.
Questions from specialist firms
What the public beta does, in plain terms
Does TraceRecord diagnose the leak or write the conclusion?
No. The investigating engineer performs the investigation, selects the source position, writes or approves the technical wording and approves the exact version. TraceRecord structures the supplied information and assembles the report. It does not validate findings, prove causation or choose certainty.
Who approves and issues the report?
The contractor or investigating engineer. A material change to the finding, source status, relied-upon evidence or a linked limitation returns the record to pending approval. A report administrator may prepare the layout but should not rewrite the technical position.
What is available in the public beta?
A browser-local fictional Trace & Access workflow, guided capture, evidence and limitation prompts, readiness checks, a watermarked report preview with four reader views, and five Investigation Tools — three of which read the case record and return work to it on an explicit confirmation. Paid report generation and firm setup are pilot propositions. There is no checkout, subscription, account or cloud storage.
How do I get a PDF?
TraceRecord assembles the reviewed record into a structured contractor report, ready to inspect and save as PDF through the browser print dialogue. There is no hosted PDF service, report archive, email delivery or client portal in the beta.
Can live case files be uploaded?
No. There is no upload route. Use fictional or properly redacted demonstration data only, and do not enter identifiable customer, property, insurer or claim information. Live pilot transfer, access, retention and deletion must be agreed separately.
Is TraceRecord a CRM or job-management system?
No. It is deliberately narrow: guided investigation capture, engineer approval and contractor-report assembly. It is not a CRM, scheduling service, payment system, upload portal, loss adjuster or expert-witness service, and it does not decide insurance coverage, liability or claim acceptance.
Next step
See whether TraceRecord fits your reporting process
Explore the fictional Trace & Access workflow, review the sample contractor report, then tell us how it behaved on your kind of job.
Pilot interest and beta feedback both go through the same Google form (opens in a new tab). There is no email enquiry route yet: operator contact details are published on the public beta scope and release status notice when they are verified. You can also prepare a redacted pilot brief locally — nothing is submitted from that page.