Parent-conference cadence: what Massachusetts and North Carolina actually require, and what the other three states don't

The question is not "do I have to hold a parent conference"

It is "by when, for which child, and what counts as having done it" — and the five states this platform models answer in four different ways. Two require a conference on a schedule. Two require nothing at this scope at all. One requires you to keep a record of the conferences you hold without ever telling you to hold one.

That spread is the reason a director who operates in two states cannot run this obligation off a single calendar reminder, and the reason a vendor who answers it with one number has told you something false about at least three of the five.

What follows is each clause, with the citation it comes from, and — stated as plainly as the requirements themselves — the two obligations on this page that our own engine does not evaluate.

Massachusetts: one cadence, two duties, three age bands

606 CMR 7.06(3) is doing more work than it looks like. It states two separate duties in two separate sentences, and then states the frequency once, governing both:

"A written progress report must be prepared periodically on the progress of each child in the program." … "The program must offer parents a conference to discuss the content of the report."

The cadence, from the same clause:

The child	A report prepared, and a conference offered, every
Infants	3 months
Children with identified special needs	3 months
Toddlers and preschoolers	6 months
School age	At least annually, at the midpoint of the child's program year

Read the second row carefully, because it is the one that breaks a calendar built on ages. The three-month cadence for a child with identified special needs applies regardless of the child's age. A four-year-old in that sub-population is on the infant cadence, not the preschool one. Our engine checks that condition before it looks at age at all, so a flagged child cannot fall through into a six-month band.

Where that flag is not set, the child is scored on the ordinary age band. We are being deliberate rather than quiet about that: an unrecorded condition resolves to "not flagged," which is the same treatment this platform gives a credential nobody has verified yet. It is not a reading of the regulation — it is what we do with a field that is blank, and it means the cadence is only as right as the record is complete.

606 CMR 7.08(7) is not a second cadence. It is a separate, on-request duty: "The licensee must make educators available for individual conferences with parents at parental request." A parent who asks gets a conference, whenever they ask. That obligation has no schedule, so nothing on a schedule can evidence it, and we do not represent it as part of the cadence above.

North Carolina: a rule that is barely a year old, and two items of six it never quantifies

10A NCAC 09 .3219 ("Family and Community Engagement Standards for Child Care Centers") is a new rule, effective July 1, 2025. If your parent-conference policy predates that date, it was written against text that did not exist yet. The section was not in the 2022 edition at all.

What it requires now:

• .3219(b)(2) — every two-star-or-higher centre's administrator must "offer an annual family conference with teaching staff … to set a goal(s) for their child."
• .3219(f)(1)(C) — at three-star-or-higher, that tightens to "at least twice annually."
• .3010 — independently of any of the above, every classroom run as an NC Pre-K program owes a written family-engagement plan with six items, none of them tiered by the centre's star rating. Four are quantified: a family-teacher conference at least twice annually (item 2), an enrollment orientation that includes a classroom visit before the child's first day (item 1), at least one annual family event with an educational component (item 4), and at least two annual family events overall (item 6). Two are not: classroom visits and participation opportunities for families (item 3), and family involvement in decisions about their own child and the program (item 5) — stated as plan language, with no frequency, count, or interval attached to either.
• .3219(g) — a bookkeeping rule, not a third obligation: a centre doing .3010's conference item for its Pre-K classroom may count that same activity toward its own star-tier requirement under .3219, rather than running the conference twice. It does not change what either rule requires on its own.

