The platform

The managed platform behind your branded field workflow product.

White-label field workflow software, operated for you: offline mobile capture, web review, dispatch, branded reports, signed webhooks, a REST API, and an MCP server. You bring the workflow and the customer relationship; FieldScroll runs everything underneath it.

What lives where

Where FieldScroll fits in your product stack.

FieldScroll is

The field layer: build, capture, govern, automate, extend

  • Branded mobile capture that works offline, and a branded web dashboard for review.
  • Dispatch, reports, and signed webhooks that close the loop with the office and downstream systems.
  • Version-aware records that keep their meaning as the workflow changes.
  • A REST API, an MCP server, and managed data sources so it fits the customer's stack.
  • Dedicated infrastructure per partner, monitored and released by us, with a monthly meeting and a quarterly review.

FieldScroll isn't

Your full system of record or custom app layer

  • The long-term database where all customer history lives.
  • A fully custom customer portal, CRM, or vertical SaaS product.
  • A multi-year archive, BI warehouse, or analytics platform.
  • A generic self-serve form builder for end users.
  • Unlimited custom screens, data models, or product features.
How a record moves

Scan, capture, review, correct, report.

FieldScroll runs the whole loop from a field visit to a finished document or downstream record — including the second visit. Your system of record stays in its own home; we deliver clean output to it.

  1. Open the right form

    A field user finds the form in the branded app, or scans a QR code that opens it with the asset already filled in.

  2. Capture offline

    Structured data, photos, signatures, location, and lookups against reference data — drafts queue on the device and sync when connectivity returns.

  3. Review on the web

    Submitted records land in a branded dashboard with search, filters, and a record detail view. Edit where permitted, or export.

  4. Dispatch a correction

    A record that needs a second visit is checked out to one field user with its media, notes, and a due date. It is locked while out; resubmitting replaces the original.

  5. Report and route

    Each submission can render a branded PDF or HTML report and deliver it to email and webhook destinations, each retried on its own, with delivery history you can see.

Capability stack

Build, capture, govern, automate, extend.

Every claim below links to the documentation that backs it. If it is not documented, it is not on this page.

  1. 01

    Build

    Turn a written procedure into a working form, report, and integration without a developer in the loop for every change.

    • AI-assisted authoring, human-approved

      Describe a form, report layout, or webhook transform in plain language. The assistant proposes a change; you review it, then apply or discard. Proposals pass the same checks as hand edits, and nothing reaches the field until you save and publish.

      Read the docs

    • Test the real logic before publishing

      Test mode runs the form as the device will — visibility rules, formulas, lookups, pages — with nothing saved. Publish to a test form to exercise capture and sync end to end.

      Read the docs

    • Logic without code

      Conditional visibility, formulas, read-only computed fields, lookups filtered by earlier answers, repeating tables, and pages.

      Read the docs
  2. 02

    Capture

    Crews keep working through bad signal, and they start from the right record instead of typing it in.

    • Offline-first mobile forms

      Branded iOS and Android. Drafts, photos, signatures, and location are stored on the device and sync when the connection returns.

      Read the docs

    • QR codes and deep links

      A printed code on a machine, vehicle, or door opens the right form with the asset's fields already filled in. You generate the codes from your own data — one or ten thousand.

      Read the docs

    • Reference data on the device

      Sites, assets, parts, prices, and controlled lists live in data sources that sync for offline lookup, filtered by the answers already given.

      Read the docs
  3. 03

    Govern

    Change tomorrow's workflow without rewriting yesterday's evidence.

    • Versions that do not rewrite history

      Every publish is an immutable version, and a record stays tied to the version it was captured against. A compatibility preview says before you publish whether existing records will follow or stay put.

      Read the docs

    • Roles and assignments

      Five roles, per-form assignments through teams and collections, and organization-level isolation enforced in the database.

      Read the docs

    • Retention, backups, deletion

      How long records, media, and logs are kept, how backups work, and what deletion actually removes — written down, not implied.

      Read the docs
  4. 04

    Automate

    One field event becomes customer-facing evidence and downstream handoffs, with visible delivery state.

    • Dispatch back to the field

      Check a submitted record out to one field user for a follow-up inspection, work order, or recheck. It is locked while out, and resubmitting replaces the original and fires a webhook.

      Read the docs

    • Reports with delivery history

      HTML/CSS templates with loops, conditionals, photos, and signatures render to PDF or HTML. Each email or webhook destination is retried on its own, and every delivery is listed with its status.

      Read the docs

    • Signed webhooks

      HMAC-signed deliveries for record, form, collection, and team events, with an optional preprocessing script to reshape the payload before it leaves.

      Read the docs
  5. 05

    Extend

    Use FieldScroll as the field layer of your customer's stack, not another isolated system.

    • REST API

      Organizations, users, forms, records, data sources, webhooks, reports, publishing, and assignments — with OpenAPI and Postman resources. Scoped, hashed keys bound to one organization.

      Read the docs

    • MCP server for AI tools

      Approved AI tools can search the docs, inspect form schemas and records, and check deliveries. Seven write tools exist and only work with write scopes on the key. There is deliberately no tool that merges a report.

      Read the docs

    • Managed data sources

      Point a data source at a Postgres or MySQL table or view and it stays in sync, so the system of record keeps owning the reference data.

      Read the docs
