Loading...
compliance

Outside Speaking Engagement Form

Use this Outside Speaking Engagement Form to collect the facts HR or compliance needs before an employee speaks publicly. It captures the event, compensation, company references, and conflict-of-interest disclosures in one reviewable record.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Technology · Healthcare · Financial Services · Education · Professional Services

Overview

This Outside Speaking Engagement Form template collects the information a company needs to review an employee’s external speaking activity before it becomes a policy issue. It captures employee identity, event logistics, audience, topic summary, compensation or benefits, and whether the employee will use the company name or discuss company business.

Use it when employees are invited to speak at conferences, panels, webinars, classes, podcasts, vendor events, or community programs and your organization needs a consistent disclosure and approval record. The template is especially useful when speaking engagements may create a conflict of interest, involve a competitor or vendor, or include paid honoraria, travel, gifts, or other benefits.

Do not use this form as a generic event registration form or as a substitute for a full outside employment policy. It is also not the right tool when the speaking activity is purely internal, anonymous, or already covered by a separate legal review process. Keep the form focused on the minimum necessary fields, use conditional logic for compensation and conflict follow-ups, and include a clear note on what happens after submission so employees know whether they are waiting for approval, disclosure acknowledgment, or both.

Standards & compliance context

  • Use data minimization under GDPR Article 5 by collecting only the employee and event details needed for conflict and disclosure review.
  • If the form is public-facing or employee-accessible through a shared portal, keep it accessible with WCAG 2.1 AA-friendly labels, validation, and keyboard navigation.
  • If the engagement touches health-related content, apply the minimum-necessary principle and avoid collecting patient or clinical details unless they are required for review.
  • For HR-related disclosures, include a reasonable-accommodation prompt only if your policy requires it and the speaking engagement process could affect access or participation.
  • Maintain an audit trail of submission, review, and approval decisions so policy exceptions and disclosures can be traced later.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Employee Information

This section identifies who is speaking so the submission can be routed, reviewed, and retained in the right employee record.

  • Employee name (required)
  • Work email (required)
  • Department (required)
  • Job title (required)

Engagement Details

This section describes the event itself, which is the core context reviewers need to judge scope, audience, and policy impact.

  • Type of engagement (required)
  • Event name (required)
  • Event organizer / host (required)
  • Event date (required)
  • Event location
    Enter the city, state/province, or virtual platform name.
  • Audience description (required)
    Briefly describe who will attend and whether the audience includes customers, competitors, vendors, students, or the general public.
  • Topic summary (required)
    Summarize the speaking topic and any company-related themes, products, services, or industry issues that will be discussed.

Compensation and Benefits

This section shows whether the engagement includes payment or non-cash value that could change the approval decision.

  • Will you receive any compensation or value for this engagement? (required)
  • Type of compensation
  • Estimated compensation amount
    Enter the estimated total value in your local currency.
  • Describe any other benefits

Conflict-of-Interest Review

This section surfaces the policy questions that matter most: company references, outside affiliations, and possible conflicts.

  • Will you use the company name, logo, or your company title in the engagement materials or introduction? (required)
  • Will you discuss company products, services, clients, vendors, or confidential information? (required)
  • Is the organizer, sponsor, or audience a competitor, vendor, customer, or potential business partner? (required)
  • Describe any potential conflict of interest
  • Has the organizer requested prior approval, a review, or a non-disclosure agreement? (required)

Disclosure, Consent, and Certification

This section creates the acknowledgment and audit trail that the employee understood the disclosure and certified the information as accurate.

  • I understand that this disclosure may be reviewed by HR, Legal, Compliance, or my manager and that additional information may be requested. (required)
  • I certify that the information provided is accurate and complete to the best of my knowledge. (required)
  • Employee signature (required)
  • Submission date (required)

How to use this template

  1. 1. Add the employee information fields and prefill them from your HR system where possible so the reviewer can identify the speaker without asking for extra PII.
  2. 2. Configure the engagement details section to collect the event name, organizer, date, location, audience, and topic summary using the right field types, such as a date picker for the event date.
  3. 3. Set up conditional logic in the compensation section so the amount and benefit description only appear when the employee indicates the engagement is compensated.
  4. 4. Route the conflict-of-interest section to the appropriate reviewer when the employee indicates company-name use, company-business discussion, or competitor or vendor involvement.
  5. 5. Require the disclosure, consent, and certification section before submission, then send the record to HR, Legal, or Compliance with a clear confirmation of what happens next.

