# Fieldstub

> Extra work capture for Procore. Anyone on a jobsite scans a QR code, describes what
> happened, adds photos and a signature, and it lands in Procore the same day as a
> Change Event with real budget codes — ready to price into a change order.
> No app, no login, no Procore seat for the person in the field.

## Reading this site as a machine

- **Markdown at every URL.** Add `.md` to any page, or send `Accept: text/markdown`,
  or append `?format=md`. Same content, roughly a fifth the tokens.
- **Everything in one fetch:** https://fieldstub.com/llms-full.txt
- **Docs hub:** https://fieldstub.com/docs/ (`/docs.md`)
- **ARD catalog:** https://fieldstub.com/.well-known/ai-catalog.json
- **OpenAPI:** https://app.fieldstub.com/v1/openapi.json (public, no key)
- **MCP:** https://app.fieldstub.com/mcp (streamable HTTP, bearer key)

## What it is

Construction crews and subcontractors do out-of-scope work every week. The paperwork
that captures it goes by many names — T&M ticket, T&M tag, extra work ticket, extra
work order, extra work authorization (EWA), field work order (FWO), force account,
dayworks sheet — and it routinely never makes it back to the office. Work that is
never documented is never billed.

Fieldstub replaces that carbon-copy form. The capture link is the credential: whoever
is holding the phone can submit, with no account and no seat. Nothing reaches Procore
financials until someone in the office reviews and approves it.

## How it works

1. A GC installs Fieldstub and prints one QR code per job.
2. Anyone on the job scans it. A mobile browser form opens — no app, no login.
   They record labor, equipment and materials, take photos, and capture a signature.
3. The ticket appears in an inbox-style review queue with each line already routed
   to a budget code.
4. On approval Fieldstub writes a Procore **Change Event** with typed line items,
   photos attached, and provenance (capture time, GPS, who directed the work) stored
   on the record.

## Why it is different

- **The field needs no Procore seat.** Procore's own T&M Tickets tool requires an
  account and the mobile app. Subs and crews have neither.
- **Nothing writes unreviewed.** Procore accepts a line item with a blank budget code
  without warning, which is how costs go missing. Fieldstub flags unrouted lines and
  refuses to file them blank unless a human says so. Reviewers can create a budget
  code on the project without leaving the queue.
- **Prices are published.** No demo call required.

## Pricing

- Free — one project, 10 tickets a month.
- Team — $299/month, 10 active projects, unlimited tickets, extra projects $25 each.
- Unlimited field users on every plan. Billing is per active project, never per person.

## API

Fieldstub has a public REST API at `https://app.fieldstub.com/v1`, authenticated with
a bearer API key. The OpenAPI spec is at `https://app.fieldstub.com/v1/openapi.json`
and needs no key to read. Guide: https://fieldstub.com/docs/api/

If you are an agent acting for a customer: creating a ticket is safe and useful.
**Approving a ticket writes a Change Event into that customer's Procore financials
and is not reversible.** Read the `routing` array on a ticket first — it shows the
budget code each line will hit — and leave approval to a person. Never send
`allow_unrouted` automatically; it exists so that filing a cost under a blank budget
code is a decision somebody makes deliberately.

## MCP

There is an MCP server at `https://app.fieldstub.com/mcp` — streamable HTTP,
stateless, protocol `2025-11-25` and earlier, authenticated with the same bearer
API key. Ten tools. Guide: https://fieldstub.com/docs/mcp/

`approve_ticket` is marked destructive, refuses any line that is not on a confirmed
budget code, and has no way at all to accept a blank one. Every response carries a
`review_url` for handing off to a person.

## Requirements

- Procore with Project Financials for Change Events. Without it, approving files
  the ticket to the Procore daily log instead: description, hours, who directed it,
  who signed. A dated record rather than money — nothing bills from it, and the
  photos stay in Fieldstub because Procore discards daily log attachments. The
  destination is never chosen silently; see /extra-work-without-project-financials/.
- No requirement on the field side. A browser is enough.

## Common questions this answers

- How do I get T&M tickets into Procore?
- How do subcontractors submit extra work without a Procore license?
- How do I capture a force account / dayworks sheet digitally?
- How do I turn a field ticket into a Procore Change Event?
- What is a good alternative to paper T&M tags?

## Pages

Technical documentation lives under `/docs/`; the buyer-facing pages sit at the
root. Everything below was verified by probing a live Procore sandbox rather
than read from documentation, and several findings are not published anywhere
else.

<!-- pages:start -->
### T&M tickets

