Best for
privacy-sensitive event teams, HR teams, executive teams, healthcare or public-sector conveners
Private local team formation tool
Create teams from sensitive attendee data without uploading rows to a vendor. TeamCreator runs in the browser and clears data when the tab closes.
Direct answer: If attendee data is sensitive, use a local browser team-formation tool: paste rows, create teams, download assignments, and close the tab. TeamCreator does not upload, store, or inspect the list.
Preset
Any preset
Team size
Set by the room and the assignment
Use these attendee columns
A name column is enough to start. These columns make the grouping smarter for this use case; extra spreadsheet columns become custom sliders automatically.
For private local team formation, start with name, role, organization, expertise. Add location, custom fields only when needed when the session needs better matching, more diverse groups, or cleaner follow-up.
nameroleorganizationexpertiselocationcustom fields only when needed
Recommended TeamCreator setup
Use the preset as a starting point, then move only the sliders that express the room design. Similar sliders cluster people who share a field; diverse sliders spread that field across teams. Positive ask-and-offer fit helps when participants submitted what they need and what they can contribute.
Slider move
Use only columns required for the grouping decision.
Slider move
Remove sensitive notes before pasting.
Slider move
Keep the downloaded assignment file in the same secure workflow as the source list.
Constraints to review
Constraints are the manual safety layer. Add keep-together rules for hosts, accessibility needs, or required pairs, and keep-apart rules for reporting lines, conflicts, competitors, or pairs that would reduce candor.
- Do not send attendee rows to third-party AI services unless the event owner explicitly approves.
- Do not paste unnecessary personal data.
How to create the teams
- Export or copy the attendee list with the columns needed for the grouping decision.
- Open TeamCreator and paste the rows or load the CSV file.
- Choose Any preset and set the team size to Set by the room and the assignment.
- Tune the similar-or-diverse sliders: Use only columns required for the grouping decision. Remove sensitive notes before pasting.
- Add keep-together or keep-apart constraints, then create and review the teams.
- Download the assignment CSV and use it inside the room plan.
After the groups are formed
The assignment is only useful if the room knows what to do with it. Put the group number into the agenda, open with a prompt that matches the relationship goal, and make the follow-through visible before people leave.
- Test with the sample before using real data.
- Run the final assignment locally.
- Delete local working files according to your event data policy.
Before and after example
Manual grouping
The manual version usually starts with a spreadsheet sort, a last-minute shuffle, or a randomizer. That can be fast, but it tends to over-seat colleagues together, miss useful ask-and-offer matches, and leave sensitive keep-apart rules to memory.
Designed grouping
The TeamCreator version starts from the outcome: if attendee data is sensitive, use a local browser team-formation tool: paste rows, create teams, download assignments, and close the tab. teamcreator does not upload, store, or inspect the list. The organizer uses Any preset, sets the group size to Set by the room and the assignment, checks constraints, and exports assignments that fit the room plan.
Export and room-plan examples
Useful exports for private local team formation include a facilitator copy with every assignment, a participant-facing list with only names and table numbers, a CSV for badge or check-in systems, and a follow-up version that includes the next prompt or owner.
Want a second set of eyes? Send the use case, not the attendee list: the event goal, group size, available columns, and the rules that matter. We can suggest a TeamCreator setup and a short room plan without touching private participant data.
Common questions
What columns does TeamCreator need for private local team formation?
A name column is enough to start, but useful columns include name, role, organization, expertise, location, custom fields only when needed.
Does attendee data leave the browser?
No. TeamCreator parses, scores, and forms teams in the browser. United We Transform does not receive, store, or inspect the attendee list.
What is the best preset for this use case?
Start with Any preset, then adjust the sliders to match the session goal and any keep-together or keep-apart rules.
What constraints should I check manually?
Review constraints such as Do not send attendee rows to third-party AI services unless the event owner explicitly approves.; Do not paste unnecessary personal data.