My WebLink
|
Help
|
About
|
Sign Out
06
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2010
>
111610
>
06
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/10/2010 2:49:07 PM
Creation date
11/10/2010 2:49:03 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
11/16/2010
DESTRUCT DATE
15Y
DOCUMENT NO
06
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
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
STANDARD CONDITIONS OF APPROVAL <br /> Community Development Department <br /> 74. The project applicant or developer shall pay any and all fees to which the property may <br /> be subject prior to issuance of permits. The type and amount of the fees shall be those <br /> in effect at the time the permit is issued. <br /> 75. The project applicant or developer shall submit a refundable cash bond for hazard and <br /> erosion control. The amount of this bond will be determined by the Director of <br /> Community Development. The cash bond will be retained by the City until all the <br /> permanent landscaping is installed for the development, including individual lots, unless <br /> otherwise approved by the department. <br /> 76. The permit plan check package will be accepted for submittal only after the ordinance <br /> approving the PUD development plan becomes effective, unless the project applicant/ <br /> developer submits a signed statement acknowledging that the plan check fees may be <br /> forfeited in the event that the ordinance is overturned or that the design is significantly <br /> changed. In no case will a permit be issued prior to the effective date of the ordinance. <br /> STANDARD CONDITIONS OF APPROVAL <br /> Planning <br /> 77. The proposed development shall be in substantial conformance to Exhibit D, dated <br /> "Received, June 29, 2010," on file with the Planning Division, except as modified by the <br /> following conditions. Minor changes to the plans may be allowed subject to the approval <br /> of the Director of Community Development. <br /> 78. To the extent permitted by law, the project applicant or developer shall defend (with <br /> counsel reasonably acceptable to the City), indemnify and hold harmless the City, its <br /> City Council, its officers, boards, commissions, employees and agents from and against <br /> any claim (including claims for attorney's fees), action, or proceeding brought by a third <br /> party against the indemnified parties and the project applicant or developer to attack, set <br /> aside, or void the approval of the project or any permit authorized hereby for the project, <br /> including (without limitation) reimbursing the City its attorneys fees and costs incurred in <br /> defense of the litigation. The City may, in its sole discretion, elect to defend any such <br /> action with attorneys of its choice. <br /> 79. All conditions of approval for this development plan shall be reprinted and included as a <br /> plan sheet(s) with the improvement plan check sets including grading, improvement/ <br /> construction, and landscaping plans, which shall be kept on the project site at all times. <br /> The applicant may request these conditions of approval be attached to the plan set as a <br /> separate document which he /she is responsible for obtaining and ensuring the <br /> conditions are securely attached. It is the responsibility of the applicant to ensure that <br /> the project contractors are aware of, and abide by, the approved plans and all conditions <br /> of approval. <br /> 80. Planning Division approval is required before any changes are implemented in site <br /> design, grading, building materials and colors, green building measures, and landscape <br /> material. <br /> 22 <br />
The URL can be used to link to this page
Your browser does not support the video tag.