What could the mobile app do?
The mobile workflow follows the agreed system scope. It could give the team access to job records, let them capture a site note or variation, or show an approval that needs attention. The website demonstrates a possible mobile job screen, not a complete product specification.
Will the app work without a signal?
Poor-connectivity requirements need to be scoped. Discuss which records must be available, which actions people need to take offline and how changes should be handled when a connection returns. Offline behaviour should be agreed and tested for your working conditions.
Can subcontractors use the app?
Start with who needs access and what each person should see or change. Employee and subcontractor roles, devices, sign-in and permissions are part of scoping. Access to a job should reflect the responsibilities of the person using it.
How are deployment and support handled?
Ask how the app will reach your team, which devices it supports, who manages updates and what ongoing support includes. Mobile deployment, third-party services and maintenance costs should be clear alongside the build scope.