City of Hartford v. Freedom of Info. Comm., No. Cv93-533024 (Sep. 16, 1994)

1994 Conn. Super. Ct. 9295
CourtConnecticut Superior Court
DecidedSeptember 16, 1994
DocketNo. CV93-533024
StatusUnpublished

This text of 1994 Conn. Super. Ct. 9295 (City of Hartford v. Freedom of Info. Comm., No. Cv93-533024 (Sep. 16, 1994)) is published on Counsel Stack Legal Research, covering Connecticut Superior Court primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
City of Hartford v. Freedom of Info. Comm., No. Cv93-533024 (Sep. 16, 1994), 1994 Conn. Super. Ct. 9295 (Colo. Ct. App. 1994).

Opinion

[EDITOR'S NOTE: This case is unpublished as indicated by the issuing court.]MEMORANDUM OF DECISION CT Page 9296 I. INTRODUCTION

The plaintiffs in this appeal, the City of Hartford and the City of Hartford Purchasing Department, (hereinafter referred to as "the City"), challenge the decision of the Freedom of Information Commission ("FOIC") in favor of the defendants, Eric Lipton, Anita Seline and The Hartford Courant. In its decision the FOIC found that the City failed to provide the defendants with prompt access to the files they requested. The files in question contained the responses of ten construction management companies to the City's request for proposals1 to perform construction management services on what is referred to as the Moylan Elementary School project ("Moylan project") and certain evaluations of these responses.2 For the reasons set forth below, I affirm the FOIC's decision in part and reverse it in part.

II. STATEMENT OF FACTS

In November 1990, the voters of the City of Hartford approved a $21 million bond ordinance to finance the Moylan project. At a later referendum, a $200 million, five to ten year school construction program was approved. An April 21, 1993 letter of the City Manager to the Mayor and Common Council, contained in the record, states that:

The City is about to embark on a $200M, five to ten year school construction program. It is clear that this amount of construction work can not be fully managed in house due to constraints on staff size. For this purpose, the City solicited proposals to hire a Construction Manager to act as the City's eyes and ears and to protect the City's interest by ensuring that all City requirements are met.

The Moylan Elementary School Project affords the City an unique opportunity to put the CM strategy into place to become familiar and comfortable with the process and to work out any difficulties prior to the new school construction program going into full swing. In addition, the CM strategy will help the City accomplish minority and female contracting goals, including CT Page 9297 affirmative action goals. Finally, the City needs to "stimulate" the local CM market for public facilities construction.

On October 28, 1992, the City issued a Request For Proposals (RFP) that, in its words, solicited "proposals from qualified construction management firms to provide bidding and construction phase management services for the Moylan Elementary School." The services, at a general level, include "review of construction documents, preparation of sub-contractor bid packages, bidding, construction administration, and construction management services during the construction phase." A rather lengthy statement of "Scope of Services" includes, among other things, "Make recommendations concerning construction feasibility, availability of labor and materials, and the time required for installation and construction of the project;" "Prepare and coordinate a detailed plan for the total development of the project, including a computerized CPM schedule;" and "Provide necessary field supervision and inspections to assure that all work is in conformance to the contract documents."

The nature of an RFP is best explained as follows:

Implicit in the definition of an RFP is the underlying rationale that, in some types of competitive procurement, the agency may desire an ultimate goal but cannot specifically tell the offerors how to perform toward achieving that goal; thus, a ready distinction arises between an RFP and an IFB [Invitation for Bids]. Typically, an IFB is rigid and identifies the solution to the problem. By definition, the invitation specifically defines the scope of the work required by soliciting bids responsive to the detailed plans and specifications set forth. . . . On the contrary, an RFP is flexible, identifies the problem, and requests a solution. Consideration of a response to an IFB is controlled by cost, that is, the lowest and best bid, whereas consideration of an offer to an RFP is controlled by technical excellence as well as cost.

System Development Corp. v. Department of Health RehabilitativeServices, 423 So.2d 433, 434 (Fla.Dist.Ct.App. 1982). Consistent with this concept, the City's RFP required detailed proposals including, among other things, "a written discussion in sufficient detail to demonstrate an understanding of the CT Page 9298 project's scope and the services required," "a detailed written summary of the firm's history and experience and capability in providing Construction Manager services," a "project management system," and "a detailed, itemized plan of proposed services."

The record contains the proposal of the ultimately successful applicant. This is an extremely detailed and technical work setting forth hundreds of proposed tasks from the initial site preparation and excavation to the installation of hardware. Items such as the precast concrete, unit masonry, and structural metals to be used are described in meticulous detail and technical language.

An advisory panel3 assisting the City Manager in the selection of a construction manager completed Proposal Evaluation Sheets on each proposal. The Proposal Evaluation Sheets are not technical in nature. Each evaluator is asked to indicate by writing Yes or No whether the proposal is or is not responsive in twelve specific areas. These areas include understanding of the project, experience, staff plan, and service delivery plan. Each evaluator is then asked to rate the respondent's overall proposal against the criteria for selection contained in the RFP on a rating scale of 1 to 15 points. Finally each evaluator is asked to provide specific comments on the strengths and weaknesses of the proposal. Some Proposal Evaluation Sheets in the record contain no comments, and some comments are illegible, but it is fair to categorize most comments as summary rather than technical —e.g. "extensive experience" or "no experience in school construction."

After reviewing the merits of each applicant and interviewing five of the ten contenders, the advisory panel submitted the names of three contractors to the City Manager on January 8, 1993. See Hartford, Conn., Munic. Code § 2-604(3) (1977). From this short list, one contractor was chosen by the City Manager and submitted to the Hartford City Council for approval.Id. Although the first recommendation, made by letter dated February 17, 1993, was rejected by the City Council, the City Manager's second recommendation, made by letter dated April 21, 1993, was received favorably. As such, on May 19, 1993, the Hartford City Council designated the second contractor as the construction manager for the Moylan project in accordance with § 2-604 of the Hartford Municipal Code. The acting purchasing agent for the City then contracted with the prevailing company. Ultimately, a letter of intent was signed on June 26, 1993. CT Page 9299

The defendants began the process leading to this case following the City Manager's first recommendation. On March 4, 1993, they requested "access to files on the 10 companies that responded to a request for proposal for the construction manager of the Moylan Elementary school [sic] project" pursuant to the Freedom of Information Act. Conn. Gen. Stats. §§ 1-7 through1-21k.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Baker v. Carr
369 U.S. 186 (Supreme Court, 1962)
Shaw v. Delta Air Lines, Inc.
463 U.S. 85 (Supreme Court, 1983)
System Development Corp. v. DEPT. OF HEALTH & REHAB.
423 So. 2d 433 (District Court of Appeal of Florida, 1982)
Stern v. Stern
332 A.2d 78 (Supreme Court of Connecticut, 1973)
Connecticut Foundry Co. v. International Ladies Garment Workers Union
411 A.2d 1 (Supreme Court of Connecticut, 1979)
Howarth Et Ux. v. Gilman
73 A.2d 655 (Supreme Court of Pennsylvania, 1949)
Zoning Board of Appeals v. Freedom of Information Commission
503 A.2d 1161 (Supreme Court of Connecticut, 1986)
Board of Education v. Connecticut Board of Labor Relations
530 A.2d 588 (Supreme Court of Connecticut, 1987)
Board of Pardons v. Freedom of Information Commission
556 A.2d 1020 (Supreme Court of Connecticut, 1989)
Sobocinski v. Freedom of Information Commission
566 A.2d 703 (Supreme Court of Connecticut, 1989)
Board of Education v. Freedom of Information Commission
585 A.2d 82 (Supreme Court of Connecticut, 1991)
University of Connecticut v. Freedom of Information Commission
585 A.2d 690 (Supreme Court of Connecticut, 1991)
Rose v. Freedom of Information Commission
602 A.2d 1019 (Supreme Court of Connecticut, 1992)
Superintendent of Police v. Freedom of Information Commission
609 A.2d 998 (Supreme Court of Connecticut, 1992)
Housing Authority v. Lamothe
627 A.2d 367 (Supreme Court of Connecticut, 1993)

Cite This Page — Counsel Stack

Bluebook (online)
1994 Conn. Super. Ct. 9295, Counsel Stack Legal Research, https://law.counselstack.com/opinion/city-of-hartford-v-freedom-of-info-comm-no-cv93-533024-sep-16-1994-connsuperct-1994.