Learn how Procore lets you create custom reports at both the account and project levels. Discover how portfolio-wide insights are formed, how to reuse report definitions, and how permissions shape who can build reports. This quick overview clarifies where reports can live, how scope affects data, and why flexible reporting matters.

Multiple Choice

A custom report can only be created at the Project level.

Custom reports can be created at more than just the Project level. In Procore, you can build a report at the account (Company) level, which lets you pull data across multiple projects, or you can create reports scoped to a specific project. This scope flexibility lets you generate portfolio-wide insights or drill down into a single project without duplicating work, and it supports standardizing metrics across your organization by reusing report definitions. Access to creating custom reports depends on your role and the Reports permissions, not on being restricted to a single project. So, you’re not limited to only the Project level.

Custom reports aren’t stuck at a single project. If you’re coordinating multiple sites or want a snapshot that spans your whole portfolio, Procore gives you options beyond the project fence. Here’s how understanding report scope can save you time, reduce duplication, and keep your teams aligned without drowning in data.

Why scope matters in reporting

Project-level reports are great for granular details: daily crew counts, material deliveries on a specific site, punch list progress for that building, and month-end cost summaries tied to a single project’s budget. But construction programs aren’t one-plot landscapes. They’re ecosystems of projects, phases, and teams that need consistent metrics to make the big decisions. When you can pull data across several projects or pull in data from the entire company, you gain a bird’s-eye view—where trends live, where bottlenecks hide, and where you can steer the portfolio toward smoother outcomes.

Different scopes, different insights

  • Project-level reports: Perfect for the specifics. If you’re tracking a single site’s subcontractor performance, weekly safety incidents, or equipment utilization on that project, this is where you’ll set the focus. It’s like looking through a magnifying glass on one corner of the job.

  • Account (Company) level reports: These are the wide-angle shots. They pull data from multiple projects so you can compare performance, standardize metrics, and identify patterns across the organization. Think of it as your executive dashboard that helps align teams and set company-wide priorities without reinventing the wheel for every project.

  • Hybrid or scoped reports: You’ll often want a blend—for example, a portfolio view that filters down to a handful of active projects. This balance keeps you from drowning in data while still delivering meaningful, actionable insights.

What makes cross-project reporting powerful

  • Standardization saves time: When you reuse report definitions, you don’t rebuild the same metrics for every project. You create once, apply everywhere, and keep consistency across the board. This is especially handy for key performance indicators (KPIs) like schedule adherence, change order value, or daily field crew hours.

  • Earlier trend detection: Portfolio-level reports reveal patterns that aren’t obvious when looking at a single site. If a particular subcontractor consistently delivers late on multiple projects, you can flag it early and adjust planning or resource allocation accordingly.

  • Better collaboration: When stakeholders across the company see the same data in the same format, conversations stay focused on the numbers—reducing back-and-forth and misinterpretations. A consistent data language helps field teams and office staff stay aligned.

Permissions and practical access

Access to custom reports isn’t a matter of being in a certain role by default. It hinges on the permissions tied to your Procore account. Some users may need elevated access to create or modify reports, while others can view and run scheduled reports. The right balance keeps sensitive data protected while ensuring teams can get the insights they need. If you’re unsure, a quick check with your administrator can confirm what you can create, view, or share.

