"
![]() |
![]() |
![]() |
Outlook makes no provision for travel time when logging meetings or other appointments. This has been something of an irritation to me when logging appointments, where the travel time often far exceeds the appointment time, so when someone raised the issue in a forum recently, I thought it might be worth creating a function to add travel time to appointments.
Outlook doesn't lend itself to using add-in templates, like Word or Excel, so I have simply made the code available as a pair of modules to download, extract from the zip file and import into Outlook's VBA editor.
I'm afraid you will have to add the macro to a button on the context sensitive Calendar Tools ribbon, but Outlook has its own ribbon editor which makes this fairly straightforward.
It should be easy enough to match the name and icon of the added macro command to match the following:
Link the button to the macro 'AddTravelToMeeting' and you should get a button group on the Calendar Tools ribbon as above.
Enter the appointment first and with the cursor in the appointment in the calendar view, click the ribbon button.
The macro pops up a userform that is used to calculater the number of minutes of travel time (each direction). The 'home' address is retained between uses (but can be changed) and the destination address is read from the appointment location.
If both addresses exist, the process will calculate the time to travel between them, in minutes, which is then rounded up to the nearest 10 minute interval. The calculation employs Google Maps so requires an internet connection. Both outward and return travel times are initially the same. You can change either or both manually to add or reduce the travel time to suit local conditions.
The travel time assumes road travel with a motor vehicle. International travel by air is not accounted for as it is difficult to accommodate flight times into the travel planning. For such use enter the travel times manually, and do not click the recalculate button.
The result in the calendar is as shown below.