Colorado child care licensing requirements

Not yet available in your state. KinderBee sells only in North Carolina today. This page is reference material — we publish what Colorado's rule text says because we read it, not because there is software you can buy from us here yet. What we sell in North Carolina

Ratios

Age group	Ratio
Infants	1:5
Mixed age 2½–6	1:10 (group cap 20)

Colorado's infant ratio is 1:5 — not 1:4, a figure that does not appear anywhere in the current rule text. An aide assigned to an infant room under 2.216(B)(2)(b) exists specifically to maintain that 1:5 ratio, which reinforces the figure rather than implying a different one.

Background checks

A background check that has only been submitted does not authorize care in Colorado. 8 CCR 1402-1 2.121(D)(4)(a) requires the check be successfully completed before an individual cares for children. Colorado also requires a separate National Sex Offender Registry check under 2.121(D)(4)(b) — a distinct gate from the general background check.

A citation note: Colorado's rule numbering changed effective 2026-02-14 (ruleVersionId 12417). Several older, still-circulating citations point at superseded rule text — worth checking that any source you're reading cites the current rule series, not last year's.

Ratio relief at naptime

Colorado permits doubling group size at naptime for preschool classrooms (2½ years and older) — but only when all of four conditions hold: at least half the children are asleep, another staff member is on-site and immediately available, the group-size cap is not exceeded, and the supervising staff member holds an early-childhood-teacher or assistant qualification. Overnight care has its own, separate 1:6 ratio for sleeping children.

Training

Colorado's training year is anchored to each employee's own start date, not the calendar year. Colorado also forbids carryover of unused training hours into the next year — a stricter rule than states that allow a capped carryover.

Facility certificates

Colorado puts both the health and the fire inspection in one clause on a two-year cycle, not an annual one — 8 CCR 1402-1, 2.122(A): "Prior to the original license being issued, following the renovation of the facility that would affect the licensing of the facility and at least every two (2) years thereafter, all child care facilities... must be inspected and obtain an approving inspection report from the local department of health or [CDPHE] and from the local fire department." If you have run a centre in a state with an annual cycle, this is the number most likely to be carried over wrong: Colorado's is twenty-four months.

KinderBee evaluates the two-year interval. You record each inspection report and its date; we score it against the twenty-four-month cadence and tell you when it has lapsed. Three honest limits: a report you have not recorded scores as missing rather than absent, since we have no connection to any state or county system; an expiry we derive from the issue date is our arithmetic on 2.122(A)'s cadence, not a date Colorado printed on your report; and the clause's other two triggers are not an interval at all — see the renovation trigger in the unevaluated list below.

These values are a fourth rule family, with provenance of its own rather than a share of the three dates in this page's status line: a full-document primary-text read recorded at organization/planning/VERIFICATION_2026-08-10.md §44 (CHA-400, 2026-10-06). Its tier is not asserted in this sentence. It is declared in the page's own source and checked against the product's rule database on every build, so a later re-read or a sixth state cannot leave it stale here unnoticed — docs/adr/0080 §1c: a tier claim names exactly one rule set, and names it somewhere a gate can see it.

Outdoor-area hazard checks

Colorado states its outdoor-area duty in two pieces, and only one of them is a record on a cadence. 8 CCR 1402-1, 2.230(C)(8) requires that "all outdoor play areas used for children's activities" be checked daily for hazards. That one we score, and we score it unconditionally — the engine returns the days with no check on record, not a count of the checks you did, because here too the gap is the finding. The current day is never a finding; a day that has not ended is not yet a lapse.

The other piece is the annual third-party certification at 2.230(D), which Colorado offers as a safe harbor from its prescriptive equipment specifications. We do not model it and we never credit it, which is set out under Obligations in Colorado's rule text we do not evaluate below. The two are easy to conflate and should not be: the daily check is owed by every Colorado facility whether or not a certification is on file.

This citation has no rule set of its own and so carries no verification tier to declare. It is primary text read in full and recorded at organization/planning/VERIFICATION_2026-08-10.md §44 (CHA-400, 2026-10-06), and it is offered here as that and nothing more.

