Yep work flow looks solid.
So typically we see either linear or non-linear errors. Linear errors are the same at every distance. I'm .2 high at 100, .2 high at 600, and .2 high at 1000. That's a zero issue, either with the app or the optic/shooter.
Non-linear issues are more like perfect at 100, within .1 at 400, .2 low at 800, .4 low at 1000, .7 low at 1200. Those are typically either drag or MV. If you're using a labradar or Garmin you can fairly safely rule out the MV and **Assuming all other inputs are correct** (hint: verify them), you can deduce that the issue is likely the result of a difference between real world drag and calculated drag. That's the point where you pull Axial Form Factor out of your tool box and adjust the Cd curve to match your barrel/load/muzzle device.
I typically recommend writing down the day's conditions (to include wind, even at 100yd), then record MPOI location at 100, 400, 600, 1000, etc... I write what the app told me, and what was actually required to hit. This way I have a record to look back on to verify if I make changes, all ranges match up.
You definitely can have linear and non-linear errors. Good equipment, pre-flight checks, and proper sample size do a lot to cutting the silly/mental and software errors down.
Another note, once you have a profile built and verified, you shouldn't need to adjust it based on location or weather. The caveat to that is MV walk with temperature, but besides that if your zero angle changes or you *think* your form factor changes from day to day, it's a great indication that something is input wrong or you have a mechanical loose end somewhere.