Make monthly refresh repeatable — Smart Study Module 6

Another analyst must be able to run your monthly report without asking where your files are.

Outcomes

• Record before/after controls
• Document file locations and refresh steps
• Recover from bad input without losing the prior report

Understand

A refresh run should record source files, row counts, total amount, exception count and refresh timestamp. These are operational controls, not decorations. Compare the latest run with the expected month and source register.

Separate raw input, transformation and report output folders. Keep an accepted prior output; validate a new candidate before replacing it. Avoid hardcoded personal paths in shared workbooks where parameters are available.

Query performance depends on transformations and connector behavior. On this tiny kit, correctness matters more than micro-optimization. Demonstrate that removing a source file changes the controls.

Follow along

1. Refresh with both monthly files: capture nine rows and ₹98,000.
2. Temporarily move February out: capture five rows and ₹48,000.
3. Restore February and compare the controls again.
4. Write an operator runbook with file contract, exception handling and rollback.

Worked example

Run control: expected_files=2; expected_rows=9; expected_amount=98000; exceptions=0

Missing February reduces the total by ₹50,000.

Practice

Return the amount missing when February is excluded.

Create a free personalized study plan · Download project instructions

Interactive practice runs in your browser.