# Procore's T&M Tickets tool: what it does, and what it needs

> 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.

Source: https://fieldstub.com/docs/procore-tm-tickets/  ·  Updated 2026-08-09
API findings verified against a Procore sandbox, August 2026

Procore has its own tool for this, and a surprising number of people evaluating third party options do not know it exists. It is worth understanding properly before you buy anything, including ours.

The short answer: it is a good tool, and whether it solves your problem comes down to one question. Do the people doing your extra work have Procore?

## What it is

[T&M Tickets](https://support.procore.com/products/online/user-guide/project-level/tm-tickets) is a project tool inside Procore for documenting out-of-scope work. In Procore's own words it modernizes the traditional carbon copy forms used on job sites.

It captures the things a T&M ticket has always captured:

- Labor, with trades and hours
- Equipment
- Materials
- A digital signature, collected on a mobile device

That object model is correct, and it is the same shape any serious tool in this category lands on. It also lines up with Procore's own cost structure, where the WBS cost type segment is natively Equipment, Labor and Materials: the three components of a T&M ticket, with no translation needed.

## What it requires

Two requirements decide most evaluations.

**A Procore seat and the mobile app.** The capture path is Procore itself, so the person filling in the ticket has to be a licensed user, signed in, with the app installed and current.

**No public REST API.** We went looking, because Fieldstub would have written to T&M Tickets if it could. Twelve resource name variants all return 404, including `time_and_materials` taken directly from the tool's own URL in the web app, tried against both the `?project_id=` and nested path conventions across API versions v1.0, v1.1 and v2.0. The tool was enabled and set to Admin on the test project and appears in its tool list, so this is not a permissions gap. Procore also publishes extensive end-user documentation for the tool and no developer documentation at all.

> Verified August 2026 against a Procore developer sandbox. An undocumented internal endpoint could exist, and an API for this tool is an obvious future release. If it ships, the calculus here changes.

## When it is the right answer

Use Procore's tool, without hesitation, when:

- The extra work is done by your own people, and they already carry Procore.
- Your crews are already trained on the mobile app and use it daily.
- You do not need to read those tickets from any other system.

In that situation a third party tool is a second thing to buy and administer for a job Procore already does inside the platform you own.

## When it is not

The gap is not a feature. It is a population.

On most jobs the people who know what actually happened are subcontractors and crew members who do not have Procore, will not be given a seat, and would not be trained on the app if they were. A tool that captures the work of people who already have Procore captures the wrong half of the problem, because that half was mostly getting recorded anyway.

The other half is a foreman in a truck with a carbon copy pad, and that pad is what never makes it back to the office.

|  | Procore T&M Tickets | Fieldstub |
|---|---|---|
| Field needs a Procore seat | Yes | No |
| Field needs an app installed | Yes | No, a phone browser |
| Captures labor, equipment, materials, signature | Yes | Yes |
| Readable by other systems | No public API | Writes a change event, which has one |
| Where the record lands | A T&M ticket | A change event with typed line items on budget codes |
| Office review before anything is filed | Inside Procore | A review queue, and nothing writes unreviewed |

We are not neutral here, so treat the right column accordingly. The left column is checkable against Procore's own documentation, and the API row is reproducible by anyone with a sandbox.

## Questions

### Does Procore have a T&M Tickets API?

Not a public one. Twelve resource name variants return 404 across API versions, on both path conventions, with the tool enabled and set to Admin. Procore publishes no developer documentation for it.

### Can a subcontractor fill in a Procore T&M ticket?

Only if they have a Procore seat and the mobile app. Most subs on most jobs have neither.

### Is Fieldstub a replacement for Procore T&M Tickets?

Only for the work done by people without Procore, which in practice is most extra work. If your own crews already use the Procore app, their tool is the simpler answer.

### Why does Fieldstub write change events instead of T&M tickets?

Two reasons. T&M Tickets is not addressable through any public API, and a change event carries the cost into the budget and on toward a change order and Procore Pay. Change events also stay editable after an integration creates them, which is what makes an office review loop possible.

## Related

- https://fieldstub.com/tm-tickets-in-procore.md
- https://fieldstub.com/docs/procore-change-events-api.md
- https://fieldstub.com/subcontractor-extra-work-without-procore.md

---

Fieldstub captures extra construction work from people with no Procore seat and files it into Procore as a Change Event. https://fieldstub.com/