CIPO Reporting Automation

Context

Canada’s Annual IP Data and Research Conference required recurring visibility into registration and attendance patterns. The reporting needed to answer practical leadership questions:

• How many people registered?
• Which offices were represented?
• Which countries were represented?
• How were in-person and virtual attendance trends changing?
• What should leadership know before the next planning decision?

Before automation, producing the weekly reporting package took hours of repetitive data handling and formatting. The work was not just “make a chart.” It involved taking messy registration inputs, normalizing them, producing consistent summaries, and making the output reliable enough for government stakeholders.

Problem

The old workflow had three main problems:

1. Manual repetition: the same compilation and formatting work had to be repeated weekly.
2. Inconsistent structure: each report risked small differences in formatting, formulas, or interpretation.
3. Review bottleneck: time was being spent on low-value copying and formatting rather than checking insights and preparing decisions.

The practical target was not an overengineered analytics platform. The target was a dependable reporting flow that reduced manual effort and increased confidence in the numbers.

My Role

I worked as a Junior Analyst and built automation/reporting workflows for conference registration and KPI visibility.

Contributions:

• Microsoft Forms data collection workflow
• Power Automate flow design
• Excel dashboard/reporting templates
• Python/Quarto reporting version using NumPy and Pandas
• Standardized attendance, office, country, and trend breakdowns
• Reporting reviewed by supervisor and used for senior-leadership / VP-level visibility

System Architecture

Microsoft Forms registration data
        ↓
Power Automate flow
        ↓
Standardized Excel workbook
        ↓
Validation + cleanup
        ↓
Dashboard / template report
        ↓
Python + Pandas / NumPy / Quarto version
        ↓
Weekly review package for leadership visibility

What Changed

Before

The weekly reporting process required manually compiling registration metrics, formatting outputs, and checking basic breakdowns. The work took more than 5 hours each week and created avoidable risk: small manual mistakes, inconsistent formatting, and slower turnaround.

After

The automated workflow moved the reporting process toward a repeatable template:

• Data flowed from Microsoft Forms into structured outputs.
• Power Automate handled repetitive movement/formatting steps.
• Excel provided a dashboard and stakeholder-friendly reporting surface.
• Python/Quarto gave a more reproducible analytics path using NumPy and Pandas.
• Weekly work shifted from manual compilation to minutes of review and verification.

Why This Mattered

This project improved the process in three ways:

1. Speed: less time spent on repetitive compilation.
2. Consistency: same template and breakdown logic each week.
3. Decision-readiness: cleaner attendance, office, country, and trend views for planning.

Skills Demonstrated

• Data cleaning and validation
• Low-code workflow automation
• Excel dashboard design
• Python/Pandas analytics
• Quarto reporting
• Stakeholder reporting
• Public-sector documentation discipline
• Translating messy operational data into leadership-ready summaries

Disclosure Notes

• No real attendee lists, office-level sensitive details, or internal files are included.
• The system was a reporting workflow for a conference and leadership reporting context, not an enterprise-wide deployment.