> For the complete documentation index, see [llms.txt](https://docs.lamsfoundation.org/tbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lamsfoundation.org/tbl/tbl-for-teachers/getting-started/tbl-design-wizard-1/design-details-and-teams.md).

# Design Details & Teams

On this first step, you need to name your learning design and set the team formation criteria.

### Naming your TBL design

Enter a **meaningful name** for your learning design. Make sure you use a name that reflects the purpose of the lesson. 

![Adding design name](/files/-MRTDSBZYXZXpEWOPJso)

{% hint style="warning" %}
The design that you create at the end of the TBL wizard can be reused in as many courses as you like. So your designs are not bound to a single lessons, but are truly re-usable learning designs. 
{% endhint %}

### Select team formation criteria 

![Selecting team allocation preference](/files/-MRTDz1i5sxgwI6GkTFp)

Teams can be set in a variety of ways to suit the classroom environment.

**Random allocation**: in Random allocation, you can either choose to set the number of total teams needed, or the number of students to be within each team. In either of these circumstances, the students will be randomly allocated to their team, and they will stay within these teams for any of the activities in the TBL lesson. 

**Teacher’s choice**: in Teacher’s choice, students are assigned to their team by you in the LAMS Monitor environment by simply drag and drop the students name into their team container (this is described in more detail in the monitoring section).

**Learner's Choice**: this option allows learners to choose their own team.

{% hint style="info" %}
For TBL, you might want to select **Teacher's choice** as it will then allow you to manually assign your students using pre-configured teams that can be used for the entire semester. 
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lamsfoundation.org/tbl/tbl-for-teachers/getting-started/tbl-design-wizard-1/design-details-and-teams.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.