South Carolina 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 South Carolina'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 & on-site staffing

South Carolina's per-age ratio table is only part of the picture: R.114-504.A(4) also sets a campus-wide floor of at least two staff persons in the center at all times, independent of how few children are enrolled at that moment. A six-child center on a single adult fails this rule even if it satisfies every per-age ratio row.

Fire drills

South Carolina's regulations set no fire-drill cadence at all — R.114-505.H(1) defers entirely to the State Fire Marshal. A center should look to the Marshal's requirements, not to a monthly-drill assumption imported from another state's rules.

Credentials

South Carolina requires fingerprint (FBI) results within 14 business days of the SLED background-check result (R.114-503.K(2)(b)) — a deadline measured from one credential event to another, not from hire. The state also re-checks its Central Registry at license renewal, not on a fixed annual cadence.

At least one first-aid holder must be present campus-wide at all times.

Training

South Carolina splits its annual hour requirement by role, with unused hours carrying over only capped, and only in the category originally earned:

Role	Annual hours
Director	20
Direct-care staff	15

The state also runs an "at least three areas" breadth test: hitting the hour total in only one or two training categories does not satisfy the requirement, regardless of total hours logged.

CPR and first-aid training time does not count toward either total. For direct-care staff that exclusion is a blanket sentence; for the director it works by omission instead — the only categories that may fill the remaining ten of their twenty hours are an enumerated list that never names CPR or first aid.

Facility certificates

South Carolina requires both a fire and a health inspection, but never as its own interval — it reaches them through the licence clock. R.114-502.A.(2), (4): at initial licensing the Department must "request in writing that health and fire officials make inspections," and those officials "shall inspect the facility... and shall put in writing... the results." R.114-502.F.(1): 120 days before a licence expires, the Department "shall request health and fire inspections" again for renewal. R.114-502.B.(1) sets the licence term itself at two years. So the cadence is effectively biennial — arrived at by composing three clauses, not read off an "every two years" sentence the way Colorado's is.

KinderBee does not evaluate either certificate. The interval is knowable; the anchor is not — your licence-renewal date is not a field this model carries, so there is no date to count 120 days back from. Rather than substitute a hire date or a calendar year and present the result as South Carolina's requirement, we decline to score it: not compliant, not non-compliant, reported as not evaluated. Both are carried in the product's own unevaluated-obligation registry and listed below.

One citation trap worth naming, because a keyword search walks straight into it: the "annual fire safety inspection" text at R.114-592.B.(1)(b) is Residential Group Care Organizations, the 114-590 series — a different facility type. It is not the child care centre requirement, and reading it as one would put an annual cadence on this page that South Carolina does not impose on you.

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.

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 South 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 — or evaluated only against a stand-in for what the clause really asks. South Carolina has more of both than any other state in the library, because its background-check regime is built almost entirely out of clocks anchored to events rather than intervals, and our model renews on an interval, with one event anchor built and starved. Both failures are listed below, in two lists, because they fail in opposite directions.

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

• The 14-business-day fingerprint window. R.114-503.K.(2)(b): "FBI prints shall be submitted for review within 14 business days upon receiving the SLED results." This is a deadline measured from one credential event to another. We record both credentials and we show you if either is missing; we do not evaluate whether the second arrived within fourteen business days of the first.
• Central Registry at licence renewal. R.114-503.K.(1)(b)(ii) anchors the re-check to "renewal times, if the employee was hired more than 6 months prior to the renewal date." The anchor is the centre's own licence cycle, which is not a date our credential model holds.
• Central Registry before a first licence. R.114-503.K.(1)(b)(i) requires the director and at least two staff checked "prior to the initial issuance of a regular or provisional license/approval." Unlike the renewal-time anchor above, no rule row in our model stands in for this one at all — it is a one-time, director-plus-two-staff duty, not a field on an ongoing requirement.
• The fire inspection's licence-renewal anchor. R.114-502.A.(2), (4) and F.(1), described under Facility certificates above. Same missing-anchor shape as the Central Registry renewal entry above, in a different rule family: the two-year interval is known, the licence-renewal date it counts from is not something we hold.
• The health inspection's licence-renewal anchor. The same clause names health officials in the same sentence as fire. Carried as a separate entry rather than one, because they are two inspections by two authorities and a centre can be current on one and not the other.

Obligations we do evaluate, and answer leniently on a stand-in

The list above is obligations the engine does not reach. This is the opposite failure, and it is worth keeping separate: a clause the engine does fire, on a substitute for the fact the rule actually turns on. It is the more dangerous of the two, because the screen does not look unanswered.

• The break-in-service fingerprint re-check. R.114-503.K.(2)(d) says fingerprint reviews need not be repeated while employment continues — the clause our federal-floor layer relies on — and then immediately adds: "however, if a person has a break in service of one year or longer, the fingerprint reviews shall be repeated." That binds both the SLED and the FBI check, and the anchor is in our model: both rows carry a twelve-month break-in-service threshold, and a recorded break expires both reviews. But nothing in the product records a break in service — no screen, no field, no import — so the engine grants relief on the absence of a record rather than on continuous employment, which is true both when continuity is real and when a gap happened and nobody told us. The leniency runs one way, in the credential holder's favour, on every record. Detail in the South Carolina fingerprint timing piece.

Record categories this state does not require

• Two categories where South Carolina's silence is the finding, not ours. A full-document read (2026-10-06) found no playground inspection record or checklist requirement — South Carolina sets equipment maintenance standards instead — and no parent-conference cadence. We do not track either, and in South Carolina there is nothing to track. We state it rather than let the absence read as an omission.

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.