Having played around today with 3.9 (iOS), I do miss the Flight Details tab for 1-click access.

I use it quite a lot not just for W&B but also to set aircraft, set takeoff time, view flight time (on iPhone, though this is now on main map like on iPad so not an issue), and set fuel. I guess this is more important when planning than in flight.

Tim, as I said I just found out that GAR filing now via the Warnings tab instead of Flight Details, hence the back & forth.

To answer your request, typical workflow consists of:

Flight Planning:
1.1) Create route using map
1.2) Select aircraft (occasionally check Empty W&B figures are correct compared to W&B Schedule)
1.3) If it's a quote, then set zero wind, (may be across multiple aircraft types)
1.4) Get total flight time
1.5) Calculate fuel requirements, and W&B, which then determines if
1.6) Route may need tweaking for extra fuel stop(s), means back & forth to fuel/W&B figures, and check new total flight
1.7) Route may need new user waypoint(s) (helicopter landing site), using postcode search etc and tweak using satellite view, saving user waypoints to cloud each time so consistent across my iPad and iPhone.
1.8) Set Land Here (creating multiple sectors)
1.9) For each sector, set takeoff times, fuel & W&B figures
1.10) Check Plog (each sector)
1.11) Tweak Altitudes if required due to MSA (IFR), Airspace, best Altitude for Flight etc
1.12) Save route (this may occur at various stages above too)

Before departure:
2.1) Open route (as may not already be open) and check all figures are completed and correct (aircraft, fuel, W&B, flight times) for each sector
2.2) Check Notams and Wx (this may force last minute route changes due to RA(T) etc)
2.3) Create Briefing Pack(s) for the main passenger sector(s) and share via email to Ops
2.4) Check charts & airfield plates up to date
2.5) copy W&B figures (aircraft tech log for each sector - Part-CAT requirement)
2.6) copy initial fuel figures (for aircraft tech log)
2.7) Submit GAR (if required)
2.8) Submit Flight Plan (if required)

End of flight:
3.1) Before pressing "Stop navigating", take screenshot of Pilot Log to capture the ATA for each sector (this is an area where the Debriefing Pack could be improved to include a decent Plog with post-flight details)

That's all fine until customer makes last minute changes to route, timings, passenger details, and sometimes aircraft.

That's all I can think of from the top of my head. Just hopes it's constructive enough for you to see why the workflow is now less efficient.

It would very easy to say something like "why don't I change the order of some of the above to combine tasks", however it's not as simple as that, and often these actions are quite quick (for me at least). Figures require continued cross-checking.