Procore AI Go and Meta Smart Glasses: What Contractors Get

Your superintendent already said it once.

To the supplier on the phone. To the sub on the walk. In the coordination meeting, the morning standup or the toolbox talk.

Asking that person to stop later and tell an app what happened is still asking them to do the work twice.

Procore AI Go and Meta smart glasses put construction voice technology in the spotlight at Groundbreak 2026, alongside Procore’s digital-twin work with NVIDIA and an asset-management collaboration with IBM. The question for a contractor is how the information gets into the record: through a new instruction to software, or from the conversation where the work was already discussed?

Hardline is the voice layer for construction. It captures calls, meetings and on-site conversations as they happen, structures the information around company standard operating procedures (SOPs), and turns it into draft project records. Those records can stay in Hardline or move into the systems the job uses through supported integrations and configured workflows.

What did Procore announce with Meta on October 21, 2026?

The October 21 announcement covers voice access to project information, a Meta glasses beta and plans to create construction records through AI Go. Those are different stages of availability.

Procore AI Go: spoken answers from project information

Procore AI Go is a voice-first app for querying project information in Procore. Announced October 21, it includes spoken answers, push-to-talk activation and local conversation history. Its open beta covers eligible North American customers in Procore’s Digital Coworker packages.

Meta AI glasses: a separate closed beta

The same announcement describes a Meta partnership for hands-free project access and first-person photos. The glasses integration is in closed beta. Procore also describes a field-productivity study with Moss Construction, independently designed by SBK Technologies.

Record creation and agents in AI Go: upcoming work

The release places creating daily logs and observations, drafting requests for information (RFIs), translation and additional agent access in its future plans. Those are distinct from the initial app’s availability.

Earlier news: a Daily Log Agent and company Skills

Some of this builds on Procore’s July news. That month it announced a Daily Log Agent and previewed Skills, a way to teach its AI agents a company’s own processes and standards.

Its AI overview also describes AI that works across third-party data and integrations, reasons over documents and takes actions inside Procore. Procore is doing far more than dictation.

The open question for a contractor is what feeds those agents: the calls, standups and site walks where decisions actually get made, or only what someone tells the app afterward.

Which Meta glasses work with Procore AI Go, and can you get them now?

The Meta glasses integration is a closed beta. Procore’s release refers to “Meta AI glasses” and does not name a specific model.

Procore AI Go itself is in open beta for eligible North American customers through the Procore Explore beta program. If you want access to either one, ask your Procore account team.

How much does Procore AI Go cost?

Procore hasn’t announced a separate price for AI Go. It’s included in Procore’s Digital Coworker Starter, Pro, and Enterprise packages, and Procore sells those packages through its sales team.

Hardline’s pricing is public and per person: see pricing.

Does Procore AI Go capture phone calls and meetings?

Not as announced. AI Go answers questions and takes photos; capturing phone calls and meetings isn’t part of the announcement.

Talk-to-text is entry-level at this point. Changing spoken words into written words is useful, but a superintendent still has to decide when to speak to the software and what to repeat.

Consider the supplier call where a delivery moves to tomorrow. The superintendent has already asked the questions, heard the answer and worked out what happens next. If the documentation process requires a second voice note, the information still depends on someone finding time to retell the call.

That is a different workflow from capturing the original conversation and preparing the daily-log entry and follow-up from it.

The same problem appears after meetings. A foreman gives an update during the standup, answers a question in the walk afterward and changes the plan on a call. A clean transcript of one dictated recap cannot recover the details that never made it into that recap.

The hard part is capturing information at the point where it gets communicated, preserving the context and turning it into something the next person can use. A record needs the right project, location, commitment and status. A task needs an owner. An RFI needs a question that still requires an answer.

A note that says “delivery moved to Monday” gives you a date. The conversation may also explain why it moved, which crew needs to change its plan and who agreed to the change. That is the context a PM needs when they were not on the call.

A company can have excellent software for searching project records and still have important decisions missing from those records. Better answers depend on the information that actually arrives.

What are the alternatives for hands-free documentation without glasses?

Hardline captures the conversations construction teams already have through the appropriate call, meeting or on-site capture mode. The original discussion supplies the information; the super does not have to reconstruct the entire conversation afterward.

Phone calls

Hardline takes notes on inbound and outbound work calls using an existing number or a Hardline work number. The call with the supplier, the architect or the sub becomes the source for summaries and draft construction records. Our guide to AI call transcription for construction explains the workflow and setup. Hardline does not retain phone call audio. More answers are in the Hardline FAQ.

Virtual and in-person meetings

For virtual meetings, Hardline’s meeting bot joins a connected meeting to take notes. In-person discussions use on-site capture. The coordination meeting and the conversations that follow can be organized within the same project. Our October meeting-notes and shared-projects update shows how those records sit together.

Morning standups

A standup contains the day’s commitments: which area is ready, what is blocked and who is coming back. With an on-site capture session started, those updates can become source material for tasks and the daily record. A stated plan should remain a plan until someone confirms completion.

Toolbox talks and site walks

A toolbox talk can contain a topic discussed, a condition raised and a follow-up someone agrees to own. On-site capture preserves that discussion for review. It does not establish attendance, a signature or a completed inspection unless those are separately verified. Hardline’s construction daily-report workflow includes on-site capture for toolbox talks and walks.

