Crew and tasks

Team members connects a person to an organization and platform user. The role name and time zone help identify who is responsible for the package, while work packages.Owner names one team member. Tasks sit beneath the package with a line number, task name, planned hours, actual hours, due date and completion date. A dependency can be recorded on the task for coordinators to check during review.

• Source. Start with the production, package or person named on the record, then follow its explicit references.
• Decision. Keep the latest status and revision visible to the person responsible for the next action.
• Evidence. Open the child records before concluding that the work is ready for review or complete.

Decide who will own each work package and how task lines will be numbered. Set the team member organization before assigning that person to a package. Agree how the team records actual hours and completion dates so overdue task views can distinguish finished work from open work. A task dependency written as text needs a clear local convention for referring to the predecessor.

A package owner plans a location permit task and an equipment preparation task. The coordinator records planned hours and due dates on both. When equipment preparation finishes, the team records its actual hours and completion date. If the permit remains open past its due date, it appears in the deadline view. The coordinator can compare task hours with the package budget before asking the reviewer to accept the delivery evidence.

The package owner is the accountability point for task exceptions. A task line can describe one piece of preparation even when several people contribute informally, so the team should use the task name and line number consistently. Planned hours and actual hours answer different questions: the first describes the intended effort, while the second records work performed. The completion date is the clearest signal that an overdue task has finished. Before review, open the task list in line order, inspect dependencies and confirm that the hours recorded belong to the correct package and production.

• Packages by owner — Review active package assignments with the named owner.
• Task deadlines — Find tasks by due date and inspect their completion dates.

Follow production planning, shoot day review and delivery review to see how records move between people.