Plan a CEO Business Trip to Lisbon

Build a private, shareable CEO business itinerary in Wanderlog.

Introduction

30 Second Summary

A business trip can unravel when meetings ignore travel time or delays erase the space needed to prepare. An executive needs a plan that keeps every handoff practical.

In this project, you will build a fictional CEO business-trip itinerary from Nigeria to Lisbon using Wanderlog. You will organize three meeting days into an executive-ready schedule before publishing a privacy-safe portfolio link.

What You'll Build

When you open your finished plan, you'll see a CEO's journey from Lisbon Airport through three structured meeting days to a planned departure.

By the end of this project, you'll have:

A five-day executive itinerary that shows arrival on 18 October 2026. It covers three structured meeting days. It closes with departure on 22 October 2026.
A mapped arrival flow from Lisbon Airport to MYRIAD by SANA in Parque das Nações. The map makes the airport-to-hotel handoff visible.
An executive-ready agenda with preparation blocks. It protects decision time. It also includes transfer buffers plus contingency notes.
A privacy-safe portfolio link that demonstrates your planning judgment without exposing confidential information.
Secret Mission: Add a late-arrival contingency that protects the CEO's first meeting.

Are there any prerequisites?

This guide uses Microsoft Edge on Windows with a Google Account.

No bookings or passenger documents are required because every trip detail is fictional.

Before We Start

This opening commitment defines the fictional executive itinerary you are creating. It also keeps the portfolio purpose clear before any hands-on work begins.

Create a Private Wanderlog Trip

Fictional executive travel plans can be mistaken for real bookings when their purpose is unclear. A private workspace keeps the portfolio draft contained while you build it.

Wanderlog combines a day-by-day itinerary with a map. This private trip gives your sample a clear home before any schedule details are added.

In this step, get ready to:

Sign in to Wanderlog through your available Google Account without importing real travel data.
Create the Lisbon trip for 18 October 2026 through 22 October 2026.
Keep the saved trip private after a refresh.

Open the browser and create the account

Your Google Account handles authentication for Wanderlog. Microsoft Edge provides the browser session for this portfolio workspace.

The sign-in flow may show a Google account chooser. It may also offer optional access to real travel information.

Press Cmd+Space (macOS) or the Windows key (Windows) to open your search bar.
Type Microsoft Edge into the search bar.
Press Enter to open Microsoft Edge.

You'll see a Microsoft Edge window with an address bar at the top.

Enter https://wanderlog.com/plan/create in the address bar.
Press Enter to load the trip creation page.
Choose the sign-in option for Google.
Complete the Google sign-in flow with your available Google Account.
Decline any optional prompt to connect Gmail.
Skip any option to import real reservations.

That keeps the portfolio boundary clean. Your Wanderlog workspace is ready for fictional trip details.

Having trouble signing in?

Allow pop-ups for Wanderlog if the account chooser does not appear.
Restart the Google sign-in path if the account chooser closes early.

Help me troubleshoot the Wanderlog Google sign-in flow.

Create the sample trip

The date range frames the CEO's complete travel window. It leaves one arrival day plus three meeting days before departure.

Enter Executive Business Visit: Nigeria to Lisbon as the trip name.
Set Lisbon as the destination.

The form now identifies the fictional portfolio trip plus its destination.

Set the start date to 18 October 2026.
Set the end date to 22 October 2026.

The selected range should now span five calendar days.

Create the trip by submitting the completed form.

You now have a saved Lisbon trip covering the complete executive travel window.

How do the five days work?

Use 18 October 2026 as the arrival day.
Reserve 19 October 2026 through 21 October 2026 for business meetings.
Use 22 October 2026 as the departure day.

Protect the draft

Wanderlog's Private visibility limits access to you plus anyone who later receives the link. That boundary protects the fictional draft before it becomes a portfolio artifact.

Open the three-dot menu near the top of the trip.
Select Trip Settings.
Set the visibility to Private.

Trip Settings should now show Private as the current visibility.

Before you test the saved state, do you expect the privacy choice to survive a reload?

Refresh the page with Microsoft Edge's reload control.
Return to your Wanderlog trip list using the site's home navigation.
Open Executive Business Visit: Nigeria to Lisbon.
Open the three-dot menu near the top of the reopened trip.
Select Trip Settings.

