Document identity
A report number identifies the record while the revision represents controlled change.
Record integrity
Revision history and audit trails for inspection records
A defensible inspection history distinguishes the issued record from a later correction. Fenwix currently gives completed local inspections a report identity and revision context, and verifies supported source records against their stored integrity data. A shared, multi-actor enterprise audit trail is a separate roadmap capability.
CURRENT, SCOPED
Completed local records and report revisions are current. Organization-wide append-only event history, shared actor identity and cross-device conflict history are not current Solo capabilities.
Source verification
Supported manifests compare the stored local source record and linked photo evidence.
Enterprise event history
Multi-user, cross-device actor events and policy-grade audit export remain planned.
Architecture flow
COMPLETED RECORD · R1
↓ controlled amendment
EDITABLE WITH REASON
↓ complete again
SAME REPORT NUMBER · R2How does a controlled revision differ from silent editing?
CURRENT
Silent editing makes it difficult to know whether a report reflects the original completion or a later correction. Fenwix requires a completed inspection to enter an amendment path before it can be changed, then issues the recompleted record as a later revision under the same report number.
- Stable report identity
- Explicit revision number
- Amendment reason in the local record
- Recompletion after the correction
- Historical behavior is preserved by manifest version rather than rewritten
What does current source-record verification cover?
CURRENT, SCOPED
The local verifier computes the supported manifest from the stored source record and compares it with the recorded digest. It also rechecks linked photo files when those files are present. Coverage depends on the manifest version attached to the record.
- Version-aware canonical record comparison
- Missing or changed linked photo detection
- Report key and local source-record match
- No claim that the field statement itself is true
- No claim that a PDF exported outside Fenwix is cryptographically signed
What would an enterprise audit trail add?
ENTERPRISE ROADMAP
Shared operations require more than a revision label. A future enterprise layer must preserve actor identity, device provenance, append-only events, synchronization conflicts, policy decisions, export history and reliable time semantics across authorized devices.
- Authenticated user and device events
- Conflict branches and explicit resolution
- Report-generation and export events
- Policy and approval history
- Retention and legal-hold behavior
- Machine-readable audit export
How should procurement test an audit-history claim?
Ask the vendor to demonstrate a correction, export and recovery path using a real record. A screenshot of an activity feed is not enough if events can disappear, identities are ambiguous or exported data cannot be independently related back to the source record.
- Can a completed record be edited without a revision?
- Does the same report identity survive correction?
- Which fields are covered by each integrity version?
- Can the system distinguish evidence submission from verification?
- What happens when two offline devices change the same record?
Frequently asked questions
Does Fenwix keep a revision number for completed reports?
Yes. A controlled amendment can produce a later revision while preserving the report number.
Can a completed record be silently overwritten?
The intended current path requires an amendment before editing and recompletion.
Is the current history a full enterprise audit trail?
No. It is a local, scoped record and revision history, not an organization-wide multi-user event ledger.
Does verification prove the inspection was factually correct?
No. It checks supported record integrity and linked evidence presence or match; it does not determine real-world truth.
Are old records forced into the newest integrity format?
No. Historical records are verified according to their own supported manifest version rather than silently rewritten.
Related architecture and product surfaces
Ask what history is recorded, covered and exportable
Current Fenwix revisions make corrections visible in the local source record. Evaluate the separate enterprise roadmap when multi-user actor history and shared policy evidence are required.
Content status: CURRENT_SCOPED · Last reviewed: 2026-08-16
Claim basis: Fenwix current application flow · Fenwix product decision record · Fenwix.net aligned master brief