Data Reprocessing Requests: When & Why to Use Them

Occasionally, updates made in the VergeSense platform require historical data to be recalculated so reports, dashboards, and insights reflect the most accurate information. This process is called data reprocessing and is sometimes also referred to as backfilling.


What is data reprocessing?

Data reprocessing recalculates historical occupancy metrics using updated metadata or floor plan information. It ensures that past data aligns with how spaces are currently defined in the platform.

Reprocessing does not change raw sensor data — it only updates how that data is interpreted and aggregated.


When is reprocessing necessary?

Reprocessing is typically required when historical context changes in a way that affects how data should be interpreted.

Reprocessing is required when you:

🏢 Change space definitions

  • Space type changes (e.g., Desk → Focus Room)

  • Space group changes

  • Capacity updates

  • Space splits or merges

  • Spaces added retroactively to a floor

These changes affect historical metrics like:

  • Time usage

  • Capacity usage

  • Aggregated building or floor metrics


🗺️ Update floor plans with historical impact

  • New floor plan versions that apply to past dates

  • Corrections to previously incorrect layouts

  • Spaces marked live or inactive retroactively


When is reprocessing not necessary?

Reprocessing is not needed for changes that only affect the platform going forward.

Reprocessing is not required when you:

  • Rename spaces (no structural change)

  • Rename Space Types

  • Add new spaces with a current or future effective date

  • Make changes that only apply from “today forward” (such as a capacity change due to adding or removing chairs)

In these cases, new data will automatically reflect the update without recalculating history.


What does reprocessing affect?

Depending on the request, reprocessing may update:

  • Historical dashboards and charts

  • CSV exports

  • Automated insights

It does not:

  • Modify raw sensor readings

  • Change previously exported files

  • Affect real-time or future data collection


How far back does reprocessing go?

VergeSense can reprocess up to 12 months of historical data, unless a different range is requested and supported.

Longer reprocessing windows may:

  • Take additional time

  • Be reviewed on a case-by-case basis

Note: When Space Groups are changed, we automatically reprocess the past 90 days. 


How to request a reprocessing

When submitting a request, please include:

  1. Account name

  2. Building(s) and floor(s)

  3. What changed (space type, space group, capacity, layout, uploaded data, etc.)

  4. Effective date of the change

  5. Why historical data needs to be updated

  6. Preferred reprocessing window (if known)

Providing this information upfront helps us process your request faster and avoid unnecessary recalculations.


How long does reprocessing take?

Most requests are completed within a few business days, depending on:

  • Number of buildings and floors

  • Length of historical data being reprocessed

  • Complexity of the changes

Your VergeSense team will confirm timing once the request is reviewed.


Best practices to avoid unnecessary reprocessing

  • Bundle multiple changes into a single request when possible

  • Confirm effective dates before submitting floor plan updates

  • Reach out to Support if you’re unsure whether reprocessing is needed

Updated

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.