Grounded in your live Procore project

The field asks.
FieldPE drafts.

An AI project engineer for your Procore job. It drafts. You issue.

Sign in to your workspace See how it works
<2 minfrom email to a drafted record in Procore
4workflows, one inbox
0issued without your approval
Four jobs, one assistant

The paperwork a PE does all day

They run off the same inbox, and every one of them waits for you.

01A sub's field question arriving by email

RFIs

Matches the sender in the Procore directory, finds the drawing and spec section that answer the question, and writes the RFI with the real sheet attached.

02Checking a submittal package against the spec

Submittal review

Compares the package against every schedule tag in the section and lists the tags it cannot find. Clears, and it closes itself in Procore.

03Marked-up drawings and cost for a change

Change orders

Drafts the change from an answered cost-impact RFI or a standalone event, runs the event → PCO → CO lifecycle, and collects sub pricing over email.

04Drawings and the specification book

Scope of work

Writes a per-trade scope from your drawings and specs, worded to hold the sub to the contract documents. Their proposal merges into it.

The workflows

Field questions become RFIs in Procore

A sub emails a question — FieldPE finds the drawing and spec that answer it, writes the RFI, and creates it in Procore as a draft.

Every schedule tag checked, not skimmed

It compares a submittal against every tag in the spec, flags what is missing, and closes it in Procore when it clears.

From a cost impact to a priced change order

It drafts the change, collects sub pricing by email, and runs event → PCO → CO with the money on both sides.

Per-trade scopes that hold the sub

It writes a grounded, per-trade scope, merges the sub’s proposal, flags gaps, and exports to Procore.

app.fieldpe.com
How it works

From your inbox to Procore, in three steps

Subs keep emailing you. You keep issuing out of Procore.

STEP 01

Connect your project

Sign in with Google or Microsoft and pick a Procore project. FieldPE pulls your live drawings, specs and directory in minutes. It runs in a browser tab next to Procore.

Aerial view of a construction project
STEP 02

The field emails in

Subs and the field send questions, submittals, priced changes, and proposals to the inbox FieldPE watches. It reads each one, grounds it in your drawings, and drafts the record.

Steel roof trusses against the sky
STEP 03

You review and issue

The draft is already in Procore, with the real sheet and spec attached. Edit it there or here, then issue it — the field question is closed without you retyping a thing. Until you do, it has gone to nobody.

Bright interior atrium of a finished building
The math

Give the PE their week back

9.7days to answer the median RFI
$1,080what answering one costs
1 in 8never needed asking at all
<2 minfrom the email to a drafted RFI in Procore

The first three come from the Navigant Construction Forum study of 1,000,000 RFIs across 1,300 projects. The last is our own timing on the projects FieldPE runs on, measured from the email arriving to the draft existing in Procore.

Grounded in

It reads the job,
not the internet.

Every draft is grounded in the drawings, specs and correspondence for that project — pulled live from Procore, and cited under the answer.

The question goes out to everything it needs, at once.
What it read comes back, cited under the draft.
Nothing is issued until you approve it.
FieldPE
reads them at once
DrawingsSheets, revisions, the current set
SpecificationsEvery section, by division
RFIsQuestions in, answers out
SubmittalsEvery schedule tag checked
Change ordersEvents, PCOs, COs
CorrespondenceThe email the job runs on

While nobody is signed in

Five jobs run while
nobody is signed in.

Five jobs run on their own — one when mail arrives, four on a timer. Every one of them stops at a draft.

They run as whoever your company designates, so Procore records a real person as the author. Nothing is issued until somebody approves it.

autopilot

Drafts from your inbox

A sub emails a question. FieldPE reads it, finds the drawing and spec that answer it, and creates the RFI in Procore as a draft — numbered by nobody, sent to nobody.

Akash · Mounting heights, toilet accessoriesread
A811 · 10 28 00 · cited in the draftgrounded
RFI-118 created in Procoredraft
auto-close

Closes approved submittals

When every schedule tag on a submittal clears, it closes the record in Procore and tells the people who were waiting on it.

Steel_doors_submittal.pdf14 / 14 tags
Closed in Procoredone
Doors & Frames notifiedsent
the RFI-to-change watcher

Turns answered RFIs into change orders

An answer that changes the work is a change order waiting to be written. It drafts the event, collects sub pricing in the same thread, and leaves the money on both sides.

RFI-104 answered · relocate roof drainsread
Change event draftedCO-005
Pricing requested from the subsent
the month-end PCO package

Packages the month-end PCO

Every change event that landed this month, gathered into one owner PCO with the backup attached, on the day you close the month.

7 change events this periodgathered
Owner PCO assembled$28,400
Backup attached11 files
the scope refresh