Getting practical with creating reports

  • Define the objective: Before you click anything, ask, “What decision will this report support?” Are you tracking month-over-month cost growth? Do you need to verify that all projects meet a safety target? Clear aims keep the report focused.

  • Choose the scope first: Start by deciding whether the report should cover a single project, a group of projects, or the whole company. If you’re comparing performance across sites, begin with an account-level report.

  • Pick the right data sources: Procore organizes data by modules—Bids, Submittals, RFIs, Daily Logs, Observations, and so on. Align the data sources with your objective. If you want to monitor field productivity, you might pull Daily Logs, Timecard data, and Crew assignments.

  • Build with reusable definitions: Create a core set of metrics you’ll reuse across reports. This could be a standard “On-time Submittals” metric, a “Cost to Complete” figure, or a safety incident rate. Reusing definitions keeps results consistent and makes it easy to roll up data later.

  • Visualize with intent: Choose visuals that tell the story. Simple tables for exact figures, line charts for trends, or bar charts to compare sites. The goal is quick comprehension, not flashy decoration.

  • Plan for cadence: Decide how often the report should refresh and who receives it. You might set a weekly portfolio briefing or a monthly executive snapshot. Automated delivery keeps everyone on the same page without manual steps.

  • Validate and refine: No report leaves the draw board without a quick sanity check. Cross-verify a few figures with site leads or project managers to catch anomalies early. It’s better to catch a small mismatch now than chase it later.

Common pitfalls to avoid

  • Too broad or too narrow: A portfolio-wide report that tries to capture everything can become overwhelming. Start with a focused set of metrics and expand thoughtfully as needs emerge.

  • Inconsistent data inputs: If different projects use slightly different conventions, the portfolio numbers won’t line up. A shared vocabulary helps: same units, same definitions, same naming.

  • Overloading with charts: A crowded dashboard can obscure the point. Keep it lean—one or two key visuals that convey the core message, plus a few supporting details for context.

  • Relying on manual refreshes: If your data lags, the report loses relevance. Automate where possible so you’re always looking at current information.

Real-world analogies to make sense of it all

Think of your reporting setup like a radio. A project-level report is the close-up mic on a single DJ spinning a track—you hear every beat and nuance. A company-level report is the studio-wide broadcast, where you can hear the overall tempo, notice who’s scratching at the right moments, and pick up on trends across the airwaves. Both are valuable; the trick is knowing when to tune in to which station.

A few practical tips for aspiring leaders

  • Start with a pilot: Create one solid portfolio report for a couple of active projects. Use it as a learning tool, then scale up.

  • Normalize timeframes: Align weeks, months, and quarters across projects so comparisons are meaningful. It saves you from apples-to-oranges comparisons.

  • Keep a data dictionary handy: Document what each metric means, where it comes from, and how it’s calculated. This keeps everyone on the same page as the team grows.

  • Automate alerts for anomalies: If a metric spikes or dips beyond a threshold, an alert helps you jump on it before it becomes a bigger issue. It’s like having a guardrail for data quality.

  • Treat reports as living documents: As projects evolve, so should your metrics. Don’t be afraid to prune stale data points or add new ones that reflect current priorities.

A quick tour of the practical benefits

  • Time savings: Reusable report definitions cut the effort needed to assemble new views. You’ll spend less time wiring data and more time interpreting what it means for the work.

  • Consistency across the portfolio: Standard metrics mean leaders aren’t chasing different numbers from different people. That consistency underpins trust and clearer decision-making.

  • Better foresight: When you can spot trends early, you can adjust scheduling, procurement, or crew deployment before problems snowball. That’s the difference between reactive fixes and proactive planning.

Bringing it back to the big picture

Custom reports, whether scoped to a single project or extended across the company, are more than just data dumps. They’re the language that connects field realities with strategic intent. They help you answer questions like, Are we delivering on time? Are costs staying within plan? Which teams are performing consistently, and where do we need to lean in? The ability to pull the right data at the right level empowers supervisors, project managers, and executives to collaborate with clarity.

As you navigate the practical world of construction management, remember that reporting isn’t a dusty chore. It’s a living tool that translates messy, real-world activity into actionable insight. When you set up thoughtful, reusable report definitions and apply the right scope—project, portfolio, or a careful blend—you create a backbone that supports smarter decisions, smoother coordination, and, frankly, a steadier pace on site.

If you’re curious about tightening up reporting in your own operations, start by identifying one portfolio-level objective you want to track for the next month. Build a compact report around that goal, keep the scope tight, and watch how the numbers start speaking in a language your whole team can understand. It’s not glamorous, but it’s incredibly effective—and it makes the work feel a lot less like guesswork and a lot more like progress.