Atlanta Government Contracts and Procurement Procedures

Atlanta's municipal procurement system governs how the City of Atlanta acquires goods, services, and construction through a structured competitive bidding framework established under the Atlanta City Code and overseen by the Department of Procurement. This page covers the definition, structure, legal drivers, contract classifications, tradeoffs, and common misconceptions surrounding Atlanta government contracting. Understanding these procedures is relevant to vendors, subcontractors, oversight bodies, and residents tracking public expenditure through the Atlanta Government Audits and Oversight framework.

• Definition and scope
• Core mechanics or structure
• Causal relationships or drivers
• Classification boundaries
• Tradeoffs and tensions
• Common misconceptions
• Checklist or steps (non-advisory)
• Reference table or matrix

Definition and scope

Atlanta government procurement is the formal process by which City of Atlanta agencies solicit, evaluate, award, and administer contracts for goods, services, professional services, and public works. The legal authority for this process is grounded in the Atlanta City Code, Title 2, Chapter 2, Article X (Purchasing), and is administered primarily by the City's Department of Procurement, a cabinet-level department reporting to the Mayor's Office.

The scope of municipal procurement covers all expenditures made with City general fund dollars, enterprise fund dollars (such as those from Atlanta's water and aviation systems), and federal pass-through grants. Contracts below a formal solicitation threshold — set by City ordinance — may be processed through simplified purchasing procedures, while contracts above that threshold require formal competitive processes including Invitations to Bid (ITB), Requests for Proposals (RFP), or Requests for Qualifications (RFQ).

Geographic and jurisdictional scope: This page addresses procurement conducted by City of Atlanta departments and authorities operating under the Atlanta City Charter. It does not cover Fulton County procurement, DeKalb County purchasing, Metropolitan Atlanta Rapid Transit Authority (MARTA) contracting, the Georgia World Congress Center Authority, or state-level contracts administered by the Georgia Department of Administrative Services. Vendors seeking county-level guidance should consult the Atlanta–Fulton County Government Relationship page. Federal prime contracts let through agencies such as the U.S. Army Corps of Engineers are also outside scope.

Core mechanics or structure

The Department of Procurement manages a centralized vendor registry through the City's online procurement portal, which vendors must complete before responding to any solicitation. Registration requires a completed Vendor/Contractor Registration Form, a valid business license, and documentation of any applicable certifications (e.g., Disadvantaged Business Enterprise, or DBE, certification).

Solicitation types are matched to contract complexity:

• Invitation to Bid (ITB): Used when specifications are fully defined and award goes to the lowest responsive, responsible bidder. Most construction and commodity contracts use this method.
• Request for Proposals (RFP): Used when scope is less defined or when qualitative factors (methodology, experience, staffing) are relevant alongside price. Award is based on a weighted scoring matrix.
• Request for Qualifications (RFQ): Used primarily for professional services (engineering, architecture, legal) under Georgia's Brooks Act analog, O.C.G.A. § 36-91-20, which prohibits price competition at the qualification stage for design professionals on public projects.
• Emergency procurement: Authorized under specific conditions (disaster, health emergency, critical system failure) and requires written justification and post-award council notification.

After award, contracts are executed through the City's contract management system. The Atlanta City Council must approve contracts above the Mayor's delegated authority threshold, which is established by ordinance. Council approval connects procurement to the broader Atlanta City Budget Process, since unbudgeted contract awards require a budget amendment.

Causal relationships or drivers

Three structural forces shape how Atlanta procurement operates in practice.

1. Federal funding compliance. Atlanta receives federal grants from agencies including the U.S. Department of Transportation, HUD, and EPA. When federal dollars fund a contract, the procurement must comply with 2 C.F.R. Part 200 (Uniform Guidance), which imposes competitive requirements, cost reasonableness standards, and documentation mandates that are stricter than baseline City Code requirements. This creates a two-track compliance environment for departments managing both local and federal funds.

2. Equity mandates. Atlanta's Office of Contract Compliance administers the City's Equal Business Opportunity (EBO) program, which establishes participation goals for Minority Business Enterprises (MBEs) and Women Business Enterprises (WBEs) on City contracts. These goals are derived from disparity studies conducted periodically to satisfy the constitutional standards set in City of Richmond v. J.A. Croson Co., 488 U.S. 469 (1989). Prime contractors on qualifying contracts must document good-faith efforts to meet subcontracting participation goals or face bid rejection.

3. Charter and code reforms. Following a federal bribery investigation that resulted in guilty pleas by City employees and contractors between 2013 and 2019, Atlanta enacted procurement reform measures including enhanced conflict-of-interest disclosure requirements and stricter ethics training mandates. These reforms are administered in coordination with the Atlanta Board of Ethics and reflect the audit function described on the Atlanta Government Audits and Oversight page.

Classification boundaries

Atlanta contracts fall into distinct legal categories that determine which rules apply:

Public works contracts (construction, reconstruction, repair of public infrastructure) are governed by O.C.G.A. § 36-91-1 et seq. (Georgia Local Government Public Works Construction Law), which mandates performance and payment bonds on contracts exceeding $100,000 (O.C.G.A. § 36-91-70) and sets bid security requirements.

Professional services contracts are governed separately under the qualifications-based selection model and are exempt from the lowest-bid rule.

Goods and supplies contracts follow commodity purchasing rules with an emphasis on competitive sealed bids.

Information technology contracts may use alternative procurement methods including cooperative purchasing agreements (piggybacking on state or other government contracts) when permitted by City Code and when the original solicitation was conducted competitively.

Sole-source contracts are the narrowest classification — permitted only when one vendor is demonstrably the only source capable of meeting the requirement, and requiring written justification approved by the Chief Procurement Officer.

Tradeoffs and tensions

Transparency vs. speed. Full competitive procurement protects public funds but introduces lead times of 60 to 120 days or more from solicitation to award. Emergency and sole-source exemptions reduce that timeline but carry elevated audit risk and public scrutiny. The Atlanta City Council oversight role creates an additional review layer that can extend award timelines.

Equity goals vs. price efficiency. MBE/WBE subcontracting goals increase competition from a broader supplier base over time but may add cost in the short term if certified firms carry capacity constraints or higher unit pricing. Courts have required cities to demonstrate ongoing statistical justification for race-conscious programs, creating periodic legal exposure.

Centralization vs. departmental flexibility. Centralized procurement through the Department of Procurement creates uniform standards but can reduce departments' ability to respond quickly to specialized operational needs. Departments such as the Atlanta Department of Watershed Management and the Department of Aviation operate enterprise funds with some procurement autonomy, creating coordination complexity.

Local preference vs. federal compliance. Atlanta's City Code historically included local vendor preference provisions, but these cannot be applied to federally funded contracts where 2 C.F.R. Part 200 prohibits geographic preferences that restrict competition.

Common misconceptions

Misconception: The lowest bid always wins.
Correction: For ITBs, the award goes to the lowest responsive, responsible bidder. "Responsive" means the bid conforms to all solicitation requirements; "responsible" means the bidder has the capacity, financial stability, and integrity to perform. A bid can be rejected even if it is the lowest price if the bidder fails the responsibility evaluation.

Misconception: Registered vendors automatically receive solicitation notices.
Correction: Vendor registration creates eligibility, not automatic notification. Vendors must actively monitor the City's procurement portal or subscribe to commodity-specific notifications to learn of active solicitations.

Misconception: Subcontractors are not subject to City requirements.
Correction: Subcontractors on contracts subject to the EBO program must be certified through the Office of Contract Compliance. Additionally, on federally funded contracts, flow-down requirements under 2 C.F.R. Part 200 apply to subcontractors.

Misconception: A contract award is final once announced.
Correction: Unsuccessful bidders have a formal protest right under City procurement rules. Protests must be filed within a specified window after award announcement, and the Chief Procurement Officer or a designated hearing officer adjudicates the protest before the contract becomes final.

Misconception: The Atlanta procurement system operates independently of state law.
Correction: Georgia state statutes — including O.C.G.A. § 36-80-27 (local government purchasing authority) and O.C.G.A. § 36-91-1 et seq. — set a floor of requirements that Atlanta's City Code must meet or exceed. State law governs bond requirements, bid thresholds, and design professional selection regardless of local preferences.

Checklist or steps (non-advisory)

The following sequence describes the standard steps in Atlanta's formal competitive procurement process for a City department initiating a contract:

1. Need identification — Department documents the requirement, estimated cost, and funding source (general fund, grant, enterprise fund).
2. Budget verification — Finance confirms appropriation availability in the relevant fiscal year budget.
3. Procurement method selection — Department of Procurement determines whether the requirement calls for ITB, RFP, RFQ, or an approved alternative method.
4. Scope/specification development — Department drafts technical specifications or scope of work; Procurement reviews for competitive neutrality.
5. EBO goal-setting — Office of Contract Compliance establishes MBE/WBE subcontracting participation goals, if applicable.
6. Solicitation publication — Procurement posts to the City's electronic procurement portal; minimum advertised period is defined by ordinance (typically 14 to 21 calendar days for standard ITBs).
7. Pre-bid/pre-proposal conference — Optional or mandatory depending on contract complexity; questions and answers are published as addenda to all registered plan holders.
8. Bid/proposal receipt and opening — Public bid openings apply to ITBs; RFP proposals are opened confidentially until evaluation is complete.
9. Evaluation — ITBs are ranked by price after responsiveness check; RFPs are scored by an evaluation committee using the published scoring matrix.
10. Responsibility determination — Chief Procurement Officer or designee reviews bidder/offeror qualifications.
11. Award recommendation — Department and Procurement prepare award recommendation for Mayor's approval or Council approval, depending on contract value.
12. Protest period — Award is announced; protest window opens.
13. Contract execution — After protest period closes or protest is resolved, contract is executed and entered into the City's contract management system.
14. Performance monitoring — Department administers contract; invoice review, deliverable acceptance, and EBO compliance monitoring occur throughout the contract term.

Reference table or matrix

The Atlanta City Charter and Code of Ordinances is the primary local law instrument establishing these procurement categories, while state statutes set mandatory floors that local ordinances cannot waive.

For a broader orientation to how Atlanta's government structure interconnects — including how the Department of Procurement relates to the Mayor's cabinet and the Council's budget authority — the site home provides navigational context across all civic topic areas.

References

• City of Atlanta Department of Procurement
• Atlanta City Code, Title 2, Chapter 2, Article X (Purchasing)
• O.C.G.A. § 36-91-1 et seq. — Georgia Local Government Public Works Construction Law
• 2 C.F.R. Part 200 — Uniform Administrative Requirements (Uniform Guidance)
• City of Richmond v. J.A. Croson Co., 488 U.S. 469 (1989)
• Georgia Department of Administrative Services — State Purchasing Division
• Atlanta Board of Ethics
• U.S. Office of Management and Budget — 2 C.F.R. Part 200 Overview