North Carolina child care licensing requirements

North Carolina is the state we sell in. This page is the rule data behind the product, not a brochure for it — if you run a centre licensed in North Carolina, the product it feeds is on sale to you today.

Ratios

North Carolina lets a center opt in to a named mixed-age group model instead of straight per-child-age ratios, by written notice to the Division — 10A NCAC 09 .0713(d). Once elected, the group's staffing is set by its composition rather than by each child's individual age band.

Credentials

Every infant room must have an ITS-SIDS-credentialed staff member present. The clock on that requirement starts at room assignment, not at hire — a detail that changes when a new hire is actually in scope for the requirement.

North Carolina also requires a child's medical file be kept separate from the personnel file (10A NCAC 09 .0701(d)), which shapes how a center should structure its own recordkeeping regardless of what software it uses.

Training

Annual professional development hours are set by credential level and then prorated by weekly hours worked — a part-time caregiver and a full-time caregiver at the same credential level do not owe the same number of hours.

Credential level	Annual hours (full-time)
Level 1	5
Level 2	8
Level 3	10
Level 4	15
Level 5	20

North Carolina also runs a rolling five-year topic-coverage matrix across the eleven federal training topics named in 45 CFR 98.41(a)(1), rather than a simple annual hour count. A center needs to know not just how many hours a staff member has logged, but which of the eleven topics those hours actually covered, and over what window.

Facility certificates

North Carolina requires an annual fire inspection (10A NCAC 09 .0304(a)) and an annual sanitation inspection (10A NCAC 09 .0304(b)) — two separate certificates, both on a twelve-month cycle. North Carolina is the strictest of the five states in this library on this point: Colorado runs the same two certificates on a two-year cycle, Georgia requires nothing recurring at all, and South Carolina and Massachusetts state no interval we can act on.

KinderBee evaluates both. You record the certificate and its issue date; we score it against the twelve-month cycle and tell you when it has lapsed, using the certificate's own expiry date where it carries one and twelve months from issue where it does not. Two honest limits: a certificate you have not recorded scores as missing, not as absent — we have no connection to any state system and cannot know you hold one — and an expiry we derive from the issue date is our arithmetic on .0304's cadence, not a date North Carolina printed on your document.

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), itself confirming an earlier North Carolina read (CHA-324). 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.

Playground inspections and parent conferences

Two record categories an unannounced North Carolina visit asks for, and both are scored.

Monthly playground inspections. 10A NCAC 09 .0302(d)(6) puts "records of monthly playground inspections documented on a checklist provided by the Division" in the record set a centre must keep. We score it the way we score a fire drill: the engine returns the months with no inspection on record, not a count of the inspections you did, because on this obligation the gap is the finding. The current month is never a finding — a month that has not ended is a plan, not a lapse. Two limits worth stating: we hold the record and its date, we do not reproduce the Division's checklist or judge what you wrote on it; and a month you inspected but did not record scores as a gap, because an unrecorded check is exactly what a visit cannot see either.

Parent conferences. 10A NCAC 09 .3219(b)(2) requires a centre's administrator to "offer an annual family conference with teaching staff … to set a goal(s) for their child," and .3219(f)(1)(C) tightens that to twice annually. The duty North Carolina writes is an offer, so that is what we record: a conference a family declines satisfies the rule exactly as a held one does, and both are stored as outcomes of the same offer. A child with no offer recorded inside a window is the gap. Which centres owe which cadence we now evaluate, against a star rating an admin has verified. 10A NCAC 09 .3010 reaches the same conference item unconditionally for any classroom run as an NC Pre-K program, against a verified classroom designation rather than a star rating — also evaluated, along with .3010's orientation and family-event quotas. Two of .3010's six items state no interval at all and stay unevaluated — stated in full below rather than left for you to discover.

These two categories carry their provenance differently, and the difference is worth naming rather than smoothing over. North Carolina's conference cadence is a fifth rule family with a tier of its own, declared in this page's source and checked against the product's rule database on every build rather than asserted in this sentence (docs/adr/0080 §1c); it rests on fresh reads of North Carolina's own Chapter 9 text recorded at organization/planning/VERIFICATION_2026-08-10.md §29 (CHA-324, 2026-10-03) and §67 (CHA-808, 2026-10-17 — the NC Pre-K row), with every active row's verified_on reconciled to the later date (§71, CHA-829) since this page states one tier for the whole family rather than one per row. The playground citation has no rule set of its own and therefore no tier to declare: it is primary text read in full at §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 North Carolina rule text 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. Those clauses are listed below rather than left to be inferred from a green status line.

Obligations in North Carolina's rule text we do not evaluate

• The ITS-SIDS clock. 10A NCAC 09 .1102(f) requires the training "completed within two months of an individual assuming responsibilities in the infant room and every three years thereafter." We evaluate the coverage duty — whether an infant room has a credentialed person present — and we evaluate the three-year renewal. We do not evaluate the two-month window, because the model renews a credential on an interval from the credential's own dates and has no term for a clock that starts at room assignment. It is carried in the product's own unevaluated-obligation registry as an incomplete clock, not treated as satisfied.
• Training-record field completeness is stricter than North Carolina's text. 10A NCAC 09 .1102 and .1103 require only proof of completion on file; they enumerate no fields. We apply a six-field union drawn from the two states that do enumerate (Colorado and South Carolina), so a complete, on-time North Carolina record can be flagged incomplete for a field North Carolina never asked for. The error is in the direction of over-flagging, never of a false pass.
• Playground-safety training re-arming on a vacancy. 10A NCAC 09 .1102(e) provides that "staff counted to comply with this Rule shall have six months from the date of employment, or from the date a vacancy occurs, to complete the required safety training." A vacancy re-arms the clock: someone leaves, and the six-month window re-opens for whoever is counted to cover that role. Verified against primary text during this content's own sign-off (CHA-346, 2026-10-05) rather than during the credential rule set's 2026-08-10 promotion pass, which is why the date differs from this page's status line. It is a verified North Carolina requirement that the product does not evaluate at all: a trigger that re-arms on a role becoming vacant has no home in a model that renews on an interval.
• North Carolina's NC Pre-K family-engagement plan, two items of six. 10A NCAC 09 .3219(b)(2) attaches a conference duty at a two-star-or-higher licence and (f)(1)(C) doubles it to twice a year at three stars and above; those two we evaluate, against a star rating an admin recorded and an admin verified — never a centre's self-report, the same discipline a staff credential needs before it counts for anything here. A verified rating below two stars (North Carolina's own unrated or one star) owes nothing under .3219, and we say so rather than charging it anyway; a location with no verified rating on file is still scored at the strictest figure, so an unconfirmed value never reads as relief. 10A NCAC 09 .3010 reaches the conference item again, unconditionally, for any classroom run as an NC Pre-K program, against a verified classroom designation rather than a star rating — a sibling predicate, not a stricter tier of .3219. That one we now evaluate too, along with .3010's other quantified items: an enrollment orientation with a classroom visit before the child's first day, at least one annual family event with an educational component, and at least two annual family events overall. What we do not evaluate is .3010's remaining two items — classroom visits/participation and decision-making involvement — and the reason is not a missing field this time: in every version of the text we have read, neither states a frequency, a count, or an interval of any kind for us to check a record against. That is a permanently open gap, the same shape as two of Massachusetts' facility-certificate rows, not an engineering backlog item — it closes only if a future primary-source read finds language this one missed, not by building anything. It is carried in the product's own unevaluated-obligation registry as nc_parent_conference_nc_prek_cross_reference.

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.