Defence SA identifies Osborne, Edinburgh and Technology Park Adelaide as defence precincts. For a supplier serving that environment, I would begin with a bounded administrative workflow and your customer’s information-handling requirements.
Which supplier records are suitable for a first app?
Start with the records your organisation has approved for the proposed hosting and support arrangements. A candidate workflow could track document requests, revision numbers, reviewer comments and outstanding actions. Establish a sample pack before design: an accepted submission, a rejected revision and a late response. Those examples determine whether the app needs a simple checklist or a controlled review process with separate author and approver roles.
How should an approval survive a revised attachment?
An approval should stay attached to the exact revision that was reviewed. The proposed app can create a new review item when a supplier replaces a document, retain the earlier decision and mark downstream actions that need another look. That makes a procurement handover more useful than a folder of similarly named files. It also gives a departing reviewer’s replacement enough context to continue the work without reconstructing an email chain.
Who handles South Australian government privacy?
The state’s Privacy Committee and Information Privacy Principles Instruction are relevant to South Australian government agency work. This should not be described as a general South Australian privacy act applying to every company. Private organisations need their own federal-scope assessment using OAIC guidance. For the app, identify which attachments contain personal details and whether an agency contract imposes additional handling conditions.
How can a remote supplier project be assessed?
Use a written boundary for both functionality and permitted information. The delivery plan should identify who provides sample documents, who accepts a revision workflow and who approves any hosting choice. Remote access, restricted material and customer onboarding conditions must be resolved before such material enters the development environment. A fixed-price milestone can then cover a reviewable administrative slice, with broader integrations quoted after the customer grants the necessary access.