Lead Risk-Assessment Questionnaire and Provider Statement (Childcare)
Lead Risk-Assessment Questionnaire and Provider Statement (Childcare) is a childcare intake form for documenting lead-testing status, exposure risks, and a provider statement for children under 6. It helps you collect only the details needed to decide on follow-up.
Trusted by frontline teams 15 years of frontline software
Built for: Childcare · Preschool · Early Education
Overview
This template is a childcare intake form for documenting lead-testing status, screening for common exposure risks, and capturing a provider statement for a child under 6. It is built around the information a childcare program actually needs: child initials, guardian contact details, whether the child has been tested, the most recent test date and result, whether documentation is available, and any reason the child has not been tested.
Use it when a childcare center, preschool, or early education program needs a consistent way to review lead risk before enrollment or during periodic updates. The exposure section helps staff identify practical risk factors such as older housing, recent renovation or peeling paint, water concerns, imported products, or hobby-related exposure. The provider statement section gives a clinician or authorized provider a place to summarize findings and recommend follow-up when needed.
Do not use this template as a general medical intake form or for children outside the target age range unless you customize the branching logic and fields. It is also not the right fit if you only need a simple contact form, because the template is designed to support a documented review, consent, and attestation. Keep the form focused: collect only the fields you will use, show optional fields only when relevant, and make the next step after submission clear.
Standards & compliance context
- Collect only the PII needed for the lead-risk decision and provider review to align with GDPR Article 5 data minimization.
- Use explicit pii_consent language before collecting contact details or health-related information.
- If the form is used in a childcare setting, keep the attestation clear so the provider statement is attributable and reviewable.
- Design the form for accessibility with WCAG 2.1 AA in mind, including labeled fields, keyboard navigation, and readable error messages.
- If you adapt the template for health-related intake, apply the minimum-necessary principle and avoid collecting unrelated medical details.
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
Child Information
This section identifies the child and the best guardian contact details so staff can match the record and follow up without collecting unnecessary data.
- Child initials
- Child date of birth
- Parent/guardian name
- Parent/guardian email
- Parent/guardian phone
Lead Testing Status
This section captures whether the child has been tested, when the most recent test occurred, and why testing is missing if it has not been done.
- Is the child under 6 years old?
- Has the child ever been tested for lead?
- Date of most recent lead test
- Most recent lead test result
- Do you have documentation of the test result?
- Reason the child has not been tested
- If other, explain
Lead Exposure Risk Screening
This section narrows the review to practical exposure factors that often matter in childcare intake, using conditional logic to avoid extra questions when they do not apply.
- Was the child's primary home built before 1978, or is the year unknown?
- Is there recent renovation, peeling paint, or visible dust in the home?
- Is there a known concern about lead in drinking water?
- Any known exposure from imported products, pottery, cosmetics, spices, remedies, or hobbies?
- Describe any other known lead exposure risks
Provider Statement
This section records the provider’s review, role, and recommendation so the form has a clear accountable summary instead of an informal note.
- Provider name
- Provider role
-
Provider statement
State whether the child has been tested for lead, summarize the result if known, and note any recommended follow-up or referral.
- Is follow-up recommended?
- Follow-up details
Consent and Submission
This section confirms permission to collect PII and captures the attestation so the submission can be used with a clear record of acknowledgment.
-
Consent to collect and use this information for childcare compliance and follow-up
This form collects limited health-related information and PII only for compliance, record matching, and follow-up. Information will be handled according to applicable privacy and recordkeeping policies.
-
Attestation
I confirm that the information provided is accurate to the best of my knowledge.
How to use this template
- 1. Set the form to require child_under_six first, then use conditional logic to show the lead-testing and exposure sections only when the child is in scope.
- 2. Configure child_date_of_birth as a date picker, guardian contact fields as standard contact inputs, and mark only the fields you truly need as required.
- 3. Ask the guardian to enter testing status, the most recent test date and result, and whether documentation is available, with a clear path for reason_not_tested when no test exists.
- 4. Show the lead exposure risk screening fields only after a lead concern is relevant, and use progressive disclosure for other_exposure_details so the form stays short when no extra context is needed.
- 5. Have the provider complete provider_name, provider_role, provider_statement, and follow_up_recommended, then route follow_up_details to the staff member responsible for next steps.
- 6. Require pii_consent and attestation before submission, then send a confirmation that explains what happens next and where the record will be reviewed.
Best practices
- Use child initials instead of a full name unless your workflow truly needs the full identifier.
- Make most fields optional and reserve required status for the minimum data needed to make the lead-risk decision.
- Use a date picker for most_recent_test_date and a yes/no field for lead_tested rather than free text.
- Hide reason_not_tested_other unless reason_not_tested is set to an option that needs explanation.
- Keep other_exposure_details short and specific so staff can quickly decide whether follow-up is needed.
- State clearly what happens after submission, including who reviews the provider statement and whether the guardian will be contacted.
- Store the submission with an audit trail if the form is used for enrollment decisions or compliance review.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this lead risk-assessment questionnaire?
Use it for childcare enrollment, periodic health intake, or any situation where you need to document a child under 6’s lead-testing status and possible exposure risks. It is especially useful for centers that need a consistent provider statement and follow-up recommendation. If you do not need lead-related screening, use a simpler intake form instead.
Does this template apply only to children under 6?
Yes, the form is structured around children under 6 because that is the age group named in the template. The child_under_six field helps you confirm whether the questionnaire applies before collecting the rest of the data. If the child is older, you can branch away with conditional logic or stop the form.
How often should this form be completed?
Most programs use it at enrollment and again when there is a change in lead-testing status, housing, renovation exposure, or other risk factors. Some providers also re-run it during annual updates or before a new placement. The right cadence depends on your childcare policy and local requirements.
Who should complete the provider statement?
The provider statement should be completed by the clinician, nurse, or other authorized provider who reviewed the child’s lead-testing status and exposure information. The provider_name and provider_role fields make that accountability clear. If a provider is not available, you should not treat the form as complete.
What should be included in the lead-testing documentation?
Capture whether testing was done, the most recent test date, the result, and whether documentation is available. That gives you enough information to verify status without collecting extra PII. If the test was not done, the reason_not_tested field should explain why in plain language.
How does this template support privacy and data minimization?
The form is designed to collect only the fields needed to assess lead risk and record a provider statement, which aligns with GDPR Article 5 data minimization. Use child initials instead of a full name if your workflow allows it, and make the PII consent field explicit. Avoid adding unnecessary identifiers or medical details that are not needed for the decision.
What are the most common mistakes when using this form?
Common mistakes include making every field required, asking for free-text where a date picker or yes/no field is better, and skipping the follow-up recommendation. Another frequent issue is collecting exposure details without using conditional logic, which makes the form longer than necessary. The attestation and consent fields should also be visible before submission.
Can this form be customized for different childcare policies or systems?
Yes, you can adjust the exposure questions, add local policy language, or change the follow-up fields to match your workflow. Many teams also connect the form to an audit trail, case-management system, or secure notification process. Keep the core structure intact so the lead-testing and provider-statement sections remain easy to review.
What should happen after submission?
The form should clearly tell the user whether the submission is complete, whether a provider review is pending, and what follow-up will happen next. If follow_up_recommended is selected, route the record to the appropriate staff member for review. A clear confirmation reduces confusion and helps staff act on the result without re-contacting the family for basics.
Related templates
Go deeper on the topic
-
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...
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
Discover how manual performance review processes drain HR productivity, introduce payroll errors, and stall talent strategy — and what automated systems fix.
-
Fix recruiting pipeline handoffs with a unified candidate portal, branded career pages, and faster offers that keep top talent engaged.
-
MangoApps is now Workday Design Approved, surfacing benefits, pay, learning, and time-off data directly inside the MangoApps platform for frontline workers.
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.
