Skip to content

Group structure

A release group does not have a universal org chart. Its structure depends on the category it releases, the people available and the amount of work that is automated. A small group may have one person covering several functions, while a long-running group may use separate specialists for sourcing, technical preparation, quality control and packaging.

The roles below describe responsibilities, not fixed ranks or job titles.

Core production roles

Role Main responsibility Where it is most relevant
Coordinator / release manager Organizes work, resolves internal decisions and makes sure a release is complete before it is submitted. Any established group; the role may be shared.
Supplier / source specialist Obtains or identifies suitable source material and verifies that it is genuine, complete and appropriate for the category. All categories, including digital and physical sources.
Cracker / reverse engineer Removes or bypasses copy protection and prepares required technical fixes. Software and games; not a normal requirement for music or ordinary video releases.
Ripper / capper / remuxer / encoder Extracts, captures, remuxes or encodes media according to the relevant ruleset. WEB, television, Blu-ray/UHD and music categories.
Audio / subtitle specialist Selects, synchronizes and checks audio tracks, subtitles and language metadata. Film and television releases, especially multi-language packages.
Packager / release builder Creates the final directory, filenames, archives and accompanying files in the required format. All categories.
Quality control / tester Checks playback or installation, technical properties, completeness, naming and rules compliance. All categories; often performed by several members.
NFO / art contributor Produces the NFO, group branding and release notes. Any group that uses a distinctive NFO or art style.
Tooling developer Maintains internal scripts and tools used for repetitive checks, metadata and packaging. Groups with highly automated workflows.

Names vary between groups. For example, a capper usually records a broadcast or stream, while an encoder transforms an existing source. In a small group both responsibilities may belong to the same person.

Category-specific structure

The release category shapes the group more than a single traditional hierarchy does.

Category Typical specialist responsibilities
Software / 0DAY Source acquisition, reverse engineering, testing, packaging and documentation.
Games / GAMEISO Source acquisition, protection analysis, game testing, disc-image or package preparation and proof.
WEB video Source selection, capture or remux, video/audio/subtitle checks, naming and packaging.
Blu-ray / UHD Disc sourcing, rip/remux/encode work, proof, media analysis and playback QC.
MP3 / FLAC Source verification, ripping or acquisition, audio QC, metadata, playlist and artwork checks.
eBooks / publishing Source or scan preparation, format conversion, metadata, proofing and packaging.

Current category rules define the actual deliverables and checks. The local Current scene rules library is therefore a better authority than any generic list of roles.

Roles around a release group

Some familiar Scene roles belong to the distribution infrastructure rather than to the group that created the release.

Role Function Relationship to a group
Site operator / administrator Maintains a private site and its access, storage and sections. Independent infrastructure; not automatically a group member.
Affiliate liaison Manages the relationship between a group and a site where the group may submit releases. A point of contact, sometimes held by an existing member.
Racer / courier Helps propagate a release between sites after it is submitted. Distribution role; modern automation means it is not always a distinct person.
Nuker / validator Reviews releases against site and category rules and records valid faults. Site or section role, not the group's internal QC.
Pre / announce service operator Maintains systems that record and announce release events. Scene infrastructure rather than production.
Ruleset signatory Represents a group when a category ruleset is agreed. A temporary representative function, not a central Scene authority.

For more context on sites, pre announcements and nukes, see Topsites and the scene system.

From source to release

A simplified responsibility map looks like this:

SOURCE
  > acquire and verify the material
  > perform category-specific preparation
  > test and check rules compliance
  > build the release package and NFO
  > PRE the finished release
  > independent site validation
  > replace or fix the release when justified

Several people can review the same stage, and one person can own several stages. PRE is the point at which a completed package is submitted as a Scene release; it is not simply another word for uploading a file to the public internet. The package itself is explained in Anatomy of a release.

Coordination, not a universal “boss”

Older descriptions often present the group leader as a boss and every other member as a subordinate. Public research and rulesets support a less rigid picture: groups are autonomous teams, leadership is internal and structures differ widely. A coordinator may set priorities, recruit contributors and settle disputes, but does not command other groups, sites or the wider Scene.

Trust still matters because members depend on one another's judgement and discretion. That does not mean every member knows every other member personally, nor that every group uses the same communication system.

What changed

Older shorthand More accurate current view
The supplier gets only physical prerelease media. Sources may be physical, broadcast or digital, depending on the category.
Every group needs a cracker. Reverse engineering is central to protected software and games, but irrelevant to many media categories.
The encoder makes every video release. A WEB release may be a direct download, capture or remux; encoding is only one possible process.
The courier is always a core group member. Distribution can be separate from the group and heavily automated.
One fixed chain produces every release. Workflows and specialist roles follow the category's current rules.

Limits of public knowledge

Release groups do not publish reliable membership lists or complete internal procedures. Names used in NFOs and public reporting can describe handles, teams or historical identities rather than a stable roster. This page therefore documents observable functions and avoids treating unverifiable claims as a universal model.

Sources & references