A birth plan is a short note about what a parent hopes for. Many people write it late, on paper, and nobody reads it. I would rather send one link in the weeks before the due date, so the answers are ready when the team needs them.
About you and the day
Name, due date, planned setting and support people. The team needs to know who to expect and where.
About labor and birth
Comfort, pain relief, cord clamping and skin to skin contact. These are the choices people feel strongly about, so they sit in the middle of the form.
About your baby
Feeding, newborn care and what matters if plans change. The last open answer gives everyone a calm way to talk if the day goes another way.
Who fills it and who reads it
The parent-to-be fills it in, alone or with a partner. A midwife, doula or clinic reads the rows. Browse more forms for clinics.
A parent's AI might ask "Where do you plan to give birth?" Then "Who will be with you?" Then "How do you plan to feed your baby?" It shows all answers and sends only after a yes. See agent-fillable forms.
One tip
Send it early and close it on the due date. Check your local privacy rules before collecting health data. This is a form, not medical advice. A shift handover form helps staff pass the plan on, and a patient referral form fits when another provider needs it.
Questions
Does the care team have to follow every answer?
No. The form only collects the parent's wishes and gives no medical advice. Read the rows as JSON or CSV, then talk them through with the parent well before the due date.
Can a partner fill it in for the parent?
Yes. Anyone with the public link can answer. A partner can also hand the form to their own AI agent, which asks for what is missing and shows every answer before anything is sent.
What if the parent changes their mind later?
Ask them to submit the form again and read the newest response. Set close_at to the due date if you want the plan to stop changing from that day.