Approval is a decision surface
A phone approval should answer four questions at a glance. What changed, why it matters, who owns it, and what happens after the decision. Anything else can remain behind the detail view. This keeps the first screen calm and makes an urgent review possible between other work.
Keep the evidence attached
A useful approval contains the source file, the relevant comparison, and the proposed action. Supervisor keeps those parts in one record. The manager can approve, return, or ask a question without moving to another app and losing the decision trail.
Design for interruption
Mobile work rarely happens in a quiet session. Save partial context, use clear action labels, and confirm the result immediately. When a connection drops, keep the decision locally and show its delivery state. The operator should never wonder whether a tap changed the business.