The star-tier duty is tiered by a centre's star rating, and ours is a real field: an admin records a location's rating and a second admin verifies it, the same two-person discipline a staff credential needs before it counts for anything on this platform. An unverified rating reads identically to no rating at all. A verified two-star-or-higher rating owes the annual conference; a verified three-star-or-higher rating tightens to twice annually; a verified rating below two stars (North Carolina's own "UNRATED" or "1") owes nothing under .3219 at all — the obligation genuinely does not attach, not even at a reduced tier. A location with no verified rating on file is still scored at the strictest figure, twice annually, because an unconfirmed value counts for nothing, not because we assume the worst about an unrated centre.

.3010's four quantified items are evaluated too, against a classroom's own verified designation rather than the centre's star rating. An admin marks a classroom as NC Pre-K and a second admin verifies it — again, never a self-report — and a verified designation triggers the twice-annual conference unconditionally, plus the orientation deadline and the two event quotas, regardless of what the centre's star rating is or whether .3219 reaches it at all. That closes the case this page used to disclose as a gap: a verified sub-two-star centre running an NC Pre-K classroom now owes and is scored on all four items, not quietly missed because .3219 never reached it.

What we still do not evaluate is items 3 and 5 — and the reason is different from every other disclosure on this page. It is not a missing field or an unbuilt model; it is that neither clause, in any version of the text we have read, states a frequency, a count, or an interval of any kind for a record to be checked against. "Classroom visits and options for parents… to participate" and "the opportunity for involvement in decision making" are real duties with no quantity attached to either, the same shape as two of Massachusetts' own facility-certificate clauses on this platform. No future engineering closes that; only a future primary-source read finding language this one missed would.

That direction — evaluate what has a value to check, disclose what has none — is not an accident and it is not a preference. It is the same choice this platform makes everywhere a duty cannot be evaluated: decline the relief, score stricter, disclose. The alternative is scoring the cheaper tier, or no obligation at all, on a predicate nobody checked — which produces a centre that passes our screen and fails the visit. Over-claiming an obligation costs you a conference you did not owe. Under-claiming one costs you the finding.

The other three states, and why this is a two-state page

This page names two states in its headline on purpose. The other three were read, not skipped, and what the reads found is worth more to a multi-state director than a fifth row would be.

• Georgia requires no parent conference. Confirmed by full-document search of all 46 rules — not by absence of a search. The only adjacent text is 591-1-1-.21(2), which requires the Center to document that it "advised the Parent(s) of the child's progress, issues relating to the child's care… and encouraged participation by Parent(s) in Center activities" — a one-time documentation duty attached to enrollment paperwork, not a conference and not a cadence. 591-1-1-.22 ("Parental Access") governs physical access to the building. No word for a recurring parent meeting appears anywhere in the chapter.
• South Carolina requires no parent conference. Confirmed by full-section search of R.114-500 through R.114-509. Every occurrence of "conference" in the centre sections is either staff training or workshop attendance (R.114-501(38)) or an unrelated administrative-hearing proceeding (R.114-130, R.114-180). None is a parent conference.
• Colorado requires the record, not the schedule. 8 CCR 1402-1 2.209(B)(2) requires the centre to maintain "observations of the child's development to document the child's progress and challenges to be discussed at parent conferences," and 2.209(B)(3) requires "a record of parent conferences, including dates of conferences, and names of center staff and parent(s)/guardian(s) involved." Both clauses assume conferences happen and must be documented when they do. Neither states how often one is required. That is a reactive record-keeping duty, and reading a cadence into it would be inventing one.

Two of those three are absence claims, which is the one kind of statement on a compliance page that nothing downstream ever contradicts — so each is stated at the scope of the search that found it, and the search is named. Georgia's is stated at chapter scope because the pass read the whole chapter. South Carolina's is stated at the scope of the centre sections, R.114-500 through R.114-509, because that is what was read. We will not widen either sentence to "this state requires nothing" on a pass that did not read the state.

What counts as having done it: an offer, not an attendance record

Both states that state this duty phrase it as an offer. Massachusetts: "must offer parents a conference." North Carolina: "offer an annual family conference." Neither requires the conference to be held.

Our engine follows the text. A conference offer carries an outcome, and a declined offer satisfies the rule exactly as a held one does. This matters more than it sounds: a centre that offers four conferences and has four parents decline is compliant, and any product that scored that centre as non-compliant would be marking it down for something its state never asked.

Three further behaviours, so the screen is not a black box:

• The gap is the violation. The engine returns the windows in which no offer was recorded — not a count, not a percentage. A missing window names itself.
• The current window is never a finding. An unfinished period with no offer yet is a plan, not a breach. Only closed windows can be holes.
• It is scored per child, not per room. Massachusetts' cadence depends on the individual child's age and sub-population, so a room-level answer would be wrong for most of the room.

What we do not evaluate

Stated here, in the body, with the clause each one comes from — because an article that chooses this subject is implicitly claiming to have covered it, and that claim is only honest if its gaps are on the page rather than in a footer.

• North Carolina's .3010 items 3 and 5 — classroom visits/participation and decision-making involvement. The two-star / three-star tier is evaluated against a verified star rating, and .3010's other four items (the conference, the orientation, and the two event quotas) are evaluated against a verified NC Pre-K classroom designation, independent of star rating. Items 3 and 5 are the two this screen does not reach, and the reason is the text itself: neither clause states a frequency, a count, or an interval of any kind, in any version we have read. That is not a field we have not built — it is primary text that gives this engine nothing to evaluate against, and no future build changes that. If a future primary-source read finds language this one missed, this page updates; until then, both items are disclosed, not scored.
• Massachusetts' written progress report (606 CMR 7.06(3)). 7.06(3) states two duties on one cadence — prepare a written report, and offer a conference to discuss it. We evaluate only the conference offer. Nothing in this platform models a progress-report artifact at all, so nothing in the product will tell you a report is missing, and a centre at full marks on our parent-conference section may still be short the report half of the same clause. The content of such a report is a written assessment of a child, which needs a privacy ruling before a field for it exists; that is deferred work, not an oversight, and this is the sentence that keeps the section from overclaiming while it is deferred.
• Whether you held the conference you offered, well. We record that an offer was made and what came of it. Nothing here evaluates what was discussed, and no part of this page should be read as saying we assess the quality of family engagement.

The boundary on all of it

We are at a pilot, disclosed stage, and nothing on this page moves that line. What this page does is state what 606 CMR 7.06(3) and 10A NCAC 09 .3219 require, with the clause each figure comes from, and name the two obligations inside that same subject we do not evaluate.

What it does not do — what we will not write — is tell you that your centre is compliant. Our inspection packet is hard-wired never to report a pass: its own summary states complete: false regardless of what is on file, because a packet with no gaps is not compliance. A licensing visit assesses your centre, and 45 CFR 98.42(b)(2)(i)(B) makes that visit unannounced.

How to check us

Massachusetts' clause was read from primary text and re-read on 2026-10-09, from Cornell's 606 CMR 7.06 text at law.cornell.edu/regulations/massachusetts/606-CMR-7-06, confirming that the progress-report and conference-offer sentences are two sentences rather than one clause with an echo. The NC parent-conferences rule set was verified against primary text 2026-10-17: .3219(b)(2) and (f)(1)(C) were quoted verbatim from Chapter_9_Child_Care_Rules_Effective_July_1_2025.pdf on ncchildcare.ncdhhs.gov on 2026-10-03. That same compiled rulebook still carried .3010's pre-amendment text as of that printing — its amendment cleared the Rules Review Commission only on June 26, 2025 and, one wording fix behind .3219, did not take effect until August 1, 2025 at the earliest, a month the July-dated compilation predates for that one rule. Re-read 2026-10-17 from oah.nc.gov's own pre-approval redline of the amendment (Commission Counsel's "Request for Changes," .3010, submitted to the agency June 10, 2025) — the rule as approved, not a notice of what was proposed — and independently confirmed against the Child Care Commission's own notice-of-rulemaking text the same day, finding .3010 carries its own unconditional cadence rather than merely cross-referencing .3219, and that it states no interval at all for two of its six items (3 and 5). The rule set's four active NC rows span two original research dates (2026-10-03 and 2026-10-17); their verified_on column is reconciled to the later date, 2026-10-17, because this page states one tier for the whole family rather than one per row, and nothing here is re-read a second time by that reconciliation. Georgia's, South Carolina's and Colorado's findings come from the separate 2026-10-06 pass, which is where the two absence searches above are recorded with their scopes.

One note about our own machinery, since this page asks you to check us on everything else. Until last week these cadences lived as constants in our code, with their provenance recorded only in a ledger — which meant that if we had ever corrected one of these numbers, this page would have gone on printing the old one. They are now rows in the same provenance-stamped table every other rule family on this site uses, carrying a status, a date and the note describing the read, and the gate that builds this site fails the build if any date printed above disagrees with its column. We are telling you that the weaker arrangement existed, and when it stopped, rather than letting the page look as though it had always been this way.

Start with North Carolina or Massachusetts for the ratio, credential and training picture alongside this one, or the state reference library for the other states we model. Which rule families have been verified against primary text, and when, is stated per family on each state's page, read from the rule sets themselves — not tallied here, because a count kept in two places is a count that goes stale in one of them.