What "verified" on this page claims — and what it does not

The three dates in this page's status line are provenance claims: each rule set's values and citations were read against primary Colorado rule text at 8 CCR 1402-1, ruleVersionId 12417, on that date, by a licensing compliance analyst, and corrections were made where the read found them. That is not a coverage claim. docs/adr/0018 §1 is the rule that keeps the two apart: a verified rule set can still carry clauses nobody evaluated. Colorado's are mostly of one kind — rules whose shape we deliberately refuse to approximate.

Obligations in Colorado's rule text we do not evaluate

• The naptime relief described above is never granted by our engine. 2.217(A)(10)'s four conditions are not things we can observe — whether half the children are actually asleep, whether a second staff member is on-site and immediately available — so we do not model the relief at all. A room our staffing board calls out of ratio at naptime may well be in ratio under 2.217(A)(10). We score stricter than Colorado and never produce a false pass, which is the safe direction, but it is not the same as evaluating the rule.
• The formal-kindergarten session ratio. 2.217(A)(11) sets a looser 1:25 for formal kindergarten class sessions. Same shape as the naptime relief and the same disposition: unmodelled, therefore denied, therefore stricter than the state.
• Group composition does not drive the band. 2.217(A)(14)(a): "The ratio for toddler groups is based on the youngest child in the group," and for preschool combinations the youngest child's ratio applies when more than 20% of the group is younger. Our engine picks a band per child from that child's age, not from the composition of the group they sit in. This is the largest unbuilt piece on this page.
• The playground-certification branch. 2.230(C) sets prescriptive equipment-dimension rules — surfacing depth, use-zone dimensions, maximum climbing height — and a facility is exempt from them only if it holds an annual third-party playground safety certification from a nationally recognised organisation (2.230(D)). We do not model that exemption, and we never credit it: a certified facility gets no relief from us, because relief we cannot observe is relief we decline to grant. Carried in the product's unevaluated-obligation registry as co_playground_certification_denied_conditional. The daily hazard check at 2.230(C)(8) is a separate duty that applies regardless of certification, and that one we do score — see Outdoor-area hazard checks above.
• The renovation trigger on the facility inspection. 2.122(A) names three triggers, not one: before the original license is issued, "following the renovation of the facility that would affect the licensing of the facility," and at least every two years thereafter. We evaluate the two-year interval. A renovation is an event, not an interval, and our model has no term for it — so a centre that renovates mid-cycle owes Colorado a fresh inspection that our twenty-four-month clock will not ask for until the cycle is up. This is the one place on this page where our gap could run lenient rather than stricter, which is why it is stated plainly rather than folded into the cadence above.

Record categories this state does not require

• One category where Colorado's rule stops short of a cadence. Colorado requires a written parent-conference procedure — observations documented, dates and attendees logged — but sets no cadence for how often a conference must happen. There is no interval here for us to check, and we say so rather than letting the absence read as a gap we are hiding.

The boundary on all of it

Every record category the product's inspection packet asks for now has a section that scores it — the packet's own not yet evidenced list is empty, for the first time since we started keeping it. Read that as a claim about structure and nothing else. The packet still hard-wires its own summary to not complete, and the obligations listed above are why: a category can have a section, and that section can still rest on a clause nobody evaluated. An empty gap list is not a pass. We would rather write that sentence than let the absence of this list read as one.

KinderBee is at a pilot, disclosed stage, not a finished compliance guarantee. We model rules from primary text and show you what the rule says and when a record stops satisfying it. We do not certify that your centre is compliant, and no software can — an unannounced licensing visit (45 CFR 98.42(b)(2)(i)(B)) assesses your centre, not your vendor. Promoting a rule set to verified does not move that line, and every one of our rule sets reading verified does not move it either: verified is a statement about how carefully we read the rules, not about how much of them the engine fires. The inspection packet inside the product hard-wires its own summary to not complete for the same reason.