Skip to main content
This page answers the questions people ask when they choose a tool for event tasks, whether they call it a checklist, a task list, the to-dos, the advance or the production checklist. Each answer starts with Yes, Partly or No, says how, and links the page with the detail.
A gig's Checklist tab with sections, their completion rings, and each task's owner, due date and statusA gig's Checklist tab with sections, their completion rings, and each task's owner, due date and status
When Soundcheck doesn’t do something today, the answer says so and gives the best way to work around it. Terms such as relative due date, advance and strike are defined in the Checklist glossary.
How to read the answers. Yes means Soundcheck does it today. Partly means it covers part of the need, and the answer says which part. No means it doesn’t, and the answer gives the workaround. A question marked Buyers ask this first is one where the wrong answer usually loses the deal or lets a task slip until show day.

Questions this page answers

Deal-breakers at a glance

These 19 questions decide most evaluations. Soundcheck answers Yes to 5, Partly to 9 and No to 5.

Worked example: a corporate conference that gets postponed

A production company runs a two-day corporate conference: advance with the hotel ballroom, load-in the night before, two show days and a strike. Halfway through planning, the client moves the conference back two weeks. Here’s how the deal-breakers play out.
1

Set up the template once

An Owner, Admin or Gig Coordinator adds the Corporate starter pack (sections Advance, Event day and Wrap), then adds due dates such as 3 weeks before and Day of show, and an Owner position such as Production Manager on each task (questions 12, 17 and 21). Tagging it with the Corporate gig type makes it the pick for corporate gigs (question 13).
2

Create the gig

Creating the gig applies the template, and every due date is counted from the first day of the conference. Owners fill in only for positions someone has already accepted, so the producer staffs the gig, then assigns the rest with Select → Assign to (questions 18 and 38).
3

Work the advance

The hotel is shared as a collaborator, with the advance tasks ticked to share. Their coordinator marks tasks done on the shared page. The dock, parking and load-in details go on the hotel’s venue record, so the next gig there starts with them (questions 48 and 49).
4

Handle the postponement

Moving the gig doesn’t move its tasks. The producer chooses Select, ticks the open tasks, and uses Due date → +7 days twice (question 22).
5

Show days

Crew tick their tasks in the mobile app, with signal (questions 72 and 73). The gig’s completion ring shows how much is done (question 78).

Building a checklist

Yes. Add a section, then type tasks under it one after another. To skip typing, choose Paste data and paste the list from a spreadsheet, email or doc, or start from a template with Use template. See Working a gig’s checklist.
Yes. Each checklist is made of named sections, and each section header shows its task count and a progress ring. You can rename, collapse and delete sections. See Working a gig’s checklist.
No. Soundcheck doesn’t have sub-tasks today. Give the group of steps its own section, or list the steps in the task’s notes. See Working a gig’s checklist.
No. A task is Not started, In progress or Complete, and there’s no “not applicable” status. Add a label such as Not needed and mark the task Complete, or delete it. See Working a gig’s checklist.
No. Tasks and sections keep their order, on the web and in the app. In the mobile app’s edit mode you can Move a task to another section. Name tasks so their order reads well, or put them in sections in the order you work. See Checklist in the mobile app.
Partly. In the mobile app, choose Edit tasks, then Add a task under a section. There’s no voice capture in Soundcheck, but your phone keyboard’s dictation works in the title field. See Checklist in the mobile app.
Partly. Tasks you add have a due date but no time. When you put someone on a run of show item, Soundcheck makes them a task that carries the item’s time, such as 2:30 PM – 2:45 PM. Run of show is in early access and rolling out; contact info@soundchecklive.io. See Automatic tasks.
No. Each gig has one checklist. Use a section for each list, such as Planning, Production, Client and Venue. See Checklist.
Partly. Automatic tasks are linked: run of show tasks to their item, act tasks to a position on the act, and close-out tasks to the contract, deposit, invoice or settlement step they stand for. A task you add yourself can’t point at a record. Name the record in the title and paste its link in the notes. See Automatic tasks.Buyers ask this first.
Partly. Close-out tasks complete themselves when you tick the matching step on the gig’s Closeout tab, and a signed contract ticks Contract signed on its own. Tasks you add yourself are completed by hand. See Automatic tasks.

