Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php on line 199

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/wp-db.php on line 3030

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/class-wp-block-list.php:14) in /home/ldfwlrfrhxph/public_html/wtbinc.com/wp-includes/rest-api/class-wp-rest-server.php on line 1648
{"id":475,"date":"2014-09-12T03:52:45","date_gmt":"2014-09-12T03:52:45","guid":{"rendered":"https:\/\/wtbinc.com\/?p=475"},"modified":"2021-04-14T03:54:20","modified_gmt":"2021-04-14T03:54:20","slug":"planning-meetings-offsite","status":"publish","type":"post","link":"https:\/\/wtbinc.com\/travel\/planning-meetings-offsite\/","title":{"rendered":"Planning Meetings Offsite"},"content":{"rendered":"

<\/h2>\n

Planning Meetings: Where and How to Begin?<\/h2>\n

When it comes to planning meetings, more and more companies recognize the fact that \u201cgetting out of the office\u201d can greatly benefit the overall impact. The common question about planning meetings is; \u201cwhere do we begin\u201d? There is not a \u201cpat\u201d answer, though, there are a number of pertinent questions that can provide a vetted process to match the objectives with the right destination. There are numerous factors to ensure excellence for the outcome of the proposed meeting.<\/p>\n

The first considerations for determining a resolution to the query is comprised of basic items:<\/p>\n

    \n
  1. When is the meeting planned?\u00a0 This is crucial because the determination of all other factors hinge on the fact that all details can be put in order for the success of the meeting program.\u00a0 Time is important to secure the best negotiated rates for airline contracts, hotel\/resort, destination management groups, food & beverage contracts etc\u2026. How many days\/nights will be the meeting extend?<\/li>\n
  2. What sort of property is ideal?\u00a0 Urban hotel or golf resort, for example.<\/li>\n
  3. City of choice for the meeting?\u00a0 What is the ideal place?\u00a0 What places are they considering?\u00a0 It is important to take careful note and be able to weigh options including all the pros and cons with alternatives if the ideal isn\u2019t working out.\u00a0 Having an experienced team providing this dialog can secure a meaningful decision that will exceed expectations.<\/li>\n
  4. Will attendees be traveling from other locations?\u00a0 (Or is it a local off-site meeting in their business city location?)<\/li>\n
  5. What is the budget?\u00a0 This is good to discuss early into the dialog because there is a world of difference if the expectations are for a moderate resort vs. a 5-star resort.\u00a0 Oftentimes these two variables can be in the same area, but the price points can be dramatically different.<\/li>\n
  6. How many people will be in attendance?\u00a0 Will they be bringing spouses\/guests or family members?\u00a0 Many companies are opting to allowing spouses\/guests\/ family members to travel but on the individual traveler\u2019s expense.\u00a0 This is especially valid to destinations that are desirable for a broad spectrum of travelers such as Hawaii, etc\u2026 Sometimes while the attendees are in their meetings, family\/spouses\/guests have access to programs that have been arranged for their enjoyment.<\/li>\n
  7. Will there meeting room requirements? Break-out rooms?\u00a0 How many people in each room? Will there be A\/V (audio-visual) requirements?<\/li>\n
  8. Will there be food and beverage requirements?<\/li>\n
  9. Who will be the decision maker on the proposed plans?<\/li>\n<\/ol>\n

    Once these basic items are outlined, our experienced team will commence the process of syphoning through the plethora of options, variables and criteria to start building a series of solid considerations for the client. Often the research is expansive, yet always thorough. Once some viable options have been secured, a detailed presentation is arranged to highlight the various choices and price-points.<\/p>\n

    However sometimes when it comes to planning meetings, there isn\u2019t the luxury of time for the actual planning. A few years back, a client contacted me on a Monday for a 4 night program, starting 3 days later on Thursday!\u00a0 I remember the initial shock at the request because it wasn\u2019t a simple, single day event. NOOOO, it was a \u201cfull-on-sales meeting\u201d for two-hundred and twenty people, who would be flying into one location in Southern California from all over North America.\u00a0 It was to be a combination meeting of incentive rewards, a shot-gun golf tournament, cocktail receptions, spa time, team-building, awards banquet, business meetings with break-out rooms and audio-visual requirements along with room \u201cgoodie bags\u201d and numerous amenities throughout the program. The bonus was that this particular group had a realistic budget and they realized that last minute would be premium pricing. But they knew what they wanted and they wanted it NOW.<\/p>\n

    So where did I begin? I knew the dates and the geography of the location requested. I quickly reached out to solid industry vendors who \u201cfit the criteria\u201d (location, availability of dates, had meeting space, was a \u201chigh end\u201d property, on-site spa and golf courses) and would be willing to work around the clock, if necessary, to get everything done in a 72-hour window. Key relationships in the travel industry can secure optimum results and that\u2019s the advantage of working with folks who have the proven successes of past experience who can go to bat for the best expectations for our valued clients. So I quickly secured all and went to contract with the resort was a matter of locking in the requirements for meetings, receptions, meals, tournaments, leisure events, team-building and transportation. The meeting was an incredible success for ALL!<\/p>\n

    This blog post was written by Carol Nosches, CTC who is the Corporate Travel Services Manager for World Travel Business Elite.<\/address>\n

    World Travel Business Elite;<\/span><\/a><\/span> when it comes to planning meetings and incentive trips…we’ve got you covered.<\/strong><\/p>\n

     <\/p>\n


    \n

     <\/p>\n

    Click Here to get a free Business Travel Analysis for your company! <\/span><\/a><\/span><\/h3>\n","protected":false},"excerpt":{"rendered":"

    Planning Meetings: Where and How to Begin? When it comes to planning meetings, more and more companies recognize the fact that \u201cgetting out of the office\u201d can greatly benefit the overall impact. The common question about planning meetings is; \u201cwhere do we begin\u201d? There is not a \u201cpat\u201d answer, though, there are a number of…<\/p>\n","protected":false},"author":918,"featured_media":476,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[137],"tags":[],"_links":{"self":[{"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/posts\/475"}],"collection":[{"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/users\/918"}],"replies":[{"embeddable":true,"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/comments?post=475"}],"version-history":[{"count":1,"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/posts\/475\/revisions"}],"predecessor-version":[{"id":3430,"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/posts\/475\/revisions\/3430"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/media\/476"}],"wp:attachment":[{"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/media?parent=475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/categories?post=475"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wtbinc.com\/wp-json\/wp\/v2\/tags?post=475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}