My WebLink
|
Help
|
About
|
Sign Out
09
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2012
>
040312
>
09
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/28/2012 4:50:26 PM
Creation date
3/28/2012 4:50:23 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
4/3/2012
DESTRUCT DATE
15Y
DOCUMENT NO
09
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
16
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
actually significantly crippled the Police Department's ability to respond to other calls for <br /> service." He also restated that the City relied on mutual aid protocols to not only <br /> manage Pleasanton's calls for service, but to get appropriate resources to this <br /> establishment. Chief Spiller believes, based on his experience, and in having worked <br /> very closely with the management staff that has been responsible for this project, that <br /> 300 or less patrons is the appropriate number in terms of the City's ability to manage <br /> providing standard public safety services to the community and supporting this <br /> operation at the same time. <br /> After lengthy discussion regarding the appropriate occupancy to allow, the Planning <br /> Commission voted 5 to 0 to limit the occupancy of the business to 300 patrons (not <br /> including nightclub staff), but with the possibility of returning to the Commission to <br /> increase the maximum number if: 1) there were no incidents requiring police <br /> involvement over the next 30 days; 2) the Club complies with all Conditions of Approval; <br /> and 3) a positive recommendation is provided by the Chief of Police and the Director of <br /> Community Development prior to scheduling a hearing before the Planning <br /> Commission. <br /> The Planning Commission also modified the existing Conditions of Approval to <br /> strengthen the security aspects of the business. Such conditions include utilization of <br /> an ID scanner at the entry, restrictions and protocols for closing the establishment in a <br /> manner that transitions the patrons out of the establishment starting at 1:00a.m. with a <br /> cleared parking lot by 2:00 a.m., the use of an approved Security Force Plan, and a <br /> posting of the club's dress code so patrons could see the dress code prior to waiting in <br /> line. The Conditions of Approval also addressed what needed to be included in the <br /> club's Security Force Plan, such as the number of security personnel on-site, job <br /> assignments, uniform specifications, training/registration/certification requirements, <br /> patron screening and entry protocols (e.g. pat-downs, queue staging, and capacity <br /> management), specifications for handling patron-removal, requirements for a video <br /> surveillance system and communication devices, and expectations for communication <br /> of security-related issues between the Pleasanton Police Department and the <br /> establishment. <br /> The Planning Commission's meeting minutes can be found in Attachment 3 and the <br /> approved Resolution and modified conditions of approval can be found in Attachment 6. <br /> In response to the Planning Commission's action, Mr. Mull, the attorney for the <br /> nightclub, filed an appeal of the modified Conditions of Approval. In his appeal, Mull <br /> objects to a condition that would limit the patrons to 300 and argues that "there is not a <br /> connection between the number of patrons and any problems that occurred with the <br /> patrons at closing time." He further argues that the occupancy reduction to 300 patrons <br /> "imposes a severe hardship on the operator and causes it to be impractical to continue <br /> operating at the location." <br /> Page 4 of 7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.