Templates and reuse

Yes. Build templates on the Checklist page. A new gig gets the template you pick, the one matched to its gig type, or your organization’s default. See Checklist templates.Buyers ask this first.
Yes. Tag each template with gig types. When you create a gig, Soundcheck picks the template for its type and shows Picked for… in the form, and you can choose another or None. See Checklist templates.
No. Use template only appears on a gig with no checklist, and a template never merges into an existing one. Add the missing tasks by hand, or paste them in with Paste data. See Checklist templates.
No. Each gig gets its own copy when the template is applied, and later template edits don’t change it. Make the change on each upcoming gig, using Select to edit several tasks at once. See Checklist templates.
Yes. On the gig, choose Task actions → Save as template. It keeps the sections, task titles and notes, but not due dates or owners, so add those in the template editor. Owners, Admins and Gig Coordinators can save templates. See Checklist templates.
Yes. Every organization starts with a Standard Tasks template, and there are 11 starter packs: Production, Venue, DJ, Band, Producer, General, Wedding, Corporate, Festival, Tour and Private party. Packs hold task titles only, so add due dates and owners after you add one. See Checklist templates.
Partly. Each template task can have an Owner position. When the template is applied, the task goes to the person who accepted that position on the gig first. Matching happens only then, so a position filled later leaves the task unassigned. To fill owners, staff the gig before you apply the template. Set owners in the web editor, because saving a template in the mobile app clears its owners and due dates. See Checklist templates.Buyers ask this first.
Yes. A template is applied when the gig is created. Soundcheck doesn’t apply one later, for example when the gig’s status changes, so the template must be in place before you create the gig. See Checklist templates.
Partly. You can keep as many templates as you like, but a gig gets one template. Build a combined template with a section per department, or name department templates clearly and add the extra tasks with Paste data. See Checklist templates.

Due dates and timing

Yes. In a template, each task’s Due is a number of days before or after the gig’s first day, from presets such as 30 days before, 1 week before, Day of show and 1 week after. When the template is applied, each task gets a real date. See Checklist templates.Buyers ask this first.
No. Rescheduling a gig doesn’t move its task due dates. Choose Select, tick the tasks, and use Due date to shift them by 1 or 7 days at a time, up to 200 tasks at once. See Changing several tasks at once.Buyers ask this first.
No. Template due dates count only from the gig’s first day. Work out the offset from the first day, for example 1 day before for a load-in the night before. See Checklist templates.
Yes. A template due date can be before the gig, on the day, or after it, and a task on a gig can have any date. See Checklist templates.
No. Offsets count calendar days. Pick offsets that land on weekdays for your usual show days, or move a weekend date by hand. See Checklist templates.
No. A due date is a day, with no time. Only run of show tasks carry a time, taken from their item. Put a time in the task’s title or notes when it matters. See Working a gig’s checklist.
No. Soundcheck has no calendar view of tasks. Use Your tasks, which lists your open tasks across gigs in date order. See Your tasks.
No. Task due dates aren’t in Soundcheck’s calendar feeds or calendar sync. Check Your tasks with the Due this week filter instead. See Your tasks.
Partly. Your tasks shows everything assigned to you across gigs, with Overdue and Due this week filters and Due today on each row. There’s no view of everyone’s tasks across all gigs, so a manager checks each gig’s Overdue filter. See Your tasks.Buyers ask this first.
Partly. Give the task that day as its due date, or group tasks in sections such as Load-in, Show day 2 and Strike. Template offsets count from the first day, so a strike task on a three-day show is 2 days after. See Working a gig’s checklist.
Partly. Due dates are days, and Today and Overdue follow the gig’s time zone. Run of show task times on the web show in your device’s time zone. See Working a gig’s checklist.

Assigning and ownership

