# Make polling budget and reconciliation worksheet

Research worksheet · 2026-09-13 · Local use only. No account connection or measured results supplied.

## 1. State the job

Scenario name: ____________________
Trigger app/module: ____________________
Schedule timezone: ____________________
Maximum acceptable delay: ____________________
Observation dates and person responsible: ____________________
Current account allowance, billing period, and date checked: ____________________

## 2. Estimate trigger checks

For one regular daily window:

`Estimated checks = round up(active minutes per day / interval minutes) × active days`

`Trigger budget = estimated checks × assumed credits per check`

Round up for planning; compare with actual timestamps before treating this as an exact count. A once-daily schedule has one planned check per active day. Do not combine scenarios with different schedules into one average.

| Scenario | Minutes/day | Interval minutes | Active days | Checks | Credits/check assumption | Trigger budget |
| --- | --- | --- | --- | --- | --- | --- |
| Illustrative hourly, all day | 1440 | 60 | 30 | 720 | 1 | 720 |
| Illustrative hourly, workdays | 480 | 60 | 22 | 176 | 1 | 176 |
| Your scenario | | | | | | |

## 3. Add processing separately

| Budget component | Your input | Calculation or evidence |
| --- | --- | --- |
| Trigger budget | | From section 2 |
| Expected processed records | | Explain estimate |
| Downstream credits per record | | Exclude trigger already counted |
| Downstream budget | | Records × downstream credits/record |
| Other fixed/dynamic work | | Record module and billing basis |
| Chosen reserve | | State amount and why |
| Planning total | | Sum trigger, downstream, other work, reserve |
| Remaining allowance | | Account allowance minus all scenarios' planning totals |

Example only: 720 trigger + 100 records × 3 downstream + 102 chosen reserve = 1,122 credits. The reserve is an illustrative choice, not a vendor recommendation. No currency price is assumed.

## 4. Reconcile with observations

| Observation | Timestamp/window | Planned count or credits | Actual count or credits | Explanation / unknown |
| --- | --- | --- | --- | --- |
| Empty trigger check | | | | |
| Representative populated run | | | | |
| Manual runs / retries | | | | |
| Total within the same window | | | | |

If a recorded run total includes its trigger, subtract the trigger before using that total as downstream cost. Dynamic modules need their own measured assumption. A missing history detail remains unknown.

Decision: keep schedule / reduce frequency / narrow window / inspect supported instant trigger / review plan

Reason and expected delay: ____________________
Recheck date: ____________________

Sources checked 2026-09-13:
- https://help.make.com/step-10-schedule-your-scenario
- https://help.make.com/credits
- https://academy-content.make.com/courses/make-basics-modules/04-trigger-modules/
- https://www.make.com/en/pricing

Do not put API keys, tokens, email contents, or customer records in this worksheet.