Describe the working day
List the users, the task each person needs to complete and the information that must reach the next team. Say where the system will be used, which devices are available and whether a person needs to review a submission before it becomes a final record.
Plan for the actual connection
Check connectivity at each proposed location rather than assuming that one office connection represents every site. If work must continue without a signal, define what can be saved locally, how records will sync and how people will recognise a failed upload. Include language, training and support requirements in the same brief.
Agree on a useful first release
Choose a small set of tasks that can be demonstrated and accepted by the people who will use them. Record responsibility for hosting, backups, access and support after launch. The main Sovereign Forge library has fuller guides to scoping software and comparing support proposals; use them alongside your Arunachal project brief.
Sources & further reading
- How to write a useful software project brief
- Plan field data collection when connectivity is unreliable
- Compare software support proposals beyond the monthly fee
Confirm current requirements for your specific activity with the responsible professionals.