Google Apps Script: how to eliminate the report someone builds every Monday.
What Apps Script can and cannot do in a mid-sized company, and the technical limits worth knowing before you start.
Almost every company on Google Workspace has someone who spends Monday morning building the same report: opening three spreadsheets, copying ranges, refreshing a pivot table, exporting to PDF and emailing it to five people. It is the most automatable task there is and the one that goes unresolved the longest, because nobody treats it as a project.
Apps Script is the automation environment already included in Google Workspace. It requires no extra license and nothing to install: you write it in the browser and it runs on Google's infrastructure. It can read and write spreadsheets, generate documents from templates, send email, move files in Drive, create calendar events and call external services.
A scheduled trigger runs the routine at whatever time you define. The Monday report can be in everyone's inbox before anyone reaches the office. That is the right way to measure the result: not in hours saved, but in the report no longer depending on one person being available.
There are three limits worth knowing before promising anything. The first is execution time: a routine cannot run indefinitely, so heavy processes have to be split into blocks that run in batches. The second is email-sending quotas, which exist and vary by account type; bulk sends need another channel. The third is performance on very large sheets: Apps Script reads fast if the data is pulled in one go, and becomes painfully slow if cells are accessed one by one inside a loop.
The underlying decision is not technical but one of governance. A routine that only one person understands transfers the risk rather than removing it: before, the company depended on that person building the report; now it depends on that person knowing how to fix the script when it fails. That is why every automation in our projects is delivered documented, with commented code, and with at least two people on the internal team able to maintain it.
And a fundamental precaution: if the routine touches payroll information or employees' personal data, the project enters the territory of Colombia's data-protection law (Law 1581 of 2012). You must define who can run it, who can see the results and where the intermediate files are stored. Automation does not exempt you from controls; it makes them more necessary, because it increases the volume of information moving without human intervention.