Yes. Each task has one assignee, chosen from your organization’s members on the gig. They get a push notification and see the task in Your tasks. See Working a gig’s checklist.Buyers ask this first.
Partly. Run of show tasks follow the people on the item, and act tasks fill from the crew who accepted that position. A template’s Owner position is matched once, when the template is applied. A task you add yourself goes to a person, not a role. See Automatic tasks.
No. A task has one assignee. Add a copy of the task for each person, or put the job on a run of show item, which gives everyone on the item their own task. See Working a gig’s checklist.
Partly. Assignees must be members of your organization. To hand work to a venue, vendor or other outside team, share the tasks with them as a collaborator, and they can update the status from their shared page. Clients don’t see gig tasks. See Sharing a gig.
Partly. A collaborator signs in with their own Soundcheck account and doesn’t take a seat on your plan. They can mark shared tasks done or reopen them. There’s no way to complete a task without signing in. See Sharing a gig.
No. Each person sees their own tasks across gigs in Your tasks, but a manager can’t open someone else’s list. On one gig, type the person’s name in Search tasks or people. See Your tasks.
Partly. On a gig, choose Select, search for the person, tick their tasks, and use Assign to. Repeat on each gig, because bulk changes work one gig at a time. See Changing several tasks at once.
No. The assignee marks a task Complete and there’s no approval step. Add a second task such as Review: … assigned to the manager. See Working a gig’s checklist.

Reminders and notifications

No. Soundcheck sends a push notification when a task is assigned, and nothing before or after the due date. Ask your team to check Your tasks with the Overdue and Due this week filters. See Your tasks.Buyers ask this first.
Partly. Task notifications arrive by push in the mobile app only. There’s no email or text message for tasks. See Your tasks.
No. There are no due-date or overdue reminders. The gig’s Overdue filter and Your tasks show what’s late. See Your tasks.
No. There’s no task digest. Open Your tasks and choose Due this week. See Your tasks.
No. Clients don’t see gig tasks and get no task reminders. Send forms, agreements and invoices through the client portal, which is in early access and rolling out; contact info@soundchecklive.io. See Client portal.
Yes. Each person can turn off the Checklist tasks push in their notification settings without turning off anything else, such as Gig changes. Owners and admins can also set it in the organization’s Notification defaults. See Your tasks.
No. Soundcheck doesn’t notify anyone when a task is completed, and tasks have no comments. Watch the gig’s completion ring, or filter by Done. See Working a gig’s checklist.

Advancing a show

Partly. The Production, Venue, Corporate and Festival starter packs each start with an Advance section, and the Tour pack has Before the run. Edit the tasks to cover your full advance. There’s no structured advance form with questions and answers. See Checklist templates.Buyers ask this first.
Partly. Share the gig with the venue or promoter as a collaborator and tick the advance tasks to share. They mark tasks done, add files and leave notes on their shared page. Sharing the venue role also gives them a Confirm load-in, specs and curfew request. See Sharing a gig.
Partly. The venue record keeps Load-in, Load-out, Dock, Parking, Access code and other details, plus restrictions such as curfew, and they fill every gig at that venue. Checklist tasks don’t write back to the venue, so copy the answers onto the record. See The venue record.Buyers ask this first.
Yes. Use one section for each part, such as Advance: hospitality and Advance: production, and assign each task to the person who owns it. See Working a gig’s checklist.
Partly. Tasks have three statuses: Not started, In progress and Complete. Use In progress for asked, and a label such as Problem for items that need attention. See Working a gig’s checklist.
No. Soundcheck doesn’t compare advance answers with a rider. Keep the rider on the gig’s Documents tab and add a task to check it against the venue’s specs. See Working a gig’s checklist.
Partly. Each gig shows its completion ring and a progress ring per section, so an Advance section tells you that show’s status. There’s no grid across gigs, so you check each show. See Working a gig’s checklist.Buyers ask this first.
Partly. Details saved on the venue record show on every gig there, on the Venue tab. Checklist tasks don’t feed the run of show, so enter times there yourself. See The venue record.
Partly. Most teams start two to four weeks out. Give advance tasks template due dates such as 3 weeks before, and they’re created with the gig and assigned to their owners. Soundcheck doesn’t send anything to the venue by itself. See Checklist templates.
Partly. The Festival starter pack has an Advance section to edit. Slot times live in the run of show, and acts on it get a task per seat on the act’s team. Changeover and backline are tasks or notes, not fields. Run of show is in early access; contact info@soundchecklive.io. See Automatic tasks.

Production checklists

Yes. Add a Load-in section with a task per check and assign each one. Crew tick their own tasks in the mobile app. See Checklist in the mobile app.
Partly. Add the checks as tasks. A time comes only from the run of show, so put each check on a run of show item and the people on it get a timed task. See Automatic tasks.
Partly. Add a Strike section with tasks such as Venue damage check. The gear count lives in inventory, where gear is ticked In as it comes back. See Packing out and back in.
Partly. The checklist isn’t tied to gear, but the gear booked on the gig has its own Out and In ticks on the Inventory tab and the Pack sheets. Gear not back in shows as still out. See Packing out and back in.Buyers ask this first.
No. Tasks don’t take photos or files. Upload photos to the gig’s Documents tab. See How the Checklist works with the rest of Soundcheck.
No. Tasks have no value fields. Someone who can edit the checklist can type readings into the task’s notes. See Working a gig’s checklist.
Yes. Give each department its own section in the gig’s checklist, and use the search box or labels to narrow down. See Working a gig’s checklist.
Yes. The Task completion ring and each section’s ring show progress, and the Overdue filter shows what’s late. In the mobile app, managers see the whole list with its progress. See Working a gig’s checklist.
Partly. Write the problem in the task’s notes, add a label such as Problem, and add a new task for the follow-up. There’s no issue type that links the two. See Working a gig’s checklist.

Client and vendor tasks

No. The client portal doesn’t show gig tasks. Its own to-dos cover agreements, forms and payments, so send the guest count and song list as forms. The client portal is in early access; contact info@soundchecklive.io. See Client portal.Buyers ask this first.
No. Clients can’t see or tick gig tasks. Track their part with a task assigned to you, and tick it when the form or payment arrives. See Client portal.
Yes. Clients never see gig tasks, and a collaborator sees only the tasks you tick to share. See Sharing a gig.
Partly. Share the gig with the vendor as a collaborator and tick their tasks. They update the status, and you see it on the gig’s checklist. The task’s assignee stays someone in your organization. See Sharing a gig.
No. Clients don’t see tasks. You choose when to send forms and invoices to the portal. See Client portal.

Crew on mobile and show day

Yes. The mobile app shows each gig’s tasks and a My checklist list across gigs. Crew can mark their own tasks done, in progress or not started, even without edit rights on the gig. See Checklist in the mobile app.Buyers ask this first.
No. Ticking and editing need a connection, and changes aren’t queued. A checklist already open stays readable, but it isn’t kept after the app restarts. Download the checklist as a PDF before you lose signal. See Checklist in the mobile app.Buyers ask this first.
Partly. In the mobile app and in Your tasks, crew who don’t manage the gig see only the tasks assigned to them. On the web gig page, people who can open the gig see its whole checklist. See Checklist in the mobile app.
Partly. Managers see every task with its assignee and status, with Mine, Unassigned and Overdue filters. There’s no summary by person. See Checklist in the mobile app.
No. There’s no check-in task. Add an Arrived on site task for each person, and they tick it on their phone. See Checklist in the mobile app.
No. Tasks push only when they’re assigned. Keep show-day times in the run of show. See Your tasks.

Status, progress and reporting

