An example of a wedding agenda

To many ads? Support ODJT and see no ads!
I like my pic, and I'm manly enough to admit it...

and I think you all know this already, because you all seem to know everything "pupus" is what they call appetizers in Hawai'i"
 
I like my pic, and I'm manly enough to admit it...

and I think you all know this already, because you all seem to know everything "pupus" is what they call appetizers in Hawai'i"
So, are you saying that your avatar is your "pupus"?:sqerr:

Now I'm getting really scared.:sqeek:
 
Three more...
 

Attachments

  • Ward.pdf
    134.4 KB · Views: 10
  • DeMassi.pdf
    166.4 KB · Views: 5
  • Nash.pdf
    153.6 KB · Views: 4
Tom I love them but...

did they do the times on the sheet was it done in military style ?

because times is the last thing that is needed to stress out brides (even more)
after you been doing weddings a long time, you know how an order is suppose to be
and get it all done as quickly as possible so they can all dance...

just curious
 
Tom I love them but...

did they do the times on the sheet was it done in military style ?

because times is the last thing that is needed to stress out brides (even more)
after you been doing weddings a long time, you know how an order is suppose to be
and get it all done as quickly as possible so they can all dance...

just curious

Dennis:

As stated earlier, the times are just for my reference.

The Ward wedding actually ended at 3 instead of 4. It was a hot day and there was no alcohol. People left early.

The DeMassi wedding ended at 9:00 instead of 10:00. The ceremony was done a half hour early and the venue moved everything up a half hour because of that. Then, there was no open bar after cocktails and that kind of killed things too. Add on top of that a Sunday wedding and few dancers and you have an early ending night.

As for Nash, hasn't happened yet.
 
Originally Posted by Ron Auger
I found some more people who made up this first dance stuff and threw it up on a website.

http://mysite.verizon.net/resoy29c/1...ssons/id7.html

It must be real - because someone put in on their website!

Where did the name “The First Dance” come from?
Emcees and DJs.

It was always known as the "Bridal Waltz" until people stopped learning how to actually dance a waltz - now we just let them sway back and forth and make rules that "no one is allowed to dance before the Bride and Groom."
 
It was always known as the "Bridal Waltz"
Says who? Can you show us where it is written? Can you prove it to us?

now we just let them sway back and forth and make rules that "no one is allowed to dance before the Bride and Groom."
You're fixated on this rule thing. No one called it a rule. Proper etiquette and tradition is not a rule, it's just what some people like to do. And as not dancing before the Bride and Groom, well it's just polite and respect. But whatever works in your world go for it.
 
Tom I love them but...

did they do the times on the sheet was it done in military style ?

because times is the last thing that is needed to stress out brides (even more)
after you been doing weddings a long time, you know how an order is suppose to be
and get it all done as quickly as possible so they can all dance...

just curious

One of my points exactly about putting times in itineraries:)

Here's a few samples of mine.

As long as you put times on the things that WILL or HAVE to happen at 'x'-time (arrival, dinner, end-time, photographer-leave time, etc), then you should be able to establish and maintain a flow that keeps you ahead of the game for everything else.

If some do better with a minute-by-minute accounting on paper, then more power to 'em. All that matters is that the job gets done right. Whatever road works for you to get there unscathed is a-okay! :sqwink:
 

Attachments

  • Sample 2.xls.pdf
    53.7 KB · Views: 12
  • Sample 3.xls.pdf
    55.6 KB · Views: 5
  • Sample 4.xls.pdf
    52.7 KB · Views: 4
  • Sample 5.xls.pdf
    50.2 KB · Views: 6
Justin (SoundsToGo):

First of all, see what happens when I read your contract? I find out that you really are not Matt. :sqerr::sqlaugh:

Anyway, I like your agendas. If I had it all to do over again, which I am not, I'd probably go with your method. As a matter of fact, I may go with your format for the rest of the events I have.

As you intimated, if times work for you, go with it and the only reason why I break things out with times is for my own use but most of the time I only really use the intro time, the backend formality time (F/D, M/S, garter, and so on), and the farewell dance time.

I have also found that having the times broken out tends to keep the photographers under control. Sorry Kirby. :sqwink:

Tom
 
Justin (SoundsToGo):

First of all, see what happens when I read your contract? I find out that you really are not Matt. :sqerr::sqlaugh:

Anyway, I like your agendas. If I had it all to do over again, which I am not, I'd probably go with your method. As a matter of fact, I may go with your format for the rest of the events I have.

As you intimated, if times work for you, go with it and the only reason why I break things out with times is for my own use but most of the time I only really use the intro time, the backend formality time (F/D, M/S, garter, and so on), and the farewell dance time.

I have also found that having the times broken out tends to keep the photographers under control. Sorry Kirby. :sqwink:

Tom

LOL.... that's a good point about photographers. Generally they'll hang out around my table or look for visual queues to see whats next. Its the guys who are always disappearing outside or who don't stay in contact with me that never seem to make it onto my recommended vendors page... :sqlaugh:

As for itinerary layouts, it really is each to his own. I like your attention to detail, but the table-format with the cells makes it kind of hard for me to read... Im sure you get used to it though.

My layout is just easier for me to read, and is easy to come back to quickly at a glance. If I have to stop and try to figure out where I am on the sheet, it's not really saving me that much time! :sqwink:


*Please note: Justin Prahar, dba Sounds To Go is in no way affiliated with that other guy (far be it from me to mention his name or help advance his SEO in any way), and any resemblance thereto is purely coincidental and unintentional, and should not be taken as an endorsement of the same. Furthermore, mention of any perceived similarity is cause of great embarrassment and intense mental and emotional anguish, and as such will not be tolerated.
 
So, using Justin's layout it would look like...
 

Attachments

  • Typical.pdf
    93.2 KB · Views: 12
And as not dancing before the Bride and Groom, well it's just polite and respect.

Polite and Respect?

C'mon Ron - put a little logic into play here.

The bride and groom spend $5,000 on a great wedding band, plus another $800 for a DJ to play the breaks, and last hour.

The bride and groom spend the first hour with a photographer, if they choose to dine before a formal dance - do you really believe that proper wedding protocol dictates that the dance floor remain EMPTY for 2 hours while the expensive band and DJ play background filler?

Did you know that the minimum room charge for a ballroom like the Westin Copley is well over $15,000? add the band/DJ and divide that by 5 hours: your "politeness" represents a waste of nearly $7,200.

If up to 40% of the reception is supposed to be background music it's no wonder so many DJs feel threatened by iPods! :)
 
So, using Justin's layout it would look like...

LOL - very clean - I like..... :sqlaugh:

I do it in exel, so I'm thinking with a slightly smaller font (and possibly shrinking logo at top) you could probably fit that sucker on one page! They typically fit on one unless its a huge bridal party or there's an involved ceremony to account for.

If you want a copy of the raw exel to muck with, including proper spacing, printing settings, font sizes, etc.... PM me your email addy.... won't let me upload .xls here. :)
 
Would you like to post the excel sheet so we can have a look at that please :)