One source record
The report is composed from the completed inspection instead of a separate document draft.
Inspection report app
CURRENTCreate reports from the inspection record, not from retyping
Fenwix turns a completed Android inspection into a numbered PDF report using the local source record. Checklist results, findings, evidence references, signatures and revision context stay connected, reducing manual re-entry while giving reviewers a clear route back to the record used to produce the report.
Stable identity
Issued records carry a report number while controlled changes increase the revision.
Scoped verification
The verifier compares the report key with the local source record and linked photo files.
From inspection to issued report
- Complete answers
- Resolve required fields
- Seal the record
- Generate PDF
- Verify or revise
What appears in a Fenwix inspection report?
The report presents the organization and document identity, inspection context, summary, findings, actions, evidence references, verification information and detailed checklist results according to the current report flow.
- Report number and revision
- Site, inspector and inspection context
- Findings, owners, due dates and evidence
- Checklist detail, signatures and page numbering
How do revisions work?
A completed record is not silently overwritten. A controlled amendment returns it to an editable state, records the reason and produces a later revision while retaining the report identity. This makes a correction distinguishable from an unrelated new inspection.
- Report number remains stable
- Revision increases after amendment and recompletion
- The source record carries revision context
- A full distributed enterprise audit log is a separate roadmap capability
What does report verification prove?
Fenwix verification checks the stored source record using its supported manifest version and rechecks linked photo files where available. It can surface a mismatch or missing file. It does not prove that the real-world statement was true or that an exported PDF was never edited outside Fenwix.
- Source-record integrity check
- Linked photo file recheck
- Version-aware verification
- No guarantee that a record is impossible to alter or automatically admissible
Report boundary
- The PDF is a derived output; the source record is the verification basis
- Report customization available only in an unpublished candidate is not claimed here
- The report supports review but does not replace professional or legal assessment
Inspection report questions
Can Fenwix create a PDF inspection report?
Yes. A completed inspection can be rendered as a PDF from the local source record.
Does a corrected report keep the same number?
Yes. The document identity remains stable and the revision changes after a controlled amendment.
Can someone verify the report online?
No public vendor-hosted verification page is currently claimed. Verification uses the supported local Fenwix source record.
Can the exported PDF ever be altered?
An exported file can be changed outside Fenwix. Fenwix provides source-record integrity checks; it does not claim that any PDF file is impossible to alter.
Build the record behind the report
Produce a report from a real source record
Complete an inspection, generate its PDF and run the local verification path before adopting the workflow more broadly.
Try Fenwix on Google PlayContent status: CURRENT · Last reviewed: 2026-08-16
Claim basis: Fenwix current application flow · Fenwix product decision record · Fenwix.app aligned master brief