Before-and-after improvement review
Design a before-and-after review with baseline, confounders and outcome evidence.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Change made | Baseline period | Outcome definition | Follow-up period | Other changes | Supported conclusion |
|---|---|---|---|---|---|
| Clarified pickup instructions | Previous four weeks | Recorded direction questions | Next four weeks | Staff schedule changed | Compare counts with limitations |
- Use one row for each implemented change and outcome being compared.
- Record the baseline and follow-up periods, outcome definition, other changes and supported conclusion. Include concise aggregate counts and source references in the relevant fields.
- Review the actual business records separately. This worksheet does not connect to accounts or change your records.
The change was made, and next month looked better. That’s encouraging, sure, but it doesn’t prove the change caused the improvement. Shop results also shift with the season, job mix, staff availability and collection timing. Define the outcome before changing anything, keep a baseline, then compare the follow-up fairly. You’re looking for useful learning here, not a research paper or a guaranteed causal claim from a small business sample.
Use with this guide
business health review
Review the scope of business health review.
BlueFinch business dashboard
Review the scope of BlueFinch business dashboard.
Track a wrap-shop reactivation campaign through paid jobs
Replies and deposits are not fully paid jobs. Follow a defined eligible customer cohort to the recorded payment outcome before judging a reactivation campaign.
Choose the outcome before acting
Track what the change actually fixes. Clearer pickup instructions? Watch customer questions and process confusion. Changed processing terms? Compare actual assessed costs under similar conditions. Fixed a contact form? Check that messages arrive, then track suitable inquiries separately. One revenue chart won't tell you whether every kind of improvement worked.
A business health review should tie the finding, proposed action, and measurement plan together. Don't wait until the change is done to pick whichever number improved. That makes the report persuasive but weak as evidence. Keep the original outcome definition. If it changes later, explain the change so the owner can judge what the comparison really shows.
Keep the baseline comparable
Use periods with the same measure, source, and calendar context. Note open days, unusual jobs, and gaps in the source data. The BlueFinch business dashboard helps you find available information, but matching cards don’t make incomplete periods comparable. Check the dates and definitions underneath before you draw a trend line.
Here’s a simple example. A shop logs twelve pickup-direction questions in four weeks, then seven in four weeks after revising its instructions. That’s an observed decline of five questions. But if the shop handled fewer pickups, compare the relevant denominator. And if staff changed how they logged questions, the measurement may have changed too. Keep those limitations visible.
Distinguish implementation from benefit
A published page correction is an implementation result. More qualified inquiries are a separate business outcome. A signed processing agreement means a decision was made. Lower verified fees come later, as a financial outcome. Keep those stages separate. Finishing setup does not mean the promised benefit has happened.
The SBA’s cost-benefit guidance supports comparing relevant costs and benefits over time. Include the work of putting a financial change in place, plus any costs that remain. Don’t assign an arbitrary dollar value to every minute saved or count every extra inquiry as a completed profitable job. Use real evidence when you have it. Label scenarios when you don’t.
Sources for this section: SBA: manage your finances
Use the result to choose the next action
If the change worked operationally but the business result is still unclear, keep observing or improve the measurement. If the process didn’t happen as expected, check how it was implemented before judging the idea. If the evidence shows harm, adjust the approach through the right approval route. A useful review lets the owner change course without pretending the original plan was certain.
Keep the source references, counts, and relevant context in the worksheet. Leave customer-level records in the authorized system. The FTC recommends minimizing sensitive information and controlling access. That applies to improvement reports as well as daily operations. End with the supported conclusion and the next evidence check. Don’t turn a modest observed result into a universal success story.
Include failed tests in the review record as well. If a revised message did not reduce confusion, that result helps narrow the next investigation. Removing unsuccessful attempts from the history makes the remaining examples look more reliable than the actual process was and encourages the same unsupported experiment later.
Sources for this section: FTC: protecting personal information
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
Use this page for general business information. It is not legal, tax, or accounting advice.