I'm planning a Microsoft 365 application for managing school trips and their costs. The proposed setup uses Power Apps for the interface, SharePoint Lists for data, Power Automate for approvals, reminders, and email notifications, and a SharePoint document library for archiving.
The workflow would let a teacher create a trip, select classes or students, enter transport and date details, add estimated costs such as travel, admission, accommodation, and other expenses, and calculate the total and cost per student. The request would then go through an approval process. After the trip, the teacher would enter the actual costs, with automatic reminders sent for anything still missing. The completed record could eventually be archived as a PDF.
I'm considering separate lists for trips, cost lines, participants, students and classes, and configurable rates such as cost per kilometre. Is SharePoint with Power Apps and Power Automate a sensible foundation, or would Dataverse be a better choice? What design pitfalls should I consider before building?
I'm also an IT administrator who develops occasionally rather than full-time. For building and maintaining the application, would Microsoft Copilot Premium without Cowork be more useful than Claude Pro? I may also want to use the AI assistant for projects outside the Microsoft ecosystem, such as WordPress.
4 Answers
For a first version, Power Apps, SharePoint, and Power Automate can work well, especially if the data volume and relationships stay fairly modest. Dataverse becomes more attractive when you need stronger relational data modeling, better security boundaries, auditing, delegation, or room to grow beyond a simple departmental app. I’d prototype the main workflow first, then decide whether SharePoint is becoming restrictive rather than committing to Dataverse immediately.
Test the awkward cases before polishing the interface: a changed trip date, a withdrawn student, a cancelled booking, a late invoice, and a trip that is already closed. Those scenarios will expose problems in approvals, recalculation, reminders, and archiving much faster than a basic create-and-approve demonstration.
Before choosing the AI tool, think about how you’ll use it. Claude is generally a good fit for code-heavy work, troubleshooting, and projects outside Microsoft 365. Copilot is more convenient when you want help inside the Microsoft ecosystem and with Power Platform concepts, documentation, or existing Microsoft content. If your work is split between both areas, the broader tool may be more useful, while Copilot’s integration may save time during the app build. Some Microsoft setups can also make other AI providers available through Copilot, depending on licensing and tenant configuration.
I’m also considering Claude because I may use it for non-Microsoft work, such as WordPress, rather than only for this application.
The biggest design issue is preserving historical decisions. Don’t let an old approved trip recalculate itself when a mileage rate changes or a student is removed from a class. Store the approved rate, participant count, and calculated estimate as a snapshot, and keep estimated costs separate from actual costs. Also define which changes require a new approval and which only need an explanation.
I’m an IT administrator and only develop from time to time, so I’m looking for something practical that won’t create too much maintenance overhead.