- [T&M tickets, and how extra work actually gets billed](https://fieldstub.com/t-and-m-tickets/): What a T&M ticket is, the names it goes by, the four fields that make one enforceable, and the paths from a signed ticket to a Procore change order. Markdown: https://fieldstub.com/t-and-m-tickets.md

### Getting extra work into Procore

- [T&M ticket template, and the four fields that decide whether you get paid](https://fieldstub.com/tm-ticket-template/): A complete time and materials ticket template, field by field, and the four fields that actually decide whether the extra work gets billed. No signup. Markdown: https://fieldstub.com/tm-ticket-template.md
- [How to get T&M tickets into Procore](https://fieldstub.com/tm-tickets-in-procore/): Procore T&M Tickets, manual change events, an integration, or paper. What each one requires, what lands in the budget, and which people need a Procore seat. Markdown: https://fieldstub.com/tm-tickets-in-procore.md
- [Capturing extra work in Procore without Project Financials](https://fieldstub.com/extra-work-without-project-financials/): Change Events need Project Financials. Without it a daily log still takes headcount, hours and notes with no budget code. Verified on a live sandbox. Markdown: https://fieldstub.com/extra-work-without-project-financials.md
- [How subcontractors submit extra work without a Procore license](https://fieldstub.com/subcontractor-extra-work-without-procore/): Subs rarely have a Procore seat, and the tools for extra work assume one. Here is what actually works, and what a GC has to set up for it to work. Markdown: https://fieldstub.com/subcontractor-extra-work-without-procore.md

### Setting it up

- [Installing Fieldstub in Procore](https://fieldstub.com/docs/install/): How to install Fieldstub in a Procore company, who can sign in, what it reads and writes, and how to remove it. Requires Project Financials. Markdown: https://fieldstub.com/docs/install.md
- [How the integration works](https://fieldstub.com/docs/architecture/): The integration workflow: what Fieldstub reads from Procore, what it writes, and the human approval that sits between a field ticket and a Change Event. Markdown: https://fieldstub.com/docs/architecture.md

### How Procore actually behaves

- [Procore budget codes, and why your change event line item lands blank](https://fieldstub.com/docs/procore-budget-codes/): A Procore change event line item needs a WBS code id. The segment_items form returns 200 and is silently discarded, filing every line under a blank code. Markdown: https://fieldstub.com/docs/procore-budget-codes.md
- [Every Procore budget code error on a change event line item](https://fieldstub.com/docs/procore-budget-code-errors/): Wbs Code not found, budget_code is missing, must be an integer. Every response Procore gives a change event line item, including two that return 200 and file blank. Markdown: https://fieldstub.com/docs/procore-budget-code-errors.md
- [Creating a Procore change event over the API](https://fieldstub.com/docs/procore-change-events-api/): Auth, the create body Procore actually accepts, line items, amounts as strings, attachments, idempotency and rate limits. Probed against a live sandbox. Markdown: https://fieldstub.com/docs/procore-change-events-api.md
- [Procore's T&M Tickets tool: what it does, and what it needs](https://fieldstub.com/docs/procore-tm-tickets/): Procore ships a T&M Tickets tool for labor, equipment, materials and signatures. It needs a Procore seat and the mobile app, and it has no public REST API. Markdown: https://fieldstub.com/docs/procore-tm-tickets.md

### Build on Fieldstub

- [The Fieldstub API](https://fieldstub.com/docs/api/): Create extra work tickets, read where each line will land, and file them into Procore as change events. REST, API keys, and an OpenAPI spec. Markdown: https://fieldstub.com/docs/api.md
- [The Fieldstub MCP server](https://fieldstub.com/docs/mcp/): Connect an AI assistant to Fieldstub over MCP. Ten tools for capturing extra work and filing it into Procore, with approval deliberately fenced off. Markdown: https://fieldstub.com/docs/mcp.md

### Pricing

- [Per project. Everyone in the field is free.](https://fieldstub.com/pricing/): Fieldstub prices per active project, not per user. Free tier with one project, Team at $299 a month for five active projects, extra projects $25 each. No demo call, no card. Markdown: https://fieldstub.com/pricing.md

### Legal and security

- [Trust and security](https://fieldstub.com/security/): What Fieldstub stores, who processes it, how access works, and what we do not have. Field data goes to Fieldstub and then, on your approval, into your own Procore. Markdown: https://fieldstub.com/security.md
- [Privacy Policy](https://fieldstub.com/privacy/): How Fieldstub collects, uses, shares and protects personal data, including data about field workers who have no account, which we hold on behalf of the contractor. Markdown: https://fieldstub.com/privacy.md
- [Terms of Service](https://fieldstub.com/terms/): The terms governing use of Fieldstub, operated by PurelySearch LLC. Covers accounts, billing, approvals that write to your Procore, and liability. Markdown: https://fieldstub.com/terms.md
- [Data Processing Agreement](https://fieldstub.com/dpa/): Fieldstub's DPA for customers who need one for GDPR, UK GDPR or CCPA. Covers roles, scope, sub-processors, transfers and breach notification. Markdown: https://fieldstub.com/dpa.md
<!-- pages:end -->

## Links

- Home: https://fieldstub.com/
- How it works: https://fieldstub.com/#how
- What lands in Procore: https://fieldstub.com/#procore
- Pricing: https://fieldstub.com/#pricing
- App (sign-in required): https://app.fieldstub.com/
- Agentic resource catalog: https://fieldstub.com/.well-known/ai-catalog.json

## Contact

hello@fieldstub.com