Short answer: Procore has no dictation button, so you dictate at the operating system level instead. On a Mac, click into any Procore text field and hold your hotkey while you speak. On iPhone, switch to a keyboard with a mic and tap it. Nothing is installed in your company's Procore account.
Everyone on a jobsite knows what a good daily log looks like. Weather, manpower by trade, what got installed, what got delayed and why, deliveries received, visitors on site, safety observations. Everyone also knows what most daily logs actually look like: "Framing continued. No issues." That gap is not laziness. It is the cost of typing a paragraph on a phone with dust on the screen at 4:45pm, standing next to a running compressor, holding a hard hat under one arm.
The thinking is fast. You could narrate the whole day in ninety seconds without stopping. It is the transcription of that thinking that is slow, and when transcription is expensive, people write the shortest thing that technically satisfies the field. Six months later a delay claim lands and the record says "no issues."
This guide covers how to speak into Procore instead of typing into it: which fields it works in, which ones you should still type, how it behaves on a jobsite versus at a desk, and where it does not help at all.
Procore does not have a dictation feature, and that turns out not to matter
If you go looking for a microphone icon in a Procore daily log, you will not find one. Procore is construction project management software, not a text editor, and text entry is something it inherits from the browser on your laptop and from the keyboard on your phone.
That inheritance is the whole trick. Dictation on Apple platforms does not belong to the app you are typing into. It belongs to the layer underneath. If a field accepts characters from a keyboard, it accepts characters from your voice, because as far as the field is concerned the characters arrived the same way either way.
For a construction company this has one very practical consequence: nothing gets installed in your Procore account. There is no integration to evaluate, no app-marketplace connector, no permission for a Procore administrator to grant, no ticket in the queue behind the four other tools that are also waiting. Whoever manages your company's Procore instance does not need to be involved, because you are not touching Procore. You are changing how text reaches your cursor.
Setting it up on a Mac
Procore in a desktop browser is where the heavy writing happens: RFI questions that need to be unambiguous, meeting minutes, correspondence, change order narratives, closeout documentation. Two habits make dictation reliable there.
Click into the field first. Text goes wherever the cursor is. If the cursor is not blinking inside the daily log note box, the words have nowhere to land. Click, confirm the cursor, then speak. This sounds obvious and it is the single most common reason a first attempt appears to do nothing.
Check your hotkey against the shortcuts you already use. Procore and your browser both claim keyboard combinations. If your dictation hotkey collides with something Procore or Chrome has already reserved, you get an unexpected action instead of a recording. Pick a combination nothing else wants and it stays out of the way for good.
With Voice Keyboard Pro on Mac the interaction is push to talk: hold the hotkey, speak a full thought, release, and the text appears at the cursor in whatever field you clicked into. Because it works system wide, the same hotkey works in Procore, in the email you write afterwards, and in the spreadsheet where you track the same information a second time.
Setting it up on iPhone, which is where the field actually lives
Most Procore usage in the field happens on a phone or a tablet, standing up, often with one hand. That is exactly the situation where typing collapses and voice wins by the largest margin.
On iPhone you have two routes. Apple's built-in dictation gives you the mic key on the standard keyboard. Or you use a keyboard that has its own mic button, which is how the Voice Keyboard Pro iPhone keyboard works: install it, enable it in Settings, hold the globe key to switch to it inside the Procore app, and tap the mic. Because it is a keyboard, it works in Procore the same way it works in Mail or Messages, with no cooperation required from the app.
One field-specific note that matters more here than in an office: get the phone closer to your mouth rather than speaking louder. Proximity beats volume every time, and it is free. We wrote about that trade in detail in our guide to choosing a microphone for dictation, and about jobsite acoustics in fixing dictation in background noise. The short version for construction: steady broadband noise like a generator or HVAC is the easy case. Other people talking nearby is the hard case, because speech is what the system is looking for.
The five surfaces in Procore worth speaking into
1. Daily logs, the field that pays for everything else
The daily log is the highest-value target because it is written every single day, it is written at the worst possible moment, and it is the record most likely to be read years later by someone looking for a reason.
Speak it in a fixed order so you stop deciding what to include. A structure that holds up:
- Conditions. Weather and what it did to work. Not just "rain" but "rain from about 10 until 1, wet slab, no concrete pour."
- Manpower. Which trades were on site and roughly how many. The counts themselves go in the structured fields.
- Work completed. Actual locations. "Drywall hung on levels 3 and 4 east" beats "drywall continued."
- Delays and interference. What stopped, who was waiting on whom, from what time to what time. This is the paragraph that matters in a dispute and the one that gets skipped.
- Deliveries and visitors. What arrived, who came, what was inspected.
Spoken, that is under two minutes. Typed on a phone it is the reason daily logs say "no issues."
2. RFIs, where the question is the deliverable
A weak RFI question costs you a week. "Please clarify detail 5" produces a response that clarifies nothing, and then another round trip. A strong RFI states what the documents show, what the field condition is, why they conflict, what you propose, and what the schedule impact of waiting is.
Nobody types that at 6pm. Spoken, it takes a minute. Say the whole thing out loud the way you would explain it to the architect on the phone, then read it back and cut anything that is narration rather than information. The habit is to overshoot and then trim, because trimming is fast and generating from a blank field is slow.
Drawing numbers, spec sections, detail callouts and dates go in by keyboard. More on that in a moment.
3. Observations and punch items
Punch walks are the purest case for voice. Your hands are holding a phone and a flashlight, you are moving, and every item needs a location, a description of the deficiency, and an assignee. Typing that means stopping at every item. Speaking it means you keep walking.
The discipline that makes dictated punch items useful: one item, one location, one deficiency. "Unit 412 bathroom, grout missing along the tub surround on the north wall" is actionable. "Grout issues" generates a callback and a second trip.
4. Meeting minutes and correspondence
OAC meetings, subcontractor coordination, preconstruction. The meeting itself is fast, and the write-up afterwards is what slips. The reliable pattern is to type the skeleton before the meeting (attendees, agenda items, item numbers), capture decisions during it, then dictate the narrative in the ten minutes right after while it is still in your head. We go deeper on the formal version of this in dictating meeting minutes, which covers how to speak a motion and why vote counts should always be typed.
On the Mac, Meeting Mode in Voice Keyboard Pro can capture a meeting with speaker detection and produce AI notes, which is useful when you are running the meeting and cannot also be the scribe. Treat what it produces as raw material, not as a distributed record. Someone still has to decide what belongs in the official minutes, and that someone is you. Tell people in the room that you are capturing notes, and follow whatever your company's policy says about recording meetings with owners and subs.
5. Emails and the writing that happens around Procore
A large share of construction writing never lives in Procore at all. It is the email to the owner explaining why the pour slipped, the text to the superintendent, the note to accounting about the delivery ticket. Because system-wide dictation is not tied to any one app, the same hotkey covers all of it. That is the difference between a tool that helps in one window and a tool that changes how the whole day feels.
Speak the sentences, type the values
This is the rule that keeps dictated documentation trustworthy, and it applies everywhere in Procore.
Dictate anything that is a sentence. Type anything that is an identifier or a quantity:
- RFI, submittal and change order numbers
- Drawing references and spec section numbers
- Dollar amounts, quantities, dimensions
- Dates in structured date fields
- Cost codes and WBS values
- Dropdowns, statuses, assignees and distribution lists
The reason is not that voice cannot produce digits. It is that number errors are silent. A misrecognized word looks wrong and you fix it. A drawing reference that came out as A-2.1 instead of A-2.11 looks completely normal and gets read as fact by everyone downstream. Nothing in the interface flags it. If you do want to speak numeric content in narrative text, our guide to dictating numbers and dates covers the phrasing that survives transcription and the two-pass proofread that catches what slips through.
One more boundary specific to jobsites: do not speak gate codes, lockbox combinations, alarm codes or anything else that gets you into a building. Type those, or better, do not put them in a note field at all.
The proper-noun problem, and the fix
Every project has a vocabulary that no general transcription system has ever seen. Subcontractor company names. The owner's rep. Street and building names. Trade jargon that is spelled nothing like it sounds. Product and assembly names from the submittal log. Internal shorthand for areas and phases.
These words are maybe five percent of what you say and they show up in a hundred percent of your logs, which is why the same three or four names being wrong every single day feels so much worse than the raw error rate suggests.
Smart Vocabulary in Voice Keyboard Pro on Mac is a personal dictionary with replacement rules for exactly this. You load the sub names, the area labels, the recurring product names once at the start of a project and they stop being wrong. It is the difference between a tool that is annoying on day three and one you keep using in month nine. This is also the honest limit of hardware: a better microphone fixes clarity, it does not teach anything the names of your subcontractors.
Documentation that has to hold up
Construction records are read adversarially. Not usually, but the ones that matter are read by someone building or defending a claim, sometimes years after the person who wrote them left the company. Dictation makes it cheap to write more, and writing more is only an improvement if the extra words are the right kind.
Some discipline that costs nothing:
- Record what you observed, not what you concluded. "The framing crew left the site at 11:15 and did not return" is an observation. "The framer abandoned the job" is a characterization, and a characterization is what gets quoted back at you.
- Attribute delays factually. Times, sequences, who was waiting on what. Skip the editorial.
- Never submit a hot entry in the same sitting. Typing used to add friction that let you cool off. Speaking removes it. If you dictated something after a bad conversation with a sub, save it and read it again before it goes anywhere.
- Read it back before you submit. Thirty seconds. This also catches the silent number errors.
What belongs in the official record and how long it is retained is your company's risk and legal team's call, not ours. Ask them before you change how project documentation is produced, particularly on public work or anything with contractual notice requirements.
Multilingual crews
Construction is one of the most linguistically mixed work environments there is, and a lot of safety and coordination information dies at the language boundary. The Voice Keyboard Pro iPhone keyboard can translate two ways while you dictate across 24 languages, so you can speak a toolbox talk summary or a coordination note in English and send it in the language the crew reads.
The caveat is the same one we give everywhere: machine translation is a first draft. It is good enough for "the east stair is closed tomorrow, use the west stair." It is not good enough for anything contractual, anything disciplinary, or a safety procedure that someone's life depends on getting right. Get a person to check those.
A workflow that survives a real week
- Do the log in the truck, not at the office. Before you start the engine, open the daily log and speak the five sections. Ten minutes later you will have lost the detail that makes it worth writing.
- Punch walks are dictate-as-you-go. One item per stop, keep moving. Do not batch punch items for later; the location detail is exactly what evaporates.
- RFIs get spoken then trimmed. Say the whole explanation, then cut it down and type in the references.
- Batch the typed fields. Do all the numbers, codes and dropdowns in one pass at the end rather than switching between voice and keyboard on every field. Switching input modes constantly is what makes people give up.
- Read before submit. Always, on anything that becomes a record.
Honest limits
Voice does not fix a project where nobody knows what happened today. It makes it cheap to write down what you know; it does not supply knowledge.
It also does not help with the structured half of Procore. Schedules, budgets, cost codes, drawing markup, photo tagging and dropdown selections are keyboard and touch work, and they always will be. If your Procore time is mostly spent in those, dictation changes less for you than it does for a superintendent writing logs.
Some environments are genuinely unworkable. Inside an active demo area, next to a running saw, in high wind with the phone at arm's length, no amount of technique saves the audio. Step twenty feet away or wait for the pour to finish. And a session that keeps producing garbage in a specific spot is telling you something about the acoustics, not about your speech.
Finally, everything here is about getting text into fields. If your actual problem is that nobody fills out logs at all, a faster keyboard is not the fix. Though it is worth noticing how often "nobody fills these out" turns out to be an input problem wearing a discipline costume, which is the same pattern we found writing about voice typing for construction managers and field service technicians.
Frequently asked questions
Does this work in the Procore mobile app or only in a browser?
Both. On iPhone and iPad, dictation belongs to the keyboard, so any text field in the Procore app accepts it. On a Mac, it works in whatever browser you use Procore in. There is no browser extension and no app plugin involved either way.
Do I need our Procore administrator to approve anything?
No. Nothing connects to Procore, no data flows through Procore's API, and no permission changes. Your IT team may have its own policy about what software goes on a company laptop or phone, which is a separate and reasonable conversation to have with them.
Will it work offline in a basement with no signal?
Voice Keyboard Pro's transcription engine needs a connection. Apple's on-device dictation does not, for supported languages. On a site with dead zones, the practical answer is to use both: the built-in mic key when you have no bars, the keyboard with its own mic when you do. Procore itself has offline behavior of its own for field data, which is worth knowing separately.
What about the noise? Does a hard hat or mask make it worse?
Anything covering your mouth muffles consonants, which is where most of the distinguishing information lives. It is workable but it costs accuracy. The bigger factor is usually distance to the microphone and whether other people are talking nearby.
Is any of this stored anywhere?
Our server stores only operational pings. No audio and no transcript content. What you dictate into a daily log goes into Procore and nowhere else on our side. What Procore does with project data is governed by your company's agreement with them, which is worth reading if you have not.
Can I dictate into drawing markups?
Into text annotations, yes, where they are text fields. Into the markup geometry itself, no. Drawing work is hands work. The rule that holds everywhere is words for language, hands for geometry.
The point
The daily log that says "framing continued, no issues" was never a reflection of what the superintendent knew. It was a reflection of what a phone keyboard costs at the end of a twelve-hour day. Change the cost of writing and the record changes with it, which is worth more on the day someone finally goes looking for it.
Voice Keyboard Pro has a free tier on both Mac and iPhone. Try it on one daily log this week and compare it to the one you wrote yesterday.