Write a short participation plan

Imagine a township scheduling an internal Teams training session with its software vendor. Office staff need to watch a demonstration, two employees will ask questions, and the vendor needs to share a sample application. Before the call, the organizer should know how each person will join, who can present, and who will handle people waiting to enter.

For Michigan township, village, and city teams, start with one scheduled staff briefing or vendor workshop. Write down the purpose, named invitees, presentation needs, and responsible organizer. Identify a covering employee for practical meeting support. Agree on the sample material appropriate to the session and give the vendor a known municipal contact for joining problems.

Confirm how outside invitees will join

Microsoft distinguishes outside participants who join as guests, people from trusted organizations, or anonymous participants. Its meeting guidance explains that administrators control the availability and defaults of many meeting features. Ask IT to confirm the approved joining method for the actual vendor and municipal meeting setup. Include anyone using an alternative device or a planned telephone connection.

Give invitees clear instructions about the intended account, meeting link, and contact for help. Have the vendor confirm which person will attend and demonstrate the application. If a replacement presenter is needed, update the organizer through the agreed contact route. Bring an access problem to IT with the meeting details and the message shown to the participant, while keeping unrelated municipal information out of the support material.

Assign presentation permissions for the task

Microsoft lists organizer, co-organizer, presenter, and attendee capabilities separately. Presenters have content-sharing capabilities and broader meeting permissions than attendees. Have the organizer review the available Who can present setting with IT and select the arrangement approved for the session. Match the planned demonstration to the people who actually need those capabilities.

Microsoft's role instructions require sending the invitation before assigning roles. Review the resulting options before the scheduled call. Meeting type matters: Microsoft's guidance says selecting specific presenters is unavailable for channel meetings. Have IT demonstrate the workflow for the meeting type your office uses, including how an authorized host will handle an approved presenter change during the session.

Assign someone to manage the lobby

Teams lobby settings cover who can enter directly and who must wait. Microsoft also documents a separate control for who can admit waiting participants. Review both with IT and the organizer. Confirm the actual settings for this meeting, including any participants joining by telephone, and name the person responsible for monitoring the waiting area.

Give that person the expected participant list and an agreed method for checking an unfamiliar arrival. Have the organizer decide how unexpected or changed attendance should be handled. In the township training example, the staff host can confirm a substitute vendor representative through the known vendor contact before admitting them. Arrange coverage for lobby monitoring while the main presenter is occupied with the demonstration.

Rehearse entry and a presenter handoff

Use a short rehearsal with approved participants and harmless sample content. Have the outside participant follow the intended invitation and joining method. Confirm the expected lobby experience, admission by the authorized host, and the role assigned after entry. Then ask the designated presenter to share the planned sample material while another person checks what attendees receive.

Practice the planned handoff between municipal staff and the vendor. Confirm who can make the approved role change and that the next presenter can continue the demonstration. Record any blocked setting, confusing instruction, or unexpected permission and give it an owner. Resolve the issue through the approved meeting setup with IT before using the workflow for the scheduled training.

Check series changes and organizer coverage

For recurring workshops, confirm the intended scope before changing roles. Microsoft distinguishes role reassignment through calendar meeting options, which applies to future occurrences, from a reassignment in the meeting's participant controls, which applies to that occurrence. Have IT show the difference in the office's deployed Teams experience and verify the result against the organizer's plan.

Microsoft also states that the meeting organizer role cannot be changed. Have IT confirm what the covering employee can actually do if the organizer is away and how the office will handle any remaining gap. Review the participation plan when staff, vendors, or meeting purposes change. Keep the verified setup and unresolved questions with the internal session's preparation notes.

Keep this checklist with the invitation plan

Review these details for one internal staff meeting before its next session.

  • Purpose, named invitees, organizer, and covering employee.
  • Approved outside-participant joining method and help contact.
  • Presenter assignments matched to the planned demonstration.
  • Lobby entry settings, admission permissions, and monitoring coverage.
  • Verified entry, sample presentation, and presenter handoff.
  • Scope of recurring changes and the result of any corrections.

YOUR NEXT STEP

Prepare one internal Teams session from invitation through presenter handoff. Confirm the outside participant's joining method, the meeting roles, and lobby coverage, then rehearse the setup with approved people and sample information.

Need a hand putting a plan in place? Explore our Managed IT services for Michigan municipalities or talk with our team.

Further reading