A rugged tablet may open a construction drawing without a network connection, but that does not establish that the file is the approved version for today's work. The field workflow must connect project identity, sheet number, revision, approval status, local availability and synchronization state.
This guide uses an editorial scenario: a tablet holds sheet A-214 Rev B, while the office later publishes Rev C. It is not a customer case or an AIDC GO compatibility test. Application features, permissions, file behavior and hardware suitability must be verified for the selected software, platform and device configuration.
Define the drawing identity before the crew leaves
Record the project or collection, drawing number, title, required revision or version set, approval status and the role allowed to use it. Similar sheet numbers can exist in different projects or collections, so a filename alone is not a sufficient identity rule.
Autodesk's current mobile Sheets documentation describes sheets organized by collection, mobile version history and update notifications in the Autodesk Forma mobile app. These are product-specific capabilities; they do not prove compatibility with an AIDC GO tablet or another document platform.
Download the required set and test it offline
Before departure, sign in under the intended field account, select the correct project and download the required sheets or files. Then disable connectivity under controlled conditions and open each needed drawing, not just the project list. Check whole-sheet view, detail zoom, references needed for the task and the storage consumed by the agreed set.
Autodesk documents project download for iOS and Android in Sync and Download Projects and file-level controls in Sync and Download Files. The latter states that downloaded files can be used offline and that “download latest version automatically” can be configured for selected files or folders. Exact behavior still depends on the named Autodesk environment, permissions and current app.
Separate “opens locally” from “approved for work”
In the editorial scenario, A-214 Rev B opens on the tablet after connectivity is lost. The screen proves that a local file is available; it does not prove that Rev B remains approved after Rev C was issued. The crew should compare the visible project, sheet and revision information with the project's authorised drawing register or status rule.
Autodesk notes in its mobile download FAQ that previously downloaded items can remain on a device under some changed download settings. That is another reason not to treat local presence as current approval. The applicable status must come from the project process, not from file openability alone.
| Field observation | What is known | What is still not established |
|---|---|---|
| Rev B opens with the tablet offline | A local copy is readable in the tested app and state | This does not establish that Rev B is the approved version for current work |
| The office has published Rev C | A newer office-side version exists in the named system | This does not establish that the field tablet has downloaded or acknowledged it |
| A sync completes without an error banner | The app reports completion for that sync attempt | This does not establish that every required sheet, markup and issue is current |
| A field note is visible on Rev B | A note is associated with the locally viewed version | This does not establish that it is linked to Rev C or visible to the office team |
Attach markups and issues to the viewed version
When a user records an issue, markup or question, retain the project, drawing number and viewed revision with the record. If the application allows version history, make the selected version visible before annotation. A photo or note timestamp alone cannot identify the sheet version that framed the observation.
Autodesk's Android guidance for issues in the mobile viewer documents issues and markups placed on 2D files or sheets, with permission and offline considerations in that named environment. It should be evaluated as an Autodesk example, not translated into a general tablet capability.
Reconcile changes after connectivity returns
After reconnecting, identify separately what uploaded from the field, what downloaded from the office and what changed version. Do not assume that one sync icon proves every direction is complete. Review unresolved errors, local-only notes, new sheet versions and records that were created against Rev B after Rev C became available.
Autodesk's mobile Sheets help describes an “updates available” message and manual sync when background sync is not enabled. It also notes that some markup or issue changes do not trigger the same sheet-update message. This supports testing each content type that matters instead of relying on one project-level status.
Resolve the Rev B versus Rev C decision explicitly
If the project process says Rev C supersedes Rev B, stop work that depends on the changed detail until the authorised version is available and understood. Preserve any Rev B field record with its original context, then decide whether it must be transferred, closed or re-created against Rev C. If the system cannot prove which revision is approved, escalate through the project document-control path rather than silently treating the local file as current.
The tablet and application can present evidence, but the project owner defines approval, supersession and conflict handling. This article does not assume that Autodesk, another app or any AIDC GO model automatically enforces those rules.
Evaluate hardware with real drawings and field actions
Test the selected drawing set, including whole-sheet navigation, small annotations, detail zoom, page changes, form or issue entry and representative offline storage. Record lighting, reflections, viewing angle, gloves or stylus use where applicable, file complexity, available storage, carrying method and power plan. Do not substitute a processor name or screen diagonal for the actual workflow.
The outdoor screen-readability guide covers reflections and viewing angles. The storage-planning guide explains why offline files and update headroom need a measured budget. The offline transaction guide provides the separate principle that local completion and server acceptance are not the same state.
Build the procurement brief around the approved workflow
Name the document platform and mobile app version, supported OS, account permissions, project and sheet identifiers, approval method, offline set, expected file sizes, markup or issue workflow, conflict handling, storage budget, display conditions, input method, mounting and charging arrangement. Use the actual drawings and field roles in evaluation.
Review the rugged tablet category, Field Service & Inspection and the rugged tablet field-operations solution as commercial entry points. Send the confirmed app, OS, file and interface requirements through Integration Support before selecting a model configuration.