Two-way data

Reference data in, finished work out.

Inbound managed sources and outbound destinations are different things. Both are listed here so the boundary is clear before an integration conversation starts.

  • Data in

    Reference data from your customer's system of record — Postgres or MySQL tables and views, CSV imports, or bulk API writes — feeds offline lookups in the field.

    Read the docs

  • Data out

    Completed records, rendered reports, and events return through webhooks, email, and the API. Outbound destinations beyond email and webhook are scoped separately.

    Read the docs
Evidence you can defend

Specific controls, not security language.

Inspection, audit, compliance, and QA programs live on evidence. These are the controls a record actually carries, and the ones FieldScroll does not claim are listed in the security documentation.

  • Who, when, where, on what

    Every submitted record carries the submitting user, the timestamp, the device model and app version, and GPS coordinates when the form captures location.

    Read the docs

  • Integrity fingerprint

    A SHA-256 checksum of the field values is computed on the device at upload and stored with the record.

    Read the docs

  • Isolation in the database

    Each customer's data lives in its own organization, enforced by row-level security on every query and by each API key's organization binding.

    Read the docs

  • Signed and scoped

    Webhook deliveries are HMAC-signed. API keys are scoped, hashed at rest, shown once, and bound to one organization.

    Read the docs
Extension model

More than a skin. Custom screens without a custom app fork.

Most white-label apps stop at branding. FieldScroll includes branded app identity, customer-facing surfaces, document branding, and environment-level configuration by default.

When a workflow needs more than a standard form, FieldScroll can add scoped custom mobile screens inside the shared app shell. Those screens use the existing authentication, navigation, sync, data access, and standard components, so your product can feel domain-specific without becoming a one-off codebase. The screens in the diagram are illustrative; custom screens are scoped separately.

Straight answers

What evaluators ask first.

How does a record move from the field to a customer or a system?
A field user opens a form — by search or by scanning a QR code — and captures data, photos, signatures, and location offline. The record syncs to the web dashboard for search, filtering, and review. If it needs a second visit, dispatch checks it out to one field user for a locked, offline follow-up. On submission, webhooks fire and any wired report renders and delivers to its email, webhook, Box, and Google Drive destinations, each retried on its own with a visible status.
What can the API and the MCP server do?
The REST API covers organizations, users, forms, records, data sources, webhooks, reports, publishing, and assignments, with OpenAPI and Postman resources. The MCP server lets scoped AI tools search the documentation, inspect form schemas and records, check whether a report was delivered, and — only with write scopes on the key — create records, forms, and webhook subscriptions. There is deliberately no MCP tool to merge a report, because a merge sends real email.
What works offline?
Forms, drafts, photos, signatures, location, and the reference data a form's lookups need. Dispatched records arrive with their media and can be finished without a connection. Everything syncs when the device reconnects.
What is available now, and what is scoped separately?
Everything on this page is shipped and documented. Custom integrations, custom development, data migration, custom document libraries, an end-customer support desk, 24/7 support or a custom SLA, heavy compliance review, and private or customer-hosted deployment are quoted separately. Word or Excel report output does not exist.

Next step

See where FieldScroll fits your offer.

A 30-minute discovery call to map your downstream customer unit, the workflows you already run, and where FieldScroll takes load off your team.

Talk with us