Agree what deserves a manager handoff
Start with a simple team agreement. Routine work follows the normal local review process. A completed task that needs a manager’s attention gets Send to manager for review. Good examples include a change with an unresolved product decision, a risky migration that needs another pair of eyes, or work a new teammate wants to walk through together. The member chooses when to make that handoff.
That action gives the task an orange Manager review state. It is separate from working and ordinary ready states, with a text label as well as color. You can distinguish “an agent has finished” from “a teammate wants me involved” as you move through the company. The signal has a purpose because it comes from an explicit request.
Review the handoff, then the evidence
Open Company mode, choose the relevant floor and enter the member’s room. The task view shows metadata such as provider, state, start and completion time, duration, local review state and manager acknowledgement. Generated labels identify task records without uploading their original titles. This is enough to locate a handoff and discuss its timing with the person who owns it.
For the engineering review, use the actual patch, tests and acceptance criteria in your normal repository workflow. Company does not copy the member’s source code or transcript into the room, and it does not remotely operate their machine. Mark metadata seen records that you acknowledged the shared item. It neither approves code nor changes the member’s local review state. Agree separately what evidence closes the engineering decision.
Make the daily count a doorway into the work
Finished today gives each member a clickable completed-task count. Open it to inspect that day’s completion metadata rather than stopping at the headline number. This is useful before a standup or a review block: you can see which execution attempts finished, what still has a local review state, and which items were explicitly passed to a manager.
Keep the interpretation modest. The count tracks completed execution attempts. It does not measure complexity, customer value, hours worked or deployed features. A resumed task can have more than one completed attempt. Use the table to prepare a specific conversation: which result needs a decision, which change still needs verification, and who would benefit from pairing?
Give the weekly check a clear question
Weekly review shows seven daily columns and lets you open the completions behind each date. Days use UTC, so a late evening run may fall on a different date from your local calendar. Shared task data has a rolling seven-day retention window. A weekly check is most useful as a review of recent activity, while the team still has the context to explain it.
Choose one question before you open the table. Did explicit review requests get a timely response? Which completed attempts still need someone to inspect the result? Is the team starting more work than it can review? Answer those questions with the people involved and the underlying development evidence. Save durable decisions in your existing project records because Company is a short recent-history view.
Keep the room comfortable as the team grows
Company starts with ten members per floor, and the floor size is configurable from one to forty. Begin at ten and increase it if your display and team routine make a denser view useful. More rooms can mean more scrolling and more information to scan. Floors let you keep a manageable view while the directory grows; a larger floor setting is not a promise about production capacity.
Sharing is enabled by default, with a member-controlled opt-out visible to managers. A private member remains in the roster without a room or shared task counts. Owners and managers do not appear as rooms. You can still switch to your own Office, run agents and review your own coding tasks. Every manager uses the same $14.99 USD monthly Team seat as a member, so keeping a hands-on role does not require a second team seat.
Explore A company view for founders who still love building, A calmer agency week, one room and one handoff at a time, Write a useful development update from completed agent work.