South Carolina daycare fingerprints: the 14-business-day FBI window, and the gap that opens after it

The short answer

Two fingerprint reviews, in order, with a 14-business-day deadline between them.

South Carolina runs a state review first and a federal one second, and the second one's clock does not start at hire — it starts when the first one's result lands (SC credentials rule set, verified against primary text 2026-10-02):

Review	When it must be done	Clause
SLED state fingerprint review	Before the person works with children	R.114-503.K.(2)(a)
FBI fingerprint review	Submitted within 14 business days of receiving the SLED results; the review itself gates unsupervised access	R.114-503.K.(2)(b)

K.(2)(a) reads that "a person shall first undergo a State fingerprint review from the State Law Enforcement Division (SLED)." K.(2)(b) then requires that "FBI prints shall be submitted for review within 14 business days upon receiving the SLED results."

Fourteen business days, not calendar days. And the trigger is receiving the SLED result, which is a date you do not control and cannot schedule from in advance. That is the whole administrative difficulty of this rule: the deadline is real, short, and anchored to someone else's turnaround.

The order matters, because it is also what lets someone start working

South Carolina's sequencing is not bureaucratic tidiness — it is the state's provisional-employment mechanism. K.(2)(b) allows provisional employment once a favourable SLED result is in hand, while the FBI review is still pending (SC credentials rule set, verified against primary text 2026-10-02).

That is why the two rows carry different gates in our data: the SLED review is required before working with children, and the FBI review is required before unsupervised access. One sentence of rule text, two thresholds.

If you operate in more than one state, do not carry a habit across the border on this question. "Can they work while the check is pending" has three genuinely different answers in the states we model: South Carolina gates on the state result having come back favourably, Colorado grants a 90-calendar-day window conditioned on the person's own criminal check already being completed, and Massachusetts allows it uncapped for as long as a cleared colleague is supervising. We cover each in that state's own page rather than collapsing them into a rule of thumb that is wrong in two of the three.

What our software does with this, stated beside the rule. We record the SLED and FBI reviews as staff credential requirements and tell you when a record is missing or expiring. We do not compute the 14-business-day window: that is a deadline measured from another credential's result date, and a credential-to-credential deadline is a relationship our model does not calculate. We also do not evaluate supervision status, so the "before unsupervised access" distinction on the FBI row is recorded as the rule's shape and is not enforced as a live condition. The 14 days are your calendar, not ours.

Do South Carolina fingerprints have to be repeated?

This is the most-searched question on the topic and it has a two-part answer, because South Carolina's answer and the applicable answer are not the same.

South Carolina's own text says no. R.114-503.K.(2)(d): the reviews "are not required to be repeated as long as the person remains employed by or continues providing teacher/caregiver services" (SC credentials rule set, verified against primary text 2026-10-02).

Federal law says every five years. 45 CFR 98.43(d)(2)(ii) (FEDERAL credentials rule set, verified against primary text 2026-10-01) requires a background re-check not less than once during each five-year period, and 98.43(a) binds "all licensed, regulated, or registered" providers — not only those taking subsidy dollars.

So the effective interval on a South Carolina fingerprint review is 60 months, set by federal law, because South Carolina states no interval of its own. We apply the stricter of state and federal at evaluation time, and None — "never expires" — is the least strict value the field can hold, so a real federal number beats it. Every requirement our engine produces names which jurisdiction's text produced its number; for these rows it says FEDERAL.

This is not us second-guessing South Carolina. K.(2)(d) tells you the state will not make you repeat the review; it does not tell you no other authority will.

The re-check trigger South Carolina does state, and the one answer we always give

K.(2)(d) has a second sentence, and it is the single most important thing on this page about what our product will and will not do for you:

however, if a person has a break in service of one year or longer, the fingerprint reviews shall be repeated

Both reviews — the text says "the fingerprint reviews," plural, covering K.(2)(a) and K.(2)(b).

We evaluate this clause, and we resolve it the same way every time: no re-check required. That sentence needs unpacking, because "we evaluate it" sounds better than the situation is.

The anchor is genuinely in our model. Both South Carolina fingerprint rows carry a break-in-service threshold of twelve months, matching the rule's "one year or longer," and when a qualifying break is on record against a person the engine marks both reviews expired rather than valid indefinitely. It is scoped the way the clause is, too: a gap that opened before a review was issued does not invalidate that review, because the review happened while the person was there. The rule's shape is modelled, not approximated away.

What is missing is the input. Nothing in our product records a break in service — there is no screen, no field and no import where you tell us somebody left and came back. So the list of breaks the engine checks against is empty for every person, and the clause resolves to "no qualifying break" on every record: identically for the employee who never left and the employee who was gone for two years.

The consequence for you is the same one it always was. A rehired South Carolina employee with a year-or-longer gap reads clean on our screen when the state requires new prints. That check is on your onboarding process. Our screen will not raise it.

We state it as a leniency rather than as "we don't model it," because those are different claims and the difference is load-bearing in both directions. An unmodelled rule is one we would have to design for. This one is designed for and unfed — one data-entry surface away — which is closer to working and, until that surface exists, more misleading on screen, because a row that reads valid gives you no hint that the question was asked and waved through. The leniency runs one way, in the credential holder's favour, on every record.

