Web view and summary
What the protocol app stores
The protocol app creates protocols and stores the related data permanently:
- Media (e.g. photos, videos) as files
- Structured data as JSON objects (including the protocol payload, metadata, and links)
That content lives in S3-compatible cloud object storage. The model treats stored objects as the authoritative, non-rewritable record for a completed protocol — not a casual working copy you overwrite at will.
Checksums and traceability
Cryptographic checksums apply to key JSON and to individual media. They support integrity and traceability: you can verify that what is delivered from storage matches what was fixed at completion and signing. For on-screen fields (hashes, signatures), see Certificates and protocol information.
Role of the protocol viewer
The protocol viewer is a read-only viewing app — in the everyday sense of free reader software (no purchase required to view; no editing of the storage layer):
- It renders the JSON and media served from S3 in a clear UI (structure, gallery, PDFs, info pages, etc.).
- It does not replace the protocol app and does not mutate canonical objects in the bucket; protocol changes — where allowed — happen in the creator’s app, not in the viewer.
That lets recipients, parties, or reviewers inspect, download, and verify content without being a paying full-product user or having write access to storage.
Web view
The protocol is shown as a web page in your browser (link from email, QR code, or share). Content reflects the structured data and media loaded from storage, split into sections you can jump to via the menu.
Typical protocol structure
Depending on occasion and template, you may see blocks such as (often represented in JSON as object, text, media, and related sections):
| Area | What it covers |
|---|---|
| Object information | Address, label, object context |
| Text information | Free and guided text, notes, descriptions |
| Media | Photos, videos, embedded documents (see also Images and media) |
| Sectors / areas | e.g. exterior, interior, or thematic areas |
| Rooms | Rooms inside areas, sometimes with their own ratings |
| Defects | Recorded defects with description, assignment, remedy, costs |
| Checklists | Checked items, answers, optional photos per line |
| Legal text | Notices, clauses, footer copy |
| Signatures | Status and display of signatures (see Signature options) |
Not every protocol includes all blocks; only what was created and published appears.
Map with annotations (defects)
When defects are tied to coordinates, a map can be shown. Markers / annotations indicate where each defect was located, so you can relate the map to lists and narrative elsewhere in the protocol.
Summary (list view)
The summary packs much of the protocol into compact lists and tables — often under a heading like “Protocol summary in list view”. It gives a quick overview and may highlight changes vs. a previous protocol (e.g. handover vs. takeback), so shifts in condition are easier to spot.
Typical blocks (labels may vary slightly):
Interior areas (or similar room/area lists)
Rooms or areas with a short status, e.g.:
- Kitchen — OK
- Bedroom — OK
Icons (checkmark, warning, etc.) make the assessment scannable.
Defects
List or table with columns such as:
- Defect (no. / title)
- Description
- Area / Object
- Remedy (e.g. tenant repair, “as-is”)
- Cost incl. VAT
Results by area
Table comparing, for example:
- Label (area)
- Current condition
- Previous condition
- Change in condition
Meter readings
Rows for meter type, ID, reading, reading date, area (or “–” if not set).
Fixtures / inventory
Items such as appliances with name, area, condition, manual / documentation (if captured).
Navigation
Use the menu (sidebar, header, or anchors) to open the full detail sections. The summary compresses content; it does not replace the detailed views.
Print view
Print from the browser (or a protocol action) produces a print-friendly layout. Lists and tables from the summary are usually included; page breaks may differ by browser.
More help
Other protocol viewer articles: Media, Documents, Signatures, Display & translation, Delete request. For creating protocols, see Create protocol; for the in-product archive, see Archive.