Edit Log
The Edit Log provides a complete audit trail of all forecast changes. It helps you understand what changed, who changed it, and why—essential for forecast accuracy analysis and compliance.Accessing the Edit Log
Navigate to Demand Forecast → Edit Log (or click the Edit Log link from the forecast dashboard).What’s Tracked
The edit log captures:| Information | Description |
|---|---|
| Timestamp | When the change was made |
| User | Who made the change |
| SKU | Product affected |
| Channel | Sales channel affected |
| Period | Time period(s) changed |
| Previous Value | Value before change |
| New Value | Value after change |
| Change Type | Absolute or percentage |
| Reason | User-provided explanation |
Edit Log View
Table Columns
| Column | Description |
|---|---|
| Date/Time | When change occurred |
| User | User who made change |
| SKU | Product changed |
| Channel | Channel affected |
| Period | Forecast period |
| Old Value | Previous forecast |
| New Value | Updated forecast |
| Change | Difference (+/-) |
| Reason | Explanation provided |
Sorting
Click column headers to sort:- Most recent first (default)
- By user
- By SKU
- By magnitude of change
Filtering the Edit Log
By Date Range
By User
Filter to see changes by specific team members:- Click the User filter
- Select one or more users
- View their changes
By SKU
Find changes for specific products:- Use the SKU filter
- Search or select SKUs
- See all changes for those products
By Channel
Focus on specific sales channels:- Click the Channel filter
- Select channels
- View channel-specific changes
By Change Type
Filter by type of modification:| Type | Shows |
|---|---|
| All | All changes |
| Increases | Only increases |
| Decreases | Only decreases |
| Overrides | Manual overrides |
| Reverts | Restored to original |
Understanding Log Entries
Example Entry
Reading the Change
| Field | Meaning |
|---|---|
| Old Value: 500 | Previous forecast was 500 units |
| New Value: 650 | Now forecasting 650 units |
| Change: +150 | Increase of 150 units |
| (+30%) | Represents a 30% increase |
Analyzing Edit Patterns
Common Analysis
Use the edit log to understand: Volume of Changes:- How many edits per day/week?
- Are certain periods heavily edited?
- Trending up or down?
- Which SKUs get most edits?
- Which channels have most adjustments?
- Who makes the most changes?
- What categories of reasons appear most?
- Are promotions driving many changes?
- Seasonal patterns in editing?
Accuracy Analysis
Compare edits to outcomes:- Find historical edits for a period
- Check what the actual sales were
- Was the edit directionally correct?
- Was the magnitude appropriate?
Edit Log Reports
Exporting the Log
Report Uses
- Audit compliance - Demonstrate forecast governance
- Team review - Discuss changes in planning meetings
- Training - Show examples of good/bad adjustments
- Process improvement - Identify patterns to address
Edit Log Settings
Admin users can configure edit log behavior:Retention Settings
How long to keep edit history:| Option | Keep Data For |
|---|---|
| 6 months | Recent history |
| 1 year | Standard retention |
| 2 years | Extended retention |
| Unlimited | Full history |
Required Reasons
Configure whether reasons are required:| Setting | Behavior |
|---|---|
| Required | Must enter reason to save edit |
| Optional | Reason encouraged but not required |
| Required for large changes | Required if change > X% |
Category Options
Configure reason categories:- Promotion
- Seasonal
- Market condition
- Product lifecycle
- Error correction
- Other
Best Practices
Review Regularly
Review Regularly
Check the edit log weekly:
- What’s being changed?
- Are changes justified?
- Any unexpected patterns?
Require Reasons
Require Reasons
Configure reasons as required:
- Builds accountability
- Improves analysis
- Helps with training
Analyze Accuracy
Analyze Accuracy
Periodically check edit outcomes:
- Were increases warranted?
- Were decreases accurate?
- Learn from discrepancies
Export for Reports
Export for Reports
Use exports for:
- Monthly planning reviews
- Quarterly business reviews
- Audit documentation
Compliance Uses
For regulated industries or audit requirements:SOX Compliance
Edit log supports Sarbanes-Oxley requirements:- Who made changes
- When changes occurred
- What was changed
- Reason documentation
Internal Audit
Provide to auditors:- Export full history
- Show access controls
- Demonstrate governance
Troubleshooting
Missing Edits in Log
Possible causes:- Date filter too restrictive
- Changes made before tracking started
- Bulk uploads may log differently
- Expand date range
- Check system start date
- Look in import/upload logs
Can’t Export
Possible causes:- Too much data selected
- Permission restrictions
- Browser blocking download
- Filter to smaller dataset
- Verify export permissions
- Check browser download settings