| Drawing-linked tasks | Documented by vendor | Tasks and photographs provide construction-plan context for follow-up. Business workflow scopePlan upload, OCR naming and version-conflict workflow : checked 29 September 2026 |
|---|
| Custom safety forms | Depends on scope | Business supports custom templates, including safety audits; Pro should not be quoted as the custom-form package. Business workflow scope |
|---|
| Reports and exports | Depends on scope | Pro adds reporting and exports. Verify the exact output needed by the client. Current plan comparison |
|---|
| Offline mobile work | Depends on scope | Previously downloaded projects can be used on iOS/Android; authenticate first and keep the app open when reconnecting. Mobile offline requirements |
|---|
| API and SSO | Depends on scope | Commercial terms are discussed separately rather than assumed in a standard self-service licence. Current plan comparison |
|---|
| Account-wide templates | Documented by vendor | Premium setup guidance describes reusable form templates across projects. Premium feature configuration |
|---|
| Custom construction forms with statuses and links | Depends on scope | Business and Business Plus include the Forms module and Custom Form Builder for default or new templates such as Safety Audits, JHAs and QA or QC inspections, with statuses, attachments, calculations, signatures, task links and plan links. Confirm plan entitlement, account-versus-project template ownership, required fields, status transitions, version behavior, deleted-form recovery, export content and whether the configured form actually implements the buyer's approval and retention procedure. Custom forms, statuses, attachments, links and signature configuration : checked 29 September 2026Business workflow scope |
|---|
| Task checklists with timestamped line-item history | Depends on scope | Fieldwire supports task checklists, reusable project and account templates, mobile completion, up to 500 checklist items per task, and reports containing who checked each item and when. Editing a template does not update checklists already placed in tasks, and account-template changes are not automatically propagated to imported project copies. Confirm template governance, obsolete-version warnings, reopening, evidence and independent verification. Task checklists, timestamped completion and account templates : checked 29 September 2026Checklist template management and update behaviour |
|---|
| Role- and form-specific permissions | Depends on scope | Form templates can restrict who may create, view and edit forms by project role, while deleting and reopening follow default role rules and status settings, allowing different treatment for safety violations, JHAs or inspections. Mobile users need supported app versions for newer permission behavior. Test Admin, Member and Follower access, form assignees, sensitive-form visibility, offline cached access, deleted and reopened records, stale clients and permission changes during a project. Form permissions by project role, form type and mobile-version dependency : checked 29 September 2026 |
|---|
| Form signatures and external-signer workaround | Depends on scope | Custom forms support signature sections and configurable minimum and maximum counts. An onsite Fieldwire user can select 'Sign as someone else' and type the person's name; an offsite non-user is handled through an exported PDF and third-party PDF editor. These routes do not by themselves establish identity assurance, electronic-signature compliance or reintegration into the authoritative Fieldwire record. Define allowed signers, witnessing, attribution, tamper evidence, external-PDF import and retention. Custom forms, statuses, attachments, links and signature configuration : checked 29 September 2026Third-party form signature limitations and PDF workaround : checked 29 September 2026 |
|---|
| Plan OCR, versioning and conflict resolution | Depends on scope | Project Admins can upload plans; Fieldwire uses OCR to scan, name, version and hyperlink sheets and provides a workflow to resolve version conflicts. Premium cloud-storage syncing is separately scoped. Confirm supported file quality and fonts, admin review, revision identifiers, superseded-sheet access, carried markups and tasks, conflict handling, notification of field users and the authoritative drawing register; OCR output is not guaranteed correct. Plan upload, OCR naming and version-conflict workflow : checked 29 September 2026 |
|---|
| Documented security and data-location controls | Depends on scope | Fieldwire's security article describes AWS hosting, access controls, data regionalization topics and multiple export routes. Treat these as vendor documentation, not proof that every standard, region or control applies to the proposed account. Request current reports, contractual region, subprocessors, encryption and key scope, support-access controls, retention, backups, incident terms and tested export and deletion behavior. Fieldwire data-security, access and regionalization documentation : checked 29 September 2026 |
|---|