Platform availability
Platform | Availability |
iOS | ✅ Available |
Android | ✅ Available |
Windows | ✅ Available |
Web / User Site | ✅ Admin management only |
Overview
Think of iField Data as the structured questions your team answers about a job, things like site conditions, building access notes, inspection findings, or client-specific details that need to travel with the project and show up on your proposal.
How Field Data fits into ArcSite
ArcSite has three ways to collect information during a job. Understanding the difference prevents mis-setup:
Tool | What it captures | Where it lives |
Field Data | Project-wide information (applies to the whole job) | Reports menu → Report Inputs → Field Data tab |
Product Attributes | Object-specific information (tied to a single drawn item) | Tapped directly on a placed product on the canvas |
Forms | Structured checklists and inspection documents | Reports menu → Forms |
Use Field Data when the information applies to the project as a whole, not to a specific measurement or product. Examples: "Was the homeowner present?", "What floor type was observed?", "Installation crew notes."
Use Product Attributes when the information is specific to one drawn object, for example, the color or model of a specific unit placed on the canvas.
How Field Data works
Field Data fields are created and managed centrally by an admin on the ArcSite User Site. Once created, they sync automatically to every team member's mobile device and appear in the Reports menu during any active drawing. This ensures your whole team collects the same information, consistently, on every job.
Collected Field Data can be:
Displayed in your proposal output using the Additional Information block in the Proposal Template
Used to show or hide content in proposals dynamically via Conditional Texts
Accessed via the ArcSite open API to push into external CRMs or automated workflows