When a shared spreadsheet needs an internal app
Conflicting copies, overwritten formulas and missing approval records are reasons to review a shared workbook. Look at where staff get stuck before deciding how much to move out of Excel.

The workflow illustrates a possible design and is not a client case study.
- Structure fields
- Build the app workflow
- Reconcile in parallel
Where do mistakes enter the shared spreadsheet?
Staff may be working from different copies without realising it, or a formula may have been changed unnoticed. These are more useful warning signs than row count. Follow a normal task through the workbook: where is data entered, which columns perform calculations, and who puts mistakes right?
Compare spreadsheet changes, Power Apps and custom work
Compare an improved spreadsheet, a Power Apps solution and custom development. Power Apps can provide an interface for connected data, but external users, permissions, integrations and licensing affect the cost and design. A new input screen still needs clear rules for the data behind it.
Move one frequently used workflow
One frequently used process gives staff a manageable place to try the new app. Give records unique IDs, validate the inputs and keep the exports people rely on. During a short period of parallel use, compare the two sets of records. Agree who will stop edits to the old sheet, when that will happen and how to return to it if the app has problems.
Check formulas and approval history
Have staff complete their usual work in the app, including simultaneous edits, missing values and duplicate entries. Test the old calculations and required exports, then compare a sample of records, totals and approval histories. Those checks show whether the new process covers the work the spreadsheet used to do.
Bring the spreadsheet and examples of what goes wrong
Bring a workbook with personal details removed, explain its formulas and list who uses it. Include the tasks where mistakes or rework happen most often.