Skip to content

Keep the project record for as long as the liability runs.

SIINC keeps Procore, Autodesk Forma and BIM 360, and Oracle Aconex project records in storage your company governs, so risk, legal and insurance teams can produce them when a claim arrives years after completion. By then the platform subscription has usually lapsed and the project team has moved on. The run history shows what was captured and when, and the audit log shows who accessed it.

Role
Risk, legal and insurance
Platforms
Procore, Autodesk, Aconex
Use cases
Project closeout, Claims and disputes, Records retention
Backups stored in
Amazon S3 or Azure Blob Storage, in your account
Drawingexecutions and audit log, exportableNoteExportable for reviewsSheetScale1:1

What risk, legal and insurance teams answer for after completion

  • Records held for as long as the company can be held liable, not as long as a licence lasts.
  • Evidence that can be produced when a notice of claim or a dispute arrives.
  • Retention obligations applied the same way across every project.
  • Answers for insurers, auditors and tenders on how project data is protected.

Questions risk, legal and insurance teams get asked about project records

How long do construction records need to be kept after completion?
Longer than the platforms keep them. When a subscription ends or a project closes, access to the record runs out within weeks, while limitation periods for building claims run for years after completion and vary by jurisdiction. These are exposure windows, not record-keeping rules, and they depend on your contracts and where the work was done, so ask your lawyer to set the period. This is general information, not legal advice.
How do we show what the record held, and when it was captured?
Use the SIINC execution history and audit log. Every run is recorded with its scope, size, warnings and errors, so you can see when each record was backed up. A checksum is recorded for every file and the run history is tamper-evident. The client audit log records every user and admin action, is kept for 12 months and can be exported for reviews.
Can project backups be locked so nobody can change or delete them?
Yes, with your own storage settings. The backups sit in your own S3 or Azure account, so your retention and immutability rules apply, and SIINC works with S3 Object Lock and Azure immutable storage turned on.
What if records are deleted from the platform before a claim is made?
They stay in your backup for the term of your plan, because Sync runs keep deletions. File versions are captured too, so what was overwritten in Procore, Autodesk or Aconex is still there, and access to the storage itself is governed by your own policies.
What do we tell an insurer or tender that asks how project data is protected?
Send them a SIINC report. Scheduled reports and the exportable audit log show what was backed up and who accessed it, in PDF, Excel, CSV or HTML.

Risk, legal and insurance backup questions

Usually daily logs, correspondence, RFIs, change orders, invoices and payments. In SIINC each of these is a module you can select for backup.

Yes, with your own storage settings. Backups sit in your own S3 bucket or Azure Blob container, so your retention, immutability and access policies apply as normal. SIINC has been tested with S3 Object Lock and Azure immutable storage turned on.

They stay in your bucket in readable form. You keep the copy.

Not yet. SOC 2 Type II and ISO 27001 are both in progress. Data is encrypted with AES-256 at rest and in transit, and SIINC is independently penetration tested.

Not when it backs up. Backups only read from the source platform and write to your storage. SIINC writes into Procore, Autodesk or Aconex only when you run a restore, which can put records back into the same account or a different one. On Enterprise, the archived-project feature brings archived Autodesk projects into backup scope, when you start it or automatically.

Start a trial workspace or book a demo and we will run the first backup with you.