You'll see Executive Business Visit: Nigeria to Lisbon with destination Lisbon.

The trip dates remain 18 October 2026 through 22 October 2026. Trip Settings shows Private.

That boundary is locked in. Your fictional itinerary now has a saved private home.

Trip not staying private?

Confirm that the reopened trip title is Executive Business Visit: Nigeria to Lisbon.
Select Private again in Trip Settings if another visibility option appears.
Refresh once more to test the saved state.

Help me check why my Wanderlog trip is not keeping its Private visibility.

Your fictional travel sample is saved behind Private visibility. Next, you'll shape its five dates into an executive agenda.

Build the Executive Agenda

Your private Wanderlog trip is ready for its working schedule. A bare list of locations leaves the CEO's business day invisible.

A useful executive itinerary shows the complete operating rhythm from arrival to departure. This step adds that rhythm through places, timed blocks, meeting notes, and travel checks.

In this step, get ready to:

Map the airport plus the hotel meeting base.
Build a five-day itinerary with timed executive blocks.
Add fictional meeting notes plus a travel-document checklist.

Add the core locations

Places added to the itinerary appear on its map. Lisbon Airport establishes the arrival point. MYRIAD by SANA gives every meeting day a consistent base in Parque das Nações.

Select 18 October 2026 in the itinerary.
Click Add a place on the arrival day.
Search for Lisbon Airport.
Select Lisbon Airport from the search results.

You should see Lisbon Airport listed on 18 October. You should also see its marker on the map.

Click Add a place again on 18 October.
Search for MYRIAD by SANA.
Select the property in Parque das Nações.

The map should now show Lisbon Airport plus MYRIAD by SANA. These markers establish the arrival flow for the portfolio itinerary.

Why use one meeting base?

MYRIAD by SANA serves as the fictional hotel plus the on-site meeting location. One base keeps the routine easy to scan.

The first hotel entry marks the start of a meeting day. The last hotel entry shows the CEO returning to the same base.

Select 19 October 2026.
Add MYRIAD by SANA as the first entry.
Add a second MYRIAD by SANA entry as the last entry.

The first meeting day should now begin at the hotel. It should also end at the hotel.

Select 20 October 2026.
Add MYRIAD by SANA as the first entry.
Add a second MYRIAD by SANA entry as the last entry.

The second meeting day should now have the same hotel-based flow.

Select 21 October 2026.
Add MYRIAD by SANA as the first entry.
Add a second MYRIAD by SANA entry as the last entry.

All three meeting days should now start at MYRIAD by SANA. Each day should return to the same location.

Place missing from the map?

Confirm that you added the place to the itinerary for a dated day. A place stored only in a separate list may stay outside the mapped daily route.

Check that the hotel result is located in Parque das Nações. Help me find the missing Wanderlog map marker.

Build the five-day structure

The dated structure gives every travel day a clear purpose. Repeated hotel entries can represent separate executive blocks once you attach times plus session details.

Return to 18 October 2026.
Add Airport arrival placeholder: 14:00 to the day's Notes area.
Add Transfer to MYRIAD by SANA: 14:30.
Add Hotel check-in: 15:30.
Add Executive briefing: 17:00.
Add Early rest: 19:00.

The arrival day should now show a complete handoff from Lisbon Airport to early rest at the hotel.

How to time each hotel block

Hover over the clock icon beside the relevant MYRIAD by SANA entry.
Select Add start time.
Enter the start time for that block.
Enter the end time in the available time field.
Add the block name to the entry's notes.

Select 19 October 2026.
Use Add a place to create four more MYRIAD by SANA entries.
Arrange the day so it contains six hotel-based entries.
Use the first entry for Breakfast preparation from 07:30 to 08:00.
Use the second entry for Morning meeting from 09:00 to 11:00.
Use the third entry for Working lunch from 12:30 to 13:30.

The first half of 19 October should now move from preparation into focused work. The lunch block should remain visible as protected executive time.

Use the fourth entry for Afternoon decision block from 14:00 to 16:30.
Use the fifth entry for Debrief from 16:30 to 17:00.
Use the sixth entry for Recovery time from 17:00 to 18:00.

The completed meeting day should show six distinct blocks. The sequence should end with recovery at MYRIAD by SANA.

Apply the same six-entry schedule to 20 October 2026.
Apply the same six-entry schedule to 21 October 2026.

The three business days should now share a consistent operating rhythm. Each day should show timed preparation, meetings, lunch, decisions, debriefing, and recovery.

Select 22 October 2026.
Use Add a place to add Lisbon Airport to the departure day.
Add Final document check: 08:00 to the day's Notes area.
Add Hotel departure: 09:00.
Add Lisbon Airport: 09:45.
Add Fictional flight placeholder: 12:00.

The departure day should now show the final checks plus the return to Lisbon Airport. The flight remains a fictional portfolio placeholder.

Add executive notes and times

Times explain when each block happens. Executive notes explain what must happen inside that block.

Keep the sample fictional

Use fictional portfolio data for every attendee. Use fictional portfolio data for every company.

Keep booking references plus passenger details out of the trip. The schedule should demonstrate planning judgment without using real travel data.

Open the notes for the Morning meeting entry on 19 October 2026.
Add Objective: Confirm the fictional market-entry priorities..
Add Attendees: CEO, Host Director, Finance Lead..

The meeting entry should now show why the session exists. It should also identify the fictional roles involved.

Add Decision required: Approve the fictional next-step plan..
Add Follow-up owner: Executive Assistant..
Apply the same four note fields to the remaining morning meeting entries.
Apply the same four note fields to all three afternoon decision block entries.

Every morning meeting plus afternoon decision block should now identify its objective, attendees, required decision, and follow-up owner.

Create a free-form note titled Travel document checklist in the trip's Notes area.
Type [] Verify passport nationality and applicable entry rules.
Type [] Confirm invitation or meeting evidence.

You should see two checklist boxes in the note. Wanderlog creates a tick box when a Notes line starts with [].

Type [] Confirm accommodation details.
Type [] Confirm return-travel evidence.

The checklist should now cover the traveller's stay plus evidence of departure.

Type [] Confirm insurance if required.
Type [] Confirm funding evidence.
Type [] Confirm emergency contacts.

The finished note should contain seven checklist boxes. Its first item keeps the entry-rule check conditional on passport nationality.

Before you review the finished plan, does every travel day now have a distinct executive purpose?

Return to the combined itinerary plus map view.
Select 18 October 2026 to confirm the arrival flow.

You should see Lisbon Airport, the transfer, hotel check-in, executive briefing, and early rest on the arrival day.

Select 19 October 2026 to review its timed agenda.
Select 20 October 2026 to review its timed agenda.
Select 21 October 2026 to review its timed agenda.

Each meeting day should show breakfast preparation, a morning meeting, working lunch, an afternoon decision block, debrief, and recovery time. The entries should remain based at MYRIAD by SANA.

Select 22 October 2026 to confirm the departure flow.
Check the map for Lisbon Airport plus MYRIAD by SANA.

You should see the final document check, hotel departure, Lisbon Airport, and the fictional flight placeholder. The map should contain both core Lisbon locations.

That is the planning backbone complete. Your trip now reads like an executive operating schedule from arrival through departure.

Your five-day agenda is ready for a pressure test. Next, you will use the map to examine whether one of its handoffs can work in practice.

Expose the Impossible Handoff

Your Wanderlog itinerary already gives the CEO a complete five-day operating plan. A polished schedule still needs a pressure test.

This step deliberately creates a handoff that the calendar accepts but the traveller cannot complete. Seeing that failure makes the missing transfer margin impossible to ignore.

In this step, get ready to:

Add Fado in Chiado as optional client hospitality on 20 October.
Create a zero-buffer handoff at 19:00.
Use the map to document the conflict.

Add an optional cultural engagement

An evening engagement creates a realistic test for the meeting-day schedule. Its optional status keeps the CEO's business objectives protected.

Select 20 October in the itinerary from earlier.
Click Add a place inside that day.

You'll see the place search panel for 20 October.

Enter Fado in Chiado in the search field.
Select Fado in Chiado from the results.

You'll see Fado in Chiado appear in the 20 October itinerary.

Hover over the clock icon beside Fado in Chiado.
Select Add start time.

You'll see a time field for the new itinerary entry.

Set the start time to 19:00.
Add Optional client hospitality. to the place notes.

The entry now starts at 19:00. Its note clearly marks the engagement as optional.

Why keep it optional?

An optional hospitality event can be dropped if the business day runs long. This protects the trip's core business purpose.

Create the zero-buffer handoff

Executive schedules fail when location changes consume time the diary has not reserved. This pressure test makes that risk visible.

Select the final meeting at MYRIAD by SANA on 20 October.
Set the meeting's end time to 19:00.

You'll see the final meeting end at 19:00.

Leave the Fado in Chiado start time at 19:00.
Keep both entries on 20 October.

Before you compare the entries, do you think this timeline can deliver the CEO from one venue to the other on time?

Compare the final meeting's end time with the Fado in Chiado start time.

You'll see the MYRIAD by SANA meeting end at 19:00. You'll see Fado in Chiado start at 19:00.

The handoff has zero minutes available. That shortfall is intentional.

Why does this handoff fail?

Adjacent entries can look organised while hiding the movement between them. Executive planning must account for elapsed time as well as geography.

Document the visible conflict

The timeline reveals the missing minutes. The map confirms that those minutes separate two different locations.

Select the day-filter control on the map.
Choose 20 October.

You'll see only the places assigned to 20 October on the map.

Compare the MYRIAD by SANA location with the Fado in Chiado location.

You'll see the meeting venue and evening venue in separate mapped locations.

Can't see both locations?

Confirm that both entries remain on 20 October. Check that Fado in Chiado was added with Add a place.

Get help checking the itinerary setup.

Return to the Notes section from earlier.
Add a new free-form note.

You'll see an empty note ready to document the schedule risk.

Enter Conflict found as the note title.
Enter The itinerary has no transfer, delay, or arrival buffer between different locations. as the note text.

The Conflict found note now records why the handoff cannot work.

Before the final check, which evidence do you expect to make the problem clearest: the matching times or the separate map locations?

Review 20 October from top to bottom in the itinerary.
Check the filtered map beside the itinerary.

You'll see the final MYRIAD by SANA meeting end at 19:00. You'll see Fado in Chiado start at 19:00 in a separate mapped location.

The Conflict found note records the missing transfer margin. It also records the missing delay margin and arrival margin.

You caught the risk before it reached the CEO. Next, you'll rebuild 20 October with protected movement time.

Make the Trip Executive-Ready

Your deliberate Day 2 test exposed a zero-buffer handoff in the Wanderlog itinerary. That conflict shows how a full meeting day can fail when travel margin disappears.

The revised day protects decision time. It also reserves transfer time.

A recovery window keeps the evening optional. Manual sequencing keeps this fix on Wanderlog's free path.

In this step, get ready to:

Repair the 20 October handoff through manual sequencing.
Protect the CEO's operating rhythm with explicit buffers.
Record practical transport guidance with conditional travel-document guidance.

Repair and reorder Day 2 manually

A feasible timeline separates the business-critical close from optional hospitality. The transfer needs dedicated time.

A refresh buffer gives the CEO space to reset before the evening event. The optional status protects the meeting if the day runs late.

In the 20 October view from earlier, select the final MYRIAD by SANA meeting entry.
Set its end time to 16:30.

You should now see the final meeting end at 16:30. Fado in Chiado should still begin at 19:00.

In the Notes area for 20 October, create a free-form note titled Transfer and refresh buffer.
Confirm Fado in Chiado remains marked as optional client hospitality.

Day 2 Order

This sequence protects the business agenda before the optional evening activity.

1. Preparation.
2. Meeting.
3. Working lunch.
4. Decision block.
5. Debrief.
6. Transfer and refresh buffer.
7. Fado in Chiado.

Drag the day's entries into the order shown above.
Replace the Conflict found note with 20 October previously had a zero-buffer conflict between MYRIAD by SANA and Fado in Chiado. The conflict has been resolved by ending the final MYRIAD by SANA meeting at 16:30 and inserting transfer and refresh time before the optional 19:00 event.
Read the reordered itinerary from top to bottom.

You should see the business blocks finish before the transfer buffer. The optional Fado in Chiado entry should remain last at 19:00.

Can't Get the Order to Stick?

Confirm every entry belongs to 20 October.
Move one entry at a time with its drag handle.

Help me troubleshoot the order of my Wanderlog itinerary entries.

Add executive operating buffers

Buffers turn a packed itinerary into an operating plan. Each buffer protects a different executive need.

How Each Buffer Works

Preparation protects focus before the meeting begins.
A protected working lunch preserves productive time without removing the meal break.
Debrief captures decisions while the discussion is still fresh.
Recovery time prevents optional activity from draining the next business block.

