What the city was allowed to spend in 2026, and out of which departments.
What this counts
City of Lakewood adopted appropriations for the calendar year — total expenditures, all funds.
Ordinance O-2025-32, as printed in the 2026 Adopted Budget book. APPROPRIATIONS, not spending. Excludes the Lakewood Reinvestment Authority, a separate legal entity the book states is not presented in it.
How this figure was reached
$313,382,438 — 2026 adopted appropriations, total expenditures, all funds. Reconciled two ways inside the book: the 14-department classification matrix sums to it exactly (and its four printed column totals do too), and the All Fund Types sources-and-uses summary states it again in its 2026 Budget column. APPROPRIATIONS, not spending; excludes the Lakewood Reinvestment Authority, a separate legal entity the book states is not presented in it. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
The revised 2025 appropriation the same ordinance adopts alongside the 2026 budget — total expenditures, all funds.
The Charter has Council adopt "the current year revised and following year" each fall: two one-year appropriations, never a two-year sum. This is the revised half.
How this figure was reached
$345,294,034 — the revised 2025 appropriation the SAME ordinance adopts beside the 2026 budget, from the All Fund Types summary's own "2025 Revised" column. The Charter has Council adopt "the current year revised and following year" each fall: two one-year appropriations whose paired-year naming reads as biennial and is not. REVISED is a different stage from adopted — 2025 was originally budgeted at a lower figure and revised upward in-year — and the two years are never summed. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “revised appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
The 2026 adopted appropriation divided by the newest Census resident estimate for the city.
Census Vintage 2025 place estimate (July 1, 2025) — the newest that exists; the 2026 calendar year begins six months after its reference date, and the page states both dates.
How this figure was reached
$313,382,438 (2026 adopted, all funds) / 156,927 residents (Census Vintage 2025 estimate for Lakewood city, Colorado, July 1, 2025 — the newest that exists; the budget year begins six months after it) = $1,997, rounded to the dollar.
Where it came from
U.S. Census Bureau, Population Estimates Program
City and town population totals, Vintage 2025 (sub-est2025.csv)
Open the source document ↗
Open flat file, no API key — api.census.gov answers HTTP 200 with an HTML "Invalid Key" page when the key is missing. FOUR OTHER STATES HAVE A LAKEWOOD (California, Ohio, Washington, New Jersey), so the row is selected on SUMLEV 162 + state FIPS 08 + place FIPS 43000 and the name and state are asserted on the row that comes back, never matched on name alone. One vintage for every year drawn (estimates are rebased between vintages), which is also why the rate series starts at 2020 — this vintage publishes no earlier year.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
Adopted appropriation to the Lakewood Police Department for the calendar year, all funds.
The city's own police department — the largest department line in the budget. NOT a corrections budget: Lakewood operates no jail; detention is the Jefferson County Sheriff's, in the county's budget, and that measure is refused on this locale.
How this figure was reached
Police: $73,052,892, 2026 adopted, ALL FUNDS — the largest department line in the city's budget. Its classification parts (personnel, services and supplies, capital) sum to this row total exactly. NOT a corrections budget: Lakewood operates no jail — detention is the Jefferson County Sheriff's, in the county's budget, and that measure is refused on this locale rather than borrowed from another government. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
2026 adopted appropriation to Public Works, all funds.
One of the seven largest department lines, named individually on the $100 receipt. Reconciled inside the 14-department matrix that sums to the citywide total exactly.
How this figure was reached
Public Works: $78,921,797, 2026 adopted, all funds — 25.18% of the $313,382,438 total. Row parsed from the 14-department classification matrix, whose rows sum to the citywide total exactly. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
2026 adopted appropriation to Sustainability and Community Development, all funds.
One of the seven largest department lines, named individually on the $100 receipt. Reconciled inside the 14-department matrix that sums to the citywide total exactly.
How this figure was reached
Sustainability and Community Development: $29,885,532, 2026 adopted, all funds — 9.54% of the $313,382,438 total. Row parsed from the 14-department classification matrix, whose rows sum to the citywide total exactly. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
2026 adopted appropriation to Non-Departmental, all funds.
One of the seven largest department lines, named individually on the $100 receipt. Reconciled inside the 14-department matrix that sums to the citywide total exactly.
How this figure was reached
Non-Departmental: $23,176,441, 2026 adopted, all funds — 7.40% of the $313,382,438 total. Row parsed from the 14-department classification matrix, whose rows sum to the citywide total exactly. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
2026 adopted appropriation to Facilities & Infrastructure Maintenance, all funds.
One of the seven largest department lines, named individually on the $100 receipt. Reconciled inside the 14-department matrix that sums to the citywide total exactly.
How this figure was reached
Facilities & Infrastructure Maintenance: $9,554,569, 2026 adopted, all funds — 3.05% of the $313,382,438 total. Row parsed from the 14-department classification matrix, whose rows sum to the citywide total exactly. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
Combined 2026 adopted appropriation to the 7 departments outside the 7 largest.
The receipt names the seven largest departments and groups the rest — the cut is by size, never by preference. The fine print names the largest department inside the group.
How this figure was reached
The 7 departments outside the 7 largest, combined: $30,875,822, 9.85% of the total. Largest inside the group: Finance, $8,590,311. All 14 department rows sum to the citywide total exactly.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
2026 adopted appropriation to Finance, all funds.
The largest department line inside the receipt's grouped remainder, named on the page with its exact figure so the size cut is checkable. Also inside the grouped total — the two are never summed together.
How this figure was reached
Finance: $8,590,311, 2026 adopted, all funds — the largest of the 7 departments the receipt groups as "all other departments". Emitted individually because the page prints its exact figure to make the receipt's size cut checkable; it also remains inside the grouped total, so the two are never summed together. 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
Money appropriated for 2026 across every fund of the city's five-year Capital Improvement and Preservation Plan.
A CALC. The plan prints a total for each of its ten funds and no total across them, so this figure is ours; the parse fails if the city ever starts printing it. CAPITAL ONLY, and never added to the citywide appropriation — the plan's four later years are the city's own forecasts and are not appropriations at all.
How this figure was reached
The 10 funds of the Capital Improvement and Preservation Plan, added: Capital Improvement Fund $24,003,304 + Conservation Trust Fund $2,145,000 + Open Space Fund $943,000 + Equipment Replacement Fund $5,350,000 + Golf Course Enterprise Fund $8,221,546 + Sewer Enterprise Fund $1,830,000 + Stormwater Enterprise $9,145,000 + Water Enterprise $0 + TABOR Fund $15,308,872 + GRANT Fund $9,155,434 = $76,102,156. Each fund total is the city's own printed figure, and every category under it reconciles to the subtotal the city printed, on all six columns; the chapter is read a second time against its own project detail sheets in both directions. THE BOOK PRINTS NO TOTAL ACROSS THE FUNDS — this sum appears nowhere in it, which is why the figure is labeled CALC wherever it is shown. ONLY THE 2026 COLUMN IS AN APPROPRIATION: the chapter's own preamble says the 2027-2030 figures "are forecasts and will not be appropriated until subsequent budgets", and the 2025 Revised column is a third quantity again (2024 carryforwards plus the 2025 original budget plus 2025 adjustments). 2026 Adopted Budget book, adopted by ordinance O-2025-32 (first reading October 6, 2025; finally passed October 20, 2025). THE STAGE IS READ OFF THE ORDINANCE, NOT THE TOTAL: the book states that no appropriation changed between the proposed and adopted budgets, so the two stages print identical figures and only the document's own cover and enactment record identify this as the adopted one.
Where it came from
City of Lakewood, Department of Finance
2026 Adopted Budget book (Adopted ANNUAL BUDGET FY 2026)
Open the source document ↗
A 30 MB PDF that parses cleanly, a PDF read as text. THE STAGE CANNOT BE IDENTIFIED BY ITS TOTAL: the book states "no changes in appropriations for all funds from the proposed budget to the adopted budget", so proposed and adopted print identical figures and only the cover and ordinance O-2025-32 (first reading Oct 6 2025, finally passed Oct 20 2025, mill levy 4.711) say which document this is — both are asserted every run. NOT BIENNIAL despite paired-year filenames: the Charter has Council adopt "the current year revised and following year" each fall — two one-year appropriations on a calendar-year basis. The publisher's own tables differ by single dollars between presentations of one figure (Personnel Services prints 141,272,319 in the classification matrix and 141,272,318 in the sources-and-uses summary); the classification matrix is the primary path and the second table must agree to within $2 per line. The Lakewood Reinvestment Authority is a separate legal entity NOT in this document, while the city checkbook INCLUDES it — the two perimeters are never reconciled against each other raw.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
Jefferson County's own adopted budget for 2026 — total expenditures, all funds.
The county's own budget document, read at the county's own printed total. This is Jefferson County's money and NOT the city's. Two separate governments; the same dollar never appears at both levels, and no figure here is ever added to a city figure or to another county's.
How this figure was reached
$934,508,200 — 2026 Adopted, total expenditures, all funds. Two independent presentations inside the book state it: the Summary of Expenditures by Category and the Summary of Expenditures by Department & Fund Type, whose department rows also sum to it. This is Jefferson County's money and NOT the city's. Two separate governments; the same dollar never appears at both levels, and no figure here is ever added to a city figure or to another county's.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
Jefferson County, Colorado
2026 Adopted Budget Book
Open the source document ↗
A 34 MB PDF, 394 pages, parses cleanly, a PDF read as text; the host 404s an invented path. CITE THE URL THAT SERVED THE BYTES: the county's own link text is "View the 2026 Adopted Budget in more detail (PDF)" and the request redirects to .../55502/2026-Adopted-Budget-Book?bidId=. The Sheriff's Office department page prints a Department Division Summary whose six divisions sum EXACTLY to the department total, and the countywide Summary of Expenditures by Department & Fund Type states that department total again from an independent presentation.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
The whole Jefferson County Sheriff's Office for 2026 — every division, all funds.
Published beside the jail line precisely so the two cannot be confused: a department is not its jail, and the readier wrong answer is always adjacent and always larger. This is Jefferson County's money and NOT the city's. Two separate governments; the same dollar never appears at both levels, and no figure here is ever added to a city figure or to another county's.
How this figure was reached
$164,401,000 — the elected Sheriff's whole department for 2026, all funds, as the county printed it. It is NOT a corrections figure: it also covers patrol, investigations and the office's other divisions. Published here only so the jail line beside it can be read as the part of this whole that it is. This is Jefferson County's money and NOT the city's. Two separate governments; the same dollar never appears at both levels, and no figure here is ever added to a city figure or to another county's.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
Jefferson County, Colorado
2026 Adopted Budget Book
Open the source document ↗
A 34 MB PDF, 394 pages, parses cleanly, a PDF read as text; the host 404s an invented path. CITE THE URL THAT SERVED THE BYTES: the county's own link text is "View the 2026 Adopted Budget in more detail (PDF)" and the request redirects to .../55502/2026-Adopted-Budget-Book?bidId=. The Sheriff's Office department page prints a Department Division Summary whose six divisions sum EXACTLY to the department total, and the countywide Summary of Expenditures by Department & Fund Type states that department total again from an independent presentation.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
The Detentions division of the Jefferson County Sheriff's Office, 2026 adopted, under the county's own name for it.
Matched as a DIVISION ROW inside the Sheriff's own department table, never on the word "Correction" — that match picks up oversight boards and commissions. This is Jefferson County's money and NOT the city's. Two separate governments; the same dollar never appears at both levels, and no figure here is ever added to a city figure or to another county's.
How this figure was reached
$66,676,900 — The Detentions division of the Jefferson County Sheriff's Office — the county jail. One of six divisions whose 2026 adopted figures sum EXACTLY to the Sheriff's printed department total, which the countywide department summary states again from a different table. This is Jefferson County's money and NOT the city's. Two separate governments; the same dollar never appears at both levels, and no figure here is ever added to a city figure or to another county's.
What this cannot be compared to
- This figure is on the basis “adopted appropriation”. A figure of the same name on another basis is a different thing, and the two must not be set against each other.
Where it came from
Jefferson County, Colorado
2026 Adopted Budget Book
Open the source document ↗
A 34 MB PDF, 394 pages, parses cleanly, a PDF read as text; the host 404s an invented path. CITE THE URL THAT SERVED THE BYTES: the county's own link text is "View the 2026 Adopted Budget in more detail (PDF)" and the request redirects to .../55502/2026-Adopted-Budget-Book?bidId=. The Sheriff's Office department page prints a Department Division Summary whose six divisions sum EXACTLY to the department total, and the countywide Summary of Expenditures by Department & Fund Type states that department total again from an independent presentation.
Date not published by the source.
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
Reported vehicle theft, on the federal basis.
What this counts
Motor vehicle theft offenses reported by the Lakewood Police Department for the calendar year.
FBI CDE agency endpoint, monthly actuals summed; a year missing any month stops the run.
How this figure was reached
1,214 motor vehicle theft offenses reported by the Lakewood Police Department in 2024 — twelve monthly actuals summed from the FBI CDE agency endpoint, with the agency identity asserted against the FBI's own Colorado roster (ORI CO0300400, Jefferson County).
What this cannot be compared to
- This series begins at 2020 because its denominator does: the Census Vintage 2025 place estimates publish no earlier year, and estimates are rebased between vintages, so an earlier year would ride on a different denominator basis. The department itself has reported NIBRS since 1997-01-01 — through the 2021 national SRS retirement, so no reporting-system break splits this agency's counts — and earlier counts exist at the same endpoint but have not been read or checked here. Nothing in this series should be read backwards past this line.
Where it came from
FBI Crime Data Explorer
CDE summarized offense API, AGENCY endpoint (Lakewood Police Department, ORI CO0300400)
Open the source document ↗
THE AGENCY ENDPOINT, NOT THE STATE ONE. It publishes NO PER-AGENCY COVERAGE SERIES, so the 90% gate every state locale applies cannot be applied here; a year is refused on the count itself against a non-report floor instead (the NYPD precedent). THE WRONG-LAKEWOOD HAZARD IS REAL — California, Ohio, Washington and New Jersey each have one — so the ORI is asserted against the FBI's own Colorado roster every run: CO0300400, JEFFERSON county, agency type City, NIBRS since 1997-01-01 (reporting incident-based through the 2021 national transition, so no SRS/NIBRS break splits this agency's series). The response carries the agency's own population served (~2% above the Census place estimate); it is recorded as a cross-check and NOT used as the denominator.
Date not published by the source.
Every period published (5)
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts
Motor vehicle theft offenses reported by the Lakewood Police Department per 100,000 city residents.
Census place resident population as the denominator — NOT the FBI matched population a state rate uses, and NOT the agency's own population served (recorded beside it as a cross-check). Never comparable with a state rate, and not ranked — the rank is a state-level measure.
How this figure was reached
1,214 offenses / 157,395 residents (Census Vintage 2025 place estimate for 2024) x 100,000 = 771.3. The FBI's own response says this agency serves 155,868 people that year — within 1.0% of the Census figure, recorded as a cross-check and not used as the denominator. NOT comparable with a state rate, which divides by the FBI's coverage-matched population.
What this cannot be compared to
- This series begins at 2020 because its denominator does: the Census Vintage 2025 place estimates publish no earlier year, and estimates are rebased between vintages, so an earlier year would ride on a different denominator basis. The department itself has reported NIBRS since 1997-01-01 — through the 2021 national SRS retirement, so no reporting-system break splits this agency's counts — and earlier counts exist at the same endpoint but have not been read or checked here. Nothing in this series should be read backwards past this line.
Where it came from
FBI Crime Data Explorer
CDE summarized offense API, AGENCY endpoint (Lakewood Police Department, ORI CO0300400)
Open the source document ↗
THE AGENCY ENDPOINT, NOT THE STATE ONE. It publishes NO PER-AGENCY COVERAGE SERIES, so the 90% gate every state locale applies cannot be applied here; a year is refused on the count itself against a non-report floor instead (the NYPD precedent). THE WRONG-LAKEWOOD HAZARD IS REAL — California, Ohio, Washington and New Jersey each have one — so the ORI is asserted against the FBI's own Colorado roster every run: CO0300400, JEFFERSON county, agency type City, NIBRS since 1997-01-01 (reporting incident-based through the 2021 national transition, so no SRS/NIBRS break splits this agency's series). The response carries the agency's own population served (~2% above the Census place estimate); it is recorded as a cross-check and NOT used as the denominator.
Date not published by the source.
Every period published (5)
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
How many people live in the city.
What this counts
Resident population of the City of Lakewood, Colorado (Census incorporated place 08-43000).
Census Vintage 2025 place estimates — one vintage for every year drawn, because estimates are rebased between vintages. The denominator of every rate on this locale.
How this figure was reached
156,927 residents, Census Vintage 2025 estimate for July 1, 2025. Lakewood city, Colorado — place 08-43000, selected by FIPS code with the name and state asserted, because California, Ohio, Washington and New Jersey each have a Lakewood too.
Where it came from
U.S. Census Bureau, Population Estimates Program
City and town population totals, Vintage 2025 (sub-est2025.csv)
Open the source document ↗
Open flat file, no API key — api.census.gov answers HTTP 200 with an HTML "Invalid Key" page when the key is missing. FOUR OTHER STATES HAVE A LAKEWOOD (California, Ohio, Washington, New Jersey), so the row is selected on SUMLEV 162 + state FIPS 08 + place FIPS 43000 and the name and state are asserted on the row that comes back, never matched on name alone. One vintage for every year drawn (estimates are rebased between vintages), which is also why the rate series starts at 2020 — this vintage publishes no earlier year.
Date not published by the source.
Every period published (6)
✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.