Review and maintain the workspace

Run a weekly review from Reports

The Reports page supports daily or weekly operational review. It provides focused views rather than an executive dashboard full of decorative graphs and feelings.

Review areas can include:

• Documents expiring in 30, 60, or 90 days
• Overdue follow-ups
• Waiting work grouped by party
• Missing required items
• Blocked customers
• Owner workload
• Customer package status

A practical weekly review might look like this:

1. Review documents expiring within the next 90 days.
2. Check overdue follow-ups and decide what needs contact today.
3. Review waiting work by party for recurring bottlenecks.
4. Look at missing required items that have not yet been requested.
5. Review workload by owner.
6. Export the report when it needs to be discussed or retained outside Sidecar.

Reports summarize the records in Sidecar. They do not determine compliance or approval.

Export your workspace

Sidecar provides workspace exports so your organization can keep a usable copy of its operational data.

From Settings, export the workspace as an Excel workbook or a ZIP containing CSV files. Exports can include customers, platforms, documents, tasks, work views, import history, and preserved metadata.

Customer Detail and other operational views may also provide narrower exports when you need a specific customer package or review list.

Export is not a substitute for Sidecar’s operational backups, but it ensures your team is not trapped inside the application when it needs its own data.

A practical daily routine

A normal day in Sidecar does not require visiting every page.

Start on Today and review the highest-priority customer. Open Customer Detail, confirm the Operational Focus, and perform or assign the next real action. Continue through the focus list until the urgent work is handled or intentionally waiting.

Then check Waiting On for follow-ups due today. Review Email Intake for replies that need classification. Use All Work only when you need the full backlog or a filtered review.

Before finishing, make sure completed work is marked complete, new waiting states have useful notes, and follow-up dates reflect when someone should actually return to the item.

That is enough. Sidecar should reduce the morning treasure hunt, not replace it with a nine-tab software ritual.

First-day checklist

By the end of the first working session, aim to have:

• Workspace preferences reviewed
• Three to five customers added or imported
• Platforms assigned where relevant
• Primary request contacts recorded
• A representative set of requested items added
• Existing documents linked where appropriate
• Missing and in-progress work identified
• At least one internal task assigned
• Waiting notes and follow-up dates recorded for active requests
• Today reviewed for a believable priority order
• One workspace export downloaded and opened successfully

You do not need every historical record before the workspace becomes useful. Add enough current information to make the next action clear, then improve the record as normal work continues.

Common setup mistakes

Treating every record as urgent

Use realistic statuses, due dates, and follow-up dates. If everything is urgent, Today becomes an anxiety generator instead of a work queue.

Using tasks for customer obligations

Use requested items for work the customer expects. Use tasks for internal actions. Keeping them separate makes ownership and package status easier to understand.

Marking waiting work complete

Waiting means another party has the next step. Keep the item active until the underlying work is resolved.

Treating a submitted item as accepted

Submission and acceptance are different events. Record the state your team can support.

Creating duplicate records instead of linking them

Before adding another document or requested item, check whether the existing records can be linked or updated. One obligation scattered across several nearly identical rows is how spreadsheets reproduce in captivity.

Relying on Activity History as the current status

Activity History explains what happened. The source record’s current status, waiting state, and follow-up date describe what is true now.

What Sidecar does not decide

Sidecar helps organize administrative workflow. It does not determine whether a company, vendor, subcontractor, employee, document, insurance policy, or customer package is compliant, approved, qualified, or legally sufficient.

Your team remains responsible for reviewing source documents, customer instructions, insurance requirements, portal decisions, and any legal or regulatory obligations that apply to the work.

Sidecar’s job is smaller and more practical: show what is missing, who has the ball, what needs attention, and what happened along the way.

Make Sidecar the operating record

Sidecar becomes more useful when the team treats it as the current record of administrative work rather than another place to copy information occasionally.

Update statuses when work moves forward. Record who has the ball, set realistic follow-up dates, and close tasks when they are finished. When everyone keeps that record current, Sidecar can become the place the team checks to understand what is missing, what is waiting, and what needs attention next.

Customer portals, email, and source documents will still exist. What Sidecar can replace is the scattered status hunt across inboxes, spreadsheets, notes, and memory.

Keeping that operational record current reduces the chance that a forgotten request, expired record, or unresolved follow-up delays work, strains a customer relationship, or contributes to lost business.