Yes. Each gig’s checklist shows a Task completion ring, a ring per section, and a bar splitting complete, in progress, not started and overdue. See Working a gig’s checklist.
Partly. Each gig’s Overdue filter shows its late tasks, and Your tasks shows yours across gigs. There’s no list of at-risk gigs. See Working a gig’s checklist.
No. There’s no task dashboard across gigs. Each person uses Your tasks with Due this week. See Your tasks.
Partly. On a gig, search by title, notes or person, and filter by All, Open, Overdue or Done. Your tasks filters by gig and by Overdue, Due this week or In progress. There’s no filter by section or date range. See Working a gig’s checklist.
No. Soundcheck doesn’t show who completed a task or when. It records when a task is assigned and when a collaborator changes a shared task’s status. Ask people to add a note such as Done by Sam, 3 PM on tasks that need a record. See Checklist troubleshooting.Buyers ask this first.
Yes. In the gig’s Export menu, choose Export Checklist… to download a PDF or CSV. See Working a gig’s checklist.
No. Soundcheck doesn’t record when a task was completed, so it can’t report late tasks. Filter by Overdue before the show to catch late ones, and note them for the template. See Checklist templates.

Dependencies and automation

No. Tasks have no dependencies. Put them in order in one section and give the later task a later due date. See Working a gig’s checklist.
No. Nothing moves or gets flagged. Shift the later tasks with Select → Due date. See Changing several tasks at once.
Partly. Soundcheck creates tasks when you put people on a run of show item, when acts need crew, when you share a role with a collaborator, and a week after the show when close-out steps such as the contract or payments are still missing. It doesn’t create tasks for other events. See Automatic tasks.
Partly. There’s no milestone type, so add milestones as tasks with due dates. Contract, deposit, invoice and payment steps are tracked on the gig’s Closeout tab. See Closeout.
No. Tasks don’t repeat. Add one task per occurrence, or put the repeating task in each gig’s template. See Checklist templates.
No. Tasks don’t send anything. Send the form yourself and tick the task. See Working a gig’s checklist.
No. A template adds all of its tasks. Keep a template for each kind of show, such as one with pyro and one without, and pick it when you create the gig. See Checklist templates.

Safety and compliance checklists

Partly. Add a Safety inspection section with a task per check, assigned to the inspector, and put it in your template. There’s no sign-off, and Soundcheck doesn’t show who completed each check. Keep the signed inspection form on the gig’s Documents tab. See Working a gig’s checklist.Buyers ask this first.
Partly. Use a section for each round, such as Before doors, During and After strike, with due dates. Tasks hold no inspection fields, so findings go in notes. See Working a gig’s checklist.
Yes. Add each permit as a task with a due date and an owner, or put them in a template with offsets such as 30 days before. Check the deadlines with the issuing authority. See Checklist templates.
Partly. Add each check as a task assigned to the person who runs it. Soundcheck shows that it’s complete, but not who completed it or when. See Working a gig’s checklist.
Partly. Tasks don’t hold files. Keep the risk assessment on the gig’s Documents tab, upload the new version when conditions change, and add a task to review it. See How the Checklist works with the rest of Soundcheck.
No. Any assignee can mark a task Complete. Collect photos and signed forms on the gig’s Documents tab. See Working a gig’s checklist.
No. Soundcheck keeps the task’s status, not who completed it or when. Keep a signed record on the gig’s Documents tab, and export the checklist after the show. See Working a gig’s checklist.

Tours, festivals and many events

Partly. Each gig gets its own copy of the template when it’s created, so every date is tracked on its own. Set the template as the one for that gig type before you create the dates, because a gig with a checklist can’t take another template. See Checklist templates.
No. There’s no grid of tasks across gigs. Open each date’s checklist, or check Your tasks if the tasks are assigned to you. See Your tasks.
Partly. A gig has one checklist, so use a section per stage or per artist. Acts on the run of show get their own tasks. You can also make each stage its own gig and group them in a project. See Projects and bulk edits.
Yes. Make it your default template, or tag it with the gig types you book, and every new booking gets it. See Checklist templates.
No. A task belongs to one gig. Add the shared task to the gig where the work happens. See Checklist.
Partly. In Your tasks, choose Select to mark your own tasks complete or change their status across gigs. A manager’s bulk edits work one gig at a time. See Changing several tasks at once.

Collaboration

