If some kids are invited, don't call the wedding child-free
WrapSheet blog
I don't mind seeing a couple's nephews at a wedding where most children weren't invited. I would mind arranging a sitter after being told that absolutely no children could come, then learning at the reception that several other parents had been given exceptions.
Couples can choose their guests. Parents would also appreciate knowing what they're agreeing to before they make expensive arrangements.
In a recent weddingplanning thread I read this morning, a bride described exactly that planning problem. She and her fiance had initially wanted a child-free wedding. He now wanted nephews and some wedding-party children there. She worried about how the other families would feel.
Replies disagreed. Some considered those exceptions ordinary; others thought excluded parents might be hurt. Several offered the most useful advice in the thread: name the people invited, and stop calling the event child-free if it isn't.
You can make exceptions. Explain them early.
Immediate-family children are a reasonable exception to me. So are infants, if that's what the couple agrees to. Neither choice obliges you to invite every cousin's teenager. You don't need to defend the entire guest list to everyone who asks.
But “it's our day” doesn't help a guest understand an exception they weren't told about. A parent who paid for overnight care may feel misled even if they would have accepted the actual arrangement.
I'd put each invited person's name on the invitation and use a short website explanation. For example: “We're only able to include the children in our immediate families. Everyone invited is named on your invitation. Please contact us if you're unsure.”
That wording needs to match the list. If you're also including wedding-party children, say so. If there's an infant exception, decide what you mean before answering individual requests. A six-year-old and a newborn raise different practical questions; one vague label won't answer both.
A newborn needs a conversation before the wedding.
An October 15 X story about a relative bringing a newborn to a child-free wedding was still drawing disagreement this morning. One reply said the parent could have stayed home; another called the reaction an overreaction. I can't verify that account, and I'm not interested in deciding a stranger's character from it.
I do agree with the reply suggesting a conversation beforehand. If leaving the baby isn't workable, ask privately whether an exception is possible. Don't turn up hoping nobody will object.
A couple can say no. They can also make an exception after understanding what their guest needs. Either answer belongs in that private conversation, well before anyone is standing outside a ceremony with a car seat.
If a guest does arrive with an uninvited child, I'd ask a trusted person to speak with them quietly. Announcing the disagreement to the room would make an already uncomfortable situation worse. Keep that conversation about the guest list. Feeding a baby shouldn't be treated as bad behavior.
Sometimes the answer will be a declined invitation.
This is the part hosts have to accept. A parent may not be comfortable leaving a newborn, may not have suitable care, or may simply decide the arrangements are too much. They don't owe a detailed defense of that decision.
Nor do they owe a larger wedding gift to apologize for missing it. Send something if you want to and can afford it. A warm message is enough if you can't.
My suggested reply from the couple would be simple: “We'll miss you, but we understand. We'd love to celebrate with you another time.” Then let the RSVP stand. You can be disappointed without asking someone to prove they care by coming anyway.