To make sample collection and site documentation defensible and compliant in a mobile inspection app, focus on three things:

1. Prove who collected what, when, where, and how
2. Preserve data integrity and chain of custody
3. Make the workflow consistent, auditable, and aligned to your SOPs/regulations

Here’s a practical checklist.

---

1) Build the workflow around your SOPs and regulatory requirements

Your app should mirror your approved procedures, not replace them.

Include:

• Required sample types, collection methods, and preservation steps
• Field parameters to record
• Acceptance criteria for sample IDs, labels, and containers
• Chain-of-custody steps
• Deviation/incident reporting
• Photo and note requirements
• Sign-off and review steps

If you work under specific rules, map the app to them, such as:

• EPA / state environmental requirements
• ISO 17025 / ISO 9001 controls
• FDA / GMP / GLP expectations
• Internal quality systems

---

2) Capture complete metadata at the time of collection

For every sample and inspection record, capture:

• Unique sample ID
• Project/site ID
• Date/time collected
• Exact location
• Collector name and credentials
• Sample matrix/type
• Depth, borehole, station, or asset ID if relevant
• Preservation method
• Container type and count
• Field measurements
• Weather/conditions if relevant
• Any anomalies or deviations

Avoid free-text only records for critical fields. Use structured fields, drop-downs, and validation.

---

3) Use reliable location and time capture

To support defensibility:

• Capture GPS coordinates automatically
• Record accuracy/precision of the GPS fix
• Save timestamp in a consistent time zone, ideally UTC plus local time if needed
• Prevent manual overwrite of system time unless there is an approved exception
• If possible, capture geotagged photos

If GPS is weak indoors or in remote areas:

• Allow manual location entry only with justification
• Record the basis for location determination
• Add maps, sketches, or reference points

---

4) Create an auditable chain of custody

Your app should log:

• Sample collection
• Sample transfer between people
• Storage conditions
• Shipment to lab
• Receipt by lab
• Any custody breaks or deviations

Best practices:

• Require electronic signatures or equivalent authenticated acknowledgments
• Timestamp every transfer
• Identify the person responsible at each step
• Maintain custody history without overwriting prior entries

---

5) Make records tamper-evident

Defensible records need clear evidence they weren’t altered improperly.

Use:

• Immutable audit trails
• Version history for every change
• Reason codes for edits
• User authentication and role-based permissions
• Read-only finalized records
• Hashing or digital signatures where appropriate

If a record is corrected, preserve the original entry and show the correction path.

---

6) Standardize photos and attachments

Photos are powerful evidence if handled correctly.

Require:

• Date/time stamp
• GPS tag if available
• Photographer identity
• Linked sample/site ID
• Clear subject matter guidelines
• Photo notes describing what is shown
• No replacement of originals; only add annotations or derived copies

Good practice:

• Capture overview, mid-range, and close-up photos
• Include scale references where relevant
• Use photo checklists for repeatable documentation

---

7) Use validation and required fields

Prevent incomplete or inconsistent documentation by making critical fields mandatory.

Examples:

• Sample ID cannot be duplicated
• Collection time must be within the inspection window
• Preservation must match sample type
• Container count must meet the method requirement
• Required photo attachments before closure
• Signature required before final submission

Also use:

• Range checks
• Logic checks
• Cross-field validation
• Controlled vocabularies

---

8) Separate draft from final records

To stay defensible:

• Allow field editing while in draft
• Lock records when finalized
• Require formal correction workflow for changes after finalization
• Keep all versions and timestamps

This helps avoid accidental overwrites and shows record lifecycle clearly.

---

9) Support offline use without losing integrity

Mobile apps often work in areas without connectivity.

Make sure offline mode:

• Stores records securely on-device
• Encrypts local data
• Tracks when data was collected versus synced
• Prevents duplicate uploads
• Resolves sync conflicts with an auditable process
• Flags unsynced records clearly

The app should preserve the original collection timestamp, not the sync time, as the primary event time.

---

10) Train users and document competence

A defensible system depends on trained users.

Maintain:

• Initial and refresher training records
• SOP acknowledgments
• Role-based permissions
• Competency checks for sample collectors/inspectors
• User guidance inside the app for critical steps

Training should cover:

• How to collect samples correctly
• How to document deviations
• How to handle corrections
• What cannot be changed after submission

---

11) Implement QA/QC checks

Add quality controls such as:

• Duplicate sample review
• Random record review
• Photo-to-record verification
• Location validation
• Lab result reconciliation
• Supervisor approval for exceptions

Track metrics:

• Missing field rate
• Edit rate after submission
• Chain-of-custody exceptions
• GPS accuracy issues
• Rejected samples or documentation gaps

---

12) Protect data security and privacy

Compliance also includes data protection.

Use:

• Role-based access control
• Strong authentication
• Encryption in transit and at rest
• Device lock and remote wipe
• Segregation of client/project data
• Retention and disposal policies

If personal data is collected, make sure you meet applicable privacy requirements.

---

13) Prepare for audits and legal review

Your app should make it easy to answer:

• Who collected the sample?
• Where exactly was it collected?
• When was it collected?
• What method was used?
• Who had custody afterward?
• Were there any deviations?
• Was the record altered? If so, how and by whom?

Have exportable reports that include:

• Full audit trail
• User actions
• Signature history
• Timestamped photos and attachments
• Chain-of-custody log
• Any exception notes

---

14) Validate the app before relying on it

If the app is used for regulated work, verify it performs as intended.

Validation should cover:

• User roles and permissions
• Required field enforcement
• Offline/online sync behavior
• Audit trail integrity
• Signature capture
• Data export accuracy
• Label generation
• GPS/photo metadata
• Error handling and recovery

Document test cases, results, and approval.

---

A practical “defensible record” checklist

Before closing a record, confirm:

• Sample/site ID is unique and correct
• Collector identity is recorded
• Time/date are accurate
• GPS/location is captured with acceptable accuracy
• Method and field observations are recorded
• Photos are linked and labeled
• Custody transfer is logged
• Deviations are documented
• Required signatures are complete
• Record is finalized and immutable
• Sync status is confirmed

---

Common mistakes to avoid

• Relying on free-text for critical data
• Allowing edits without audit trail
• Not recording time zone or GPS accuracy
• Overwriting originals instead of versioning
• Missing chain-of-custody steps
• Using shared user accounts
• Letting offline records sync without conflict controls
• Not validating the app before use

---

If you want, I can turn this into:

1. a field-ready checklist,
2. a QA/compliance SOP outline, or
3. a mobile app requirements list for your inspection team.