# Fieldstub — you did the work, you just never billed it

> Anyone on the job scans a code and submits extra work from a phone browser. It lands in Procore the same day as a Change Event with real budget codes. No app, no login, no Procore seat.

Source: https://fieldstub.com/ · Docs: https://fieldstub.com/docs/

## The problem

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. At closeout the general contractor cannot substantiate the cost to the owner, so the GC eats 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, no Procore seat. 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 this one

**The people doing the extra work don't have Procore.** Every other tool in this category assumes the person holding the information has a seat, a login and twenty minutes. Subs and crews have none of those and never will.

- **The field needs no Procore seat.** Procore's own T&M Tickets tool requires an account and the mobile app.
- **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.

Start: https://app.fieldstub.com/start

## Requirements

- Procore with Project Financials, for Change Events. Without it, tickets are still captured and filed with the signed record.
- Nothing on the field side. A browser is enough.
- A Procore admin installs the app once. After that anyone in the Procore company directory can sign in, and nobody else can.

## For developers and agents

- REST API: `https://app.fieldstub.com/v1` — spec at https://app.fieldstub.com/v1/openapi.json (no key needed to read)
- MCP server: `https://app.fieldstub.com/mcp` — streamable HTTP, bearer API key
- Guides: https://fieldstub.com/docs/api/ and https://fieldstub.com/docs/mcp/

Creating a ticket is safe to automate. **Approving one writes a Change Event into a customer's Procore financials and is not reversible.** Read the `routing` array on a ticket first — it shows which budget code each line will hit — and leave approval to a person.

## Docs

How Procore actually behaves, verified by probing a live sandbox. Several findings are not published anywhere else.

- [Procore budget codes, and why your change event line item lands blank](https://fieldstub.com/docs/procore-budget-codes.md)
- [Creating a Procore change event over the API](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.md)
- [How to get T&M tickets into Procore](https://fieldstub.com/tm-tickets-in-procore.md)
- [How subcontractors submit extra work without a Procore license](https://fieldstub.com/subcontractor-extra-work-without-procore.md)
- [The Fieldstub API](https://fieldstub.com/docs/api.md)
- [The Fieldstub MCP server](https://fieldstub.com/docs/mcp.md)

Everything in one file: https://fieldstub.com/llms-full.txt

## Contact

hello@fieldstub.com