The operations team needs reports it can rerun without changing their meaning. You will use fresh combinations of customers, orders and shipping fields, then review the operational choices around those reports. Keep the reporting window explicit and give every output its intended grain. A script can execute successfully while answering the wrong question.
Use the source tables as the evidence. Missing plans and emails remain meaningful audit cases; removing them can make a report look cleaner while hiding the rows the team needs. For a stored result, inspect the rows after the build. For a scheduled job, separate what the SQL proves from what an execution identity, scheduler and monitoring service must establish in Google Cloud. These exercises revisit supported features rather than introducing another scripting construct.