The budget
What the city was allowed to spend in 2026, and out of which funds.
Citywide totals
What this counts Total Net Expenditures (All Funds) in the City and County of Denver's Final 2026 budget — all funds, excluding internal service charges and interfund transfers.
The book itself calls this "a more accurate picture of total City expenditures" than the gross figure, which is why it is the headline. Printed in $ thousands; five true citywide totals exist for this one year, so the quantity is named at every occurrence.
How this figure was reached Total Net Expenditures (All Funds), 2026: $5,411,388 thousand, as Exhibit 2 prints it — the value is stated at $-thousands precision by the publisher. Reconciled: the six fund groups sum to the printed gross exactly ($5,858,807 thousand), and gross less $447,419 thousand of internal service charges and interfund transfers is the net exactly. The book calls the net figure "a more accurate picture of total City expenditures", which is why it is the headline here. FOUR OTHER TRUE CITYWIDE TOTALS exist for 2026 — the gross, the ~$4.4B appropriated-funds-less-duplications figure, and the two General Fund totals — so the quantity is named at every occurrence.
What this cannot be compared to This figure is on the basis “total net expenditures”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Total Expenditures (All Funds) before removing internal service charges and interfund transfers — the same 2026 budget counted gross.
Published beside the net figure, never instead of it. The $447.4M gap between the two is money the city pays itself.
How this figure was reached Total Expenditures (All Funds), 2026, gross of interfund duplications: $5,858,807 thousand. Counts internal service charges and interfund transfers that the net figure excludes — money the city pays itself. Excludes non-appropriated special revenue funds and grants, as the book states of this exhibit.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Total 2026 General Fund appropriations in the Annual Appropriation Ordinance (CB25-1813): agency, transfer and program items plus the General Fund Contingency.
Reconciled two independent ways to the dollar: the summary's printed components, and the sum of all 64 ordinance items — including a $1 placeholder appropriation.
How this figure was reached General Fund Total Appropriations, 2026: $1,676,329,510, reconciled two independent ways to the dollar. Path one: the summary's own components — annual appropriations $1,642,853,548 plus the General Fund Contingency $33,475,962. Path two: all 64 General Fund items of the enacted ordinance schedule summed, including the $1 placeholder appropriation for Denver Cares — the dollar that makes the sum exact. The Final book's PROSE still says the appropriation "is proposed to decrease to $1.674 billion"; the enacted tables print this figure, and the tables carry.
What this cannot be compared to This figure is on the basis “gf appropriations”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 General Fund appropriation less $13.25M of appropriations the city estimates will go unspent — the figure most press coverage headlines as "the budget".
A DIFFERENT QUANTITY from the appropriation, $13.25M apart, and the book prints both. Exhibit 2 labels THIS figure "General Fund Total Appropriations", which is the book's own footnoted naming trap.
How this figure was reached General Fund Total Expenditures, 2026 estimated: $1,663,079,510 — the appropriation less $13,250,000 of appropriations the city estimates will go unspent. This is the "$1.66B" most press coverage headlines. A DIFFERENT QUANTITY from the appropriation, and Exhibit 2 prints this figure under the LABEL "General Fund Total Appropriations" — the book's own footnote explains that its exhibit folds the unspent line in. Labels are read per table here, never carried between tables.
What this cannot be compared to This figure is on the basis “gf estimated expenditures”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 largest single item among the General Fund items of the 2026 Annual Appropriation Ordinance, by its printed amount.
A CALC rank; the amount is the item's own printed figure, and the item is asserted to be the one den-police-budget reconciles.
How this figure was reached Ordinance item 01010-3510000, the Police Department, $280,421,884: rank 1 of 64 General Fund items. Second is 01010-3530000 ($174,253,830) and third 01010-3520000 ($158,081,466).
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 number of General Fund items in the 2026 Annual Appropriation Ordinance, the set the largest-line rank is taken over.
Counted by the parser, which proves the items sum to the printed General Fund Total Appropriations to the dollar.
How this figure was reached 64 General Fund items read from the ordinance schedule; together they sum to $1,676,329,510, the printed General Fund Total Appropriations.
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Ordinance item 01010-6513000, Denver Cares: a one-dollar placeholder appropriation among the General Fund items.
The dollar that makes the 64 items sum to the printed General Fund Total Appropriations exactly.
How this figure was reached Ordinance item 01010-6513000, Denver Cares: $1, as the enacted General Fund schedule prints it.
What this cannot be compared to This figure is on the basis “gf ordinance item”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 book's prose total for all appropriated funds less duplications, 2026, as the sentence states it: rounded by the publisher to a tenth of a billion.
NAMED, NOT REPUBLISHED. The page quotes it in the book's words beside the four totals it does publish; the arithmetic path from the printed fund totals to it is not printed in one place, so it is never a tile and never a denominator.
How this figure was reached The budget summary's sentence: "The total 2026 budget for all appropriated funds (less duplications) is $4.4 billion". Rounded by the publisher to a tenth of a billion. Named on the page in the book's own words and not republished as a figure: the arithmetic path to it from the printed fund totals is not printed in one place.
What this cannot be compared to This figure is on the basis “appropriated funds less duplications”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Public safety
What this counts General Fund annual appropriation to the Denver Sheriff Department, which runs the city's jails — ordinance item 01010-3530000.
Denver is consolidated, so the city runs its own jails (the Downtown Detention Center and the county jail). The agency is a Sheriff DEPARTMENT and the canonical measure name is kept — see namingExceptions. NOT the whole cost of the jails: jail health care rides in the Denver Health operating agreement's appendix lines, emitted as their own observations and named on the page beside this figure.
How this figure was reached Denver Sheriff Department, General Fund annual appropriation, 2026: $174,253,830 — ordinance item 01010-3530000, reconciled to the dollar against the four Schedule 100B division lines (Administration $40,233,699, Jail Operations $100,690,674, Specialized Operations and Analysis $32,123,631, Mental Health and Programs $1,205,826). NOT the whole cost of the jails: jail health care rides in the Denver Health operating agreement's appendix lines (B-3 acute and chronic care at DCJ and DDC, and A-6 prisoner medical services — both emitted as their own observations). Whether those sit inside or outside this appropriation is not established from the book alone, so they are named beside this figure and never added to it or subtracted from it.
What this cannot be compared to This figure is on the basis “gf annual 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 General Fund annual appropriation to the Denver Police Department — ordinance item 01010-3510000.
Three Schedule 100B division lines sum to the ordinance item exactly.
How this figure was reached Denver Police Department, General Fund annual appropriation, 2026: $280,421,884 — ordinance item 01010-3510000, reconciled to the dollar against the three Schedule 100B division lines (Administration $41,016,759, Investigations $93,687,623, Patrol Districts $145,717,502). General Fund only — grant and special-revenue money is not in this line.
What this cannot be compared to This figure is on the basis “gf annual 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Denver Health operating agreement's appendix line B-3, "Acute and Chronic Health Care at DCJ and DDC" — health care inside the city's two jails, 2026 appropriated.
Named beside the Corrections budget so the Sheriff line is never mistaken for the whole cost of the jails. Never summed with the other health line: the publisher prints no combined total.
How this figure was reached Denver Health operating agreement, appendix line B-3 "Acute and Chronic Health Care at DCJ and DDC": $21,740,490, 2026 appropriated (the appendix's own column heading). Whether this sits inside or outside the Sheriff Department's General Fund appropriation is not established from the book alone, so it is named beside the Corrections budget and never added to it or subtracted from it.
What this cannot be compared to This figure is on the basis “oa 2026 appropriated”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Denver Health operating agreement's appendix line A-6, "Prisoner Medical Services (at DHHA)", 2026 appropriated.
The second jail health-care line, published separately for the same reason.
How this figure was reached Denver Health operating agreement, appendix line A-6 "Prisoner Medical Services (at DHHA)": $5,418,974, 2026 appropriated. Published separately from B-3 — the publisher prints no combined jail-health total and this pipeline never sums components a publisher does not sum.
What this cannot be compared to This figure is on the basis “oa 2026 appropriated”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Where $100 goes, by fund group
What this counts General Fund: share of every $100 of Denver's 2026 all-funds gross budget (estimated expenditures basis — Exhibit 2 folds the unspent line in).
A CALC over the publisher's own Exhibit 2 fund breakout, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached General Fund: $1,663,080 thousand of $5,858,807 thousand = $28.38 of every $100 (largest-remainder cents; the exact share is 28.3860%).
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Enterprise funds: share of every $100 of Denver's 2026 all-funds gross budget (the airport, wastewater, golf and other self-funded operations).
A CALC over the publisher's own Exhibit 2 fund breakout, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Enterprise funds: $1,272,494 thousand of $5,858,807 thousand = $21.72 of every $100 (largest-remainder cents; the exact share is 21.7193%).
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Appropriated special revenue funds: share of every $100 of Denver's 2026 all-funds gross budget (money earmarked by its source).
A CALC over the publisher's own Exhibit 2 fund breakout, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Appropriated special revenue funds: $970,822 thousand of $5,858,807 thousand = $16.57 of every $100 (largest-remainder cents; the exact share is 16.5703%).
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Capital projects funds: share of every $100 of Denver's 2026 all-funds gross budget (building and maintaining assets).
A CALC over the publisher's own Exhibit 2 fund breakout, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Capital projects funds: $951,306 thousand of $5,858,807 thousand = $16.24 of every $100 (largest-remainder cents; the exact share is 16.2372%).
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Debt service funds: share of every $100 of Denver's 2026 all-funds gross budget (paying down what was borrowed).
A CALC over the publisher's own Exhibit 2 fund breakout, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Debt service funds: $864,162 thousand of $5,858,807 thousand = $14.75 of every $100 (largest-remainder cents; the exact share is 14.7498%).
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Internal service funds: share of every $100 of Denver's 2026 all-funds gross budget (services the city sells itself).
A CALC over the publisher's own Exhibit 2 fund breakout, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Internal service funds: $136,943 thousand of $5,858,807 thousand = $2.34 of every $100 (largest-remainder cents; the exact share is 2.3374%).
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 six fund-group shares summed: exactly $100.00 by construction.
Largest-remainder allocation guarantees the sum; the underlying fund groups sum to the printed gross exactly.
How this figure was reached The six fund-group shares sum to exactly $100.00 by largest-remainder construction, and the six underlying totals sum to the printed gross exactly in the publisher's own precision.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Collected for another body
What this counts The Denver Downtown Development Authority's tax-increment money budgeted inside the City and County of Denver's 2026 all-funds total (project 38383).
The only line counted as passed through, by decision. The Denver Health sales-tax fund ($67,659,469) is NOT counted: it is Denver's own tax, dedicated by a vote.
How this figure was reached Denver Downtown Development Authority, project 38383, 2026: $60,000,000, as the Capital Projects Funds summary prints it. The book describes it as "Tax Increment Financing revenues remaining after the payment of debt obligations and associated expenses, to be expended in accordance with the DDA Act" — the Authority's own revenue, budgeted by the city.
What this cannot be compared to This figure is on the basis “tax increment for another body”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Authority's $60,000,000 as a percent of Total Net Expenditures (All Funds), 2026.
A CALC; the formula is on the methodology page. Rounds to 1.11%.
How this figure was reached $60,000,000 ÷ $5,411,388,000 (Total Net Expenditures, all funds, 2026) × 100 = 1.1088%, printed as 1.11%.
What this cannot be compared to This figure is on the basis “total net expenditures”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Authority's $60,000,000 as a percent of Total Expenditures (All Funds), gross, 2026.
A CALC; the formula is on the methodology page. Rounds to 1.02%.
How this figure was reached $60,000,000 ÷ $5,858,807,000 (Total Expenditures, all funds, 2026, gross) × 100 = 1.0241%, printed as 1.02%.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Capital
What this counts 2026 capital appropriations in the five capital funds the Final budget book publishes project by project — the sum of those five schedules' own printed Grand Totals.
A PART of the capital budget, never the whole: the Bond Project Funds and the Grant/Other Capital Funds are published as fund totals and no finer, and the capital contingency is reserved rather than assigned to a project. The whole is published beside this figure as its own observation.
How this figure was reached 140 capital projects across 5 funds, $269,316,418 for 2026: Winter Park Parks and Recreation Fund $5,325,000 + Capital Improvement Fund $194,964,443 + State Conservation Trust Fund $13,420,000 + Parks Legacy Capital Improvement Fund $31,900,795 + Entertainment and Cultural Capital Fund $23,706,180. Every fund's rows sum to its own printed Grand Total exactly, and every Grand Total equals the Expenditures/Appropriations row printed in that fund's financial summary. NOT THE CAPITAL BUDGET: the city's own printed total for all seven capital fund groups is $659,901 thousand, and the difference is the two fund groups published as fund totals and no finer (Bond Project Funds $230,286 thousand, Grant/Other Capital Funds $152,932 thousand) plus $7,367 thousand of contingency reserved against no project. Enterprise-fund capital ($291,405 thousand) is outside that total altogether.
What this cannot be compared to This figure is on the basis “capital appropriation project grain”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Total CIP Expenditures by Fund, 2026 appropriated — the city's own printed total for all seven capital improvement fund groups.
Printed twice in one table, by fund and by department, and both halves are asserted to agree. Printed in $ THOUSANDS. Enterprise-fund capital is NOT in this total — the book keeps it in a separate block and so does this pipeline.
How this figure was reached Total CIP Expenditures by Fund, 2026 appropriated: $659,901 thousand, stated at $-thousands precision by the publisher. Printed twice in one table and asserted to agree: the seven fund rows sum to it, and so do the twelve by-department rows. A third printing sits 700 pages away in Exhibit 2, whose Capital Projects Funds row ($951,306 thousand) is this total plus the enterprise funds' capital — asserted, not assumed.
What this cannot be compared to This figure is on the basis “cip expenditures all funds”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Total Enterprise Fund CIP Expenditures, 2026 appropriated — capital spending by the operations that pay their own way, the airport most of all.
Named beside the CIP total and never added to it: the book prints the two separately, and the operations behind this figure are funded by their own charges rather than by taxes.
How this figure was reached Total Enterprise Fund CIP Expenditures, 2026: $291,405 thousand (Wastewater Management $63,900, Sidewalks $33,007, Environmental Services $2,550, Golf $14,000, Aviation $177,948, $ thousands). The book keeps this OUTSIDE the CIP total and so does this page. None of it is published project by project in this document.
What this cannot be compared to This figure is on the basis “enterprise capital expenditures”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 capital improvement funds’ 2026 contingency reserve, as the citywide capital table prints it — money inside the capital budget that is not assigned to any project.
Part of why the project rows cannot sum to the capital budget. Its row prints a dash in the 2024 column, which is how a parser that only matches figures drops it.
How this figure was reached Capital contingency, 2026: $7,367 thousand, the citywide capital table's own by-department row. It is inside the capital budget and assigned to no project, which is part of why the project rows below cannot add up to the budget above them.
What this cannot be compared to This figure is on the basis “cip expenditures all funds”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 capital appropriations in the Winter Park Parks and Recreation Fund (Schedule 30001), listed project by project.
The schedule's own printed Grand Total, equal to the 15 project rows beneath it and to the fund summary's Expenditures/Appropriations row.
How this figure was reached Winter Park Parks and Recreation Fund, Schedule 30001: $5,325,000 appropriated for 2026 across 15 projects in 3 fund-org groups. Reconciled three ways — the rows sum to this Grand Total exactly, the fund summary prints the same figure as its Expenditures/Appropriations row, and this total plus $255,486 of fund contingency equals the citywide capital table's printed 5,580 thousand for "Winter Park and Recreation Funds". Spend against these appropriations is NOT published for any project anywhere in this book: the schedules carry one column, 2026 Appropriated.
What this cannot be compared to This figure is on the basis “capital appropriation project grain”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 capital appropriations in the Capital Improvement Fund (Schedule 31000), listed project by project.
The schedule's own printed Grand Total, equal to the 73 project rows beneath it and to the fund summary's Expenditures/Appropriations row.
How this figure was reached Capital Improvement Fund, Schedule 31000: $194,964,443 appropriated for 2026 across 73 projects in 24 fund-org groups. Reconciled three ways — the rows sum to this Grand Total exactly, the fund summary prints the same figure as its Expenditures/Appropriations row, and this total plus $5,708,118 of fund contingency equals the citywide capital table's printed 200,673 thousand for "Capital Improvements". Spend against these appropriations is NOT published for any project anywhere in this book: the schedules carry one column, 2026 Appropriated.
What this cannot be compared to This figure is on the basis “capital appropriation project grain”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 capital appropriations in the State Conservation Trust Fund (Schedule 35000), listed project by project.
The schedule's own printed Grand Total, equal to the 23 project rows beneath it and to the fund summary's Expenditures/Appropriations row.
How this figure was reached State Conservation Trust Fund, Schedule 35000: $13,420,000 appropriated for 2026 across 23 projects in 2 fund-org groups. Reconciled three ways — the rows sum to this Grand Total exactly, the fund summary prints the same figure as its Expenditures/Appropriations row, and this total plus $442,134 of fund contingency equals the citywide capital table's printed 13,862 thousand for "State Conservation Trust Funds (Lottery)". Spend against these appropriations is NOT published for any project anywhere in this book: the schedules carry one column, 2026 Appropriated.
What this cannot be compared to This figure is on the basis “capital appropriation project grain”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 capital appropriations in the Parks Legacy Capital Improvement Fund (Schedule 36000), listed project by project.
The schedule's own printed Grand Total, equal to the 19 project rows beneath it and to the fund summary's Expenditures/Appropriations row.
How this figure was reached Parks Legacy Capital Improvement Fund, Schedule 36000: $31,900,795 appropriated for 2026 across 19 projects in 2 fund-org groups. Reconciled three ways — the rows sum to this Grand Total exactly, the fund summary prints the same figure as its Expenditures/Appropriations row, and this total plus $0 of fund contingency equals the citywide capital table's printed 31,901 thousand for "Parks Legacy Capital Improvement". Spend against these appropriations is NOT published for any project anywhere in this book: the schedules carry one column, 2026 Appropriated.
What this cannot be compared to This figure is on the basis “capital appropriation project grain”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 capital appropriations in the Entertainment and Cultural Capital Fund (Schedule 39000), listed project by project.
The schedule's own printed Grand Total, equal to the 10 project rows beneath it and to the fund summary's Expenditures/Appropriations row.
How this figure was reached Entertainment and Cultural Capital Fund, Schedule 39000: $23,706,180 appropriated for 2026 across 10 projects in 4 fund-org groups. Reconciled three ways — the rows sum to this Grand Total exactly, the fund summary prints the same figure as its Expenditures/Appropriations row, and this total plus $961,204 of fund contingency equals the citywide capital table's printed 24,667 thousand for "Entertainment and Cultural Capital Funds". Spend against these appropriations is NOT published for any project anywhere in this book: the schedules carry one column, 2026 Appropriated.
What this cannot be compared to This figure is on the basis “capital appropriation project grain”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
The fund groups in dollars
What this counts General Fund: its 2026 total in Exhibit 2 of the Final 2026 budget book, the fund breakout of the all-funds gross total (estimated expenditures basis — Exhibit 2 folds the unspent line in).
Printed in $ thousands. The six groups sum to the printed gross exactly, which parseExhibit2 asserts before anything is emitted.
How this figure was reached General Fund, 2026: $1,663,080 thousand, as Exhibit 2 prints it. This row is the ESTIMATED-EXPENDITURES quantity, printed in thousands, although Exhibit 2 labels it "General Fund Total Appropriations"; the book's own footnote says so. One of six fund groups that sum to the printed gross of $5,858,807 thousand exactly.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Enterprise funds: its 2026 total in Exhibit 2 of the Final 2026 budget book, the fund breakout of the all-funds gross total (the airport, wastewater, golf and other self-funded operations).
Printed in $ thousands. The six groups sum to the printed gross exactly, which parseExhibit2 asserts before anything is emitted.
How this figure was reached Enterprise funds, 2026: $1,272,494 thousand, as Exhibit 2 prints it. One of six fund groups that sum to the printed gross of $5,858,807 thousand exactly.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Appropriated special revenue funds: its 2026 total in Exhibit 2 of the Final 2026 budget book, the fund breakout of the all-funds gross total (money earmarked by its source).
Printed in $ thousands. The six groups sum to the printed gross exactly, which parseExhibit2 asserts before anything is emitted.
How this figure was reached Appropriated special revenue funds, 2026: $970,822 thousand, as Exhibit 2 prints it. One of six fund groups that sum to the printed gross of $5,858,807 thousand exactly.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Capital projects funds: its 2026 total in Exhibit 2 of the Final 2026 budget book, the fund breakout of the all-funds gross total (building and maintaining assets).
Printed in $ thousands. The six groups sum to the printed gross exactly, which parseExhibit2 asserts before anything is emitted.
How this figure was reached Capital projects funds, 2026: $951,306 thousand, as Exhibit 2 prints it. One of six fund groups that sum to the printed gross of $5,858,807 thousand exactly.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Debt service funds: its 2026 total in Exhibit 2 of the Final 2026 budget book, the fund breakout of the all-funds gross total (paying down what was borrowed).
Printed in $ thousands. The six groups sum to the printed gross exactly, which parseExhibit2 asserts before anything is emitted.
How this figure was reached Debt service funds, 2026: $864,162 thousand, as Exhibit 2 prints it. One of six fund groups that sum to the printed gross of $5,858,807 thousand exactly.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Internal service funds: its 2026 total in Exhibit 2 of the Final 2026 budget book, the fund breakout of the all-funds gross total (services the city sells itself).
Printed in $ thousands. The six groups sum to the printed gross exactly, which parseExhibit2 asserts before anything is emitted.
How this figure was reached Internal service funds, 2026: $136,943 thousand, as Exhibit 2 prints it. One of six fund groups that sum to the printed gross of $5,858,807 thousand exactly.
What this cannot be compared to This figure is on the basis “total expenditures gross”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Per resident
What this counts Total Net Expenditures (All Funds), 2026, divided by the Census resident population of the City and County of Denver.
A CALC over den-budget-net and den-population; the formula is on the methodology page.
How this figure was reached $5,411,388,000 (Total Net Expenditures (All Funds), 2026) ÷ 740,613 residents (Census Vintage 2025, 2025) = $7306.6338, stored to the cent and printed to the dollar.
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Total Expenditures (All Funds), 2026, gross, divided by the Census resident population of the City and County of Denver.
A CALC over den-budget-gross and den-population; the formula is on the methodology page.
How this figure was reached $5,858,807,000 (Total Expenditures (All Funds), 2026, gross) ÷ 740,613 residents (Census Vintage 2025, 2025) = $7910.7537, stored to the cent and printed to the dollar.
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 General Fund Total Appropriations, 2026, divided by the Census resident population of the City and County of Denver.
A CALC over den-gf-appropriations and den-population; the formula is on the methodology page.
How this figure was reached $1,676,329,510 (General Fund Total Appropriations, 2026) ÷ 740,613 residents (Census Vintage 2025, 2025) = $2263.4352, stored to the cent and printed to the dollar.
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
The Denver Health tax fund
What this counts Special revenue fund 11892, the Denver Health and Hospital Authority Tax Fund, 2026: ordinance item 11892-6520000.
Counted as Denver's own money, by decision: a tax Denver's voters levied on themselves and dedicated by a vote. Three printings agree.
How this figure was reached Fund 11892, 2026: $67,659,469, printed three times and the printings agree: the fund's budget summary, the program-and-positions table, and ordinance item 11892-6520000.
What this cannot be compared to This figure is on the basis “sr ordinance item”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Full-time-equivalent positions budgeted in fund 11892 for 2026, for administration of the Denver Health contract.
Printed twice and the printings agree. They are why the fund is an upper bound on what reaches Denver Health.
How this figure was reached 1.50 FTE in fund 11892 for 2026, printed in the fund's budget summary and in the program-and-positions table.
What this cannot be compared to This figure is on the basis “budgeted fte”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Revenue and tax rates
Where the money comes from, and tax rates, as the city’s own budget book prints them.
Property tax
What this counts The Total Tax Levy row of the book's "Denver Tax Levy Assessment" table: the City and County's levies and School District No. 1's, in mills (dollars per $1,000 of assessed value).
Each government's components are reconciled to its printed total, and the two totals to this one, in thousandths of a mill. Special districts that cover only part of the city are not in it, as the table's own note says.
How this figure was reached Total Tax Levy, 2025 column: 79.602 mills, the City and County's 27.328 plus School District #1's 52.274, each reconciled to its own printed components. The City and County block includes the Urban Drainage and Flood Control mill, which the table's own note calls a special district.
What this cannot be compared to This figure is on the basis “levy mills”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Total Tax Levy-School District #1 row of the book's levy table, in mills.
The school district's money, not the city's. Reconciled to its three printed components.
How this figure was reached Total Tax Levy-School District #1, 2025 column: 52.274 mills, reconciled to its three printed components.
What this cannot be compared to This figure is on the basis “levy mills”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Dedicated taxes
What this counts The sales and use tax rate Denver voters added in 2024 (Ballot Measure 2Q) to create the Denver Health and Hospital Authority Tax Fund.
Read from the fund's own overview sentence in the book.
How this figure was reached The book's overview of fund 11892: voters approved Ballot Initiative 2Q, "raising the local sales and use tax by 0.34 percent".
What this cannot be compared to This figure is on the basis “ballot rate”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Where the money comes from
What this counts Exhibit 1 "Total Financial Sources", column "Total Appropriated Governmental Funds", 2026 budget: what the General Fund, the special revenue funds, the debt service funds and the appropriated capital funds expect to take in.
A DIFFERENT SCOPE FROM EVERY SPENDING TOTAL ON THE SITE. The enterprise funds (the airport, wastewater, golf) and the internal service funds are not governmental funds and are not in it, so it is never compared with the all-funds gross or net. Printed in $ thousands. Reconciled four ways: the ten rows to the printed total exactly, each row across the five fund groups exactly, the pie chart's $-millions table, and the General Fund column against Schedule 100A.
How this figure was reached Total Financial Sources of the appropriated governmental funds (Exhibit 1), 2026 budget: $3,143,594 thousand, as printed. Its ten source rows sum to it exactly; each row is the same row summed across the five fund groups exactly; the pie chart's table prints it as $3143.59 million; and the General Fund column's $1,664,329 thousand is Schedule 100A's General Fund Total Revenues of $1,664,328,521 to the thousand.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Property Tax", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Property Tax", Total Appropriated Governmental Funds, 2026 budget: $656,966 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Sales and Use Taxes", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Sales and Use Taxes", Total Appropriated Governmental Funds, 2026 budget: $1,328,272 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Other Taxes", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Other Taxes", Total Appropriated Governmental Funds, 2026 budget: $207,886 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Intergovernmental Revenues", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Intergovernmental Revenues", Total Appropriated Governmental Funds, 2026 budget: $330,165 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Licenses & Permits", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Licenses & Permits", Total Appropriated Governmental Funds, 2026 budget: $59,713 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Fines and Forfeits", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Fines and Forfeits", Total Appropriated Governmental Funds, 2026 budget: $47,198 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Interest Earnings", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Interest Earnings", Total Appropriated Governmental Funds, 2026 budget: $60,357 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Fees", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Fees", Total Appropriated Governmental Funds, 2026 budget: $90,317 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "Charges for Services and Uses", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "Charges for Services and Uses", Total Appropriated Governmental Funds, 2026 budget: $215,556 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Exhibit 1 row "All Other Revenues", column "Total Appropriated Governmental Funds", 2026 budget: one of ten source rows that sum to the governmental funds Total Financial Sources.
Printed in $ thousands, under the book's own label. Not a citywide revenue figure: the enterprise and internal service funds are outside it.
How this figure was reached Exhibit 1, "All Other Revenues", Total Appropriated Governmental Funds, 2026 budget: $147,164 thousand. One of ten rows that sum to the printed $3,143,594 thousand exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Property Tax: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Property Tax: $656,966 thousand of $3,143,594 thousand = $20.90 of every $100 (largest-remainder cents; the exact share is 20.8986%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Sales and Use Taxes: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Sales and Use Taxes: $1,328,272 thousand of $3,143,594 thousand = $42.26 of every $100 (largest-remainder cents; the exact share is 42.2533%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Other Taxes: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Other Taxes: $207,886 thousand of $3,143,594 thousand = $6.61 of every $100 (largest-remainder cents; the exact share is 6.6130%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Intergovernmental Revenues: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Intergovernmental Revenues: $330,165 thousand of $3,143,594 thousand = $10.50 of every $100 (largest-remainder cents; the exact share is 10.5028%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Licenses & Permits: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Licenses & Permits: $59,713 thousand of $3,143,594 thousand = $1.90 of every $100 (largest-remainder cents; the exact share is 1.8995%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Fines and Forfeits: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Fines and Forfeits: $47,198 thousand of $3,143,594 thousand = $1.50 of every $100 (largest-remainder cents; the exact share is 1.5014%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Interest Earnings: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Interest Earnings: $60,357 thousand of $3,143,594 thousand = $1.92 of every $100 (largest-remainder cents; the exact share is 1.9200%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Fees: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Fees: $90,317 thousand of $3,143,594 thousand = $2.87 of every $100 (largest-remainder cents; the exact share is 2.8730%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Charges for Services and Uses: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached Charges for Services and Uses: $215,556 thousand of $3,143,594 thousand = $6.86 of every $100 (largest-remainder cents; the exact share is 6.8570%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 All Other Revenues: its share of every $100 of the appropriated governmental funds' 2026 Total Financial Sources (Exhibit 1).
A CALC over the publisher's own Exhibit 1 rows, largest-remainder to cents so the column sums to exactly $100.00.
How this figure was reached All Other Revenues: $147,164 thousand of $3,143,594 thousand = $4.68 of every $100 (largest-remainder cents; the exact share is 4.6814%).
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 ten source-row shares summed: exactly $100.00 by construction.
Largest-remainder allocation guarantees the sum; the ten rows underneath sum to the printed Total Financial Sources exactly.
How this figure was reached The ten source-row shares sum to exactly $100.00 by largest-remainder construction, and the ten rows sum to the printed Total Financial Sources exactly.
What this cannot be compared to This figure is on the basis “governmental funds financial sources”. 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 and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 Total Financial Sources of the appropriated governmental funds (Exhibit 1), 2026 budget, divided by the Census resident population of the City and County of Denver.
A CALC over den-sources-total and den-population; den_per_resident_v1 names this total among the ones it divides.
How this figure was reached $3,143,594,000 (Total Financial Sources of the appropriated governmental funds (Exhibit 1), 2026 budget) ÷ 740,613 residents (Census Vintage 2025, 2025) = $4244.5839, stored to the cent and printed to the dollar.
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 largest of the ten Exhibit 1 source rows of the appropriated governmental funds, 2026 budget, by its printed amount.
A CALC rank; the amount is the row's own printed figure.
How this figure was reached Sales and Use Taxes, $1,328,272 thousand: rank 1 of 10 source rows of the appropriated governmental funds. Second is Property Tax ($656,966 thousand) and third Intergovernmental Revenues ($330,165 thousand).
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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 number of source rows in Exhibit 1's governmental funds total column, the set the largest-source rank is taken over.
Counted by the parser, which proves the rows sum to the printed Total Financial Sources exactly.
How this figure was reached 10 source rows read from Exhibit 1's governmental funds total column; together they sum to the printed $3,143,594 thousand.
Where it came from City and County of Denver, Department of Finance (Budget and Management Office) Mayor's 2026 Budget — Final (budget book, carrying the Annual Appropriation Ordinance CB25-1813 as enacted text)
Open the source document ↗
A 19.5 MB PDF that parses clean, a PDF read as text. THREE TRAPS. (1) Three budget stages sit one path segment apart under /budget/2026/ — identify the stage by what the document prints about itself (cover FINAL, the fiscal-year title line, Council Bill CB25-1813), never the filename; the /v/N/ path segment is a CMS version that moves under a stable filename (/v/3/ redirected to /v/4/ the day it was probed). (2) Five true citywide totals for one year — gross, net, appropriated-less-duplications, GF appropriations, GF estimated expenditures — so the quantity is named at every occurrence. (3) The same words name two quantities inside one book: Exhibit 2's row "General Fund Total Appropriations" prints the GF summary's Total EXPENDITURES figure, because it folds the estimated-unspent line in — the book's own footnote says so. The Final book's PROSE also keeps proposal-stage language ("is proposed to decrease to $1.674 billion") that the final tables contradict; the tables carry the enacted figures.
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.
Schools
Pupils, funding and graduation in the school district inside the city. The district is a separate government, and its money is never added to the city’s.
Pupils
What this counts Students enrolled in Denver Public Schools on the annual October count date.
CDE Student October collection, at district grain — the same collection and the same count date as the statewide figure, which is why the measure carries the same name. It counts students ATTENDING the district, not children living in the city: Colorado has open enrollment, and the publisher's own count of students attending from outside the district is published beside it.
How this figure was reached 89,210 students enrolled in Denver County 1 on the October 2025 count date. Reconciled: the workbook's 186 district rows sum to its own printed State Total of 870,793 for this year, to the student.
What this cannot be compared to The enrollment series starts at 2017-18 rather than 2015-16, and the reason is a property of the workbook rather than of Denver: its district rows sum 160 students short in 2015-16 and 163 students short in 2016-17 of its own printed State Total, because the sheet lists the organizations that exist today while each column is that year's actual statewide count. Publish the years that can be measured and stop. Where it came from Colorado Department of Education 2025-26 LEA Level PK-12 Membership Workbook (XLS)
Open the source document ↗ · publisher’s page ↗
The October-count workbook at DISTRICT grain — the same collection, the same count date and the same definition as the statewide workbook, which is why this measure carries the same name as the state's. Its trend sheet publishes eleven years and NINE of them reconcile: the 186 district rows sum to the sheet's own printed State Total, to the student, from 2017-18 on. The two OLDEST columns are 2015-16 (160 short) and 2016-17 (163 short), because the sheet lists the organizations that exist today while each column is that year's actual statewide count — so the earliest columns carry students enrolled in organizations that have since closed and have no row. The series starts where it can be measured. CDE serves this behind an opaque resource-manager uuid, read off the publisher's own link text and never constructed.
Date not published by the source.
Every period published (9) ✓ 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 pupil count the school finance formula funds Denver Public Schools on (worksheet line FC9), to the tenth of a pupil as the worksheet prints it.
A DIFFERENT QUANTITY from the October membership count and smaller: the formula counts online and ASCENT students separately and may average a district across years. Published so the per-pupil figure's denominator is a figure a reader can see.
How this figure was reached 84,508.5 funded pupils for Denver Public Schools in FY 2025-26, worksheet line FC9 — the formula's own count, not the October membership. Read from "FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)". Its 179 district columns sum to its own printed state total of $9,998,058,062.99 on the Total Program line, to the dollar.
Where it came from Colorado Department of Education FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)
Open the source document ↗ · publisher’s page ↗
The state education department's district funding calculation worksheet for FY 2025-26, the last one it published for that year. One column per district: Denver Public Schools is the column headed "DENVER COUNTY 1" under the county "DENVER", asserted in every file. Lines read: GT1 (Total Program after the budget stabilization factor), FC9 (total funded pupil count), GT7 (funding per pupil, re-derived as the first over the second to the cent), and GT12, GT13 and GT14 (property tax, specific ownership tax and the adjusted state share), which must make up the district's adjusted Total Program (GT11) to the cent. Every district column on the Total Program line sums to the worksheet's own state total to the dollar. This year funds districts under the new formula (HB24-1448); the "New Formula" sheet is the one read.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Students attending Denver Public Schools whose parents live in another Colorado district, on the October 2025 count date.
The qualifier on the boundary proof. The district's boundary is the city's exactly; its student body is not the city's children exactly, because Colorado has open enrollment. The workbook prints a District Total for this direction and the rows sum to it; it prints NO total for the reverse direction, so none is published.
How this figure was reached 7,505 of the students attending Denver Public Schools in October 2025 have parents living in another Colorado district — the workbook's own printed District Total, equal to its 34 rows summed. The largest single origin is Adams-Arapahoe 28J at 2,224. The same workbook lists the reverse direction district by district and prints NO total for it, so none is stated here.
Where it came from Colorado Department of Education 2025-26 LEA Level PK-12 Membership Workbook (XLS)
Open the source document ↗ · publisher’s page ↗
The October-count workbook at DISTRICT grain — the same collection, the same count date and the same definition as the statewide workbook, which is why this measure carries the same name as the state's. Its trend sheet publishes eleven years and NINE of them reconcile: the 186 district rows sum to the sheet's own printed State Total, to the student, from 2017-18 on. The two OLDEST columns are 2015-16 (160 short) and 2016-17 (163 short), because the sheet lists the organizations that exist today while each column is that year's actual statewide count — so the earliest columns carry students enrolled in organizations that have since closed and have no row. The series starts where it can be measured. CDE serves this behind an opaque resource-manager uuid, read off the publisher's own link text and never constructed.
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.
Results
What this counts Share of a Denver Public Schools anticipated-year-of-graduation cohort graduating within 4 years.
CDE graduation/completion statistics at district grain, anticipated year of graduation basis — the same measure and the same basis as the statewide figure. One workbook per cohort, and only the 4-year row of each is read.
How this figure was reached 81.9% of the 6,943 students in Denver Public Schools' anticipated-2025 graduation cohort graduated within four years, from CDE's 2024-25 release. That release prints the cohort size and the rate and no graduate count, so the rate is not re-derived from its own operands here. The release proves it is the release it claims to be: its own STATE TOTALS 4-year rate for this cohort is 85.6%, the figure CDE published for it. Only the 4-year row is read — the same file also prints 5-, 6- and 7-year rates for three earlier cohorts.
Where it came from Colorado Department of Education Graduation/completion district workbooks, one release per cohort (2018-19 through 2024-25)
Open the source document ↗ · publisher’s page ↗
Seven separate workbooks, one per anticipated year of graduation, declared with their uuids in the shared library. THE TRAP IS INSIDE EVERY FILE: each release prints four rows per district — the 4-year rate for its newest cohort, then the 5-, 6- and 7-year rates for the three cohorts before it — so reading a release's latest cohort without checking the rate type reads a 7-year rate as a 4-year one. FOUR OF THE SEVEN SIT UNDER THE SAME GENERIC LINK TEXT on the archive page ("District and School Graduates and Completers by Subgroups"), so each file proves it is the release it claims to be: its own STATE TOTALS 4-year rate must equal the figure CDE published for that cohort. CDE has also used three header vocabularies and five sheet names across the seven, so every column is resolved by header text and every sheet name is declared per release.
Date not published by the source.
Every period published (7) ✓ 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 statewide share of the anticipated-year-of-graduation cohort that graduated within four years, as printed in the same CDE release as the district figure.
A COMPARISON LINE on this locale: the state's figure, never added to or averaged with the district's.
How this figure was reached 85.6% statewide, the STATE TOTALS 4-year rate printed in CDE's 2024-25 release — the same release, cohort and definition as the district figure beside it.
Where it came from Colorado Department of Education Graduation/completion district workbooks, one release per cohort (2018-19 through 2024-25)
Open the source document ↗ · publisher’s page ↗
Seven separate workbooks, one per anticipated year of graduation, declared with their uuids in the shared library. THE TRAP IS INSIDE EVERY FILE: each release prints four rows per district — the 4-year rate for its newest cohort, then the 5-, 6- and 7-year rates for the three cohorts before it — so reading a release's latest cohort without checking the rate type reads a 7-year rate as a 4-year one. FOUR OF THE SEVEN SIT UNDER THE SAME GENERIC LINK TEXT on the archive page ("District and School Graduates and Completers by Subgroups"), so each file proves it is the release it claims to be: its own STATE TOTALS 4-year rate must equal the figure CDE published for that cohort. CDE has also used three header vocabularies and five sheet names across the seven, so every column is resolved by header text and every sheet name is declared per release.
Date not published by the source.
Every period published (7) ✓ 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 national four-year adjusted cohort graduation rate, NCES Digest table 219.46.
A COMPARISON LINE on this locale. NCES has published through the class of 2021-22; later years are not yet published. NCES flags the 2019-20 and 2020-21 classes with COVID-era comparability caveats.
How this figure was reached NCES Digest 219.46, four-year adjusted cohort graduation rate for the nation, class of 2022. NCES flags 2019-20 and 2020-21 with COVID-era comparability caveats.
Where it came from National Center for Education Statistics Digest table 219.46 — public high school 4-year ACGR by state, 2011-12 to 2021-22
Open the source document ↗
The U.S. comparison line on the graduation chart: the federal four-year ACGR, the same basis as CDE's rate. Read by the shared the shared library, which is proved against values another locale already publishes before any figure is emitted.
Date not published by the source.
Every period published (4) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
Funding
What this counts Denver Public Schools' Total Program for the fiscal year: the school finance formula amount after the budget stabilization factor, before the Charter School Institute transfer, from the last district funding worksheet the state education department published for that year.
One worksheet per fiscal year, FY 2014-15 to FY 2025-26. NOT the district's budget, which also carries federal money, bond money and grants, and NOT the city's money: the district is a separate government. In dollars of each year. FY 2025-26 is the first year on the new formula (HB24-1448), marked as a series break.
How this figure was reached $1,030,737,221.27 of Total Program for Denver Public Schools in FY 2025-26, worksheet line GT1 (after the budget stabilization factor). Read from "FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)". Its 179 district columns sum to its own printed state total of $9,998,058,062.99 on the Total Program line, to the dollar. Not the district's budget, and not the city's money: the district is a separate government.
What this cannot be compared to This figure is on the basis “total program worksheet”. A figure of the same name on another basis is a different thing, and the two must not be set against each other. HB24-1448's new school funding formula phases in from FY 2025-26, and the worksheet for that year funds the district on the new formula's sheet. The line runs straight through, and the page marks the year: FY 2025-26 is the first figure computed by the new formula, so the change from FY 2024-25 is partly a change of rules. Where it came from Colorado Department of Education FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)
Open the source document ↗ · publisher’s page ↗
The state education department's district funding calculation worksheet for FY 2025-26, the last one it published for that year. One column per district: Denver Public Schools is the column headed "DENVER COUNTY 1" under the county "DENVER", asserted in every file. Lines read: GT1 (Total Program after the budget stabilization factor), FC9 (total funded pupil count), GT7 (funding per pupil, re-derived as the first over the second to the cent), and GT12, GT13 and GT14 (property tax, specific ownership tax and the adjusted state share), which must make up the district's adjusted Total Program (GT11) to the cent. Every district column on the Total Program line sums to the worksheet's own state total to the dollar. This year funds districts under the new formula (HB24-1448); the "New Formula" sheet is the one read.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Denver Public Schools' Total Program per funded pupil, as the district funding worksheet prints it, re-derived to the cent.
INCLUDES THE LOCAL PROPERTY-TAX SHARE, like Colorado's statewide figure and unlike Florida's FEFP per student, which is the state share alone. The denominator is the FUNDED pupil count, a school-finance quantity, not the October membership count published beside it.
How this figure was reached $12,196.85 per funded pupil for Denver Public Schools in FY 2025-26, worksheet line GT7. Re-derived: $1,030,737,221.27 / 84,508.5 = $12196.85. Includes the local property-tax share. Read from "FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)". Its 179 district columns sum to its own printed state total of $9,998,058,062.99 on the Total Program line, to the dollar.
What this cannot be compared to This figure is on the basis “total program worksheet”. A figure of the same name on another basis is a different thing, and the two must not be set against each other. HB24-1448's new school funding formula phases in from FY 2025-26, and the worksheet for that year funds the district on the new formula's sheet. The line runs straight through, and the page marks the year: FY 2025-26 is the first figure computed by the new formula, so the change from FY 2024-25 is partly a change of rules. Where it came from Colorado Department of Education FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)
Open the source document ↗ · publisher’s page ↗
The state education department's district funding calculation worksheet for FY 2025-26, the last one it published for that year. One column per district: Denver Public Schools is the column headed "DENVER COUNTY 1" under the county "DENVER", asserted in every file. Lines read: GT1 (Total Program after the budget stabilization factor), FC9 (total funded pupil count), GT7 (funding per pupil, re-derived as the first over the second to the cent), and GT12, GT13 and GT14 (property tax, specific ownership tax and the adjusted state share), which must make up the district's adjusted Total Program (GT11) to the cent. Every district column on the Total Program line sums to the worksheet's own state total to the dollar. This year funds districts under the new formula (HB24-1448); the "New Formula" sheet is the one read.
Date not published by the source.
Every period published (12) ✓ 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 part of Denver Public Schools' Total Program the State of Colorado pays: the district's adjusted state share, worksheet line GT14 (GT7.4 while the budget stabilization factor existed, asserted equal).
Printed on the same worksheet as the total. Named beside the two local lines so the per-pupil figure cannot be read as state money. Never summed with any city figure.
How this figure was reached $264,781,943.39 of Denver Public Schools' FY 2025-26 Total Program is the state share, worksheet line GT14. Line GT12 (property tax) $728,289,937.88, GT13 (specific ownership tax) $37,665,340.00 and GT14 (state share) $264,781,943.39 make up the district's adjusted Total Program (GT11) of $1,030,737,221.27 to the cent, and with no Charter School Institute transfer that is the Total Program published.
What this cannot be compared to This figure is on the basis “total program worksheet”. A figure of the same name on another basis is a different thing, and the two must not be set against each other. HB24-1448's new school funding formula phases in from FY 2025-26, and the worksheet for that year funds the district on the new formula's sheet. The line runs straight through, and the page marks the year: FY 2025-26 is the first figure computed by the new formula, so the change from FY 2024-25 is partly a change of rules. Where it came from Colorado Department of Education FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)
Open the source document ↗ · publisher’s page ↗
The state education department's district funding calculation worksheet for FY 2025-26, the last one it published for that year. One column per district: Denver Public Schools is the column headed "DENVER COUNTY 1" under the county "DENVER", asserted in every file. Lines read: GT1 (Total Program after the budget stabilization factor), FC9 (total funded pupil count), GT7 (funding per pupil, re-derived as the first over the second to the cent), and GT12, GT13 and GT14 (property tax, specific ownership tax and the adjusted state share), which must make up the district's adjusted Total Program (GT11) to the cent. Every district column on the Total Program line sums to the worksheet's own state total to the dollar. This year funds districts under the new formula (HB24-1448); the "New Formula" sheet is the one read.
Date not published by the source.
Every period published (12) ✓ 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 property tax revenue counted toward Denver Public Schools' Total Program, worksheet line GT12.
One of the two local lines the worksheet prints. The worksheet prints no local-share total before FY 2025-26, so the two local lines are published separately and never added here; the three lines are added only to CHECK them against the adjusted Total Program (GT11), at ingest.
How this figure was reached $728,289,937.88 of Denver Public Schools' FY 2025-26 Total Program is property tax revenue, worksheet line GT12. Line GT12 (property tax) $728,289,937.88, GT13 (specific ownership tax) $37,665,340.00 and GT14 (state share) $264,781,943.39 make up the district's adjusted Total Program (GT11) of $1,030,737,221.27 to the cent, and with no Charter School Institute transfer that is the Total Program published.
What this cannot be compared to This figure is on the basis “total program worksheet”. A figure of the same name on another basis is a different thing, and the two must not be set against each other. HB24-1448's new school funding formula phases in from FY 2025-26, and the worksheet for that year funds the district on the new formula's sheet. The line runs straight through, and the page marks the year: FY 2025-26 is the first figure computed by the new formula, so the change from FY 2024-25 is partly a change of rules. Where it came from Colorado Department of Education FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)
Open the source document ↗ · publisher’s page ↗
The state education department's district funding calculation worksheet for FY 2025-26, the last one it published for that year. One column per district: Denver Public Schools is the column headed "DENVER COUNTY 1" under the county "DENVER", asserted in every file. Lines read: GT1 (Total Program after the budget stabilization factor), FC9 (total funded pupil count), GT7 (funding per pupil, re-derived as the first over the second to the cent), and GT12, GT13 and GT14 (property tax, specific ownership tax and the adjusted state share), which must make up the district's adjusted Total Program (GT11) to the cent. Every district column on the Total Program line sums to the worksheet's own state total to the dollar. This year funds districts under the new formula (HB24-1448); the "New Formula" sheet is the one read.
Date not published by the source.
Every period published (12) ✓ 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 specific ownership tax (a vehicle registration tax shared with the district) counted toward Denver Public Schools' Total Program, worksheet line GT13.
The second local line. Published separately from the property tax line for the reason given there.
How this figure was reached $37,665,340.00 of Denver Public Schools' FY 2025-26 Total Program is specific ownership tax, worksheet line GT13. Line GT12 (property tax) $728,289,937.88, GT13 (specific ownership tax) $37,665,340.00 and GT14 (state share) $264,781,943.39 make up the district's adjusted Total Program (GT11) of $1,030,737,221.27 to the cent, and with no Charter School Institute transfer that is the Total Program published.
What this cannot be compared to This figure is on the basis “total program worksheet”. A figure of the same name on another basis is a different thing, and the two must not be set against each other. HB24-1448's new school funding formula phases in from FY 2025-26, and the worksheet for that year funds the district on the new formula's sheet. The line runs straight through, and the page marks the year: FY 2025-26 is the first figure computed by the new formula, so the change from FY 2024-25 is partly a change of rules. Where it came from Colorado Department of Education FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)
Open the source document ↗ · publisher’s page ↗
The state education department's district funding calculation worksheet for FY 2025-26, the last one it published for that year. One column per district: Denver Public Schools is the column headed "DENVER COUNTY 1" under the county "DENVER", asserted in every file. Lines read: GT1 (Total Program after the budget stabilization factor), FC9 (total funded pupil count), GT7 (funding per pupil, re-derived as the first over the second to the cent), and GT12, GT13 and GT14 (property tax, specific ownership tax and the adjusted state share), which must make up the district's adjusted Total Program (GT11) to the cent. Every district column on the Total Program line sums to the worksheet's own state total to the dollar. This year funds districts under the new formula (HB24-1448); the "New Formula" sheet is the one read.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Statewide Total Program over the statewide funded pupil count, both from the state-total column of the district funding worksheet that funds the district beside it.
A COMPARISON LINE on this locale: the state's figure, never added to or averaged with the district's. In dollars of each year, not adjusted for inflation.
How this figure was reached $9,998,058,062.99 statewide Total Program / 841,862.1 statewide funded pupils = $11,876.12, from "FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)" (the worksheet prints $11,876.12 on its own per-pupil line).
What this cannot be compared to The statewide comparison line crosses the same formula change as the district line: FY 2025-26 is the first year computed by HB24-1448's new formula, so the change from FY 2024-25 is partly a change of rules. Where it came from Colorado Department of Education FY2025-26 District Funding Calculation Worksheet - HB25-1320 Updated January 14, 2026 (XLS)
Open the source document ↗ · publisher’s page ↗
The state education department's district funding calculation worksheet for FY 2025-26, the last one it published for that year. One column per district: Denver Public Schools is the column headed "DENVER COUNTY 1" under the county "DENVER", asserted in every file. Lines read: GT1 (Total Program after the budget stabilization factor), FC9 (total funded pupil count), GT7 (funding per pupil, re-derived as the first over the second to the cent), and GT12, GT13 and GT14 (property tax, specific ownership tax and the adjusted state share), which must make up the district's adjusted Total Program (GT11) to the cent. Every district column on the Total Program line sums to the worksheet's own state total to the dollar. This year funds districts under the new formula (HB24-1448); the "New Formula" sheet is the one read.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
Crime
Reported vehicle theft, aggravated assault and burglary, on the federal basis.
Vehicle theft
What this counts Motor vehicle theft offenses reported by the Denver Police Department per 100,000 people it serves.
FBI CDE agency endpoint, with the agency's own population served as the denominator — the New York City precedent. Drawn beside the Colorado and U.S. lines, which divide by the FBI's own state and national population figures instead, and the page states that difference where they meet. Not ranked: the rank is a state-level measure a city is not eligible for.
How this figure was reached 5,549 motor vehicle theft offenses reported by the Denver Police Department in 2025 / 733,212 population served x 100,000. The agency's own population, published in the same response — not a Census figure and not the FBI's state population.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. Where it came from FBI Crime Data Explorer CDE summarized offense API, AGENCY endpoint (Denver Police Department, ORI CODPD0000)
Open the source document ↗
AN ORI IS A CONSTRUCTED URL AND THE ENDPOINT FAKE-200s. A remembered Denver-shaped ORI resolved to a campus police department, and an INVENTED ORI returns well-formed JSON carrying only national series — so the ORI comes from the publisher's own state roster (which names Denver Police Department, county DENVER, NIBRS since 2005-01-01), and the run asserts the agency's own series name is in the payload. The agency endpoint publishes NO per-agency coverage series, so the 90% coverage gate the state locales use cannot be applied here; the refusal is a non-report floor on the count itself, the New York City precedent. The response carries the agency's own population served, which is the rate's denominator — a different quantity from the FBI's population for a whole state. Read for three offenses since 8 October 2026 (motor vehicle theft, aggravated assault and burglary; the offense is the path segment and nothing else changes), 2014 through 2025, and every offense response must print the same population served for every year.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Aggravated assault offenses reported by the Denver Police Department per 100,000 people it serves.
FBI CDE agency endpoint, with the agency's own population served as the denominator — the New York City precedent. Drawn beside the Colorado and U.S. lines, which divide by the FBI's own state and national population figures instead, and the page states that difference where they meet. Not ranked: the rank is a state-level measure a city is not eligible for.
How this figure was reached 4,686 aggravated assault offenses reported by the Denver Police Department in 2025 / 733,212 population served x 100,000. The agency's own population, published in the same response — not a Census figure and not the FBI's state population.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. Where it came from FBI Crime Data Explorer CDE summarized offense API, AGENCY endpoint (Denver Police Department, ORI CODPD0000)
Open the source document ↗
AN ORI IS A CONSTRUCTED URL AND THE ENDPOINT FAKE-200s. A remembered Denver-shaped ORI resolved to a campus police department, and an INVENTED ORI returns well-formed JSON carrying only national series — so the ORI comes from the publisher's own state roster (which names Denver Police Department, county DENVER, NIBRS since 2005-01-01), and the run asserts the agency's own series name is in the payload. The agency endpoint publishes NO per-agency coverage series, so the 90% coverage gate the state locales use cannot be applied here; the refusal is a non-report floor on the count itself, the New York City precedent. The response carries the agency's own population served, which is the rate's denominator — a different quantity from the FBI's population for a whole state. Read for three offenses since 8 October 2026 (motor vehicle theft, aggravated assault and burglary; the offense is the path segment and nothing else changes), 2014 through 2025, and every offense response must print the same population served for every year.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Burglary offenses reported by the Denver Police Department per 100,000 people it serves.
FBI CDE agency endpoint, with the agency's own population served as the denominator — the New York City precedent. Drawn beside the Colorado and U.S. lines, which divide by the FBI's own state and national population figures instead, and the page states that difference where they meet. Not ranked: the rank is a state-level measure a city is not eligible for.
How this figure was reached 4,296 burglary offenses reported by the Denver Police Department in 2025 / 733,212 population served x 100,000. The agency's own population, published in the same response — not a Census figure and not the FBI's state population.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. Where it came from FBI Crime Data Explorer CDE summarized offense API, AGENCY endpoint (Denver Police Department, ORI CODPD0000)
Open the source document ↗
AN ORI IS A CONSTRUCTED URL AND THE ENDPOINT FAKE-200s. A remembered Denver-shaped ORI resolved to a campus police department, and an INVENTED ORI returns well-formed JSON carrying only national series — so the ORI comes from the publisher's own state roster (which names Denver Police Department, county DENVER, NIBRS since 2005-01-01), and the run asserts the agency's own series name is in the payload. The agency endpoint publishes NO per-agency coverage series, so the 90% coverage gate the state locales use cannot be applied here; the refusal is a non-report floor on the count itself, the New York City precedent. The response carries the agency's own population served, which is the rate's denominator — a different quantity from the FBI's population for a whole state. Read for three offenses since 8 October 2026 (motor vehicle theft, aggravated assault and burglary; the offense is the path segment and nothing else changes), 2014 through 2025, and every offense response must print the same population served for every year.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Aggravated assault offenses per 100,000 people in Colorado, reported counts and population both from the FBI CDE summarized API.
A COMPARISON LINE on this locale: another government's rate, drawn beside Denver's and never added to or averaged with it. Its denominator is the FBI's own population figure, where Denver's is the population its police department serves. Years below 90% population coverage are gaps.
How this figure was reached 19,408 offenses / 6,012,561 population x 100,000; coverage 99.1%. The population is the FBI's own figure for the whole geography in the same response, every resident and not only those served by agencies that reported, so this line and the U.S. line are worked out the same way. Where coverage is below 100% the rate reads low by up to the uncovered share.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. This source covered 96.4% of the population in this period. Where it came from FBI Crime Data Explorer CDE summarized offense API (state + national, with populations and coverage)
Open the source document ↗
The Colorado and U.S. comparison lines, read by the same shared function and with the same 90% coverage gate as the Colorado page. National 2021 coverage is below that gate (the national reporting transition), so the 2021 U.S. figure is a visible gap, never a plotted point.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Aggravated assault offenses per 100,000 people in the nation, reported counts and population both from the FBI CDE summarized API.
A COMPARISON LINE on this locale: another government's rate, drawn beside Denver's and never added to or averaged with it. Its denominator is the FBI's own population figure, where Denver's is the population its police department serves. Years below 90% population coverage are gaps.
How this figure was reached 792,153 offenses / 345,206,793 population x 100,000; coverage 96.4%. The population is the FBI's own figure for the whole geography in the same response, every resident and not only those served by agencies that reported, so this line and the U.S. line are worked out the same way. Where coverage is below 100% the rate reads low by up to the uncovered share.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. This source covered 96.4% of the population in this period. Where it came from FBI Crime Data Explorer CDE summarized offense API (state + national, with populations and coverage)
Open the source document ↗
The Colorado and U.S. comparison lines, read by the same shared function and with the same 90% coverage gate as the Colorado page. National 2021 coverage is below that gate (the national reporting transition), so the 2021 U.S. figure is a visible gap, never a plotted point.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Burglary offenses per 100,000 people in Colorado, reported counts and population both from the FBI CDE summarized API.
A COMPARISON LINE on this locale: another government's rate, drawn beside Denver's and never added to or averaged with it. Its denominator is the FBI's own population figure, where Denver's is the population its police department serves. Years below 90% population coverage are gaps.
How this figure was reached 17,212 offenses / 6,012,561 population x 100,000; coverage 99.1%. The population is the FBI's own figure for the whole geography in the same response, every resident and not only those served by agencies that reported, so this line and the U.S. line are worked out the same way. Where coverage is below 100% the rate reads low by up to the uncovered share.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. This source covered 96.4% of the population in this period. Where it came from FBI Crime Data Explorer CDE summarized offense API (state + national, with populations and coverage)
Open the source document ↗
The Colorado and U.S. comparison lines, read by the same shared function and with the same 90% coverage gate as the Colorado page. National 2021 coverage is below that gate (the national reporting transition), so the 2021 U.S. figure is a visible gap, never a plotted point.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
What this counts Burglary offenses per 100,000 people in the nation, reported counts and population both from the FBI CDE summarized API.
A COMPARISON LINE on this locale: another government's rate, drawn beside Denver's and never added to or averaged with it. Its denominator is the FBI's own population figure, where Denver's is the population its police department serves. Years below 90% population coverage are gaps.
How this figure was reached 649,280 offenses / 345,206,793 population x 100,000; coverage 96.4%. The population is the FBI's own figure for the whole geography in the same response, every resident and not only those served by agencies that reported, so this line and the U.S. line are worked out the same way. Where coverage is below 100% the rate reads low by up to the uncovered share.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. This source covered 96.4% of the population in this period. Where it came from FBI Crime Data Explorer CDE summarized offense API (state + national, with populations and coverage)
Open the source document ↗
The Colorado and U.S. comparison lines, read by the same shared function and with the same 90% coverage gate as the Colorado page. National 2021 coverage is below that gate (the national reporting transition), so the 2021 U.S. figure is a visible gap, never a plotted point.
Date not published by the source.
Every period published (12) ✓ 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 per 100,000 people in Colorado, reported counts and population both from the FBI CDE summarized API.
A COMPARISON LINE on this locale: another government's rate, drawn beside Denver's and never added to or averaged with it. Its denominator is the FBI's own population figure, where Denver's is the population its police department serves. Years below 90% population coverage are gaps.
How this figure was reached 18,746 offenses / 6,012,561 population x 100,000; coverage 99.1%. The population is the FBI's own figure for the whole geography in the same response, every resident and not only those served by agencies that reported, so this line and the U.S. line are worked out the same way. Where coverage is below 100% the rate reads low by up to the uncovered share.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. This source covered 96.4% of the population in this period. Where it came from FBI Crime Data Explorer CDE summarized offense API (state + national, with populations and coverage)
Open the source document ↗
The Colorado and U.S. comparison lines, read by the same shared function and with the same 90% coverage gate as the Colorado page. National 2021 coverage is below that gate (the national reporting transition), so the 2021 U.S. figure is a visible gap, never a plotted point.
Date not published by the source.
Every period published (12) ✓ 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 per 100,000 people in the nation, reported counts and population both from the FBI CDE summarized API.
A COMPARISON LINE on this locale: another government's rate, drawn beside Denver's and never added to or averaged with it. Its denominator is the FBI's own population figure, where Denver's is the population its police department serves. Years below 90% population coverage are gaps.
How this figure was reached 665,377 offenses / 345,206,793 population x 100,000; coverage 96.4%. The population is the FBI's own figure for the whole geography in the same response, every resident and not only those served by agencies that reported, so this line and the U.S. line are worked out the same way. Where coverage is below 100% the rate reads low by up to the uncovered share.
What this cannot be compared to The FBI retired summary (SRS) reporting nationally on 2021-01-01; NIBRS counts every offense in an incident rather than only the most serious. The Denver Police Department itself has reported NIBRS since 2005-01-01 — the FBI's own roster states the date, and the ingest asserts it — so DPD's series does not cross a counting change here. The national comparison line DOES cross it: national coverage fell below the 90% gate in 2021, so that year is a gap on the U.S. line, and the page says so beside the lines. This source covered 96.4% of the population in this period. Where it came from FBI Crime Data Explorer CDE summarized offense API (state + national, with populations and coverage)
Open the source document ↗
The Colorado and U.S. comparison lines, read by the same shared function and with the same 90% coverage gate as the Colorado page. National 2021 coverage is below that gate (the national reporting transition), so the 2021 U.S. figure is a visible gap, never a plotted point.
Date not published by the source.
Every period published (12) ✓ Sealed. Read from the checked data and re-derived against its own source record. Nothing here was worked out for you.
People
How many people live in the city.
What this counts Resident population of the City and County of Denver.
Census county estimate. Denver is consolidated, so the county row is the city — no summing, no name matching.
How this figure was reached 740,613 residents, Census Vintage 2025 estimate for 2025. The Census COUNTY row for Denver County is the city, because Denver is a consolidated city and county on one boundary. This differs from the FBI agency response's "population served" (the vehicle-theft rate's denominator) by about 2.5% — two denominators, two jobs, never interchanged.
Where it came from U.S. Census Bureau, Population Estimates Program County population totals (Vintage 2025)
Open the source document ↗
Denver is a consolidated city and county, so the Census COUNTY row IS the city — no summing, no name matching, unlike New York City's five-borough sum. Open flat file, no API key: api.census.gov answers HTTP 200 with an HTML "Invalid Key" page when the key is missing, so the flat file is the honest path.
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.