The reporting page lives at https://lengrowth.com/reporting.

The reporting shell does three important things:

If no company is selected, the page shows a workspace selection card that says "Select a Workspace". If a company is selected, the page tells you "Showing [company name]" and reminds you that you can use the company dropdown in the header to switch.

That structure is deliberate. Reporting is only useful if you know exactly which company the results belong to.

Use reporting when you want to:

If you are still deciding what the work should be, go back to the dashboard, growth page, or company workspace first. Reporting is strongest after the work has already been created and some results exist.

The page is company-specific, so there is no useful report until a company is active. If you are not on the right company, the report will still load, but it will load the wrong company's data.

The workspace selection card is the page's fallback state. It is there so you can get into reporting from a blank account without needing to hunt for another route first.

If your account has multiple companies, use the header dropdown to switch once you are already on the page. That keeps the page aligned with the correct source of truth for the report.

The report page uses a short cache inside the browser session. That means a previously loaded report for the same company may appear immediately before fresh data finishes loading.

In practice, that means:

This behavior is useful because it prevents a blank screen every time you revisit the same company. It also means you should wait for the report to settle before making a judgment about whether a value changed.

If the report refresh fails, the page keeps the company context and shows an error message instead of throwing you out of reporting entirely.

The exact content inside the reporting workspace depends on the company and the data available for it, so the safest way to use the page is to read the shell first and then inspect the report area itself.

The reporting page is most useful when you treat it as a bridge between work and result. If a report says something moved, the task list and pipeline are where you find the detailed history behind that movement.

The page also records that a company switch happened on the reporting route, which helps the system keep the reporting view aligned with the company you actually selected. You do not need to do anything with that detail directly. Just know that the page is designed to respect company switching cleanly.

After the report loads, the next step is usually not to edit the report itself. Instead, you use reporting to decide what needs attention next:

That makes reporting a review surface, not a creation surface. It is where you check whether the workflow is producing the right results, not where you write the work itself.

That means no company is selected in the header yet. Choose a company or create one first.

The page may be showing a cached copy while it refreshes the newest data. Wait a moment and re-check the report for the selected company.

Double-check that you are on the right company in the header. Reporting is scoped to the selected workspace, so a different company may have very different evidence.

The page shows a specific error state when report loading fails. The company tasks and assessments still exist, but this reporting view needs a retry.