It is not quite North Carolina's shape, either, though the two get compared. North Carolina's vacancy-based re-arm (10A NCAC 09 .1102(e)) we do not model at all. South Carolina's is built and starved. Neither will warn you, and we would rather you heard why they fail differently from us than work it out from a screen that looks settled.

The Central Registry check, and the anchor we cannot express

South Carolina also requires a Central Registry of Child Abuse and Neglect check. K.(1)(b) sets two triggers, and we model only the second (SC credentials rule set, verified against primary text 2026-10-02):

Trigger	Clause	Modelled?
Director(s) plus at least two staff persons, "prior to the initial issuance of a regular or provisional license/approval"	R.114-503.K.(1)(b)(i)	No
Director(s) and staff, including the emergency person, "prior to employment and at renewal times, if the employee was hired more than 6 months prior to the renewal date"	R.114-503.K.(1)(b)(ii)	Yes — the pre-employment gate

Two disclosures belong right here rather than at the bottom of the page.

The initial-licensure trigger is not modelled at all. K.(1)(b)(i) is a one-time, role- and count-scoped event tied to a centre's first licence. Our Central Registry row seeds only the ongoing (ii) check, which means a brand-new South Carolina centre reads clean on that row when it should not. If you are opening, that check is yours to run and evidence.

"At renewal times" is an anchor we have no term for. The renewal date in K.(1)(b)(ii) is your centre's own licence cycle, not a fixed number of months from anything in the employee's record. Our model cannot express it, so the row carries no interval and reads as a one-time check rather than a wrong recurring one. Federal law then supplies the only recurring clock on this row too — 60 months, 45 CFR 98.43(d)(2)(ii).

South Carolina is the one state where the federal floor does most of the work

Across the five states we model, the federal five-year re-check mostly changes nothing, because most states already meet or beat it under their own authority. South Carolina is the exception, and it is worth understanding why before you read any vendor's "federal five-year rule" copy.

South Carolina record	State interval	Effective interval	Set by
SLED state fingerprint review	none stated	60 months	Federal — 45 CFR 98.43(d)(2)(ii)
FBI fingerprint review	none stated	60 months	Federal — 45 CFR 98.43(d)(2)(ii)
Central Registry check	none stated	60 months	Federal — 45 CFR 98.43(d)(2)(ii)
National Sex Offender Registry (NSOR) search	absent from South Carolina's text	60 months	Federal — 45 CFR 98.43(b)(2), (d)(2)(ii)

That last row is the only one of its kind in our entire rule library. For every other state, the federal floor can tighten an interval a state already states; South Carolina is the only state where it adds a record the state's own text does not require at all. 45 CFR 98.43(b)(2) names an NSOR search as a component of the required check, and R.114-503 does not. We add it.

We are precise about how that addition is authorised, because "the federal set has a row your state doesn't, so we'll add it" would fabricate a gap in three other states. Georgia bundles its checks under a single Comprehensive Records Check and Massachusetts under a single Background Record Check; both already cover the same ground under a name the federal set does not share, and adding rows to them by name-mismatch alone would invent findings. The South Carolina NSOR row is added from a primary-source finding that South Carolina's text is genuinely silent on it — a specific, per-state, per-record entry in our code, never a generic fallback.

Scope limit, stated plainly: only the four background-check components at 45 CFR 98.43(b) are modelled in our federal rule set. The rest of 45 CFR Part 98 is not, and nothing on this page is a general federal compliance claim.

Why none of South Carolina's intervals could have been miscited

A short note on method, because it is the reason you should trust a citation on this page more than one on our Colorado page.

A state usually states a requirement in one subsection and a renewal interval in a different one. Pairing an interval with the requirement's citation attributes a number to a clause that does not contain it — and a reader who clicks through finds no interval and reasonably concludes the vendor made it up. We have caught that defect three times in our own rule data, in Colorado twice and in Georgia once, and it is the reason our extraction process now carries requirement clause and renewal clause as separate fields for every jurisdiction.

South Carolina is the one state that defect cannot reach. Almost every row here has no state interval at all, so there is no number available to misattribute. The one row that does have an interval states it in the same subsection as the requirement, and we verified that directly rather than inferring it:

R.114-505.G.(1)(b) — "A new health assessment shall be obtained by the director and staff at least every four years after the initial assessment."

Same subsection, requirement and interval together, quoted from primary text.

The rest of what South Carolina requires of the people in your rooms

Background checks are the gate directors ask about. These are the other staff credential rules we model for South Carolina (SC credentials rule set, verified against primary text 2026-10-02):

Requirement	Shape	Clause
New staff orientation	Provided by the director "prior to their employment," for all new staff, volunteers and emergency persons	R.114-503.K.(5)(a)
Pediatric first aid and CPR	Coverage duty — at least one certified person present in the centre at all times children are in care, and during group outings or field trips	R.114-503.K.(5)(h)
Health assessment	Within three months before employment or within the first month of employment; renewed at least every four years	R.114-505.G.(1)(b)
Tuberculosis clearance	Written evidence from a physician or health resource that a new employee is free from communicable tuberculosis, before working with children	R.114-505.G.(1)(c)

