What belongs on your company OS home screen

A company OS home screen should help someone decide what needs their attention today. Start with the work waiting for a decision and give each item a route to the record behind it.

At RWS, the AI Native service includes a company OS website where customers can see their work and information. Its contents should reflect the covered routines, connected systems, and responsibilities agreed for that business. The screen is one part of the recurring service.

Start with decisions someone can make

Put approvals and unresolved exceptions near the top. Each item needs enough context for its owner to act: what happened, what decision is needed, and which evidence supports the proposed action.

Illustrative example: a job is ready for billing, but its completion record contains an unapproved change. The home screen could show the job, the missing approval, and the person responsible. Opening it should reveal the original agreement and the change awaiting review.

A button that approves the charge needs an explicit permission rule. Viewing the item should never imply authority to approve it.

Show where the answer came from

A status needs a source and a last-checked time. If a connection stopped updating, keep that failure visible. A stale “complete” label can send someone into the next task with the wrong assumptions.

Give company knowledge the same treatment. A process answer should point to the maintained document and identify who owns it. When two documents disagree, assign someone to settle the conflict before the answer is used for consequential work.

Keep access specific

Choose what each role needs to see. A staff member handling a job may need its customer details and approved instructions. Access to every company record creates avoidable exposure and makes the useful information harder to find.

Use this short review when deciding whether an item belongs on the home screen:

• Who uses this information, and what action does it support?
• Where is the underlying record maintained?
• How will someone know the information is current?
• Who handles the item when its normal process fails?

Test it against an ordinary morning

Ask the person responsible for daily operations to walk through a sample workday. Can they find the decisions waiting for them, inspect the evidence, and tell which work has finished? Include a failed connection and a missing approval in the exercise.

Keep the first screen small enough to use during that walkthrough. Add another view when a recurring responsibility requires it. A company OS earns its place when people can use it to resolve covered work and verify the result.