There are two ways to engage in Team Scoring.
Ask a Qualifying Question (link to related article)
Ask a question like: “Which team are you on?” and give the audience a couple of answers, that represent your team names.
Create a Participant List with Close-Ended Descriptor (this solution article)
Create a Participant List (Tools --> Manage Participant List) with a close-ended descriptor (e.g. “Teams”) and fill out the team assignment for each participant.
Open the Participant List Manager:
Click on New List:
Name your Participant List:
When you're entering the Keypad ID, make sure that you use the right format: the ProVOTE Classic keypads need to be entered by their Serial Number (on the back, under the bar code), while all other keypads (both MyVOTE models and ProVOTE TXT or ProVOTE 2) need to be entered by their Keypad ID. Our handy tooltip on the Add Participant page will help you decide:
As you're filling out the Keypad ID and the name of each participant, Add a new Custom Descriptor field:
Name your new Custom Descriptor and make sure that it's a close-ended one:
Add values/names to your Close-Ended Descriptor and Save (click OK):
When you are back to the Participant List, assign each participant to the team you want them to be on:
Once you have a Participant List, make sure that it has all the people you need in it:
Finally, back in Tools --> Settings --> Team Settings, make sure that you tell the software about the Participants you just created:
DON'T FORGET THAT ONLY QUESTIONS WITH CORRECT ANSWERS AND POINTS WILL BE ASSOCIATED WITH TEAM SCORE SLIDES!
Just ask the questions that have correct answer and points assigned to them and the software will track the points according to your team association. Whenever you’d like, you can insert the Team Score slide and show who’s winning at the time. You can insert multiple Team Score slides throughout the presentation to see cumulative standings.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article