Set every pre-meeting preparation block from 19 to 21 October to 30 minutes.
Mark every working lunch as protected time.
Review the first half of each meeting day.

You should see a 30-minute preparation block before each meeting. Each working lunch should be clearly protected.

Set every post-meeting debrief to 30 minutes.
Update every recovery note to reserve a recovery window before optional evening activity.
Review the end of each meeting day.

You should see a 30-minute debrief after the meeting work. A separate recovery period should follow.

Add an owner to every meeting block.
Add an intended outcome to every meeting block.
Scan all meeting notes.

Every meeting block should now identify who owns it. Each block should also state the result it needs to produce.

Decision Log Structure

A decision log turns meeting discussion into accountable follow-up. Use these four fields.

Decision.
Owner.
Deadline.
Next action.

In the trip's Notes area, create a free-form note titled Decision log.
Enter the four field labels shown above as separate lines.
Read the saved note.

You should see four separate labels. They should read Decision, Owner, Deadline, and Next action.

Record transport and document choices

Arrival guidance needs a primary route. It also needs a fallback.

Travel-document guidance must remain conditional because departure from Nigeria does not establish passport nationality. Legal residence also affects where an application belongs.

In the trip's Notes area, create a free-form note titled Transport and document notes.
Record the Metro from Aeroporto station in the arrivals area as the primary airport option.
Read the arrivals transport section.

You should see the Metro listed as the primary route. The note should remind the traveller to check live service before travel.

Record P2, Level 2, arrivals level as the fallback pickup for Bolt or Uber.
Read the updated arrivals transport section.

You should now see a primary Metro option. You should also see the exact fallback pickup location.

Add an instruction to verify passport nationality first.
Add an instruction to verify legal residence next.
Read the travel-document section.

The document check should begin with the traveller's own circumstances. It should avoid assuming that departure from Nigeria determines visa status.

Add Portugal's official visa portal as the source to consult after those checks.
Add a conditional line stating that Portugal lists VFS locations in Abuja and Lagos only if the traveller must apply from Nigeria.
Read the updated guidance.

The note should direct the learner to Portugal's official source. The Nigeria service locations should appear only as a conditional path.

End the note with This is conditional guidance, not a visa determination.
Read the final sentence.

Your note should clearly separate planning guidance from an individual visa determination.

Before you review 20 October from top to bottom, do you expect any two entries to overlap?

Review the 20 October itinerary from top to bottom.

You should see the final MYRIAD by SANA meeting end at 16:30. You should see a transfer and refresh buffer before optional Fado in Chiado at 19:00.

You have cleared the hardest scheduling gap. Day 2 now protects the business agenda without sacrificing the optional evening.

Your itinerary now shows the judgment behind an executive travel plan. Next, you will turn it into a privacy-safe portfolio artifact.

Publish a Safe Portfolio Version

Your itinerary now protects the CEO's business priorities. The schedule is ready for a portfolio handoff.

A strong handoff proves your planning judgment without exposing passenger details or commercially sensitive information.

Your Wanderlog trip remains private during this process. A view-only link becomes the safe portfolio handoff.

In this step, get ready to:

Sanitize every itinerary entry.
Create a Can view portfolio link.
Test the link in Microsoft Edge InPrivate mode.

Sanitize the itinerary

A sanitized itinerary keeps your planning logic visible. It removes details that could identify a passenger or a real business.

A reviewer can still assess how you sequence the trip. They can also see how you protect executive decisions.

What needs to be fictional?

Personal names become role labels.
Company names become fictional placeholders.
Flight details become fictional placeholders.
Booking references become fictional placeholders.
Passport details become fictional placeholders.
Phone numbers become fictional placeholders.
Payment details become fictional placeholders.

Review the full itinerary for identifying details.
Replace each personal name with a role such as CEO, Host Director, or Executive Assistant.
Replace every remaining sensitive detail with a clearly fictional placeholder.
Read the sanitized itinerary from arrival through departure.

You should now see role labels wherever people are named. Every sensitive detail should clearly read as fictional.

The trip title, public venue names, planning logic, and decision structure remain visible.

Create view-only access

Sharing a portfolio link can feel exposed. These two permissions keep the handoff controlled.