Best practices

  • Mark only the fields you truly need as required, and keep optional fields available for edge cases without blocking submission.
  • Use a date picker for the event date, a single-select for engagement type, and a multi-line field only for topic summary or conflict details.
  • Add conditional logic so compensation and conflict follow-up fields appear only when the employee’s answers make them relevant.
  • Include a plain-language disclosure that explains how the information will be used, who will review it, and whether the submission is an approval request or a disclosure notice.
  • Ask whether the employee will use the company name or mention company business before asking for detailed conflict notes, so reviewers can triage faster.
  • Keep the form aligned with the minimum-necessary principle by avoiding collection of sensitive personal data that is not needed for the review.
  • Provide a submission confirmation that tells the employee whether they should wait for approval, proceed with conditions, or expect follow-up questions.

What this template typically catches

Issues teams running this template most often surface in practice:

The employee leaves the audience description too broad, which makes it hard to judge whether the event is public, internal, or vendor-facing.
The compensation section is incomplete because the form does not distinguish between cash payment, honorarium, travel, gifts, or other benefits.
The employee forgets to disclose use of the company name or company business, which can create endorsement or representation concerns.
The conflict details field is used for vague comments instead of a clear explanation of the outside organization and the potential issue.
The form asks for unnecessary personal data, which slows completion and creates avoidable privacy risk.
The reviewer cannot tell whether the submission is pre-approval or disclosure-only because the form does not state the workflow clearly.
The employee signs before all conditional fields are completed, leaving the record incomplete for audit purposes.

Common use cases

Technology executive keynote review
A product leader is invited to keynote a conference and wants to mention the company’s roadmap. The form captures the topic, organizer, audience, and whether the company name or business will be referenced so Legal can review the disclosure.
Healthcare clinician conference panel
A clinician is asked to speak on a panel sponsored by a vendor and may receive travel support. The form records compensation, vendor involvement, and any potential conflict so compliance can assess minimum-necessary disclosure and policy alignment.
University guest lecture approval
An employee is invited to guest lecture at a university and will speak about industry practices without naming the employer. The form documents the event details and confirms whether the session is unpaid and low-risk or needs review.
Financial services webinar disclosure
An analyst is joining a webinar hosted by a trade association and may be quoted as a representative of the firm. The form captures audience, topic, and company-reference fields so compliance can decide whether prior approval is needed.

Frequently asked questions

What is this form used for?

This form is used to review an employee’s outside speaking engagement before or after it is accepted, depending on your policy. It gathers the event details, compensation, audience, and any company-related references so HR, Legal, or Compliance can assess conflicts of interest. It also creates a clear disclosure record and audit trail.

Who should complete and review it?

The employee should complete the form with the event facts they know, and a manager, HR partner, or compliance reviewer should assess the submission. If your policy requires approval before acceptance, route it to the reviewer before the employee confirms the engagement. If the event is already scheduled, use the form to document disclosure and any required restrictions.

When should this form be submitted?

Best practice is to submit it as soon as the speaking invitation is received and before the employee agrees to participate. That gives reviewers time to check for conflicts, compensation issues, and use of company name or business references. If your process allows post-approval reporting, keep the same form but make the timing requirement explicit.

Does this form need to collect compensation details?

Yes, if your policy treats paid speaking engagements differently from unpaid ones. The compensation section should use fields that match the data you need, such as compensation type and amount, plus any non-cash benefits. Avoid collecting unnecessary financial details beyond what is needed for review and recordkeeping.

How does this help with conflict-of-interest review?

The conflict section prompts the employee to disclose whether they will use the company name, mention company business, or speak for a competitor or vendor. That helps reviewers identify potential conflicts, endorsement concerns, or policy exceptions. Conditional logic can surface follow-up questions only when a risk is flagged, which keeps the form shorter and easier to complete.

What are the most common mistakes when using this form?

Common mistakes include leaving the audience description too vague, skipping compensation details, and failing to note whether company branding or business topics will be mentioned. Another issue is making every field required, which can frustrate users and reduce completion quality. The form should also include a clear statement about what happens after submission.

Can this be customized for different approval workflows?

Yes, it can be adapted for pre-approval, disclosure-only, or post-event reporting workflows. You can add conditional logic for paid versus unpaid events, internal versus external audiences, or competitor and vendor involvement. You can also route submissions to different reviewers based on department or job title.

How does this compare with ad-hoc email approvals?

An ad-hoc email thread is hard to search, easy to miss, and often incomplete. This form standardizes the fields needed for a decision, creates a consistent record, and makes it easier to track approvals and exceptions. It also reduces back-and-forth by collecting the right details up front.

What integrations are useful for this template?

Common integrations include HRIS for employee identity fields, workflow tools for routing approvals, and document storage for retaining the submission record. If your process requires signatures, connect it to an e-signature step or a confirmation workflow. Calendar or ticketing integrations can also help track event dates and reviewer deadlines.

Ready to use this template?

Get started with MangoApps and use Outside Speaking Engagement Form with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?