Documents › 01018578514a1fb249c46cfd27014ded9828f8be:11-123
339 - 11.29.23 Transcript_POST Advisory Committee Meeting.pdf
About this document
- Layer
- packet: an item in a POST meeting packet
- Type as titled
- transcript (kind from title)
- File
- 01018578514a1fb249c46cfd27014ded9828f8be application/pdf
- Cases
- none: board business or reference material
Page 46 · file page 56
larger image
Text: digital text layer
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
POST Advisory Committee, November 29, 2023
KATHRYN S. SWANK, CSR, RPR (916) 390-7731
46
MR. GROTTKAU: So it could be. So if there's a
Public Records Act request for, for instance, your
agency, the Richmond Police Department, that says "We
would like to know everybody that attended the training
and who didn't," that's public information.
So we would redact certain information from
profiles, for instance, but we would be required to
report that. And if you have mitigating factors that
list the reason for mitigation, that would be something
that may have to be released.
MEMBER THERRIAULT: Okay.
EXECUTIVE DIRECTOR ALVAREZ: So the intent of this,
however, is agency specific. So it would be -- in this
scenario, it would just be "Richmond Police Department,"
and you couldn't drill down and see which individuals
have completed and not completed.
But as Jim pointed out, we do get regular Public
Records Act requests saying "Which officers did not
complete" --
MEMBER THERRIAULT: Sure. And I agree that
transparency is important. But I agree with everyone
else that there's -- without that, by putting in
historical -- by putting something ongoing, you know,
people are doing PRAs, quite frankly, for news articles.
That's what they will probably be doing them for, at
56
Keys: ← → or j k turn pages; / finds.