Loading...
compliance

Lead Risk-Assessment Questionnaire and Provider Statement (Childcare)

This childcare lead risk-assessment questionnaire and provider statement collects lead-testing status, exposure risks, and follow-up actions for children under 6. Use it to document what was reviewed, what needs attention, and what the provider is authorizing.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Childcare Centers · Family Childcare Homes · Early Childhood Education · Head Start Programs

Overview

This template is a childcare health form for documenting lead-testing status, known exposure risks, and any follow-up actions for children under 6. It combines a short child-identification section, consent and disclosure language, lead-test fields, exposure-factor questions, and a provider statement so staff can keep one record instead of piecing together emails, notes, and separate attachments.

Use it when your program needs a clear, repeatable way to ask whether a child has been tested for lead, whether results are available, and whether any exposure sources or mitigation steps should be recorded. The conditional logic should keep the form short when there is no known exposure and expand only when follow-up is needed. That makes it easier for families to complete and easier for staff to review.

Do not use this template as a general medical intake form or to collect unrelated health history. It is not meant for broad diagnosis, treatment planning, or open-ended clinical notes. Keep the data minimized to what the childcare program actually needs, and avoid collecting unnecessary PII. The form works best when a provider statement is required only when your policy or local process calls for it, and when the submission flow clearly explains what happens after the form is sent.

Standards & compliance context

  • Because this form collects health-related information about a child, it should use consent and disclosure language that explains the purpose, storage, and sharing of the data.
  • Apply data minimization by collecting only the fields needed to document lead-testing status, exposure risk, and follow-up actions.
  • Use accessible labels, logical field order, and keyboard-friendly controls to support WCAG 2.1 AA expectations for public-facing forms.
  • If the form is used in a regulated childcare workflow, keep an audit trail of submission, review, and any follow-up action taken.
  • If provider authorization is required, make the authorization field explicit and avoid implying clinical approval where none has been given.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission and Child Identification

This section ties the record to the correct child and classroom while keeping identification fields limited to what the program actually needs.

  • Submission Date (required)
  • Child Initials (required)
  • Child Date of Birth (required)
  • Program or Classroom
  • Primary Contact Email

Consent and Disclosure

This section explains why health information is being collected and captures the family’s acknowledgment before any sensitive data is submitted.

  • I consent to the collection and review of this child's lead-testing and risk-assessment information for childcare compliance and follow-up purposes. (required)
  • I understand this information will be used only for lead-risk assessment, required follow-up, and audit trail purposes. (required)
  • I am authorized to provide this statement on behalf of the child, family, or program. (required)
  • Who is completing this form? (required)

Lead-Testing Status

This section records whether the child has been tested, when the test occurred, and what documentation supports the result.

  • Has the child been tested for lead? (required)
  • Date of Most Recent Lead Test
  • Lead Test Result
  • Upload test documentation

    Optional supporting document such as a lab report or provider letter.

Risk Assessment and Exposure Factors

This section captures known exposure concerns and uses branching fields to collect only the details that apply.

  • Is there any known or suspected lead exposure risk? (required)
  • Possible exposure sources
  • Describe the exposure concern

    Briefly describe only what is needed for follow-up.

  • Actions already taken to reduce exposure

Follow-Up and Provider Statement

This section documents next steps and the provider’s review so the childcare file shows what action is expected and who authorized it.

  • Is follow-up needed? (required)
  • Recommended follow-up actions
  • Provider statement

    Summarize the child’s lead-testing status, risk assessment, and any required next steps.

  • Provider Name

Acknowledgment and Submission

This section confirms the information is accurate, signed, and ready to enter the program’s recordkeeping workflow.

  • I confirm the information provided is accurate to the best of my knowledge. (required)
  • Signature (required)
  • Signature Date (required)

How to use this template

  1. 1. Set the child-identification fields to collect only the minimum needed for matching the record, using date pickers for dates and a short text field for initials.
  2. 2. Configure consent and disclosure text so families understand what health information is being collected, why it is needed, and who will review it.
  3. 3. Add conditional logic to show lead-testing, exposure, and follow-up fields only when the child has been tested, has known exposure, or needs provider review.
  4. 4. Assign the form to the appropriate staff member or provider workflow so the submission is reviewed, documented, and stored with an audit trail.
  5. 5. Review the completed record for missing validation, confirm the provider statement when required, and route any follow-up actions to the correct classroom or family contact.

