Skip to main content
A position is a functional role your organization staffs for: Lead Vocals, FOH Engineer, Tour Manager. Define each one once at the organization level, then reuse it in onboarding, call lists, gig team-building, and crew availability.

​
Positions vs roles

Positions describe the work someone does. Roles describe their access. They’re independent. For example, someone can be a Member with positions for Guitar and Vocals, while a Gig Coordinator schedules gigs without any performance position at all.

​
Why define positions

  • Consistency: standardized role names across every gig and report
  • Speed: pick from a list instead of retyping roles each time
  • Matching: members carry positions, so Soundcheck can suggest the right people when you staff a gig
  • Coverage: see who can fill each role and spot gaps

​
Managing the catalog

1

Open Positions

Settings → People → Positions. The Teams tab or page lists roster templates (+ New template); it does not manage the position catalog. Your active positions show grouped by section, such as Vocals, Strings, Brass, Percussion, and Production.
2

Add positions

Open Add positions. Pick from the built-in list (use Search positions… to find one), or create your own under Create custom position: with a name, an optional short code, and a section.
3

Set details

Give a position a short code (for example MV), used on the roster and shift board. Set a default day rate for the position.
4

Hide or delete

Hide a position you don’t use; hidden positions stay listed below the active ones so you can show them again. Custom positions can also be deleted.
5

Save

Changes stay pending until you choose Save Changes. Cancel discards them.
Keep names professional, since they can appear on invoices and contracts.
Deleting a position removes it from historical assignments. If you may need it for records, hide it rather than deleting.

​
Positions and imports

When you import events or members, Soundcheck matches each position name (case-insensitively) against your catalog.
  • Match found → the member is linked to the existing position.
  • No match, auto-create on → the position is created automatically and added to your catalog, then linked. Subsequent rows with the same name reuse it.
  • No match, auto-create off → the row is skipped with a warning: “unknown position — skipped (add it to the org catalog or enable auto-create).”
The placeholder name default (common in exports from other tools) is treated as a non-position and skipped. It never creates a catalog entry.
If you’d rather control your catalog tightly, seed your positions first and leave auto-create off. Unknown names then surface as warnings you can review instead of silently expanding the list.

​
Member positions

Members carry the positions they can fill. These are set two ways:
  • By the member during onboarding (the Positions step) or on their profile.
  • By an owner or admin directly from the member’s profile.
Saving a member’s positions replaces their previous set rather than adding to it. Review the full selection before saving.
Assigned positions feed availability requests, saved team presets, onboarding, and gig team-building. Org-wide crew calendars may be unavailable depending on your plan and which features are turned on for your organization.

​
Positions during onboarding

Add a Positions onboarding step so members pick the roles they play from your active catalog. The step assigns from the existing catalog only. Create or update your positions first so the choices are right.

Organization setup

Add the Positions step to onboarding.

​
Positions on a gig

When building a gig’s team:
1

Add a position

In the gig’s team section, add a position from your catalog.
2

Add multiples as needed

The same position can appear several times (2× Background Vocals, 3× Security).
3

Set per-position detail

Performance fee, fee notes, and any special instructions.

​
Naming conventions

Consistent names keep reporting and staffing clean:
  • Prefer “Lead Vocals” over “singer”; “Sound Engineer (FOH)” over “Sound”
  • Group with prefixes: “Vocals - Lead”, “Vocals - Background”, “Guitar - Lead”, “Guitar - Rhythm”
  • Standardize across the org: “Lead Guitar”, never a mix of “Lead Guitarist” and “Guitar 1”

​
Troubleshooting

Confirm it’s saved in the catalog and refresh the gig. Check you have permission to edit the gig.
Those names weren’t in your catalog and auto-create was off. Add them to the catalog (or enable auto-create) and re-run the import.
Only custom positions can be deleted. Hide a built-in position instead. Hiding also preserves history for a position in use on active gigs.

Teams overview

How team management fits together

Call lists

Saving rosters with call order

Team building

Staffing events

Imports

Bulk-load events and members