# Teams and Guilds


A **Team** is a group of Contributors who learn and work together. A **Guild** is a team that has earned a public, scored standing, and whose name rises and falls with the work done under it. A Developer organization can work with either one as a supply partner instead of recruiting each Contributor separately.

Most of this is not released yet. Each section below says so where it applies, and [What works today](#what-works-today) lists what you can use now.

## Why work in a team

> **Not released.** Creating a team, inviting members, and the team features in this section are not available in the production Contributor portal.

Working alone, you learn a Campaign's standards from its instructions and from your own rejected submissions. A team shortens that.

- **Learn from people doing the same work.** Members share best practices with named authors and real examples, so a newcomer can see how experienced members handle the hard cases.
- **Agree on how you work.** A team can publish a policy, such as a quality checklist, that each member reads and acknowledges. A newer version asks for a new acknowledgment and never rewrites what you accepted before.
- **Take on work too large for one person.** A team lead can agree a quantity and a deadline with a Developer, then split it into assignments. You commit only when you accept your own share.
- **Build a record others can see.** A team profile can show **publicly shared work**: the tasks members chose to make public, how many were accepted, and the acceptance rate over one stated period. It never presents this as all of the team's work, and a contributor's name appears only if that contributor allows it.

You can belong to several teams at once. Each team keeps its own chat, policies, and assignments.

**What stays yours.** You still do each task under your own account. Your submissions, course results, credentials, reputation, and earnings remain individual records. Leaving a team ends the membership. It does not delete your work, hand your earnings to anyone, or change who is credited with what you already did.

### Team roles

| Role | Responsibility |
| --- | --- |
| Steward | Publishes the team profile, assigns roles, hands over leadership, and accepts or ends partnerships on the team's behalf |
| Lead | Within the authority granted, handles invitations and join requests, curates shared practices, and proposes assignments |
| Contributor | Answers for their own membership and responds to assignments. Membership alone gives no authority over other members |

A Steward cannot sign your personal agreements for you, or present their own course results, reputation, or verification as if every member had met them.

## Why a Guild

> **Not released.** Guilds, Guild tiers, and the Guild premium are not available in production.

A Guild turns a respected Contributor's following into organized, accountable supply. Its leader recruits people, trains them, and holds them to a standard. A Guild is not created from scratch: a team becomes one once it has earned it. That takes time together, members who stay active, accepted work done under the team's name, and a leader with a strong personal record who has brought new people to their first accepted task.

A Guild's standing is a **Guild Reputation Score** and a **tier** from 0 to 4, calculated only from work members do **under the Guild's tag**. Work you do on your own never counts toward a Guild, and work done under the tag always does.

| What happens under the Guild tag | Effect on the Guild |
| --- | --- |
| A member's work is accepted | The Guild's score rises |
| A member's work is rejected, or a member receives a strike | The Guild's score falls by roughly three times what an acceptance adds |
| The leader acts promptly on a struggling member | The damage fades faster, and the score credits the leader's stewardship |
| The Guild delivers committed quantities on time | Its reliability rises; small, always-met commitments count for little |

That asymmetry is the point: a name that could only go up would tell a Developer nothing.

**What members get.**

- Access to Campaigns that admit only Guilds of a minimum tier. From tier 4, a Developer can reserve a Campaign for a named Guild.
- A share of the Guild premium described below, on top of the normal reward.
- A permanent Passport record of the Guild, your rank, your tenure, and the Guild's tier while you were in it.

**What a Guild cannot do to you.** Other members' mistakes never lower your personal reputation score. If the Guild's tier falls because of performance, its perks stay for a grace period, which gets shorter each time it happens again; after a confirmed integrity violation they end at once. Either way you lose perks, never your record. Your earnings and payout route stay yours, and leaving costs nothing you have earned. A leader who asks for off-platform dues, or tries to redirect your payments, breaks the leadership terms.

**History is public.** A Guild's profile shows its full tier history, including drops, periods at risk, recoveries, and strikes. A strike that was overturned stays visible and is marked vacated.

### How the Guild premium is paid

The premium is paid by the Developer, not taken from members.

1. When authoring a Campaign, the Developer chooses a premium rate within the band the Guild's tier permits. The rate is fixed when the Campaign is accepted.

   | Guild tier | Premium the Developer can set |
   | --- | --- |
   | 0–2 | None |
   | 3 | 5% to 15% |
   | 4 | 5% to 20% |

2. For each accepted submission, the member keeps the **full reward** they would have earned working alone.
3. The premium adds an extra amount to that submission. The leader's share of the **extra only** is set between 20% and 80% in the Guild's signed charter, and cannot be changed afterward.
4. The rest of the extra goes to the member who did the work.

For example, a task pays 10.00 and the Developer set a 10% premium, so the extra is 1.00. With a 30% leadership share in the charter, the leader receives 0.30 and the member receives 10.70. The Developer pays 11.00.

There is no Guild reward multiplier and no cut from the base reward. Leadership is one level deep: no one earns from the people a member recruits. Every member can see the Guild's leadership share.

## Why a Developer organization works with a team

> **Not released.** Partner teams, delivery orders, Guild admission, and the Guild premium are not available in the production Developer portal.

Recruiting Contributors one at a time works for a small study. When you need steady volume or scarce expertise, a team or Guild gives you:

- **One counterpart for capacity.** You agree a quantity and a deadline with a team lead instead of waiting to see who joins. The lead commits only after members accept their shares, so the promise reflects people who have actually agreed to the work.
- **A track record before you commit.** A team profile shows its specialties and the acceptance record of its publicly shared work. It lists a Developer as a partner only when both sides agree to be listed, so a partnership you start stays private unless you choose otherwise.
- **Quality with consequences.** A Guild loses more for a rejected submission than it gains for an accepted one, and that history is public. The leader is paid only on accepted work, so it pays to recruit selectively and to act early on weak work.
- **Training you don't have to run.** A Guild can require its own courses before members work under its tag, on top of what your Campaign requires.
- **A dedicated channel.** An active partnership has a shared room for briefs, capacity, and delivery. The team's internal chat and members' private records stay private.
- **Access you control.** You can admit only a partner team, Guilds of a minimum tier, or, from tier 4, one named Guild. Admission by team, by Guild, and by a named member list is planned; see [Run a private pipeline for a contracted team](/tasks/use-cases#run-a-private-pipeline-for-a-contracted-team).

**What you pay.** The Campaign's normal reward, as today. A Guild premium is optional: you decide whether to offer one, and at what rate within the Guild's band.

**What does not change.** Each Contributor still meets your Campaign's requirements individually, and each submission is still reviewed and credited to the person who made it. A partnership gives Contributors no role in your organization, and gives your members no authority over the team.

<a id="what-works-today"></a>
## What works today

**Contributors.** Team relationships already on record appear under **Passport → Roles & teams**. That view summarizes records; it is not a team-management workspace. Having no team relationship does not stop you from joining a Campaign: [join a Campaign and complete a task](/tasks/participate) on your own. Today, team membership does not share eligibility between members, and it does not create a collective payout.

**Developers.** To work with a group of Contributors you already know, use an invite code on the Campaign's **Entry Gate**, as described in [Run a private pipeline for a contracted team](/tasks/use-cases#run-a-private-pipeline-for-a-contracted-team). To work with colleagues, invite them to your [Developer organization](/collaboration/organization).

[Feature availability](/help/updates) tracks Contributor Teams. To ask whether a collaboration feature is open to your account, contact [hello@humanbased.ai](mailto:hello@humanbased.ai).