300.06 field services activities report (officer's written log)

1. Number: 300.06
SUBJECT: FIELD SERVICES ACTIVITIES REPORT (OFFICER’S WRITTEN
LOG)
Page: 1
Date: 9/3/02
Approved: Ryan Drabek, Director Revised: 6/27/13
I. PURPOSE
To establish a uniform procedure for the completion of the Field Services Activities
Report.
II. POLICY
The Field Services Activities Report or Officer’s Written Log shall be completed by each
Animal Control Officer (ACO) assigned to work the field when the Chameleon database
is down or out of service. The log should be updated after each call to ensure the correct
times and actions are documented correctly.
III. SCOPE
Applicable to all Field Operations personnel.
IV. FORMS
Field Services Activities Report (Officer’s Written Log)
City Codes To Be Used On Field Activities Report (Logs)
Electronic Log Activity Result Codes and Required Information
V. REFFERRENCES
Not applicable.
VI. DEFINITIONS
Not applicable.
VII. PROCEDURE
A. Officer’s Written Log.
The Officer’s Written Log is a form that is used to accurately describe all
activities taken by ACOs, Senior ACOs and Lieutenants assigned to field duties.
Special attention is to be given to accurately and concisely describe what actions
are taken during the handling of requests for service. Abbreviations may be used

2. Number: 300.06
SUBJECT: FIELD SERVICES ACTIVITIES REPORT (OFFICER’S WRITTEN
LOG)
Page: 2
Date: 9/3/02
Approved: Ryan Drabek, Director Revised: 6/27/13
in the completion of the Officer’s Log, provided they conform with the list
included as attachments to this policy.
All entries will be block printed by using black ink. Felt tip pens are not to be
used. White correction fluid or correction tape is to be used to make corrections.
Officer’s Logs are to be completed as follows (refer to the numbered sections on
sample):
1. DAY/DATE: The abbreviated day of the week and the entire date
(numerical date accepted). For example, 1-10-03.
2. OFFICER: First initial, last name and badge number.
3. RIDE-ALONG: First initial, last name and badge number (if applicable)
of a trainee, trainer, explorer or other observer.
4. COURT DATE: Court appearance date as given in briefing.
5. CODE 7: Lunch/Dinner break starting time as assigned in briefing.
6. END MILES: Assigned vehicle odometer reading at end of shift.
7. START MILES: Assigned vehicle odometer reading at beginning of shift.
8. TOTAL MILES: Difference between start and end miles.
9. UNIT: Assigned County unit number.
10. PAC: Assigned PAC set number.
11. VEH DISCREP: If there are vehicle discrepancies, enter “YES”, if no
discrepancies enter “NO”. Discrepancies are to be noted in the remarks
section of the Officer’s Log during the allotted time for equipping a
vehicle for service. All discrepancies shall be brought to the attention of
the Watch Commander immediately.
12. PATROL AREA(S): AM or PM followed by a dash and the assigned
geographical area. If more than one area is assigned, each geographical
area is to be entered. If assigned as a cover unit, CW is to be entered.
13. # OF STARTING CALLS: Number of calls received at the start of the
shift.
14. # OF CALLS RECEIVED: Number of calls received from dispatch,
supervision, and calls received from other ACO’s.
15. FIELD INITIATED CALLS: Number of calls initiated in the field. These
calls are to be indicated by an asterisk in the body of the log text next to
the starting time of the call. Actions that qualify as field initiated are:
animal impounds during routine patrol time, citation issued, any calls
involving fees collected.
16. SUBTOTAL OF CALLS: Sum of lines 13, 14 and 15.

3. Number: 300.06
SUBJECT: FIELD SERVICES ACTIVITIES REPORT (OFFICER’S WRITTEN
LOG)
Page: 3
Date: 9/3/02
Approved: Ryan Drabek, Director Revised: 6/27/13
17. UTM’S: Total number of calls that were not handled during the shift.
18. TOTAL: Difference between lines 16 and 17.
19. START: Time (24 hour clock) that the service activity begins. The time
will include driving time from the previous call, when applicable.
20. CLEAR: Time (24 hour clock) the service activity ended.
21. CITY: the approved abbreviation (Attachment II) for the city or
unincorporated area of the County where the service was rendered.
22. ACTION: Approved action code (Attachment III) for the service activity.
23. ARRIVAL: Actual arrival time (24 hour clock) at the location of the
service activity, when applicable. In most cases this time will be different
than the start time of the call.
24. LOCATION: Physical location where the action pertaining to the call is
performed. For example, residence, back yard, front yard of, sidewalk in
front of, block number of, intersection of, etc.
25. ADDRESS: Numerical address, street name, or cross streets of the call.
26. ACTIVITY NUMBER: Activity numbers, including any sequence
numbers other than one (1). Write the last six digits of the activity number,
unless the first two digits do not correspond with the current year. In
which case, write the whole number. (e.g. In the year 2013, Activity A13-
022345 would be recorded as 022345 and Activity A12-056545 would be
recorded as A12- 056545).
27. On the line under the Activity number, enter the Animal ID for any
impounded animal(s)
28. REMARKS: All information that accurately details the actions taken
during the activity. Accepted abbreviations may be used. The following
are remarks which are required when specific action codes are used:
a. Animal Descriptions on any animal impounded. (Alive or dead,
including the animal’s species, sex, breed, color, age, and
license/microchip number info, I.D. tags worn, etc.)
b. Any serial numbered forms initiated (e.g. citation, receipt book,
notice to comply, or treatment record).
c. License number of any license sold.
d. Kennel identifying tag (Blue tag).
29. CAGE: Show applicable cage number in box or appropriate abbreviation
for other acceptable disposition.
30. TAG NUMBER: Assigned blue tag number.

4. Number: 300.06
SUBJECT: FIELD SERVICES ACTIVITIES REPORT (OFFICER’S WRITTEN
LOG)
Page: 4
Date: 9/3/02
Approved: Ryan Drabek, Director Revised: 6/27/13
31. I CERTIFY… Officer’s signature and badge number.
32. REVIEWED BY: Initial and badge number of reviewer.
33. APPROVED BY: Initials of approving Lieutenant.
34. DATE REVIEWED: Date Officer’s log was reviewed.
35. DATA INPUT: Initial of the data operator and the date the information
was stored in the computer.
B. Special Aspects:
1. Any time an officer is at OC Animal Care for reasons not relating to a
particular call such as a staff meeting for example, OCAC will be entered
as the city code. If the work being performed at OCAC is related to a
particular call, including all reports and paperwork, the corresponding city
code should be utilized.
2. At end of shift, inputting time is to be accounted for by listing the city
code where the actions occurred, “O” for action code and then enter
“computer work” or “inputting” in remarks section.
C. Form Distribution:
Officer’s Logs shall be completed at the end of the officer’s shift and forwarded
to supervision via the appropriate “pigeon hole” in the Squad Room. If the officer
is unable to complete the log at the end of their shift they are to contact the Watch
Commander for guidance.