Philippines staffing guide · Published
On this page
Keep a meeting follow-up tracker when the owner is traveling
A practical guide for keeping meeting commitments visible while a business owner travels and an overseas VA covers the follow-up queue.
Meetings produce commitments that feel obvious in the room and become ambiguous a day later. When the owner travels, the assistant may have the notes but not the authority to confirm a price, a hire, or a delivery date. A follow-up tracker keeps each commitment attached to an owner and a deadline. The owner's calendar is not the same as the team's commitment list.
The tracker should separate what was said from what was agreed and what still needs approval. That distinction lets a Philippines-based assistant prepare the next step without pretending to hold authority the owner never delegated. It also gives the owner a short review list instead of a folder of raw notes. A tracker that is too detailed will be abandoned before the second day of the trip.
Why travel breaks meeting follow-up
Travel compresses the owner's review time and shifts the working day, so follow-ups that depended on a quick hallway confirmation stop moving. The assistant sees the notes but may not know which promises were final. Within two days, a simple action can turn into a guessing game about who agreed to what. The assistant needs to know which decisions can wait and which cannot.
The risk grows when the owner answers one message from a phone and the answer never reaches the shared record. A tracker gives that reply a durable home and shows which items are still waiting. It also protects the owner from being asked the same question in three different threads. A shared record prevents the same question from being answered differently in two threads.
Separate meeting notes from commitments
A note records what was discussed, while a commitment records what someone agreed to do by a stated time. The tracker should contain only commitments, decisions, and open questions, with a link back to the notes. That keeps the list short enough to review on a phone between flights. Link the meeting notes rather than pasting the whole transcript into the tracker.
For each commitment, record the person who made it, the exact action, the due date, and the evidence that would prove completion. If the meeting produced only a general intention, label it as an open question rather than a task. An intention without an owner is not a follow-up item yet. If the meeting produced no commitment, close the item with that finding.
Build the tracker fields before departure
Use a small set of fields: source meeting, commitment, owner, deputy, due date, status, and next action. Add a field for the approval needed, because travel often removes the person who can approve. Keep the status values tied to real work rather than to a feeling of progress. Keep the status list short enough to fit on one screen.
The deputy field matters most when the owner is away. Name the person who can answer routine questions and the limits of that authority. If no deputy exists, mark the item as blocked until the owner returns instead of letting the assistant improvise a decision. A deputy without a written limit is only a second guess.
Run a short daily follow-up pass
Open the tracker at the same time each day and sort by due date, then by the age of the last update. Send the owner one compact list of items that need a decision, with the question and the consequence of waiting. Do not bury the list inside a long status email that the owner will read after the trip. Put the decision deadline in the subject line of the daily note.
For items the assistant can complete, do the preparation and record the result. For items that need owner approval, keep the evidence ready and set a follow-up time. The daily pass should end with every open item having a named next action and a date. The pass should end with a clear owner for every unresolved item.
Protect the owner's limited review window
Batch decisions by topic so the owner can review several related items in one sitting. Put the most time-sensitive question first and include a recommended option only when the company has authorized one. A clear question with two viable choices is easier to answer than an open request for direction. A recommendation should include the trade-off the owner is accepting.
Respect the owner's stated availability, but record the time zone used for every deadline. A due date without a clock can slip by a full day when the owner is crossing time zones. When a deadline is at risk, tell the affected internal owner before the deadline passes rather than after. Record the time zone beside the deadline so the next assistant does not convert it twice.
Review what slipped after the owner returns
After the trip, review the tracker for items that missed their dates and record the cause. A missed follow-up may reveal an unclear commitment, a missing approval, or a deputy who was never named. Fix the field or the rule that allowed the slip instead of blaming the assistant who noticed it. Ask whether the missed date was caused by the owner, the assistant, or an external party.
Close completed items with the evidence that the action happened, not just the fact that a message was sent. Then archive the trip's tracker and keep the open items in the normal queue. The next travel period should start with fewer unknowns than the last one. Keep the evidence of completion next to the item until the trip review is closed.
Make the tracker useful after the trip ends
When the owner returns, move the unresolved commitments into the normal operating queue instead of leaving them in a travel folder. Keep the trip label only as a reference, because a separate list becomes invisible once the next priority arrives. Review the items that were completed late and ask whether the date or the owner was unrealistic. A separate travel folder should not become a second backlog.
The tracker should also capture what the assistant learned about the owner's decision preferences. That knowledge can improve the next packet without turning into an assumption about authority. A short debrief is enough to turn one trip into a better routine. Write one sentence about the next trip's preparation before the details fade.
Keep a small note about which questions the owner answered quickly and which ones needed more context. That note helps the next packet, but it should not become a shortcut around approval. The goal is fewer avoidable interruptions, not a quieter queue that hides decisions. Close the trip review with one change for the next departure.
At the end of the trip, compare the tracker with the owner's calendar and identify the decisions that could have been prepared earlier. A recurring pattern may justify a standing approval for a narrow task, but only after the owner defines its limits. The next trip should inherit that rule rather than repeat the same scramble. A tracker that survives the trip should be simple enough to update from a phone.
Questions and operating boundary
Who owns a meeting commitment?
The person who made the commitment, with a named deputy for decisions during travel.
What if the owner cannot be reached?
Mark the item blocked, keep the evidence ready, and tell the affected internal owner about the delay.
What counts as a closed follow-up?
Evidence that the agreed action happened, not merely that a message was sent.
Source
sba.gov provides authoritative background and does not endorse this service.