How to recover a takeoff after changing devices
Keep your existing copies, compare their drawing revisions and completed work, then restore the best available backup. Review the recovered quantities and costs before syncing again.
Stop before deleting or overwriting anything
Keep the old device, replacement device, local project folders, portable backups, exports, and Cloud workspace unchanged until you know which copy contains the most complete approved work. A newer file timestamp does not prove that its drawing issue or scope is correct.
If the old device still opens the project, record the project name, drawing issue, last completed task, visible quantity totals, estimate version, and last known upload or backup. Capture the facts needed to compare copies before attempting a restore.
- Old device preserved when available
- Replacement device left unchanged
- Project and drawing identity recorded
- Last completed work noted
- Available backups inventoried
Related: Rivet Cloud recovery path — Understand encrypted revisions, state checks, and recovery copies.
Inventory every recovery path
List the last known local workspace, dated portable backups, exported evidence, and any optional Rivet Cloud revision. For each candidate, record its date, device, user, drawing issue, measured scope, estimate stage, and whether another person may have changed it.
Rivet is local-first and optional Cloud syncing does not replace an independent portable backup. The safest recovery candidate is the one whose content and project identity can be verified, not simply the copy with the most recent label.
Related: Multi-device takeoff workflow — Plan device continuity before the next handoff.
Restore account access
Sign in as the correct named Rivet member and confirm the intended workspace and subscription plan. Each named member can connect up to two devices; device access should remain assigned to the actual user rather than shared through one account.
Cloud downloads and account changes require connectivity. If access, verification, or a device limit blocks recovery, stop and use the account recovery options or contact support instead of creating duplicate projects or deleting evidence.
- Correct named member
- Intended workspace confirmed
- Connection available for Cloud actions
- Device authorization checked
- No shared credentials used
Related: Limited-connectivity preparation — Prepare local access and backups before leaving coverage.
Compare local work, backups, and Cloud revisions
Inspect each available copy and compare the drawing issue, completed takeoffs, quantities, notes, assumptions, and estimate totals. Confirm that the copy contains the approved work before choosing it.
Rivet prevents older work from silently replacing a newer Cloud revision and keeps a recovery copy before a Cloud download replaces local work. Retain that copy until the recovered estimate has been reviewed.
Related: Windows and Android workflow — Assign device roles and release one approved state.
Restore one working copy without erasing the others
Use the supported portable-backup import or Cloud download path that matches the selected source. Restore to the replacement device, verify the project and drawings, and avoid immediately uploading until the recovered quantities and estimate have been reviewed.
If the chosen source is older than documented work, identify the missing interval and recreate only from reliable field notes, exports, emails, marked drawings, or another preserved copy. Record any reconstruction as a reviewed change rather than presenting it as an untouched original.
- Selected source documented
- Other copies retained
- Restored project opens correctly
- Drawing issue verified
- Missing interval identified
Reconcile, approve, and create a new baseline
Compare recovered quantities, costs, proposal state, RFIs, and assumptions with the pre-change record and any work completed on another device. Decide whether to keep, reject, or investigate each difference.
After a qualified reviewer approves the recovered state, create a new dated portable backup and record the responsible owner. Only then should the team publish the next Cloud revision or retire obsolete device copies under its retention process.
- Quantity variance reviewed
- Estimate and proposal reconciled
- Unresolved differences assigned
- Approval and responsible owner recorded
- Fresh portable backup created
Frequently asked questions
Can I recover a takeoff if the old device is unavailable?
Recovery requires another preserved source, such as a portable backup, an available Cloud revision, or sufficient approved evidence to reconstruct missing work. Preserve all candidates before choosing.
Is the newest Cloud revision automatically the approved estimate?
No. It may be the newest technical revision, but the team must still verify its drawing issue, scope, quantities, costs, and approval state.
Should Cloud replace portable project backups?
No. Rivet Cloud supports device continuity, while a dated portable backup remains an independent recovery path before device changes and major revisions.