A practical incident record stack for Fraser Valley strata properties

When a strata property has a disputed door, damaged common area or after-hours access concern, no single record is likely to answer every question. A guard may document what was observed on patrol. A photo can show a condition at a particular time. The building’s digital key fob system may record a credential event. The property manager’s job is to preserve those records and explain how they relate, without treating one as proof of everything.

For Fraser Valley strata councils, a workable incident stack has three parts: physical security coverage, a consistent guard report with appropriate photo documentation, and records from the property’s own access-control system. They are separate sources. They do not automatically combine, and they may not tell the same story.

1. Define the incident and the record owner

Before a dispute occurs, agree who receives reports, who can request fob-system records, and where the incident file will be kept. Usually, the property manager or another designated strata representative coordinates that file. Keep an incident reference, such as a property-approved case number, on each item or in the file index.

Write down the basic scope of a security assignment: which areas are to be checked, what observations should be reported, and who should be contacted for an urgent concern. Those details should match the site and the council’s procedures. They help keep a guard report focused on assigned duties rather than assumptions about why someone was present.

2. Use patrol for observations, not conclusions

A licensed guard or mobile patrol can provide a physical check of agreed areas and record relevant conditions. At a strata property, that might include a door found open, visible damage, an obstruction, or a concern reported to the guard. The report should separate what the guard directly observed from what another person told them.

Zentra Protection provides security guards and mobile patrol in the Fraser Valley and other parts of its British Columbia service area. Its service information describes documented site updates, photo documentation where appropriate, and supervisor reviews. A council or property manager should confirm the assignment’s reporting expectations in advance, including how reports and exceptions will be communicated.

A photo can help show a condition, but it is not a complete incident account. The report should identify the location, observation time, and why the image was taken, using the agreed reporting format. Avoid collecting images that are unnecessary to document the site issue. Record relevant context in words rather than relying on a photograph to explain it.

3. Request the matching fob records

For a relevant access concern, the property manager can consult the strata’s own digital key fob or access-control records under the property’s established procedures. Identify the door or reader, the time window, and the incident reference before requesting an extract. Preserve the original export or record as received; if a working copy is annotated, keep it distinct from the original.

A fob event can show that a credential was recorded at a reader. It does not, by itself, establish who physically used the credential, why it was used, or what happened after the door opened. Likewise, a patrol observation may confirm a door’s condition later without showing who opened it earlier. Treat each source according to what it actually records.

4. Reconcile the timeline carefully

Put the guard report, relevant photos and access-system records in a single incident file, but keep their source and original timestamps visible. Note any difference in clocks or time formats before comparing events. If the records do not align, say so; do not quietly adjust a timestamp to make the sequence appear certain.

A useful incident summary lists the reported concern, the records gathered, the time range covered, and what remains unknown. It should distinguish confirmed observations from interpretations and identify who assembled the file and when. If the matter may involve an insurance claim, provide the records through the appropriate property or claims process and avoid promising that documentation will determine coverage or liability.

Trade-offs and a simple routine

More records do not always mean a clearer account. Frequent patrols can produce useful observations but add cost and can still miss activity between visits. A fob system can offer a time-stamped event record, but it cannot replace a person checking a physical condition. Photos add context, but only when they are relevant and explained. Set retention and access practices with the property’s policies and the advice of its appropriate professional advisers.

1. Assign an incident-file owner and a consistent reference method.
2. Agree on patrol priorities, reporting expectations and escalation contacts.
3. For each concern, preserve the original report, photos and relevant access records.
4. Build a timeline that identifies gaps and uncertainty instead of filling them with assumptions.

For a broader handoff process between tenant concerns and guard records, see how to connect incident reports to shift records. Strata councils considering apartment security in Langley or elsewhere in the Fraser Valley can ask a provider what coverage and reporting format fit the site, then confirm that the property’s fob-record process has a named owner.

A consistent condo incident log stack is less about buying another platform than agreeing on responsibilities and preserving useful records. Zentra Protection provides strata and condominium security, guards, mobile patrol and documented site updates. Councils can discuss site requirements and reporting expectations before deciding whether physical coverage belongs in their plan.