Three shape notes that change how you roster and file against these.

The first aid/CPR duty is one combined certification, and it travels. K.(5)(h) asks for "at least one person who is certified in pediatric first aid, including rescue breathing, CPR, and management of a blocked airway" — a single certification covering all of it, unlike Georgia, which requires one person holding two separate cards. South Carolina's duty is also campus-wide rather than per-classroom, and the clause extends it explicitly to group outings and field trips: a trip that takes your only certified person off-site leaves the centre uncovered and does not cover the trip if that person stays behind.

Two provisions in that same rule are recommendations, not duties, and we did not seed them as duties. K.(5)(h) also addresses infant and toddler classrooms and mealtimes in recommending language. We model the required coverage and left the recommended provisions out. Scoring a centre against a recommendation would produce findings the state would not.

South Carolina sets no renewal interval on the first aid/CPR certification. Our row therefore carries none. Your certificate's own printed expiry governs. We will not put a 24-month figure in South Carolina's mouth because that is the common term printed on cards — a vendor default presented as a state requirement is the error this library exists not to make.

The health assessment's window is wider than our field. The rule allows the assessment within three months before employment or within the first month after. Our model carries it as "within 30 days of hire," which captures the post-hire deadline and not the pre-hire allowance. An assessment done two months before a start date satisfies South Carolina and will not confuse our screen, but the field is narrower than the rule, and you should know which one you are looking at.

What this page does not cover

A reference page with no stated gaps is marketing. These are the limits of what is above.

• The break-in-service fingerprint re-check is evaluated, and always answers "no re-check required." K.(2)(d), described above. The twelve-month anchor is in our model and nothing records a break in service, so the clause grants relief on every record whether a break happened or not. Yours to track, and the most consequential limit on this page — the one place where a row reading valid means a question was asked and waved through rather than not asked.
• The 14-business-day FBI window is not computed. It is a deadline from another credential's result date, and that relationship is not one our model calculates. We state the rule; we do not schedule from it.
• K.(1)(b)(i)'s initial-licensure Central Registry check is not modelled. A new centre reads clean on that row.
• "At renewal times" is not expressible. The licence-cycle anchor in K.(1)(b)(ii) has no equivalent in our model, so that row carries no state interval.
• Supervision status is not evaluated. South Carolina's FBI review gates unsupervised access. We record that as the rule's shape; we do not know who is supervising whom at 3pm, and we do not claim to.
• None of South Carolina's background checks is evaluated as a live presence gate. In states that issue a formal eligibility determination — Colorado and Massachusetts — our engine bars an uncleared adult from a caregiving role at the moment of evaluation. South Carolina's records are modelled as record requirements rather than determination-tracked presence gates, so they surface as held, missing, or expiring, and not as a room-level block.
• The determination we can hold is eligible or ineligible, and that is all. 45 CFR 98.43(e)(2)(i) limits what a provider receives to that binary. We have no field for a disqualifying offence, deliberately, so do not expect a record to explain itself.
• South Carolina's annual training hours are a different rule family and are not claimed here. South Carolina's training-hour requirement — with its director/caregiver split, its category breadth test and its capped carryover — is an accumulating ledger rather than a credential with an expiry, and it is versioned separately from South Carolina's credential rules. This page states nothing about that rule set, including its verification status and any finding open against it — both are stated per family on South Carolina, read from the rule set itself rather than restated here.
• This is the credentials rule family only. South Carolina's ratio rules are verified separately from its credential rules, and this page makes no claim about them. Which rule families have been verified against primary text, and when, is stated per family on each state's page in the state reference library, read from the rule sets themselves rather than tallied here. Check South Carolina before relying on a South Carolina claim from any other family.
• 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.

How to check us

Every South Carolina clause on this page was read from scstatehouse.gov/coderegs/Chapter%20114.pdf — the South Carolina Legislature's own host for the Code of State Regulations. That host carries the full chapter text with its South Carolina State Register amendment history inline, and we confirmed it is primary rather than a mirror before relying on it. Both rules cited here live in that chapter: R.114-503 (Staffing) and R.114-505 (Staff health).

One citation correction worth naming, since it is the kind of thing you may find in older material including some of our own. The 14-business-day FBI deadline is at K.(2)(b), in Subsection K, Staffing. R.114-503's subsections run A through K, and J is Communication, not Staffing — a J(2)(d) cite for this rule, which we carried in two places and have fixed, points at the wrong subsection entirely. If you are comparing us against a document that cites J, the document is wrong.

For the federal clauses: 45 CFR 98.43 via Cornell LII, with the effective date confirmed against the Federal Register as published (81 FR 67438).

Start with South Carolina for the full per-family picture, including which of South Carolina's rule families have been verified against primary text and which have not. The companion piece how often background checks must be renewed covers how the federal five-year floor interacts with all five states we model — South Carolina is the state it changes most.