Procore custom reports can combine project details from tools such as RFIs, submittals, daily logs, and timecards. Add filters, group related records, and view key dates in one place. That broader view can make it easier to spot how a pending response or submittal may affect the wider project schedule.

Multiple Choice

A custom report allows you to report on multiple tools at once.

Custom reports in Procore can pull information from multiple tools in a single report. This means you can include fields from RFIs, Submittals, Daily Logs, Timecards, and other modules together, then apply filters, groupings, and summaries to get a cross-tool view of project status. For example, you could create a report that shows Submittal status and RFI responses alongside responsible parties and due dates, helping you see how issues across different areas impact the schedule. No special admin approval is required to build such a report—you just need the appropriate permissions to access the tools involved.

A superintendent rarely gets the full project picture from one screen. A submittal may be waiting on a response while an RFI holds up a decision, and a daily log may show that the affected crew is already on site. Procore custom reports can bring information from multiple tools into one view, making it easier to spot these connections and follow up before small delays spread.

That matters because construction data tends to live in separate places. Each tool has a job: RFIs track questions and responses, Submittals follow reviews and approvals, and Daily Logs record what happened in the field. These records make sense on their own. The challenge comes when a superintendent needs to see how they relate.

One report, several tools

A custom report can include information from more than one Procore tool. Depending on the tools and fields available to the person creating the report, it may combine details such as RFI status, submittal status, responsible parties, and due dates. That gives a superintendent a broader view than a report built around a single workflow.

Think of it like a jobsite whiteboard that gathers notes from different crews. The value isn’t simply having more information in one place. It’s being able to notice a link: a late submittal and an unanswered RFI may both affect the same area of work. When those items appear together, the next conversation can be more focused.

A cross-tool report can also reduce the need to open several separate screens just to assemble a basic status update. That doesn’t replace the source records or the teams responsible for them. It gives project staff a shared view they can use to identify what needs attention.

Turning scattered details into a useful view

A report is most useful when it answers a clear question. “Show me everything” sounds convenient, but a long list of unrelated fields can be harder to read than the separate tools themselves. Before building a report, define the decision or conversation it should support.

For example, a superintendent might want to review items that could affect work planned for the coming days. A report could bring together open RFIs and pending submittals, along with due dates and assigned reviewers or responsible parties. A project team might then look for items tied to the same building area, trade, or schedule activity.

Filters help narrow the results. A report could focus on a specific project, a date range, a status, or a set of responsible parties, depending on the fields available. Grouping can help organize the information—for instance, by status or assignee—while summaries can make totals easier to scan. The aim is a view that supports a next step, not a spreadsheet with every possible column.

Here’s a simple example. A submittal for a material is still under review, and an RFI about its installation detail remains open. Seen separately, each item may look like one more task on a long list. Seen together, they may point to a coordination issue that deserves a timely conversation with the relevant team.

A report doesn’t replace follow-up

A custom report can highlight relationships, but it can’t decide what those relationships mean. Two records that appear together may be unrelated. A delayed item might affect a future activity rather than the work happening today. The project team still needs to check the details, confirm ownership, and agree on what happens next.

That distinction is important. Reports are a way to organize information, not a substitute for field judgment or communication. A superintendent may use a combined view to flag a concern, then open the original RFI or submittal to read its full history. The report points toward the record; it doesn’t tell the whole story.

This is also why a small, focused report often beats a massive one. If the team can quickly see the status, due date, and responsible party, they’re more likely to use the view in a coordination meeting. If the report is crowded with fields that nobody acts on, it becomes background noise. Keep the useful details close together and leave out the rest.

Permissions and access still matter

Creating and viewing a custom report depends on the user’s permissions and the project setup. Someone may need access to the tools and data included in the report. If a field or tool isn’t available to a user, the report may not show the information they expect. Project administrators can help clarify access, but special approval isn’t automatically required just because a report includes multiple tools.

Permissions aren’t just a technical detail. They help control who can see or manage project information. If a report looks incomplete, it’s worth checking whether the user has access to every relevant tool and whether the report’s filters are narrowing the results. A blank section doesn’t always mean the project has no records; it may mean the data isn’t visible in that view.

Teams should also agree on how they interpret the report. For instance, decide what “open” means for a particular workflow and who is expected to respond when an item appears in a follow-up list. Clear ownership keeps a report from becoming a passive dashboard that everyone sees and nobody acts on.

Building a report people will actually use

Start with the work at hand. If the main concern is coordination between design decisions and material approvals, include fields that help the team trace those items. If the goal is a broader status review, use a date range and group the results in a way that makes ownership clear.

It can help to ask a few practical questions before sharing a report:

  • What decision should this view support?

  • Which tools contain the information needed?

  • Which fields help someone take the next step?

  • Who needs access to the report and its underlying records?

  • How often should the team review it?

These questions keep the report tied to real project needs. They also help avoid a common snag: building a polished view that doesn’t fit the rhythm of the jobsite. A daily coordination huddle may call for a short list of near-term concerns, while a weekly project review may need a wider summary.

Once the report is in use, gather feedback. If a field causes confusion or a filter hides useful items, revise the view. Reporting works best as an evolving part of project communication, not a one-time setup that nobody revisits.

The bigger picture

Procore custom reports can pull information from multiple tools, giving superintendents a way to connect details that would otherwise sit in separate workflows. With thoughtful fields, filters, and groupings, one view can help teams see how RFIs, Submittals, Daily Logs, Timecards, and other project information intersect.

The real benefit is not simply fewer clicks. It’s a clearer path from information to action. A well-built report helps a team notice what may be connected, check the underlying records, and bring the right people into the conversation. On a busy project, that kind of shared visibility can make coordination feel less like chasing scattered notes—and more like keeping the work moving together.