Look beyond submission
A successful submission does not allocate a photographer, explain property access or deliver a report. Those steps need their own states, responsibilities and information.
Make the handovers explicit
Map what each role needs to know and when. Use the same underlying property and job records so that different interfaces do not create separate versions of the work.
Deliver one connected slice
A first release can remain small while still respecting the wider workflow. Booking and availability foundations are useful when they leave a clear path to allocation, production and delivery.