Keeps scopes current

When the architect reissues a sheet or a spec section changes, the per-trade scopes are rebuilt against the new set rather than quietly going stale.

A-201 reissued · rev 4detected
29 trade scopes rebuiltcurrent
Nothing thinner than beforeguarded

Every trade on the job

A scope per trade,
in the trade’s own language.

One project on FieldPE today carries 29 of these. Each is written against the contract documents for that job, not a template — with no CSI codes left in the final document.

Div 0301

Concrete

Forming, placing, finishing — and who patches the slab after somebody else cores it.

Div 0402

Masonry

Units, mortar, reinforcing, and the flashing that is always somebody else’s line.

Div 0503

Structural steel

Framing, connections and deck. Penetrations need the engineer of record, and the scope says so.

Div 0704

Thermal & moisture

Roofing, waterproofing, sealants. The trade whose exclusions cost the most when nobody reads them.

Div 0905

Finishes

Drywall, flooring, paint, ceilings — the division with the most overlapping claims on one wall.

Div 2106

Fire suppression

Heads, mains, and the ceiling coordination nobody owns until it is written down.

Div 2207

Plumbing

Domestic water, waste, vent. Where it crosses the sprinkler main is a scope line, not a surprise.

Div 2308

HVAC / Mechanical

Equipment, duct, controls. VAV terminal units are the classic thing one bidder quietly excludes.

Div 2609

Electrical

Service, distribution, devices. Floor boxes and feeders are the usual change-order origin.

Div 3110

Earthwork

Excavation, backfill, compaction — and rock, which is a differing site condition, not an inclusion.

Divisions follow MasterFormat. A scope names what the trade includes, what it excludes, and the gaps no trade has priced — which is where change orders come from.

The guardrails

Reads your project

Pulls the live drawing set and spec sections straight from Procore. If the architect reissues A-201, the next draft cites the reissue.

Attaches the real sheet

The cited drawing is downloaded from Procore and attached — the actual sheet, not a summary.

Refuses to guess

No matching spec? It says so rather than inventing a clause. Can’t route it? It asks you.

Knows what isn’t work

Lunch invites, delivery notices and alerts are ignored. Only real field conditions get drafted.

Files natively

Drawing number, specification, cost code, assignee and distribution — filled in Procore’s own fields.

Human gate

Drafts land in Procore; nothing leaves it for an architect, owner or sub until a person clicks approve.

The difference

The old way vs FieldPE

One RFI, by hand and with FieldPE.

The old way

  • ✕Retype every field question into an RFI by hand
  • ✕Dig through the set for the right sheet and spec section
  • ✕Remember to fill each Procore field, every time
  • ✕Chase the sub over email while the clock runs
  • ✕Find out at closeout that a submittal was never logged

With FieldPE

  • ✓Drafted straight from the email that came in
  • ✓Grounded in your live drawings, the real sheet attached
  • ✓Filed into Procore's own fields, natively
  • ✓Routed to the right person from your directory
  • ✓Human-approved before anything is issued
Security & trust

What it will and will not do with your job

Things it will not do, whatever you ask it.

Human gate

FieldPE drafts it in Procore for you, but nothing is issued to the architect or emailed to a sub until a person does it. Every send is yours.

Enterprise single sign-on

Your team signs in with the Google or Microsoft accounts they already use. Access is limited to an approved list you control. Take someone off the list and their session stops working.

Grounded, never invented

It cites the sheet and spec section, or it says it could not find one. It will not write you a clause that is not in the book.

Your data stays in Procore

It reads your live drawings and specs and files into your project's own fields. Everything files into your Procore project. FieldPE keeps no second copy of the log.

Before you sign in

Questions PEs ask first

The trust and setup answers — separate from how each workflow runs.

Does it change my Procore data without approval?+
It creates drafts in your Procore project so they're ready when you are — but a draft goes to nobody. Nothing is issued to an architect, owner or sub until you do it.
How do I get started?+
Sign in with Google or Microsoft, connect your Procore account, pick your project, and you're drafting in minutes — no data migration, no setup project.
Is my project data secure?+
Your project data is never used to train AI models and is never sold. Each company's data is isolated in the database, credentials are encrypted, and nothing files without your approval. See our privacy policy for details.
Which Procore tools does it work with?+
RFIs, Submittals, Change Orders (PCO/CCO), and Documents for scopes of work.
What if it can't find an answer?+
It won't guess. If no drawing or spec matches, it says so and routes the item back to you to decide — nothing gets invented.
Do I have to change how my team works?+
No. Subs email you like they already do; FieldPE drafts from those emails and files into the same Procore your team uses.

Stop retyping the field's questions.

Sign in and work your queue.

Sign in to your workspace