Public Changelog / Product Updates
Feature releases, bug fixes, improvements, and product update notes for QuoteFinder.ca in one public place
Why this page exists
QuoteFinder.ca evolves over time. Features are added, workflows are improved, labels change, bugs are fixed, and some product behavior may be updated to improve clarity, trust, safety, or platform reliability.
This Public Changelog / Product Updates page helps users understand what changed and when — without needing to guess whether something is a bug, a new feature, or a workflow update.
Plain-English goal
We aim to publish clear update notes that help clients, providers, brokerages, and team admins understand product changes and what (if anything) they need to do next.
What this page is for
- public release notes for product updates and feature changes;
- bug fix summaries and UI/UX improvements;
- workflow changes affecting clients, agents, or brokerages/teams;
- known-issue notices (where appropriate);
- product changes that may relate to help/policy updates (with links).
What this page is not for
- private support tickets or account-specific troubleshooting;
- confidential security details or sensitive anti-abuse methods;
- legal policy text (the policy pages control);
- a guarantee that every user sees a feature at the same time;
- real-time status monitoring (unless explicitly linked to a status page, if available).
Product notes vs policy pages
If a product update is connected to a policy or terms change, the relevant policy/terms page controls the binding rules. Changelog notes are summaries for product understanding.
What may be included in product updates
| Update type | Examples | Why it may be published |
|---|---|---|
| New features | New workflow screens, filters, team tools, help prompts | Users need to understand new capabilities and how to use them |
| Improvements | UI cleanup, label changes, mobile usability updates, clearer status wording | Reduces confusion and improves usability |
| Bug fixes | Broken page fixes, dashboard display fixes, form errors, logic corrections | Lets users know known issues were resolved |
| Workflow changes | Quote handling steps, team admin flow updates, verification-related product prompts | Users may need to adjust their process |
| Help / docs-linked changes | New help content, changed labels, updated guidance links | Supports adoption and clearer self-service |
| Known issues / limitations | Temporary quirks, rollout limitations, partial availability notes | Sets expectations and reduces duplicate support requests |
How we may structure a changelog entry
A typical changelog or product update post may include:
- date (publish/update date);
- release title (plain-English summary);
- what changed (feature/fix/improvement summary);
- who is affected (clients, providers, brokerages, team admins, staff);
- what you may need to do (if anything);
- rollout notes (if release is phased);
- related help/policy links where relevant.
Good changelog entries answer 3 questions
What changed? Who does it affect? Do I need to do anything?
Suggested changelog labels (plain-English)
QuoteFinder.ca may use one or more labels to make updates easier to scan:
- New — new feature or capability
- Improved — usability or workflow improvement
- Fixed — bug fix or issue resolved
- Changed — behavior/flow/wording change
- Known Issue — currently identified issue or limitation
- Deprecated — feature/path being phased out
- Docs Update — help/guidance update related to product changes
Versioning and release names (how to interpret them)
Some updates may be published with a version number, release tag, or internal build label. Other updates may be published as plain-English product notes without a version number.
Where version numbers are shown publicly, they are intended to help identify a release — not to imply that every user receives the update at the exact same moment.
| Release note style | Example | What it means |
|---|---|---|
| Plain-English product note | “Improved quote request status labels on Market page” | User-facing description of a change |
| Versioned note | “Platform Update vX.Y.Z” | A named release/build reference (if used publicly) |
| Hotfix note | “Hotfix: mobile layout issue on agent dashboard” | Targeted fix, often for a specific bug/regression |
| Rollout note | “Phased rollout: team admin improvements” | Feature may appear gradually across accounts |
Version labels are for identification
A version label helps identify the release note, but your account experience may vary during staged rollouts, account-type differences, or configuration-specific deployments.
Rollout timing and phased releases (important)
Not every change appears to all users at the same time. QuoteFinder.ca may use staged or phased rollouts to reduce risk, validate behavior, and improve reliability.
Why rollout timing may vary
- phased release strategy (gradual rollout);
- account type differences (client/provider/team);
- feature flags or configuration differences;
- bug fix prioritization by affected area;
- operational or support readiness for larger changes.
What to do if you don’t see an update yet
Check the changelog entry for rollout notes first. If the feature should be available for your account/workflow but is not visible, contact support and include the update title/date and the page URL you are checking.
Bug fixes and known issues (how we may communicate them)
When practical, QuoteFinder.ca may publish concise notes about important fixes and known issues to reduce confusion and duplicate support messages.
Bug fix notes may include
- what was affected (page/feature/workflow);
- a plain-English symptom description;
- who was most affected (if known);
- whether a workaround is still needed (if any);
- date/time of fix publication (high-level).
Known issue notes may include
- what is not working as expected;
- temporary limitations or partial behavior;
- affected user groups or pages (if known);
- temporary workaround (if safe and appropriate);
- follow-up note once resolved.
Security-related limits
For security and abuse-prevention reasons, QuoteFinder.ca may avoid publishing technical details that could expose vulnerabilities or internal detection methods.
Deprecations and behavior changes
Sometimes a workflow, label, page element, or feature behavior may change or be phased out. When useful, QuoteFinder.ca may post a changelog note to explain the change and what replaces it.
What a deprecation note may cover
- what is changing or being removed;
- why the change is being made (clarity, reliability, safety, product simplification, etc.);
- what users should use instead;
- when the change takes effect (if applicable);
- links to updated help/docs pages.
Product changes that may also require documentation updates
Some product updates affect help content, policy summaries, onboarding guides, or support labels. In these cases, QuoteFinder.ca may publish linked updates across product and documentation pages.
| Product change | Possible related update | Where to check |
|---|---|---|
| New team workflow / role behavior | Help docs + team admin guidance updates | Help for Brokerages / Team Admins, Help for Team Members / Staff |
| Verification-related workflow prompt changes | Verification help and policy clarifications | Verification Help / Document Submission Guide, Identity / Verification Policy |
| Billing/credits flow changes | Billing help / refund policy-linked updates | Billing & Credits Help, Refund / Credits Policy |
| Trust & safety reporting UI/labels | Help / safety / enforcement page updates | Consumer Safety Hub, Trust & Safety Enforcement / Policy Violations |
How to use this page effectively (quick checklist)
- Check the date of the update first.
- Read the “who is affected” section (if included).
- Look for rollout notes before assuming something is broken.
- Check linked Help/Policy pages if the change affects your workflow.
- Contact support with the update title/date if you need clarification.
How to report a possible regression or issue after an update
If you believe a recent update caused a problem, contact support and include enough detail to help reproduce the issue.
Helpful first-line labels:
- Product update issue — suspected regression after a recent change
- Bug report — something appears broken or inconsistent
- Feature question — need clarification on a new/changed behavior
- Docs mismatch — help page appears inconsistent with current product behavior
What to include in a changelog-related bug report
- page URL(s);
- what you expected to happen;
- what happened instead;
- role/account type (client/provider/team admin/staff);
- screenshots (if possible);
- the changelog entry title/date you think is related (if known).
Why this helps
Clear bug reports reduce back-and-forth and help support/product teams determine whether the issue is a bug, rollout timing difference, configuration issue, or expected behavior change.
Related pages
- Updates / Newsroom
- Marketplace Transparency Reports / Stats
- Help Center
- Help for Clients
- Help for Agents
- Help for Brokerages / Team Admins
- Help for Team Members / Staff
- Trust & Safety Enforcement / Policy Violations
- Consumer Safety Hub
- Privacy Policy
- Contact / Support
Last updated: February 23, 2026
