AI Tools for Construction Project Management: RFIs, Logs, Reports

For a small contractor, a general assistant (ChatGPT, Claude or Gemini) drafts RFIs and weekly reports, while a field app holds the daily log: CompanyCam turns voice notes and photos into one, and JobTread summarises a week of them. Nothing should go out unread: a named person checks each draft, and every figure comes from your own records.

Small firms often buy a tool for each document separately and then retype the same facts three times. The three belong to one chain. A line in Thursday's log spots a clash, the clash becomes an RFI, and the wait for the answer shows up in the weekly report. Capture each fact once, where it happens, and let the tools reshape it for each reader.

Follow me on Instagram@sagnikteaches

One fact, three documents: how the paperwork chain works

Take one sentence from a supervisor's voice note: the beam over the Room 3 doorway is lower than the drawing shows. On Thursday it belongs in the daily log. On Friday it has to become an RFI (a request for information, the formal question that goes to the design team), because someone must answer it before the doors can be ordered. A week later it needs one line in the client's weekly report, because the client will wonder why one door is shorter than the rest. Same fact, three documents, three readers. Every time someone retypes it, a number can change.

Connect on LinkedInSagnik Bhattacharya

The running example is an illustration, not a real project: an eight-week fit-out of a 140-square-metre physiotherapy clinic. The contractor is a small firm with a site supervisor, a part-time office manager and six to eight trades on site most days. Over eight weeks that produces about 40 daily logs, roughly a dozen RFIs and eight weekly reports. The drawing numbers, prices and people are invented.

Subscribe on YouTube@sagnikteaches

Split the work so each person does what a machine cannot:

• Site supervisor: speaks the daily note into a phone (two minutes), then reads the draft against the day's photos (five minutes).
• Office manager: runs the drafting prompts for RFIs and the weekly report, keeps the RFI log and chases answers.
• Owner or project manager: signs each RFI before it leaves and each weekly report before the client sees it, and types the four numbers the assistant must never estimate.

Set the assistant up once per job. In ChatGPT or Claude, create a Project (a saved workspace with its own files and standing instructions) and put in the drawing register, the specification index, your RFI template and the contract's response period. Claude's Free plan allows up to five Projects; in ChatGPT, Projects hold 5 files on Free, 25 on Go and Plus, and 40 on Pro and Business. Check your client's confidentiality terms before uploading their drawings. Business plans such as ChatGPT Business and Claude Team do not train on your content by default, and the consumer plans have a model-training switch in their privacy settings that is worth finding on day one.

Daily log: from a two-minute voice note to a checked entry

A daily log is the site's diary: who was there, what got done, what arrived, what went wrong. It earns its keep months later, when a client queries a delay or an inspector asks what happened on a particular Tuesday. That is why the facts in it must be yours. The assistant's job is formatting. Yours is confirming.

The routine has four steps.

1. Speak in the same order every day: date, weather, who was on site, work done room by room, deliveries, inspections, problems, safety, tomorrow. A fixed order is what keeps the drafts consistent from one day to the next.
2. Turn speech into text. The simplest route is the microphone button on your phone's keyboard. The other is a field app: CompanyCam's Walkthrough note lets you narrate while taking photos, for up to 15 minutes per walkthrough, in the mobile app only.
3. Paste the transcript into the assistant with a prompt that forbids guessing.
4. Read the draft against that day's photos, correct it, then save it. The saved entry is the record. The draft is not.

Here is the kind of transcript a supervisor might produce after a busy Thursday in week two:

Daily log, Thursday, week two, clinic job. Eight of us on site today: two carpenters, the electrician and his apprentice, two plasterers, the plumber for half a day, and me. We boarded rooms two and three and taped and jointed room one. The electrician pulled the cables for the treatment-room sockets and found the beam over the door to room three sits lower than the drawing shows, about two thousand and eighty-five clear. Vinyl delivery came but we're a roll short, two rolls not three. The building inspector didn't turn up for the framing check, rebooked for Monday. Rain for about an hour first thing, stopped the loading-dock work. Near miss: a stack of boards slid off the trolley, nobody hurt, I told the lads to strap them. Tomorrow: finish jointing, second-fix plumbing starts, I'll chase the vinyl.

And the prompt that keeps the assistant on a short lead:

