Reviewing Documentation Performance Across Projects

Opening the project performance view

To review documentation performance across projects in Atloria, start from the signed-in workspace and open the reporting area available to your role. If you work in the administrative workspace, look for the Analytics area from the admin navigation. In some workspaces, project reporting may also be available from a project analytics screen. The key is to open the view that shows project-level metrics rather than a single project’s details.

When the analytics screen opens, first confirm you are looking at a Projects view, a project grouping, or a table/chart that lists multiple projects together. If the screen offers a grouping or comparison selector, switch it to Projects before you start reviewing results. This keeps your comparison focused on project performance instead of broader totals.

Before reading any numbers, check the date range control. Set it to the exact reporting period you want to review, such as the current month, quarter, or another period your team uses for reporting. If you compare projects with the wrong date range selected, the results can look inconsistent even when the underlying work is healthy.

Next, review any visible filters. Clear Project, Team, and Status filters unless you intentionally want a narrower view. A filtered dashboard is useful for targeted reviews, but it can distort comparison if you forget a filter is still active from an earlier session.

Use this quick check before you continue:

• Open Analytics
• Switch to Projects or the project comparison view
• Set the correct date range
• Review Project, Team, and Status filters
• Confirm the screen is showing multiple projects in the same reporting context

Reading project-level documentation trends

Once the project performance view is open, read the screen one project at a time before drawing conclusions across the full list. In Atloria, this usually means scanning a project table, summary cards, or a trend chart that shows how each project is performing during the selected period. Focus on the metrics shown on screen, such as documentation output, completion rate, quality score, or engagement trend, depending on what your workspace includes.

A single low value does not always mean a project is struggling. The trend visualization is often more useful than one isolated number because it shows whether the project is slipping briefly or declining over a longer period. A short dip may reflect a recent release cycle or a temporary pause in content work. A steady downward line across the full date range is a stronger sign that the project needs attention.

Sorting helps you review faster. If the project table allows sorting, click the column for the metric that matters most to your review. For example, sort by completion rate to bring the weakest projects to the top, or sort by quality score to find projects that may need editorial support. Re-sort as needed to look at the same set of projects from different angles.

If a project row can be opened, select it to view a detail panel or project-specific analytics screen. Compare the current period with the previous period if that comparison is shown. This helps you tell the difference between a project that has been weak for several periods and one that is already recovering.

Useful review habits include:

• Scan the full list before focusing on outliers
• Sort by one metric at a time
• Use trend lines to confirm whether change is temporary or sustained
• Open project details when a row looks unusually strong or weak

Comparing outcomes across teams and projects

After you understand the project list, shift to team comparison. In Atloria, use the Team filter or any group by control that separates projects by owning team. This lets you compare projects in the same reporting view without jumping between unrelated screens. If you recently reviewed enterprise and project reporting differences, use that context here rather than repeating setup steps from Comparing Enterprise and Project Reporting for Documentation Programs.

When team grouping is active, compare the same metrics across each team’s projects. Look for side-by-side columns or charts that show differences in output, quality, and timeliness. One team may publish a high volume of documentation but show weaker quality results. Another may produce less content but maintain stronger completion or engagement patterns. Reading these measures together gives a more balanced picture than relying on a single score.

Sorting is especially helpful inside team views. Change the sort order so the highest- or lowest-performing projects appear first within each team grouping. This makes it easier to spot whether one team has a single problem project or whether several projects are trending in the same direction. If the list is long, compare the top and bottom projects in each team before reviewing the middle.

Keep your comparison fair by holding the reporting setup steady. Use the same:

• Date range
• Status filters
• Project scope
• Team selection rules

If one team is shown for the current quarter and another is effectively narrowed by an extra filter, the results will not be comparable. Before presenting findings, glance back at the filter bar and confirm every team is being measured under the same conditions.

Finding projects that need support or investment

A useful project review does more than identify winners and lagging teams. It helps you decide where to direct support. In Atloria, start by looking for projects with declining trend lines, low completion results, or weaker outcomes than similar projects in the same team. These are often the first candidates for follow-up.

Use the signals visible on the dashboard to flag projects for review. Depending on the screen, this may include low rows in a sorted table, negative period-over-period movement, or visual indicators that show a drop from the previous period. A project with weak results in several areas at once usually deserves more attention than a project with one isolated low metric.

To decide what kind of help a project needs, compare output metrics against quality or engagement measures:

• If output is low and quality is also low, the project may need broader operational support.
• If output is high but quality or engagement is weak, the project may need content improvement rather than more volume.
• If quality is strong but output is consistently behind, the team may need workflow support to publish more reliably.
• If several projects owned by the same team show the same weakness, the issue may be team-wide rather than project-specific.

Open the project’s detail view when possible and compare the current period with the previous one. This helps confirm whether the project is in a temporary slowdown or part of a wider pattern. Also check whether the same team has multiple underperforming projects. Repeated weakness across a team often points to process issues, while one isolated project may need targeted content investment.

