How Constructable Works

Performance and Connectivity

Constructable is designed to keep your everyday project work responsive, even on a large project. For supported project data, you may see a change on screen before Constructable confirms it.

Verified October 12, 2026

Constructable is designed to keep your everyday project work responsive, even on a large project. For supported project data, you may see a change on screen before Constructable confirms it.

Fast local interactions

Many supported changes appear quickly instead of making you wait for Constructable to send the change and receive confirmation. For example, an update you make during a site walk may appear on your screen right away while Constructable confirms it in the background.

That immediate update does not mean Constructable has confirmed the change. If Constructable cannot accept it, it may show an error or replace what you see with the saved version. Do not assume your teammates have received an update until Constructable confirms it.

Fresh updates across the team

When Constructable accepts new work or finishes background processing, connected sessions are prompted to refresh the relevant data. Your teammates should normally see accepted changes without reloading the entire page.

Updates are not instant or guaranteed while a device is disconnected. A weak jobsite connection, file processing, or a long-running operation can delay what another person sees.

Progressive loading on large projects

Constructable loads large projects in stages. It loads essential information first, then brings in more records and detail as the page or task needs them. Search results and detailed drawing views can also fill in over time. This lets you start working without waiting for every record or high-resolution file.

A loading placeholder does not necessarily mean information is missing. Give the view time to finish, especially after you open a large project, switch projects, search across many records, or zoom deeply into a drawing.

Downloading your project data to a device can take a while when there's a lot of it. If it runs long, you'll see Hang tight, it's still loading. Leave that screen open — the app opens on its own when the download finishes, and closing or reloading starts the download over. (The Make it go faster button is there for morale. It doesn't change the download.) If the download actually fails, you'll see We couldn't load your data instead, and Reset and reload clears the copy saved on this device and downloads a fresh one.

What this means for you

  • A common supported edit can appear on your screen before Constructable confirms it.
  • Teammates who are online usually receive your accepted changes shortly after they happen.
  • You may be able to start working in a large project while additional details continue to load.
  • Repeatedly refreshing can interrupt an upload, restart a long data download, or hide the real connection problem. Check the status shown in your current workflow first.

Prepare for changing connectivity

Prepare drawings for offline viewing before entering a low-connectivity area. Reconnect regularly to refresh project records, run search and AI workflows, complete file transfers, and confirm saved changes.

In the native app, store the sheets, disciplines, or drawing areas you need while you're online, then test them on your device before field work. Offline storage isn't available in a web browser. See Storing drawings for offline viewing.

If something looks stale or incomplete

  1. Confirm that your device is online and that you are in the intended organization and project.
  2. Wait for any upload, processing, or saving indicator to finish.
  3. Once your connection is stable, reopen the record or refresh once.
  4. Verify the change in its normal workflow before you rely on it.
  5. If the problem continues, report the project, record, time, browser or device, connection state, and any visible error.

For workflow-specific help, see Troubleshoot Search, Troubleshooting Drawings, and Troubleshooting Photos.