Tasks are how Airstudio tracks the work around a photography business that is not the shoot itself: importing a roster, printing QR codes, chasing a signed contract, retouching a rework, cleaning a sensor. A task has an owner, a due date, a status, and a record it belongs to. Collections of tasks can be templated so the same workflow runs the same way for every job, school, or season.
| Layer | What it is | Example |
|---|---|---|
| Task Collection Template | A reusable blueprint: a set of tasks with due-date offsets, assignees, stages, automations, and notification rules | Senior Portrait Day with 14 tasks from 30 days before to 21 days after |
| Task Collection | The template applied to one record, with real dates and real people | Senior Portrait Day on the Lincoln High job on October 14 |
| Task | One piece of work, in a collection or on its own | Print QR codes, due October 12, assigned to the Lab team |
Templates are built once by a manager. Collections are created whenever the work recurs, usually by applying the template to a job. Tasks are what everyone else sees and completes.
Every task can belong to a Job, Organization, Subject Group, Subject, or Equipment Item, or to none of them (miscellaneous). The attachment decides where the task appears: a job's tasks show on the job's Tasks tab, a school's on the organization, and so on. Template types match these records, so a Job template's due dates count from the job date.
Tasks in the left navigation has tabs for:
Tasks also appear on each job, organization, subject group, subject, employee, and equipment item.
All employees can see and work the tasks assigned to them. Managing templates, statuses, and priorities is for administrators and scheduling managers. The Tasks area is not included in the Basic subscription.