Philippines staffing guide · Published
On this page
Create a podcast guest booking tracker for an overseas assistant
A booking tracker that keeps guest outreach, recording dates, release status, and consent in one place so an overseas assistant can move a booking forward without rebuilding context.
A podcast guest booking tracker keeps outreach, recording dates, and release status in one place, so an overseas assistant can move a booking forward without rebuilding context. The tracker should show who was contacted, what was promised, and which step comes next. Without that record, a guest can be booked twice or dropped after a long email thread. A simple sheet with named owners is enough to start.
The assistant usually owns the logistics rather than the editorial decision. That boundary should be written into the tracker: the host approves the guest, and the assistant confirms dates, collects bios, and sends the prep email. Recording where each approval happened prevents the assistant from guessing. It also gives the host a fast way to review the pipeline before the next recording block.
List the fields before outreach begins
Start with the fields the host will actually use: guest name, topic, contact route, source of the introduction, proposed recording dates, and current status. Add a consent field for recording and release, plus a link to the published episode once it exists. Keep the list short enough that the assistant can fill it during a call. Every extra column adds a chance for silence, so remove fields nobody reads.
Name the status values in advance, such as researched, invited, confirmed, recorded, and published. Use exactly those words in every row so a filter returns a reliable list. Write who may change each status: the assistant can move a guest to invited, but only the host should mark an episode approved. A shared vocabulary removes the guesswork that makes handoffs slow.
Keep outreach evidence beside each guest
Record the date of the first message, the channel used, and the last reply. Paste a short summary rather than the whole thread, and link the thread if the client needs the detail. Note any promise the host made about format, timing, or promotion. Promises are the part most likely to be forgotten when a booking moves to a new assistant.
Set a follow-up date on every open invitation and review the list twice a week. A guest who has not replied after two polite messages should move to a parked status rather than stay open forever. Write the reason for parking so the host can decide whether to try a different route. The tracker should show a realistic pipeline, not an optimistic one.
Prepare the guest without promising too much
Send a short prep note that names the recording time in the guest's time zone, the platform, the expected length, and the host's topic. Ask for a bio, a headshot, and any pronunciation notes before the recording day. Explain how the episode will be used and where it may appear. A guest who knows the plan is less likely to cancel at short notice.
Do not promise a release date, a promotional package, or an edit review unless the host has approved it. Put approved commitments in a single field so the assistant can quote them accurately. If a guest asks for something new, record the request and route it to the host. The tracker becomes evidence of what was agreed, which protects both sides when memory differs.
Confirm the recording window in both time zones
Store the recording time in the host's time zone and the guest's time zone, and show both in the confirmation email. Ask the guest to reply with a one-line confirmation so the booking is not based on silence. Send a reminder one day before and a short link ten minutes before the call. These small steps prevent the most common failure in remote bookings.
If a recording is rescheduled, keep the original date in a change log and record who moved it. A single current date hides the pattern of repeated moves, which is useful when the host reviews the production calendar. Notify the editor and any promotion owner when a date changes, because their work depends on the recording. A date is not confirmed until every dependent person has seen it.
Track consent and release without assuming
Record when the guest consented to be recorded and whether the consent covers the final edit and promotion. Keep the consent message or form linked in the row, not just a yes or no. If the guest asks to remove a segment, log the request, the decision, and the date. Consent evidence matters more than a friendly email thread when a question arises months later. A short note about what the consent did not cover is also useful.
Check the consent field before an episode moves to published. If the record is missing, pause the release and ask the host rather than filling the gap with an assumption. The assistant can prepare the question and the options, but the host owns the final call. A short pause before release is far cheaper than removing an episode after it has been promoted.
Review the tracker at a fixed interval
Once a week, review every open row and ask which one has no next action. Rows without a next date are the ones that quietly stall. Check that confirmed recordings have a prep email, a consent link, and a named editor. Keep the review to fifteen minutes so it actually happens, and close it with one sentence about what changed.
Once a month, compare the tracker with the published episode list and fix any mismatch. Look for guests who were booked but never recorded, and for episodes released without a consent record. Ask the host which status values are still useful and remove the rest. A tracker that matches reality is worth more than a detailed one that does not.
Questions and operating boundary
Who should own the booking tracker?
The assistant can own the daily upkeep, but the host should approve guests and any promise about release or promotion. Write that split in the tracker itself.
How long should a guest stay in the pipeline?
Set a review date after the second follow-up. If there is no reply, park the row with a reason so the host can decide whether to close it.
What if a guest wants to review the edit?
Record the request and route it to the host before agreeing. An edit review is a commitment that changes the production schedule, so it needs an owner.
Source
ftc.gov provides authoritative background and does not endorse this service.