V.I.S.I.O.N.™ Workflow / Operator Manual
Verified Interagency Safety Information & Oversight Network · Fictional/no-record prototype documentation
Operating doctrine
Protect people. Protect rights. Protect the record. The mobile field flow captures information first, generates a fixed report second, and then sends the report into the reviewer workbench for triage, action tracking, and revision-safe updates.
Primary sequence
- Start New Field Report
- Person Entry
- Scene Entry
- Hazards Entry
- Items Entry
- Photos / Attachments
- Notes
- Final Review
- Generate Fixed Report
- Review through Workbench
Page functions
Home / Start
Starts a new fictional field report and confirms the current configured mode.
Person Entry
Captures person type, unknown identifier, alias/description, identity confidence, safety caution, rights visibility, and person notes.
Scene Entry
Captures scene type, location description, scene status, staging notes, preservation condition, and weather/visibility notes.
Hazards Entry
Prompts the user to actively look for chemical, terrain, mechanical, stored-energy, electrical, biohazard, fire/heat, weapons/violence, traffic, weather, structural, water, animal, visibility, and other hazards.
Items Entry
Captures item/property name, item type, handling status, location/description, and custody/preservation note.
Photos / Attachments
Captures photo/attachment category, related section, mock/sanitized file name, markup/annotation note, safe-photo acknowledgment, and prototype/non-evidence acknowledgment. Prototype users must not upload real protected records or real evidence images.
Notes
Captures note category, priority, field/reviewer note, and recommended next action.
Final Review
Shows the captured summary, missing/skipped sections, hazards, items, attachment indicator, and final generation control.
Sequence flowchart
Open protected workspace ↓ Launch mobile simulator ↓ Start New Field Report ↓ Person Entry → Scene Entry → Hazards Entry → Items Entry → Photos → Notes ↓ Final Review ↓ Generate Fixed Report ↓ Reviewer Workbench ↓ Status tracking / action board / revision-safe updates
Revision rule
The generated report is read-only by default. Corrections must create a revision copy. The original report/note remains untouched, and any revised version receives a visible revised-copy tag.
v28 update
Scene Entry Refinement
Scene Entry is now treated as a capture/interview page. It records scene type, location description, scene status, staging/approach notes, preservation condition, and weather/visibility notes before the user moves to the dedicated Known / Observed Hazards step.
Hazards remain separate so the fixed report can show basic scene context and hazard recognition as distinct sections.
v29 build standard
Hazards Entry Refinement
Purpose: Hazards Entry is a dedicated capture and training page. It stays separate from Scene Entry so the user is prompted to actively look for hazards before moving deeper into the workflow or touching items.
- Capture: Known / Observed Hazards checklist plus Other / describe.
- Guidance: Selected hazards generate approach / staging prompts.
- Preservation: Selected hazards generate scene-preservation prompts.
- Acknowledgment: User acknowledges hazard review and scene preservation before Items Entry.
- Report: Generated fixed report includes a dedicated Hazards Entry Summary.
Hazard categories: Chemical, Terrain, Mechanical, Stored Energy, Electrical, Biological / biohazard, Fire / heat, Weapons / violence risk, Traffic / roadway, Weather / environmental, Structural / collapse, Water / drowning, Animals, Visibility / darkness, and Other.
v31 Safety Review + Training Links
After Hazards Entry, the mobile interview should include a Safety Review step that uses the selected hazards to suggest relevant Dingfelder Training topics. This keeps the field form focused while still using the existing Dingfelder training library as the safety-reference backbone.
- Safety Review belongs after Hazards Entry and before Items Entry.
- Training links should support preparation and after-action review, not distract from urgent field action.
- The generated fixed report should include selected hazards, suggested safety review topics, selected training review topics, and the Safety Review acknowledgment.
- The primary training link is
/training/.
v31 Hazard Review Cards
Hazard rows now split selection and guidance. The left side selects the hazard. The right-side Review control opens a short in-app reference card. Review cards are scene guidance only; they are not quizzes, certifications, or replacements for agency policy.
The Chemical review card must emphasize hazardous and explosive gases, unknown vapors, oxygen displacement/asphyxiation risk, upwind approach if someone is down, immediate assistance, proper PPE/monitoring/trained support, and the rule: do not become the next victim.
v33b Openable Photo Preview
Photos / Attachments should allow the selected mock/sanitized image to be opened from Photos / Attachments, Final Review, and the generated fixed report. The open image link is for prototype verification only; it does not make the attachment evidence and does not replace agency photo/evidence policy.
- Show selected file name.
- Show an image preview when possible.
- Provide an Open selected image link.
- Clear preview/open link when the file is removed or a new report starts.
- Continue to warn users not to upload real protected records or sensitive images.
v34 — Notes Entry Refinement
Notes Entry is the final safe capture step before Final Review. It captures note category, priority, field/reviewer note, recommended next action, follow-up status, and a no-restricted-data acknowledgment. Shared logs, status boards, action tracking, and revisions remain in Reviewer Workbench after a report exists.
- Note category
- Priority
- Field / reviewer note
- Recommended next action
- Follow-up needed status
- Safety acknowledgment
v35 Final Review + LSAR Path Logic
Final Review must show captured, missing, and skipped sections before the fixed report is generated. A Sheriff’s Department LSAR remains under Law as the authority/mode, while LSAR / search is selected as the operational path. If evidence, remains, suspicious items, conflicting information, or crime-scene indicators appear during a search, the workflow should remind users to preserve, document, and escalate according to agency policy.
v36 Generated Fixed Report Refinement
The generated fixed report is the read-only output of the entry interview. It should not look like another entry form. It must show branding, report status, operational path, all captured summaries, missing/skipped indicators, openable photo support, and audit/generation information.
- Generated Fixed Field Report title
- Fictional/no-record prototype label
- Read-only / revision-protected notice
- Person, Scene, Hazards, Safety, Items, Photos, and Notes summaries
- Missing / skipped section summary
- Audit / generation summary
Corrections after generation must create revision copies or follow-up notes. The original generated report remains preserved.
v37 — Open Finished Report as Revision
A generated fixed report remains read-only. Corrections are made by choosing Create revision copy, entering a revision reason, updating the copied interview fields, and generating a revised report. The original generated report remains preserved and the revised copy carries report ID, original report ID, revision number, reason, timestamp, and build version.