My fiancé told my cousin he could propose at our reception before asking me

My cousin asked for seven minutes during our wedding reception.

He needs them to propose to his girlfriend.

I learned about this after my fiancé had already said yes.

My cousin Ryan called him because he wanted the proposal to be a surprise from my side of the family. His plan is to catch the bouquet, make a short speech about love and then invite his girlfriend onto the dance floor.

There are several problems with this plan, including the fact that he is not eligible to catch a bouquet I am not throwing.

My fiancé apparently focused on the emotional part. He likes Ryan, likes Ryan’s girlfriend and thought it would be generous to share the moment. He told Ryan, “That sounds great. Let me check the timing.”

Ryan heard yes.

When my fiancé told me, he was smiling. I thought he was joking.

I do not want a proposal at our reception.

I know how that sentence can sound. We will have hours of attention, photographs, speeches and a cake with our names near it. Seven minutes devoted to someone else would not erase our marriage.

The issue is not a fear that another couple will steal the spotlight. It is that the proposal would change the emotional responsibility in the room.

What if she does not want a public proposal? What if she hesitates? What if she says yes because 120 people are watching and feels differently later? Our reception would become the location of an intensely private decision we helped stage.

Ryan insists she would love it. He says she has shown him videos of wedding proposals and joked that he should learn from them.

Maybe she would be thrilled.

I still do not want to spend dinner waiting to see whether my cousin has correctly interpreted a joke.

There is also a family dynamic. Ryan’s mother, my aunt, already knows. She has told my mother, who cried and called it “a beautiful continuation of the day.” My mother then asked whether the photographer could stay near the dance floor to capture it.

The idea is becoming part of the schedule without passing through me.

When I told my fiancé I wanted to say no, he apologized immediately. He said he should have answered, “We’ll discuss it,” instead of sounding enthusiastic. He is willing to call Ryan and take responsibility.

I appreciate that. I also know my cousin will understand that the real objection is mine.

Ryan has already bought the ring. That fact keeps being presented as urgency, although it has nothing to do with our reception. The ring will remain functional on another day.

My aunt says proposing with the whole family present is meaningful because relatives live across several states and may not gather again soon. That is the strongest argument. Their grandparents would witness it. His girlfriend’s parents will also be guests.

I can understand why the room feels valuable to him.

It was still assembled for a different commitment.

I offered a compromise: he could propose privately the morning after the wedding and invite family to a casual breakfast afterward. He says the surprise would be weaker because his girlfriend will suspect something once the wedding is over.

He suggested proposing after our official exit, when the reception is effectively ending. That sounds better in theory, but many guests will have left, the venue staff will be clearing and our photographer’s contracted time will be over. It also still requires our wedding to become the setup.

My fiancé now thinks we should simply say no without proposing alternatives. He says every compromise keeps us involved in planning somebody else’s engagement.

He is right. I am offering alternatives because I want Ryan to agree that my boundary is generous.

He may not.

Would you allow the proposal after the final dance, offer a separate family moment that weekend or decline completely? Is saying no possessive, or is a wedding one of the few events where the hosts are allowed to refuse a second major milestone without defending the decision?