These are deliberate work sessions and selected project records. People choose what to capture and share. The goal is a useful record of the work, with the company’s disclosure and access practices applied to the conversation.

What does real-time capture mean?

Real-time capture means taking the information from the conversation while it happens. It removes the need to rely on a later reconstruction of everything that was said.

Capture, processing, review and delivery are separate steps. Hardline’s on-site capture can work offline and process after reconnection. Phone calls need signal. Drafts are reviewed before approved records sync. A useful promise about capture should be clear about when each of those steps happens.

The result is an end-of-day review built on the day’s conversations, rather than a blank form and someone’s memory.

Our guide to automating construction daily reports explains the review step, including the information a conversation can supply and what needs another source.

How does a conversation become a record that matches company SOPs?

A transcript is source material. The useful output depends on the job’s process.

A company might require a daily-log entry organized by location and trade, a punch item with a responsible party, or an RFI draft using its own naming and review conventions. A verbal discussion about extra work may need a record of what was requested and a follow-up for written authorization.

Hardline structures information around those requirements. The workflow determines the fields, format, review and destination. It should preserve the source and distinguish a reported fact, a future commitment and a confirmed result.

For example, imagine this ordinary sequence. This is an illustration, not a customer result:

• During the standup, the electrical foreman says the west corridor will be ready Friday.
• On the walk, the superintendent identifies an unresolved sleeve location.
• In the coordination meeting, the architect asks for the question in writing.
• On the supplier call, a delivery moves to Monday.

The resulting records should reflect all four discussions. Friday remains a commitment. The sleeve location becomes an open question for review. The architect’s request becomes an RFI follow-up. The supplier’s revised date appears as a stated delivery update with any follow-up assigned.

Those conversations do not prove installation is complete, grant a formal approval or establish the schedule impact by themselves. Keeping those distinctions intact makes the record more useful later.

The construction AI notetaker and field-notes guide compares capture methods and outputs. The important comparison is whether the original discussion becomes the record your process needs.

Does all this information have a place in Procore?

Some of it has an obvious home: a daily-log entry, an RFI or a task. The discussion around it can span all three, or remain useful before there is a final document to file.

The reason the crew changed sequence. The condition attached to a verbal agreement. The question the foreman raised that still needs an answer. Those details give the next person a way to understand the update and act on it.

A transcript can be stored with a project, but the useful detail still needs to be connected to the decision or follow-up it explains. Capturing the original discussion preserves that context while the formal records take shape.

Hardline keeps the conversation available alongside the records drafted from it. Selected discussions and notes can also stay in a shared Hardline project. A conversation can be useful to the people running the job without immediately becoming a new RFI or daily-log entry.

The job also runs across systems. Procore’s marketplace reflects that contractors use other tools alongside their core platform. A GC may use one project-management system, a specialty contractor another, and an owner may require a separate reporting format.

Hardline structures information for the configured destination and format. Supported integrations include Procore, Fieldwire and Autodesk Forma, and the document types that sync vary by integration. See what syncs to Procore. Hardline also has an open MCP server, so any MCP-compatible tool or AI assistant can connect to it. Company-specific workflows and additional destinations need the appropriate configuration. It can also work on its own.

The useful result is a record that matches your SOPs, with enough context for the next person to understand what changed, who agreed and what is still open.

And you should not have to pay an arm and a leg for it. Hardline’s published pricing is per person, rather than a percentage of your company’s revenue. Glasses are a separate hardware purchase.

Can you wear Meta smart glasses on a construction site?

Smart glasses make sense when they fit the work, the person wearing them and the site’s rules. They can make a microphone available without holding a device, and supported camera-equipped models can add visual context.

Hardline takes a device-agnostic approach, including Meta glasses and supported safety-rated options such as Lucyd Armor. A client’s camera policy, the foreman’s prescription and the task’s eye-protection requirements all matter when selecting hardware.

Safety ratings belong to the exact configuration. Lucyd’s support documentation lists Armor base and Armor Slim with supplied non-prescription lenses as Z87+ high impact. Armor Vantage is basic impact; prescription qualification is separate.

On August 5, 2026, we published our field test of smart glasses on a construction jobsite. A conversation captured with Meta glasses became a formatted punch list. The article covers the practical hardware questions and includes our jobsite demonstration.

Hardline has run on Meta glasses on active sites since our August 2026 field test.

The job should decide what goes on the foreman’s face. The software should make the information useful afterward.

Procore AI Go vs Hardline: how do they compare?

Here is how the two line up on the conversations a job runs on. Procore availability reflects the October 21 announcement linked above.

Sources: Procore press release (Oct 21, 2026) and ENR coverage.

What should contractors do now?

Procore AI Go is set to make daily logs and RFIs a little easier to produce and recall. That’s table stakes. It still starts from someone asking it a question or telling it what happened. The phone calls and meetings where decisions get made aren’t part of the announcement.

Hardline captures the information the first time, as it happens, from meetings, jobsite conversations and phone calls. Then it turns that into the work that needs to get done: daily logs, RFIs and tasks that follow your SOPs, in Procore or wherever the job runs. On-site capture works without signal and processes once you reconnect.

Your team already did the work. Don’t make them do it twice.

Watch Hardline’s smart-glasses field test.