Reporting automation
Automated Client Reporting
A one-click app that turns Worksection tasks and costs into formatted, review-ready client reports.
- Python
- Streamlit
Worksection API- Excel
The one click, unpacked
Pick a client. Pick a month. That is the whole input
Everything else already lives on the client — which language they read, what they are billed in, how their rate works and what their report is supposed to look like. Change the client and the same run produces a different document.
Ukrainian·UAH·Hourly, per role
Settings changed — run it again to rebuild the draft.
What the run does
- 01Pull from WorksectionTasks, subtasks and time entries for the selected period, read straight from the API.
- 02Apply the client’s settingsLanguage, currency, rate model and how much detail this particular client is shown.
- 03Group and priceWork rolled up by project and role, hours priced at the rate that was actually agreed.
- 04Render from the templateThe client’s own layout, headings and totals — filled in, not rebuilt from a blank sheet.
- 05Save as a draftNothing is published yet. Whatever the client already received stays exactly where it was.
- 06Wait for approvalThe run stops here on purpose. A person decides whether this draft becomes the master.
What you get
- Client
- Meridian Foods
- Period
- October 2025
- Tasks by project
- Hours by role
- Costs and totals
Switch the client above and run it again — the same six steps hand back a Ukrainian UAH document instead of an English one. Nothing in the run changes; only what is stored on the client does.
Why it is safe to press
Nothing reaches the client until a person says so
Automation is only worth having if pressing the button carries no risk. The app can be re-run as often as you like — it writes drafts, never over a file a client already has.
- 01Draft
Every run lands here. Regenerate it, throw it away, or run it again with different settings.
- 02Review
Someone opens the draft and checks the period, the totals and what this client is shown.
- 03Master
Only an approval writes the master — the single version anyone is allowed to send.
Kept behind the master- v3published 02 Dec
- v2kept
- v1kept
- Re-running is safe — a new run replaces the draft, never the master.
- Every published version is backed up and stays readable.
- A client never sees a draft, so a half-built report cannot go out.
What it changed
The same report, by hand and by app
The data and the client’s format do not change. What changes is how many manual steps sit between Worksection and a file you are willing to send.
| What changes | By hand in ExcelStarting from last month’s file | With the appSame settings, every time |
|---|---|---|
| Starting a report | By hand in ExcelOpen last month’s file to recall the period, the format and the rate | With the appPick the client and the period — the format is already theirs |
| Getting the work in | By hand in ExcelExport tasks, then regroup them by project and role by hand | With the appTasks, subtasks and time entries come straight from Worksection |
| Language and currency | By hand in ExcelRemembered per client, and occasionally remembered wrong | With the appStored on the client — the same run renders Ukrainian UAH or English USD |
| Rates and costs | By hand in ExcelRetyped each time, and quietly out of date after a rate change | With the appPriced from the agreed rate model at the moment of the run |
| Sending it out | By hand in ExcelThe finished file is the only file — one mistake overwrites the last one | With the appA draft is reviewed, then published, and the previous version is kept |
| The month after | By hand in ExcelThe whole assembly repeats, one client at a time | With the appOne click per client, with the period as the only thing that changes |