In Wanderlog, Private limits access to the owner plus people holding the link. Can view removes edit permission for shared viewers.

Open the three-dot menu near the top of the trip.
Select Trip Settings.
Confirm Private remains selected.
Close Trip Settings.
Select Share near the top of the trip.
Choose Can view.
Copy the displayed sharing link.
Save the copied link here: your Wanderlog Can view link.

That is the sharing boundary in place. Your trip remains private while the portfolio link grants view-only access.

Test the handoff

A Microsoft Edge InPrivate window gives you a clean viewer session. This reveals whether the link works outside your signed-in owner view.

Before you open the link, do you expect the viewer to see editing controls or any real-world identifiers?

Use Microsoft Edge's top-right menu to open an InPrivate window.
Paste your Wanderlog Can view link into the address bar.
Press Enter to load the trip.

The itinerary should load in view-only mode. You should not see controls that allow edits.

Review the arrival flow on 18 October 2026.
Review the three meeting days from 19 to 21 October 2026.
Review the departure flow on 22 October 2026.
Inspect the map for Lisbon Airport, MYRIAD by SANA, and Fado in Chiado.
Inspect the itinerary for preparation blocks, travel buffers, and the resolved 20 October conflict.
Inspect every note for real passenger, company, booking, passport, contact, or payment data.
Select an itinerary entry to test whether edit controls are available.

You should see the complete five-day itinerary.

You should find no edit controls.

You should find no real passenger, company, booking, passport, contact, or payment data.

Does the handoff look wrong?

Return to the owner window if edit controls appear.
Confirm Can view in the sharing panel.
Copy the sharing link again if the InPrivate page does not load.
Remove any real-world identifier that appears during the review.

Ask for help with the specific handoff problem: Help me troubleshoot my private Wanderlog portfolio link without exposing its URL or any sensitive trip data..

You've turned a private planning exercise into controlled portfolio proof. A reviewer can now see your travel-planning judgment without gaining edit access.

Secret mission

Add a Late-Arrival Contingency

An executive itinerary earns trust when it can absorb a late arrival. Add a clear trigger for changing the arrival plan. Move the briefing to protect preparation before the first meeting. Give the Executive Assistant a clear communication duty.

Clean Up Your Resources

Choose whether to keep your itinerary available, pause portfolio sharing, or delete the trip entirely. This project has no ongoing costs because it created only a free Wanderlog itinerary.

Resources you used:

Private Wanderlog trip Executive Business Visit: Nigeria to Lisbon containing fictional portfolio data.
Copied Can view portfolio link tied to the private trip.

Keep everything running

No action needed. Choose this if you want to keep using the itinerary as a portfolio sample.

Your Executive Business Visit: Nigeria to Lisbon itinerary remains available in Wanderlog.
Your trip stays Private. You can still share view-only access through the Can view link.

Pause - I'll come back to this later

Pause portfolio sharing while keeping the itinerary ready for future updates.

Keep the trip visibility set to Private.
Remove the copied Can view link from any portfolio page or message where you shared it.
Return to Executive Business Visit: Nigeria to Lisbon when you are ready to update the sample.

Delete - I don't want to use this again

Remove the private trip if you no longer want to keep this portfolio sample.

Return to the Wanderlog home page.
Select Profile.
Select Your profile.
Open the three-dot menu for Executive Business Visit: Nigeria to Lisbon.
Select Delete.
Return to Your profile.

You should no longer see Executive Business Visit: Nigeria to Lisbon in your trip list.

Remove the copied Can view link from any notes or portfolio drafts that contain it.
In Microsoft Edge, open a new InPrivate window.
Paste the copied link into the address bar.
Press Enter.

The copied link should no longer provide access to the deleted portfolio itinerary.

Nice Work!

You made it. You built a privacy-safe executive itinerary in Wanderlog that a hiring manager or client can review.

You've learned how to:

Build a five-day executive itinerary that carries a CEO from Lisbon Airport through three meeting days to departure.
Use mapped locations to expose a zero-buffer handoff. Repair the conflict through manual sequencing. Protect the executive's operating rhythm with buffers.
Produce a privacy-safe handoff that combines conditional travel-document guidance with sanitized view-only sharing.
Secret Mission: Add a late-arrival contingency that protects the CEO's first meeting through an alternate airport transfer plus a named communication owner.

Ready to quiz yourself?