How to Get on Business Continuity Podcasts

To get on business continuity podcasts, pitch one decision you handled during planning, disruption, recovery, or an exercise. Show your role and evidence, then explain the trade-off and limits. Match that case to a current show's audience. Then verify interview format and public guest permission separately. Relevant expertise creates editorial fit, but it does not create access.

Build the premise around one continuity decision

"Business continuity expert" is a credential claim, not an episode. A producer needs a problem that creates a useful discussion. A team may have discovered that its critical dependency sat outside the formal plan. An exercise may have exposed unclear authority. A recovery target may have failed because the business and technology teams defined the service differently.

Choose a case where your responsibility is precise. Perhaps you designed the exercise, mapped the dependency, led the response, rebuilt the communication path, or challenged an assumption. Claim only the work you did. Continuity outcomes usually depend on operators and technology teams as well as facilities and suppliers. Communications staff work with legal reviewers and senior decision-makers to shape them too.

Prepare a private pitch dossier before looking for contacts. Record:

• the listener role and decision;
• the disruption and dependency, including the planning assumption;
• your direct responsibility;
• the evidence approved for discussion;
• the trade-off or failed approach;
• the other teams that contributed;
• confidentiality and speaking-authority limits;
• any product or consulting interest, including training, insurance, or a book.

The dossier should reveal whether the premise still works after sensitive details are removed. If the story collapses without a client name or confidential metric, it is not ready for outreach. The same applies when it depends on unreleased incident detail.

Match the case to the show's working audience

Start with the Convokast podcast directory and its business podcast category, then inspect the current official feed for every candidate. Business continuity overlaps with facilities resilience and crisis management, but these fields do not serve the same decisions.

A facilities case should explain the building or workplace mechanism, not hide it behind a generic resilience label. A crisis-management case needs the decisions made under pressure. An enterprise-resilience case needs governance and ownership, not only a chronology of the incident.

If the same pitch appears to fit every row without revision, the premise is still too broad.

Verify current production before researching a contact

Read the latest official release and the channel description. Look for a finale or hiatus notice. Changes to the publisher or feed name deserve the same attention, as does a shift in subject. A directory page can remain visible long after the recording calendar closes.

The Business Resilience DECODED feed makes the rule clear. Older episode notes directed prospective contributors to apply to be a guest. The official feed now says the program stopped releasing new episodes and includes a finale. The closure notice overrides the old route.

Business Continuity Today and Mostly Crisis Management both provide useful archives, but their latest releases are not current. Confirm a return before investing in a tailored proposal.

Facility Resilience has current releases and named interviews. Crisis Management Minute is relevant to crisis work but does not establish a recurring guest format. Production and subject fit are separate from the need for guests.

Separate interview evidence from permission to pitch

A current interview archive confirms that outside voices appear. It cannot tell you whether the producer welcomes cold submissions. The guest may have been invited or referred. Editorial research or an existing professional relationship may also explain the booking.

Use the guest-access verification guide to classify each route. A self-application permits a person to propose themselves for consideration. By contrast, a nomination permits a recommendation. Topic requests may invite a subject while withholding permission for a personal pitch.

General contacts require restraint because their published purpose may have nothing to do with the podcast. A short routing question can ask whether the team reviews podcast proposals and where they belong. Do not hide a full biography and pitch inside that question. Product demos and customer support retain their stated purposes, as do advertising and conference speaking. So do association membership and sponsor enquiries.

The current continuity shows reviewed for this guide do not publish a verified open application or nomination route. A relevant introduction or direct invitation may still create a permitted path. It should not be reported as public access.

Turn the incident into evidence, not a victory story

Continuity stories become suspicious when every decision looks obvious after the event. Real disruptions involve partial information, competing priorities, dependencies that were not documented, and recovery choices that transfer risk elsewhere.

Tell the producer what can support the episode. Public evidence may include an approved after-action report, published policy, regulator notice, or court record. A weather event, vendor status report, or organizational statement can also support the account. Internal evidence belongs in the pitch only when it is cleared for public discussion.

State what the evidence cannot prove. A faster recovery may reflect the plan and experienced staff. Lighter impact, supplier help, or luck may also explain it. An exercise may improve awareness without proving that the organization would perform the same way in a real event. A lower incident count may follow changed reporting rather than lower risk.

Do not combine several confidential incidents into one invented case. You can describe a recurring pattern as a pattern if you explain the scope and limits of your observation.

Set confidentiality and authority before outreach

Continuity professionals handle sensitive material. Plans can expose single points of failure, alternate sites, key suppliers, and technology dependencies. Contact trees, security weaknesses, and executive succession arrangements can be sensitive too. Removing the organization name may not protect it if the site or system remains recognizable. The incident sequence or counterparties can identify it too.

Separate public evidence from approved experience and restricted information. The proposed episode must stand on the first two groups. Restricted details stay out of the pitch and preparation call, as well as the recording and follow-up.

Speaking authority needs the same care. Running an exercise does not authorize someone to speak for the employer, client, regulator, or insurer. Suppliers and emergency services speak for themselves. State the capacity in which you would appear. Obtain any required legal, communications, employer, or client approval before sharing identifiable details.

A narrower case that survives review is better than a dramatic premise that loses its evidence after acceptance.

Disclose commercial and vendor interests early

Consultants and software leaders can bring useful experience. Insurers, trainers, and authors can too. The producer still needs to know what they sell and how it connects to the subject. Put that relationship in the first proposal.

Frame the episode around the listener's decision rather than the product. If the method belongs to your company, identify it. For a case from client work, disclose that relationship even when the client remains unnamed. Vendor involvement in the result must also be disclosed, not presented as independent proof of the vendor's claims.

Sponsorship and editorial selection are different. Buying an advertisement does not establish a guest booking unless the publisher offers a clearly labeled sponsored interview format. A commercial route should never be described as editorial acceptance.

Write a pitch that gives the host useful questions

Open with the listener and decision. State the condition that made it difficult and your direct role. Then identify the evidence you can discuss. Add the trade-off or limitation that prevents the story from becoming a sales case.

A useful continuity pitch might center on how a team found a dependency during an exercise and changed ownership before the next test. It could examine why a technically correct recovery plan failed to match the business service. It could show how facilities and technology teams worked with communications staff to resolve conflicting priorities without pretending that one person saved the organization.

Give the host question territory rather than a script. The producer should be able to challenge the assumption and ask what failed. They should also identify who disagreed and examine what the team still does not know.

Use audience overlap to check that the show's listeners own or influence the decision. When the evidence and permissions are ready, use the verified route and the podcast pitch generator to turn the dossier into one show-specific proposal.