- Archives
- Records Management
- Directory of University Records
- File Classification
- The Model File Classification Plan
- Administration
- Advancement
- Committees
- Communications
- Equipment and Supplies
- Facilities
- Finances
- Governance
- Human Resources
- Information and Technology Management
- Liaison and Cooperation
- Policy
- Records and Information Management
- Research Management and Administration
- Student Services and Records
- Teaching and Academic Programs
- Frequently Asked Questions
- Transfer Paper Records
- Transfer Digital Records
- Retrieve Paper Records
- Annual Destruction and Accession Process
- Links and Resources
- Directory of University Records
- FIPPA
- Digital preservation
- Resources
- About
- Mission, vision and values
- Contact us
- Feedback and comments
- Our blog
- Archival Film Flashes Back to 70s Student Life
- Manuscript Traces SFU's Architectural History
- Early University News Publications Now Digitally Available
- Digitized Programs Commemorate SFU’s Opening & Installation Ceremonies
- Archives Celebrates Fall Convocation with Release of Digitized Programs
- Films Capture Visual History and Sentiment of Time Gone By
- Lost and Found: Simon Fraser Letters
- Oral History Provides Glimpse into Mind of SFU’s First Chancellor Gordon Shrum
- Early SFU Photos Tell a Story That Frames Our World
- Aerial Photos Capture Campus Landscape & Photographer’s Legacy
- You have what...?!! and other interesting things you didn't know about the SFU Archives
- Charting the course of history: documenting SFU's early days from the student perspective (Part 1)
- Charting the course of history: documenting SFU's early days from the student perspective (Part 2)
- Helping others find their history in the future: Preserving the records of the Students of Caribbean and African Ancestry at SFU
- Preserving the sparks of global revolution in the Adbusters Media Foundation fonds
- Reflections of a co-op student
- Debunking popular myths and conspiracies with the Barry Beyerstein fonds
- In "The Beginning...": First student film returns to SFU
- "Got any pictures of Terry Fox?"
- My summer in the archives: a co-op placement retrospective
- Seeing the world through Arthur Erickson's eyes
- Beer (records) in the Archives!
- Quartet in the Quadrangle: PSQ Records Come to SFU
- Navigating silences and filling gaps: finding Black stories in the Archives
- Boxes, boxes, and more boxes: my summer co-op at SFU Archives
- Finding queer joy in the SFU Archives: Out On Campus records now available
- The Selma Wassermann fonds
- Personal and political in the archives of Andrew Petter
- Walking tour
- Glossary
Patrol Reporting Records
Function
Administration
PIB
No
RRSDA Number
2009-006
Department
Campus Safety and Security Services
Description, purpose and use of records
Records used to report or log daily security patrols of the University as evidence that proper procedure was followed and in support of incident investigations. Items of interest (e.g., notices, special requests from the Campus community, operational irregularities, incidents, etc.) are also noted for communication to subsequent patrol shifts for informational purposes, follow-up, etc.
Records include patrol notebooks, shift reports, and security notices. This retention schedule also covers electronic entries of the daily security patrols, recorded as chronological dispatch entries in an incident reporting and investigation management database. Entries are assigned unique dispatch numbers generated by the database, and include shift start and end times, locations, movements, and activities.
Irregular occurrences encountered while on patrol may be escalated to an incident investigation in the incident reporting and investigation management database. In these cases, all relevant dispatch entries are physically attached to the incident report or linked by a common reference number (see RRSDA 2009-001, Incident Reporting Records).
The electronic dispatch entries of the daily security patrol in the incident reporting and investigation management database are searchable by name and personal identifiers. Therefore, the dispatch entries constitute a Personal Information Bank (PIB). See PIB description.
Retention periods
| Records | Active | Semi-Active | Total retention | Final disposition |
|---|---|---|---|---|
| Patrol Notebooks and Database Entries of Daily Security Patrols | CY + 1 year | 5 years | CY + 6 years | Destruction |
| Shift Reports and Security Notices | CY + 1 year | Nil | CY + 1 year | Destruction |
Active = Active Retention Period, Keep in Office; Semi-Active = Semi-Active Retention period, transfer to University Records Centre; CY = Current calendar year; CFY = Current fiscal year; CS = Current semester; S/O = Superseded or obsolete; OPR = Office of Primary Responsibility; Non-OPR = All other departments
Authorities
These records are created, used, retained and managed in accordance with the following authorities:
- University Act (RSBC 1996, c. 468)
- Limitation Act (RSBC 1996, c. 266)
- Freedom of Information and Protection of Privacy Act (RSBC 1996, c. 165)
- Reporting Procedures: Security Notebooks (SFU Campus Security S.O.P. No. 13.05; 22 Nov. 2004)
- Reporting Procedures: Campus Security Notices (SFU Campus Security S.O.P. No. 13.06; 22 Nov. 2004)
- Security Patrols: Patrol Procedure (SFU Campus Security S.O.P. No. 15.01; revised 22 Nov. 2004)
- Recruit Training Manual (SFU Campus Security S.O.P. Appendix H, s. 6, "Security Notices")
Retention rationale
The total retention period ("CY patrol activity documented + 6 years") recommended for Patrol Notebooks and Electronic Database Entries of Daily Security Patrols ensures the University maintains evidence that proper procedure was followed and in support of incident investigations. It also meets the University's responsibilities under section 3(5) of the Limitation Act (RSBC 1996, c. 266). The total retention period ("CY report or notice issued + 1 year") recommended for Shift Reports and Security Notices is a sufficient timeframe to meet the administrative needs of the Department, including using the records as a ready reference to highlights of the daily patrol for follow-up, as back-up documentation in the event of clerical error when entering the information in the database, or if a related investigation results. For those security notices that include personal information, this retention period also meets the University's responsibilities under the FOI / POP Act (RSBC 1996, c. 165, s. 31), which requires that personal information used to make a decision that directly affects an individual must be retained for at least one year.
Retention and filing guidelines
FILING GUIDELINES
Closed or filled patrol notebooks should be maintained together by calendar year in which the last entry was made. This will facilitate the application of retention periods. Within these calendar year groupings, notebooks can also be arranged alphabetically by patrol officer name. This will allow for the ready location of notebooks of specific patrol officers.
Shift reports and security notices are retained by calendar year with reports arranged chronologically in file volumes and notices arranged chronologically by month.
RECORDS DISPOSITION
Patrol notebooks complement, rather than mirror, the electronic database entries. For instance, in addition to individual patrol notebook entries, an overall picture or objective perspective from multiple patrol officers is often recorded in the database. And, when a patrol officer is attending a scene and is unable to write in their patrol notebook, they must radio their actions to the dispatcher who records it in the database in real time. Therefore, the patrol notebooks and electronic database entries together make up the complete record. As a result, the same retention period and final disposition should be applied to both record types to ensure this schedule is applied consistently.
Shift reports are born-digital. Once printed to paper, electronic versions of these reports become transitory and can be deleted immediately. Alternatively, the electronic records can be maintained for ease of future reference, but should be deleted upon the expiration of the total retention period recommended in this schedule.
Organizer scheduling software and email correspondence are used to communicate items of interest and highlights to the next patrol supervisor on shift. Since the information communicated is reflective of the shift report and security notices, this electronic data is redundant and should be deleted immediately.
At the end of the active retention period ("CY patrol activity documented + 2 years") for patrol notebooks and database entries, box and transfer the notebooks to the University Records Centre (URC). For each box prepare a box contents listing, itemizing all notebooks contained in the box. Always include ONE copy of the file list inside the box sent to the URC taped to the underside of the lid; keep ONE copy for your own records; and send ONE copy (paper or electronic) to the Archives (see Procedures for Transferring Records to the University Records Centre).
Electronic database entries of daily security patrols (or dispatch entries) cannot be transferred to the URC at the end of the active retention period. Therefore, it is the Department's responsibility to maintain these records for the ensuing semi-active period and to delete them at the end of the total retention period. If the data has value for the generation of longitudinal statistics, and it is to be retained longer than the retention periods outlined in this schedule, the data should be anonymized. Maintaining personal information after the recommended retention period places an undue burden on the University to continue to guard against the unauthorized use or disclosure of that personal information in accordance with the FOI / POP Act and this records series' status as a PIB.
Status
RRSDA is in force
Approval Date
8 Dec 2009
Last Revised Date
8 Dec 2009