Sheets is in beta. Here is what is open.

A record you can follow

A useful tracker answers more than what happened. Someone reviewing an item should be able to find who owns the next action, when it is due and what has changed since the last conversation. Sheets brings those details together in a record, with notes and history alongside the work.

The beta includes a RAID log template for actions, risks, issues and decisions. Create it from New sheet, then use the dashboard and board to review the same records. RAID is a Sheets template, so you do not need to maintain a separate module for this kind of work.

Start with one tracker that already has a reason to exist. Pick a review your team actually runs, such as the weekly project handoff. Agree who will maintain it and what a finished item means before bringing over a large file. That makes the first review useful even while you are learning the product.

Your status names, with a consistent meaning

Sheets supports status names chosen for the sheet. Each status is tied to a stage, such as new, in progress, on hold or closed, and can say whether the item is waiting on the customer or the provider. The words help your team read the tracker; the stage gives the status a consistent meaning in the workflow.

The RAID template starts with New, With Customer to Resolve, With Provider to Resolve, On Hold, Cancelled and Closed/Complete. The provider label uses the account display name when one is set. You can rename labels in sheet settings. Keep the owner separate from whose court it is in: a person on your team can still own follow-up while a customer has the next move.

On Hold remains visible as open work but is not counted as overdue. An item due today is not overdue either. Cancelled is a separate finish from Closed/Complete, and changing an existing record to Cancelled requires a note explaining why. Write that explanation for the person who will open the item after everyone has forgotten the meeting.

The owner is responsible for follow-up. Whose court it is in tells you who has the next move.

Look at the records behind the dashboard

This example uses the real RAID dashboard component with invented records and a fixed review date. It is a read-only product view, not a picture of a customer account. Look at the next-conversation list, the missing owners and the status board. These are different ways to inspect the same work, rather than separate lists to reconcile.

The demonstration is also a useful way to decide what to test with your own team. Choose one overdue item, one item with no owner and one waiting on the customer. For each, ask whether the next person would know what to do without starting another thread.

Bring your rows, then read the warnings

The RAID template accepts supported CSV or XLSX imports. Once a readable file has been mapped for that template, the import keeps rows with damaged cell values for review instead of dropping them for those problems. A blank title gets a fallback title. Unrecognized choices and unreadable dates produce warnings, and the original cell text stays with the imported record.

That is a specific import behavior, not a promise that any workbook will transfer perfectly. Entirely blank file rows are ignored, and a row that cannot be imported is reported as an error. Review the preview, check the resulting counts and read the warnings. Columns without a mapping are flagged; a working value can differ from the original text when it needs correction.

Owner names must match the workspace roster. An unmatched name stays in the original record while the working item is unassigned. An unknown status is warned about and uses the sheet's default new status. Treat those warnings as a review list before you rely on the dashboard. Keeping a row is the beginning of the cleanup, not proof that every value is ready.

What is outside the beta, and how to turn it off

Sheets does not provide cell formulas or live two-way sync with another tool. An import copies records into Panora; editing the original file does not keep both places aligned. Choose which tracker your team will maintain after the import, and make that choice clear at the next review.

Sheets is enabled by default for accounts in the beta, with an account-level override. An admin can open Settings, find Modules, clear the Sheets checkbox and select Save modules. This hides Sheets from the menu and closes access to its routes. Dismissing the beta notice only dismisses the notice; it does not turn the module off.

Use the beta to test a real, bounded workflow. Bring questions about confusing status names, warnings that need explanation or records that are hard to review. The useful feedback is concrete: what you were trying to decide, what you expected to see and what the record actually showed.

• Explore Sheets
• Read about the beta