You are drafting a construction daily log from my voice-note transcript.
Rules:
1. Use only what the transcript says. If a field is not mentioned, write "Not stated".
2. Never add weather, dates, quantities, names or formal records (toolbox talks, inspections passed) that I did not mention.
3. Fields, in this order: Date, Weather, On site (by trade, in person-days; a half day is 0.5), Work completed (by room), Deliveries (say if short), Inspections (attended or not, and the result), Issues and delays, Safety, Planned tomorrow.
4. Start any line that might need an answer from the design team with "POSSIBLE RFI:".
5. Write numbers as digits with units, exactly as spoken.
Transcript:
[paste transcript here]

A first draft often looks like this (sample output, before editing):

Four things need changing before this goes in the file:

• Weather. The note said rain for about an hour. "Through the morning" is a tidy-up that would support a weather-delay claim the supervisor never made.
• Headcount. The plumber was there for half a day, so the day was 7.5 person-days, not 8.
• Safety. The supervisor told the crew to strap their loads. The draft promoted that to a "toolbox talk held", which is a formal record. Unless a talk was given and signed for, change it back.
• The RFI tag. The beam line should start with "POSSIBLE RFI:" so the Friday filter catches it. Assistants drop an instruction like this now and then, so look for it every time.

Those fixes take about two minutes. The tag is the bridge to the next stage: each Friday the office manager filters the week's logs for it, and every hit is an RFI candidate. For a fuller treatment of voice-note logs on their own, see can AI write a construction daily report from voice notes, and for ready-made wording see the ChatGPT prompts for site diaries, RFIs and variations.

Where the log lives: four options and what they cost

You do not need a paid app for a two-week job. For an eight-week job with subcontractors and a client who wants photos, one is worth pricing. This is what the vendors' own pages showed on 29 October 2026, in USD.

Procore is the platform small contractors hear about most. Its pricing page describes an upfront annual fee by product, based on your annual construction volume, with unlimited users, and it asks you to request a custom estimate, so there is no small-job price to quote. Raken, another daily-report app firms ask about, showed no prices and no AI features on the page I could load, so I have left it out of the table. If either is on your shortlist, ask for a quote and a demo using one of your own daily logs.

Two sizing rules help. Under roughly a dozen RFIs a job, a numbered sheet and an assistant beat any paid RFI module. Past that, or once subcontractors and the client both need to see the log, a field app earns its monthly fee, because the thing you are buying is a shared record rather than a smarter draft.

RFIs: let the AI draft the question and leave the references alone

A good RFI asks one question, points at the exact drawing and specification references, shows what you found, proposes an answer and says by when you need one. The assistant is good at the wording, the neutral tone and the options. It cannot know the current revision of a sheet unless you tell it, and when it is not told, it may fill the gap with something that looks right.

So give it a closed list of references and let it use nothing else:

Draft an RFI to the architect from the notes below.
Use only these references: A-201 revision C (door schedule), S-104 revision B (structural openings). Do not cite any other drawing, revision or specification section.
Format: RFI number, subject line (location, element and the problem in under 90 characters), date issued, to, from, response needed by and why, references, observation, question, proposed solution, possible impact.
Tone: neutral and factual. Do not suggest the design is wrong.
Proposed solution to include: a 1,980 mm door leaf with matching frame head, three-week lead time.
Impact wording: say "possible" and "price to follow" where I have not given a figure.
Notes: [paste the log line, the measurement and the photo caption]

A typical result, before the office manager edits it:

RFI-007: Room 3, door D3: clear height under beam 2,085 mm, drawn as 2,200 mm
Date issued: Friday, week 2
To: Architect  From: [your name], site supervisor
Response needed by: Friday, week 3. The door set must be ordered that day to arrive before hanging in week 7.
References: A-201 revision C (door schedule); S-104 revision B (structural openings)
Observation: On Thursday we measured the clear height under the beam over the Room 3 doorway at 2,085 mm. A-201 shows 2,200 mm. Photo 14, with the tape in frame, is attached.
Question: Please confirm the door set to use at D3. A standard 2,040 mm leaf with its frame needs about 2,110 mm.
Proposed solution: a 1,980 mm leaf with matching frame head (about 2,050 mm overall), three-week lead time. Alternatives welcome if the structure allows.
Possible impact: cost and programme impact possible on the proposed door; price to follow. No programme impact if answered by the date above.

The sums behind "response needed by" are worth doing on paper, because they decide whether the RFI is urgent or merely polite. Count in working days from the start of the job.

The answer is due on the very day the order has to go in, so there is no spare day. That is why the RFI states the date and the reason, and why the log should say "order at risk on day 15 if no reply" as a decision for the owner. If the answer arrives on day 14, as it does in this example, nothing slips. If it arrives on day 19, the doors reach site four working days later than needed, and that is a delay you can evidence from the RFI log rather than argue about.

