My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Business Retention and Development Committee Agenda and Packet 2015 01 05
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
BUSINESS RETENTION & DEV COMMITTEE
>
2006-2019 Business Retention and Development Committee Agendas and Packets
>
2015 Business Retention and Development Committee Agendas and Packets
>
Business Retention and Development Committee Agenda and Packet 2015 01 05
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/10/2021 2:09:37 PM
Creation date
1/7/2015 9:40:28 AM
Metadata
Fields
Template:
City Council Records
Doc Type
Boards Commissions Committees Records
Supplemental fields
Test
BRADPKT 2015 01 05
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
26
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).
Show annotations
View images
View plain text
Business Retention & Development Committee <br />Meeting Minutes <br />November 3, 2014 <br />Page 3 of 4 <br />Builders are always provided with a list of items that must be completed when an inspection <br />fails. Building safety is always consistent with code. <br />Discussion began about the complexity of getting to a CO. Some feel the process is too <br />complex, whereas others feel it isn't complex, but final issues come as a surprise when the <br />project is wrapping up. <br />Economic Development will work with Planning and Building Safety to develop a document <br />that outlines all the required items the City needs to issue a CO. Clarity up front when a permit <br />is issued may help later in the process. Each City's requirements are somewhat different and a <br />document outlining Louisville's requirements may be helpful. <br />Discussion began about not issuing Temporary Certificates of Occupancy. Some were <br />surprised we don't issue TCO. Not everything comes together when we want it to. As long as <br />we are protecting public safety, we should issue. We don't want a reputation of inflexibility. <br />We want to serve residents and public interests. Russ explained that it is a matter of <br />semantics. Alfalfa's was technically issued a "TCO" but the building department issued a CO <br />with conditions, not a TCO. We won't compromise on building /public safety. <br />Chairperson Dalton asked if we are allowing people to occupy buildings, conditioned upon <br />receiving assurance that non -life safety items will be completed, what is the problem? Lipton <br />is concerned that an inflexible reputation will result. <br />Chair Dalton asked for public comments. Rick Brew stated the subdivision controls many of <br />the aspects to achieving completion. Building permits and CO's are withheld until public <br />improvements are completed. Residential new construction is different than <br />commercial /industrial permits. <br />Russ stated TCO aren't ideal for the banks. The CO is an important document to transition <br />into permanent financing or allowing a sale. <br />Menaker stated he was aware of instances where CO has been held. Valid reasons to <br />withhold a CO, however; anecdotally, we don't have a reputation of being easy to work with. <br />Perhaps BRaD should visit with those who just built and bring comments back. Planning and <br />Economic Development are preparing a questionnaire of development and building permit <br />process. <br />City Manager Fleming stated there is a different person to go to instead of directly to the <br />Building Department when expectations aren't being met. Economic Development can be the <br />advocate for the project. Planning can't pick and choose who to give incentives to. DeJong <br />has been performing an advocacy role for the developer /contractor /tenant. Communicating <br />DeJong's services to projects should be more pronounced. <br />4 <br />
The URL can be used to link to this page
Your browser does not support the video tag.