Filtering the data to answer specific management questions

Broad comparisons are useful, but management reviews often need narrower answers. In Atloria, use the filter controls at the top of the analytics screen to narrow the dashboard to the projects you want to examine. Start with Project filters when you need to review a specific portfolio, ownership group, or business area. This is especially helpful when leadership wants to discuss one segment without the noise of unrelated projects.

Adjust the date range to match the question you are trying to answer. A shorter period can reveal recent changes in output or completion, while a longer period is better for spotting sustained patterns. If your review includes multiple meetings, keep the same date range across each session so your comparisons stay consistent.

Use Status or activity-based filters when you want to separate active work from projects that are completed or no longer in focus. This prevents archived or inactive projects from lowering averages or cluttering the list. If your workspace includes team ownership filters, combine them carefully so you can answer questions like:

• Which active projects are slipping this month?
• Which team’s current projects have the weakest completion trend?
• Which portfolio shows strong output but weak engagement?
• Which projects improved after a recent process change?

Some Atloria workspaces may support saved or reusable reporting views. If you see an option to save the current view, use it for recurring leadership reviews so you do not have to rebuild the same filter set each time. If no save option appears, record the filter combination you used and keep it consistent for future reviews.

Resolving misleading comparisons in the dashboard

When a comparison looks wrong, check the reporting setup before assuming the projects themselves changed. In Atloria, the most common cause of misleading results is an inconsistent date range. If one widget, chart, or table appears out of step with the rest of the screen, confirm the selected period is applied everywhere in the current view. A mismatched period can make one project appear to drop sharply when you are actually looking at different time windows.

If a team appears to be missing projects, inspect the active filters first. A leftover Project, Team, or Status filter can remove rows from the comparison without making the issue obvious at a glance. Also review whether the project grouping you selected is showing only a subset of projects rather than the full list.

Trend lines can also be misleading when the selected period is too short or does not include enough historical activity. If a chart looks incomplete, widen the date range and check again. A longer reporting window often makes the trend easier to interpret and reduces the impact of one unusual week or release cycle.

When one project appears unusually strong or weak, open its detail panel instead of relying only on the summary row. Look for signs of a recent content spike, a reporting gap, or a sudden change limited to the current period. This extra check helps you avoid overreacting to outliers.

Before sharing your conclusions, run through these checks:

• Confirm the same date range is used across the view
• Review all active filters
• Check whether the chart includes enough history
• Open unusual projects in their detail view
• Compare outliers against the previous period before escalating

For a broader admin perspective on reporting areas, see Monitoring Administrative Analytics and Activity.

Overview

Atloria includes an Analytics area in the admin workspace, but the current Analytics & Insights screen is presented as a coming soon area rather than a fully populated reporting dashboard. You can still use the screen to understand where project-level reporting is intended to live and how it fits into the wider administrative workspace.

From the Admin area, you can open the card labeled Analytics. The card description refers to usage statistics and insights, which signals that this is the place to look for cross-project reporting when that view is available in your workspace. The screen header reads Analytics & Insights, with supporting text about usage statistics and performance metrics. This confirms that the area is meant for reviewing higher-level reporting rather than editing project content.

What you can reliably identify on the current screen:

• The page title is Analytics & Insights
• The page sits within the Admin workspace
• The purpose of the page is usage statistics and performance metrics
• The current state is a coming soon notice rather than a detailed report

Because the visible screen is a placeholder, you may not yet see live charts, project tables, team comparisons, or saved reporting views in every Atloria environment. If your workspace includes a more complete analytics experience, use the guidance in the sections above to review projects consistently. If your screen only shows the placeholder message, treat this document as preparation for the reporting workflow Atloria is introducing.

For related project-level analysis patterns, see Analyzing Documentation Performance Across Projects.

Prerequisites

Before you try to review documentation performance across projects in Atloria, make sure you can access the parts of the workspace where reporting is exposed. The most important requirement is that you can sign in successfully and reach the authenticated workspace. If you need help with account access, use Signing In to Atloria and Solving Access Problems.

You should also be comfortable moving through the Admin workspace, since the available reporting entry point in the provided workspace appears there. Open the Admin area and confirm you can see the main cards, including Users & Permissions, Organizations, Documents, Projects, and Analytics. If the Analytics card is not visible, your role may not include access to that area.

Before starting a comparison review, it helps to have:

• Access to the Admin workspace
• Visibility of the Analytics entry point
• A clear reporting period you want to review
• Familiarity with the projects or teams you are comparing
• Permission to open project areas if you need to validate a result in more detail

Because the current Analytics & Insights page may still be in a placeholder state, you may not be able to complete every comparison task in all workspaces yet. In that case, use this guide to prepare your review method and to recognize the controls to use once project-level reporting is available in your Atloria environment.

If your goal is to move from comparison into action planning, continue with Turning Analytics into Documentation Improvement Actions.