SAG / ARCHITECTURE NOTE
Fixed Competitor Baseline: How to Track Monthly Changes Alongside the Gap from the Baseline
A comparison method that fixes the first competitor data entered and tracks differences against the company’s monthly data. If the comparison target and questions change every month, it is difficult to distinguish improvements in the company’s performance from changes to the baseline. A consistent baseline helps keep work on track.
What Is Baseline Comparison?
This is a comparison method that fixes the first competitor data entered and tracks differences against the company’s monthly data. This note approaches baseline comparison in terms of the responsibilities of input, transformation, and output, rather than as a feature name. To trust the analysis results, it must be clear what data was entered, what was checked, and how far the conclusions can go.
Why Is This Technique Needed?
If the comparison target and questions change every month, it is difficult to distinguish improvements in the company’s performance from changes to the baseline. A consistent baseline helps keep work on track.
Design Principles and Data Flow
Store the initial data together with its condition keys, and do not change it in subsequent queries. Show the fixed baseline time and the time of the company’s current observation at the same time.
Initial competitor observation → Unchanging baseline → Monthly gap for the company’s data
Each stage must not describe the success of the previous stage as the achievement of the next. Recording the data identifier, period, and validation status throughout makes it possible to locate where omissions and errors occurred and determine what needs to be checked again.
Connection to the SAG Architecture
SAG competitor comparison stores the initially registered baseline data for each set of conditions and compares it with the company’s data for the selected month. This is a comparison against a fixed baseline, not the competitor’s real-time ranking for that month.
SAG’s operational value lies in connecting this relationship to pages and questions, comparison results, and improvement tasks. Rather than reading only numbers, customers can review both what needs strengthening and the basis for their decisions. Patterns requiring additional application should be interpreted according to the scope of the relevant paragraph.
Illustrative Example and Criteria for Interpretation
For illustration, if the competitor baseline is rank 3 in July and the company is ranked 8 in October, the difference from the baseline is five positions. You cannot claim that the competitor was also ranked 3 in October without a separate October observation.
The example above is provided to explain the structure and calculation; it is not measured performance from a specific customer. In an actual report, the selected period, target, observation conditions, and source records must be linked so that the same judgment can be verified again.
Practical Validation Checklist
| Flow stage | Item to check |
|---|---|
| Initial competitor observation | Display the baseline registration time |
| Unchanging baseline | Confirm that conditions match |
| Monthly gap for the company’s data | Preserve the history of baseline changes |
Check that the meaning remains consistent not only for valid inputs, but also for missing data, duplicate data, and data with different conditions. Connecting validation items to the completion criteria for a task can reduce the gap between a feature description and actual operations.
Limitations and Points to Note When Applying
A fixed baseline is useful for operational comparisons, but it may miss the latest market changes. When resetting the baseline periodically, it is appropriate to retain the new baseline as a new version rather than overwrite the existing one.
Research and Official Documentation
- W3C PROV Overview — A provenance framework that describes relationships between data, the activities that generate it, and responsibility.
The external resource provides background on the design topic above; it does not certify every SAG implementation or customer outcome. The interpretation of this note’s application and its illustrative example are organized around the SAG operational structure. Source checked: 2026-10-06.
Further Reading and Feature Details
- Related architecture note
- Try the service connected to baseline comparison
- Feature-specific FAQ
- Discuss implementation scope
How to Continue Reading About This Technique
Distinguish monthly samples, the denominator for citation rate, competitor baselines, and Goal achievement rates.
SAG / KNOWLEDGE LINKS