What is a Scoring Date?

SecurityScorecard gathers and compiles data daily. Because data collection for a given day is still ongoing, the data can only be compiled and published after the day ends. This means there is typically a 48–72 hour delay between when data is gathered and when it appears on the platform.

The scoring date (also referred to as the effective date or platform date) lags a few days behind the current date. This delay occurs because any changes to a scorecard must first be calculated and then published to the platform before they are visible. This process typically takes 2–3 days from the date the changes are made.

The table below illustrates how data moves through the pipeline:

This is a simplified timeline for illustrative purposes. Due to various factors, data processing may take longer than one day. Data visible on the platform does not update at a fixed time during the day.

What triggers a scoring recalculation?

Almost all changes that require a scoring recalculation follow the scoring date concept, meaning they take a few days to appear on the scorecard. This includes:

• Findings that are approved for removal from the scorecard (for example, a finding marked as resolved that still appears under open findings)
• Changes made to the digital footprint of the scorecard
• Changes made to a custom scorecard, including modifications to the digital footprint or source scorecard

In all of these cases, the scoring date must catch up to the date when the changes were made before those changes are visible on the platform.

Example

In the example below, a finding was marked for resolution on May 15, 2024. At that time, the scoring date was May 12, 2024. The finding will drop off the scorecard once the scoring date advances to May 15, 2024.

Note: The exact scoring date and time are not fixed. When scheduling a task using a script, it is recommended to reference the scorecard date rather than the current date.