Track a Sports Deadline assignment and notifications
Use the core assignment workflow to keep event facts, intake segments, deadlines, and delivery checks beside the photographs. You need a known assignment and verified destination details. The checklist records your work; it does not prove a remote recipient received a file.
Set up the assignment
- Open Live FTP Desk and choose Assignment Workflow in its header.
- Create/select the assignment and choose Sports Deadline (Human Culling) where appropriate.
- Enter sport, venue, teams/subjects, coverage segment, and card/intake batch. Record the assignment date/time and location.
- Set the deadline and human select target. Record primary delivery and a backup route.
- Use Add to Google Calendar if you want a prefilled calendar entry. Review and save it in Google; opening the entry does not finish scheduling. Local image/archive paths are not part of that handoff.
- Save the assignment. Confirm your facts, caption template, connection test, and backup plan in the preparation checklist.
- Ingest and cull normally, then caption and export the final set. Confirm output and remote receipt before marking delivery complete. Save after changing the plan or checklist.
Choose workflow defaults
Settings → Workflow Presets holds the global default, photographer overrides, external-editor hints, checks, and package choices. The job/event override wins over photographer and global defaults. A preset name does not establish that every external-editor/archive step is automated; inspect the actual action and result.
Configure optional notifications
Open Settings → Notifications. Choose the supported provider or endpoint and enter your own configuration. Available workflows include Slack, Airtable, generic endpoints, job ledgers such as Google Sheets, and messenger handoff. Use the provider test and inspect its result before enabling arrival/delivery messages. Confirm a real received test at the destination. Turn off unwanted notifications rather than assuming closing Settings disables them.
Stored information and recovery
Assignments, notes, events, and checklist state use the existing local workflow record. Notifications and remote ledger writes are separate external actions. If a send fails, inspect the destination before retrying to avoid duplicates. If the wrong workflow appears, check job > photographer > global precedence. For an optional service handoff use BrowserPro Connect. For local deliverable files use Workflow Packages.