Best practices

  • Mark required fields clearly and keep optional fields optional so families do not abandon the form.
  • Use a date picker for submission date, child date of birth, and test date instead of free text.
  • Keep exposure questions specific by offering a multi-select list of common sources and a short follow-up detail field only when needed.
  • Use progressive disclosure so families with no known exposure do not see unnecessary clinical or follow-up questions.
  • Include a plain-language line explaining what happens after submission, including who reviews the form and how follow-up is communicated.
  • Collect only the minimum necessary health information and avoid asking for unrelated identifiers or broad medical history.
  • Make the signature and provider authorization steps accessible and easy to complete on mobile devices.

What this template typically catches

Issues teams running this template most often surface in practice:

The child date of birth is entered in free text and later needs manual correction.
The lead-test result is described in a paragraph instead of a structured field.
Exposure sources are left blank because the form does not guide users with examples or conditional prompts.
Follow-up actions are not captured, leaving staff without a clear next step.
Consent is implied instead of being explicitly acknowledged before health information is submitted.
The provider statement is completed by the wrong person or without a clear authorization field.
Too many required fields make the form harder to finish and increase incomplete submissions.

Common use cases

Childcare Center Enrollment Coordinator
A center uses this form during enrollment to document whether a child under 6 has been lead-tested and whether any exposure concerns need follow-up. The coordinator can route the record to the right classroom and keep the file consistent across families.
Pediatric Provider Follow-Up Packet
A provider office completes the statement section after reviewing a child’s lead status and exposure history. The form gives the childcare program a structured record of the provider’s guidance and any recommended next steps.
Head Start Health Intake Team
A Head Start program uses the template to standardize health intake across sites while minimizing the data collected. Conditional logic keeps the form short unless testing gaps or exposure risks require follow-up.
Family Childcare Home Owner
A home-based provider uses the questionnaire to document health information without relying on informal email threads. The form creates a clear record of consent, submission date, and any actions the family must complete.

Frequently asked questions

Who should use this childcare lead risk-assessment questionnaire?

Use this template for children under 6 when a childcare program needs to document lead-testing status, known exposure risks, and a provider statement. It is especially useful for enrollment, annual health updates, or when a child has a known exposure concern. If your program does not collect health-related information, this form is not the right fit.

When should this form be completed?

Complete it at enrollment, when a child transfers into a new classroom, after a reported exposure, or when a provider requests follow-up documentation. Many programs also use it on a recurring basis tied to health record updates. The key is to capture the current status, not rely on old paperwork.

Who should fill out the provider statement section?

The provider statement should be completed by the licensed clinician, pediatric provider, or other authorized health professional identified by your program policy. The childcare staff member should not guess or paraphrase clinical findings. If a provider signature is required, make that field explicit and keep the wording aligned with your local documentation rules.

What information should be collected, and what should be left out?

Collect only the minimum necessary details needed to document lead-testing status, exposure sources, and follow-up actions. Use conditional logic so you do not show every field when a child has no known exposure or no follow-up is needed. Avoid collecting unrelated PII or extra health history that is not needed for the stated purpose.

How does this template support compliance and privacy?

Because it collects health-related information about a child, the form should include clear consent and disclosure language, a plain explanation of how the data will be used, and a submission confirmation line. It should also support accessibility with clear labels, required-versus-optional fields, and keyboard-friendly controls. If your workflow stores records, keep an audit trail of who submitted and reviewed the form.

What are the most common mistakes when using this form?

The biggest mistakes are making every field required, using free-text fields for dates or test results, and asking for more detail than the program actually needs. Another common issue is skipping the follow-up section when a test is positive or exposure is known. The form should guide the user through branching questions so only relevant fields appear.

Can this template be customized for different childcare settings?

Yes. You can adapt the classroom field, provider authorization wording, and follow-up actions for centers, family childcare homes, or Head Start-style intake workflows. Keep the core structure intact so the form still documents testing status, exposure risk, and provider review in a consistent way.

How does this compare with collecting lead information by email or paper notes?

A structured form is easier to review, easier to store, and less likely to miss a required follow-up field than ad-hoc emails or handwritten notes. It also creates a cleaner audit trail and makes it simpler to route the record to the right staff member. For recurring intake, a template reduces back-and-forth and improves consistency.

Go deeper on the topic

Related concepts
  • Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
  • Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
  • A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
  • AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
Related guides

Ready to use this template?

Get started with MangoApps and use Lead Risk-Assessment Questionnaire and Provider Statement (Childcare) with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?