Because data changes the minute you pull it, SecureSheet has tools available for you to manage data before and after go-live – from complete data refreshes and updating specific column values to adding new employees. Using the various import/export capabilities in SecureSheet, SecureSheet administrators can accommodate and manage your changing data scenarios. Here are some considerations around preserving audit history :


Before go-live:

  • Import/Export refreshes to your data as many times as desired or needed.
  • When you import a different number of rows, or anything changes about the order of the rows you import, compared to the current data set in SecureSheet, the SecureSheet Cell History will be wiped clean from that point in time. This becomes highly important after go-live, but is rarely an issue before go-live.
  • The main consideration for preserving cell history after go-live is to accommodate tracking the status of an employee in the structure of your SecureSheet before go-live.
    • For example, an Employee Status column can track "Termed" status. If an employee terminates during the open planning period, changing the employee status to "Termed" preserves the cell history.
      • If needed, employees with "Termed" status can be filtered out of manager views such that they do not hit the budget during the process.
  • Another consideration is if you have a requirement around the sort order of your data. You may sort your data in any order desired. For on-going data management after go-live, if you want to export and resort data, import resorted data, and preserve cell history through the process, make the SecurSheet Support team aware of this requirement. 
    • There is a property on your SecureSheet to sync cell history with each row's Unique ID on import, and this can be set by the SecureSheet Support team. The Unique ID is the value that is stored in Column A on the main tab in your SecureSheet.
  • If you have minor data adjustments to make, you may update the data values in any value-based column in the .All Data (Edit) or the Administration views in SecureSheet. When you click Save Changes, your updates will be visible immediately.


After go-live:

  • SecureSheet tracks all cell level data changes (before and after go-live). Think of SecureSheet as a big grid with a lock on each and every cell in the SecureSheet structure. This means that SecureSheet knows the cell based on its value and its position in the structure. If the number of rows or the order of the rows changes from what is in SecureSheet to something different contained in an import file, SecureSheet will infer a different number of rows or a different order of rows as a new file, and will wipe the cell history clean up to that point.
  • In order to preserve cell history, the number of rows and the order of the rows must remain consistent through the planning cycle.
    • For on-going data management after go-live, if you want to export and resort data, import resorted data, and preserve cell history through the process, make the SecureSheet Support team aware of this requirement prior to go-live.
    • Any additional rows must be added online, not through an import with additional rows added to an Excel file and then imported.
  • If an employee terms during the planning cycle, change the employee status column and do not delete the row. Rows must not be deleted during a planning cycle in order to preserve cell history. If a row is deleted, cell history will be wiped clean.
  • If you have minor data adjustments to make, you may update the data values in any value-based column in the .All Data (Edit) or the Administration views in SecureSheet. When you click Save Changes, your updates will be visible immediately.


Tools for managing data:


Video Resources: