This page concerns the Central Coast Significant Urban Area in New South Wales. For a mobile food business, the proposed workflow starts with the trading unit and event rather than a single permanent shop address.
Which council paperwork should the app reference?
Reference the registrations and notifications applicable to the actual trading arrangement. Central Coast Council’s food safety guidance describes its processes for food premises and temporary or mobile operations. The app can retain a submitted form, council reference and follow-up request beside the event. A tick marked by a staff member should mean the internal task is complete, not that the council has approved the business.
How can a daily checklist help the next shift?
Make unresolved items visible before the next team starts selling. A proposed checklist might record equipment checks, an issue raised by a staff member and the person assigned to resolve it, using the procedure supplied by your food-safety lead. Separate a missed check from a failed one. If a device is shared at the stall, record the responsible shift and require a deliberate handover instead of treating every entry as the owner’s personal action.
What happens to customer and staff information?
Keep operational evidence separate from personal contact lists. For a council customer, the NSW Information and Privacy Commission describes the applicable state public-sector privacy laws; this is not a general classification of every private food operator. Scope the private business separately. The proposed app should let an event coordinator see the documents required for that event without exposing unrelated staff records or customer enquiries from another location.
Which event should become the first release?
Choose one recurring event with known preparation tasks and a clear close-down routine. I would walk through a late staff replacement, a missing notification reference and an unresolved equipment issue before quoting the pilot. The resulting remote build has a written fixed price and explicit acceptance steps. Stock purchasing, customer loyalty and accounting can remain separate until the event workflow has proved useful to the people running it.