No. Tasks have notes but no comments or mentions. Write updates in the notes, or talk in your team’s usual channel. See Working a gig’s checklist.
No. Files go on the gig’s Documents tab, or on the run of show item the task belongs to. See How the Checklist works with the rest of Soundcheck.
Yes. Each change saves on its own. If someone else changed the checklist first, Soundcheck refreshes it and asks you to retry, instead of overwriting their change. See Working a gig’s checklist.
No. There’s no history per task. Assignments and collaborator status changes are recorded, but other edits aren’t. See Checklist troubleshooting.
No. Tasks have no discussion, and clients don’t see tasks. A collaborator sees a shared task’s notes, so keep internal notes off tasks you share. See Sharing a gig.
No. Tasks have no messaging. Contact the person outside the task. See Working a gig’s checklist.

Importing and integrations

Partly. Copy the list from your spreadsheet or tool and use Paste data on a gig. Soundcheck reads sections and due dates, and keeps owner names in the notes for you to assign. Then choose Save as template to reuse it. There’s no direct connection to Asana, Trello or monday.com. See Working a gig’s checklist.Buyers ask this first.
No. Soundcheck connects to calendars and Slack for gigs, but tasks don’t go to them, and there’s no Microsoft Teams connection. Task notifications are push only. See Your tasks.
Partly. There’s no Zapier connection. Through Soundcheck’s MCP server, an AI assistant can read a gig’s checklist and update a task, but not add one. Enterprise plans include API access. See MCP catalog.
Partly. Paste an email or call notes into Paste data, and Soundcheck turns it into tasks for you to review. An assistant connected through MCP can update a task’s status, title, notes, due date, assignee or section, but can’t add tasks. See Working a gig’s checklist.
Yes. Nothing stops you running both. The two don’t sync, so keep gig tasks in Soundcheck, where they follow the gig’s people, run of show and close-out. See How the Checklist works with the rest of Soundcheck.

Permissions, data and pricing

Yes. Owners, Admins and Gig Coordinators manage templates. Editing a gig’s tasks needs the gig’s Checklist or Lead assignment, or Checklist on every gig. Everyone else can only change the status of tasks assigned to them. See Checklist.Buyers ask this first.
Partly. Clients never see tasks, and in the mobile app crew see only their own. There’s no private setting per task, so keep fees and negotiations on the gig’s finances rather than in task notes. See Checklist.
Partly. In Your tasks and the mobile app, freelancers see the tasks assigned to them on gigs they’re on. Crew who aren’t members of your organization don’t see the checklist. See Your tasks.
Partly. Clients and collaborators don’t take seats. To be assigned tasks, a person must be a member of your organization, and members count toward your plan’s seats. See Subscription plans.
No. No plan limits tasks or templates. Bulk changes handle up to 200 tasks at a time. See Subscription plans.
Yes. Tasks are included on every plan. See Subscription plans.
Yes. Share the gig with the promoter as a collaborator and tick the tasks that are theirs. They see only those tasks and can update their status. See Sharing a gig.
Yes. Archiving a gig keeps its checklist, read-only. See Checklist.
Yes. Archive the gig. Nobody can edit an archived gig’s checklist, including assignees. See Who can see and do what on a gig.
Partly. Export each gig’s checklist as a PDF or CSV, or export the whole workspace, which includes checklist templates and gig checklists. Workspace export is in early access; contact info@soundchecklive.io. Tasks have no history to export. See Export a workspace and restore it.
Partly. For a copy you control, download a gig’s checklist as a PDF or CSV, or export the whole workspace. See Export a workspace and restore it.
No. Deleting a task or checklist can’t be undone. Limit editing to the people who need it, and export the checklist before big changes. See Checklist troubleshooting.
No. Overdue tasks don’t notify anyone. Assign high-risk tasks to a manager who checks the Overdue filter, and label them so they’re easy to find. See Your tasks.

Checklist

Start here: the ideas and a first checklist

Checklist templates

Starter packs, due dates and owners

Automatic tasks

Tasks from the run of show and close-out

Glossary

Checklist terms, from advance to strike