A before and after for the subject line

Most RFI logs become unreadable because of the subject lines. "Door query" tells nobody anything in week six. "RFI-007 Room 3, door D3: clear height under beam 2,085 mm, drawn as 2,200 mm" tells the architect what to look at and tells you what you asked. Ask the assistant for a subject line under 90 characters that names the location, the element and the problem, and the log sorts itself.

When it is not an RFI

Assistants will happily turn any question into an RFI, so decide the document before you draft. A question about something the drawings or specification leave unclear, conflicting or missing is an RFI. A request to change scope or add cost is a change request, and turning site messages into change orders covers that route. Offering a different product is a substitution request. Reporting poor work is a snag or non-conformance item. Mixing them is how a simple question turns into a dispute about who agreed what.

The log itself needs only a few columns: number, date issued, subject, location, references, needed-by date and its reason, contract response date, date answered, who answered, status, cost impact (yes, no or to be confirmed), time impact and the linked change order. Keep it in one sheet, and paste the open lines into the weekly report prompt. If a drawing revision lands mid-job, check what changed before raising anything, which is where comparing drawing revisions with AI saves a wasted RFI. Submittals follow the same logic, and submittals and sub chasing is the place to read next.

Weekly report: five paragraphs and four numbers you type yourself

A client does not want the logs. They want to know what happened, what is next, what you need from them and whether the money and the date are safe. Five short paragraphs answer that: progress this week, coming next week, decisions needed from the client, RFIs and changes, and the programme and cost position.

The fifth paragraph is where assistants do harm, because it is made of numbers and judgements. Take the figures from your own records and hand them over in a block:

Figures for this report (typed by me; use exactly as written, do not estimate or round):
Percent complete (from schedule of values): 34%
Variations approved to date: $2,150 (VO-001 and VO-002)
Variations pending client approval: $1,122 (VO-003, door sets)
Days lost this week: 0 (cumulative 1)
Forecast completion: Friday, week 8 (unchanged)

Then paste the week's five daily logs, the open RFI lines and the figures block, and ask for plain language, one paragraph per heading, no blame, and nothing that is not in the inputs. If your logs already live in JobTread, its AI daily log summary is a sensible starting point, because it combines several logs into one shareable summary. CompanyCam describes its Progress Recap as project details, an AI-written summary and photos combined into a report for customers or managers. Either way, the same four edits apply.

A short week-three draft might read as follows:

Progress: all treatment-room partitions are boarded, rooms 1 and 2 are taped and jointed, and first-fix electrical and plumbing are complete. Next week: jointing in rooms 3 and 4, second-fix plumbing starts, and the ceiling grid goes up in the waiting area. Decision needed from you: please confirm the reception floor vinyl colour by Wednesday so the order can go in. RFIs: RFI-007 on the Room 3 door height was answered on Thursday; we have ordered a shorter door leaf to suit the structure, and a change quotation for $1,122 is attached for your approval. Position: 34% complete; variations approved $2,150, pending $1,122; no days lost this week; forecast completion unchanged.

Before it goes out, the owner reads it for four things. First, any sentence that judges rather than reports, such as "we are comfortably on programme", comes out unless the figures say so. Second, nothing pending may read as approved. Assistants blur this when a quotation is "attached". Third, two RFIs must not be merged into one. Fourth, the tone must not blame anyone. Where the cost of a change is known, the $1,122 above was built from two made-to-order door sets at $410 each plus three hours of extra carpentry at $52 an hour, which is $976 before a 15% margin. The report states the result and the change quotation carries the working.

Where the numbers go wrong when figures are spoken

Voice transcription is good with words and unreliable with numbers, and the damage compounds because every later document copies the first one. In the sample log above the figure came through correctly. Suppose it had not, and the transcript had rendered "two thousand and eighty-five" as 2,058. The log would keep it. The RFI would repeat it. The weekly report would repeat it again. Nobody would notice, because three documents agreed with each other.

The error would matter. With 2,085 mm clear, the proposed 1,980 mm leaf and head (about 2,050 mm overall) leave 35 mm of tolerance. With 2,058 mm they leave 8 mm, which is tight once a door lining is packed out and the finished floor goes down. The architect would be answering a question about a different opening from the one on site.

Four habits stop this:

• Speak figures digit by digit when they matter: "two, zero, eight, five millimetres".
• Take a photo with the tape in frame for every measurement that drives an RFI, and name the photo in the RFI.
• Add a closing line to each log and RFI: "Figures checked against photo 14 by [initials]".
• Copy figures into the weekly report from the RFI log, not from memory or from the last report.

The hours and dollars across one eight-week job

Any time saved on a job this size is modest, so work it out honestly before buying anything. These minutes are assumptions for this illustration. Time one real week before you trust them for your own firm.

The assisted minutes include the checking, which is the part people skip when they quote savings. At an internal cost of $45 an hour, 22.3 hours is about $1,005. Against that, an assistant at $20 a month for the two months of the job costs $40. If you add CompanyCam Core at $63 a month billed annually, that is $756 a year; spread across six jobs it is $126 a job. Net of both, the job comes out about $839 ahead. A bigger prize hides behind that sum: logs saved the same day, RFIs sent while the beam is still exposed, and a client who is told on Friday rather than discovering on Monday.

Checking after the first job that the chain held

After job one, count rather than feel. Four measures cover the chain, and the pass marks here are illustrative targets to adjust.

If the third measure is not zero, stop adding tools and fix the figures routine first. A faster way to produce a wrong number helps nobody. If all four pass, the next step is usually the one nearest the money, which for most small contractors is the change-order chain rather than another report.

Questions small contractors ask before buying

Can ChatGPT or Claude write an RFI without my help?

It can draft one, but only from facts you give it. Paste in the drawing and specification references, a photo caption and your proposed fix. If you leave the references out, assistants tend to invent plausible ones, including revision letters they cannot know. Check every reference against the issued set before the RFI leaves the office.

Do I need Procore to run RFIs on small jobs?

Usually not. Procore charges an upfront annual fee by product, based on your annual construction volume, with unlimited users and a custom estimate, so there is no published small-job price. A numbered RFI log kept in a shared sheet works for a handful of RFIs. Fieldwire lists RFIs only on Business Plus, at $89 per user a month billed annually. Decide by how many RFIs you raise and who needs to see them.

Can a voice note replace the daily log form?

A voice note can feed the form, not replace it. The saved log is a record you may rely on in a dispute months later, so the facts in it must be yours. Let the assistant structure the note, then read the draft against the day's photos and correct anything it embellished, such as a formal inspection or toolbox talk you never held.

Which weekly report figures should never come from AI?

Percentage complete, approved and pending variation values, days lost and the forecast completion date. Take them from your schedule of values, cost report and delay log, then type them into the prompt as figures. The assistant can format and explain them. It should not estimate them, and a sentence such as 'on track' is a judgement you make.

Further reads

• Construction Photo Documentation App: What AI Adds, and Which Plan — Compare photo-app plans before deciding where logs live.
• AI in the Construction Field: Photos, Voice Notes and Punch Lists — Photos and voice notes turned into punch lists.
• AI Software for Construction Scheduling: Programme Updates After Delays — Update the programme after a delay without redrawing it.
• AI for Electrical Project Management: Diaries, RFIs, Snag Lists — The same chain from an electrical subcontractor's side.
• AI Tools for Shop Drawings: Checking Fabrication Drawings Against the Spec — How a steel or mechanical subcontractor can use ChatGPT, Claude and Bluebeam to compare drawings with the spec, and the checks that must stay human.
• AI Contract Management Software Demo: 10 Questions for Contractors — Ten demo questions for contractors, each with an example: data location, clause accuracy, retention dates, scans, export, price and cancellation.
• AI Software for Custom Home Builders: Selections, Budgets, Client Portal — What a custom builder should test in construction software: allowances and selections, budget truth, client portal and AI summaries, with JobTread's AI named.
• Best AI App for General Contractors: Site and Office Tools Compared — Site and office AI tools priced per month for a six-person firm, each with a worked example, plus four stacks from $189 a month.
• Five AI Apps for Construction Site Work: Photos, Logs, Checks — Five apps for photos, daily logs and site checks, with the AI features each one lists, which plan carries them, and what four users would pay.
• Which AI Tools Should a General Contractor Buy? What to Skip — A buy-first order, a skip list with triggers, and a hours-it-must-save test for a general contractor, priced for a six-person remodelling firm.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: JobTread pricing, features and AI pages; CompanyCam pricing page and help-centre article on AI features for documents; Fieldwire pricing page; Procore pricing page; Anthropic Claude pricing page; plan limits from OpenAI and Anthropic vendor pages (read 29 October 2026).