How remote teams use Plane

A distributed team's working day often picks up where another region left off. Sam, an engineer in New York, might start with a feature ready for review from the Berlin office, a new request from Cloverquay Retail, and an updated onboarding decision. Each calls for a different next action, but none requires everyone to be online together.

Plane connects customer requests, code activity, review discussions, and decisions to the work they concern. When the next region comes online, contributors can pick up with the context they need, without scheduling a status call.

We'll look at how remote teams catch up on progress, handle new requests, continue Engineering work across shifts, make decisions, and track delivery progress.

Start your day with the right context

Sam needs to review his responsibilities, catch up on notifications, and understand what moved forward during Berlin's working hours. Your work shows his responsibilities, Inbox surfaces relevant updates, and Plane Agents answer broader questions about project progress.

Review responsibilities in Your work

Sam starts his day after the Berlin team signs off. In Your work, the Assigned tab shows the export progress indicator awaiting his review alongside other tasks. Created and Subscribed tabs keep requests he raised or follows in one place, while Summary groups his workload by state and priority. Activity lists the actions Sam has taken in the workspace.

Catch-up on important updates in Inbox

While Your work shows Sam's responsibilities, Inbox surfaces notifications about work he's directly involved in, including items assigned to him, created by him, mentioned in, or subscribed to. He sees a mention from Berlin asking for his review of the export progress indicator and an update that an onboarding item is ready for feedback.

Selecting an Inbox notification opens the corresponding work item, where Sam can review the discussion and respond. Inbox points him to the update; the work item is where he follows through.

Get up to speed with Plane Agents

For a broader catch-up, Sam asks Captain Catch-up, a Plane Agent scoped to the Engineering project, to summarize the past 24 hours. It highlights recent progress and work needing attention, with links to the relevant work items. Sam can choose what to review next without scanning every individual notification.

Handle incoming requests across time zones

New ideas can reach a team outside its working hours. Intake gives the next shift a place to review customer feature requests and internal proposals before accepting them into project work.

Collect and triage submissions in Intake

Cloverquay Retail's operations team in Boston wants store managers to move stock between locations through one workflow. A manager should be able to request a transfer, specify the items and quantities, and confirm receipt at the destination store. Cloverquay Retail submits the idea through a public Intake Form without needing access to the Engineering project. The request enters Intake for the team to review.

When the Berlin team starts work, the triage owner reviews how transfers should be initiated, who can approve them, and when the receiving store confirms delivery. They accept the request as a work item for Engineering, preserving the customer's requirements for the team planning the feature.

Keep context with Customers and Customer Requests

The account owner records Cloverquay Retail's stock-transfer proposal as a Customer Request, adds a source link to the Intake submission, and links the Engineering work item for inter-store inventory transfers.

The Engineering work item defines the transfer flow, including selecting source and destination stores, recording quantities, and confirming receipt. The linked Customer Request explains which customer proposed the workflow and why it matters to their operations. If another retailer asks for the same capability, its request can link to the existing work item, giving the team a clearer picture of customer demand.

Continue work that another contributor started

When Engineering work moves between regions, the next contributor should be able to build on the previous shift's progress. The work item brings together the implementation record, review notes, and the next action.

Inspect implementation activity through GitHub and GitLab

Consider the export progress indicator from Sam's Inbox. Marcus, Sam's colleague in Berlin, has opened a GitHub pull request that adds progress updates for large CSV exports. The implementation is ready for review, and Sam is taking the next pass on the large-file workflow. Because the pull request references the Plane work item, Sam can open its Development panel to find the code changes and review their status. Teams using GitLab or Bitbucket can follow merge requests and pull requests in the same Development section.

The Development panel points Sam to the code changes, while the work item holds the intended user experience, implementation notes, and review context.

Follow handoffs through work item activity

Before the Berlin shift ends, Marcus adds the staging link to the export progress indicator work item and asks Sam to review the large-file workflow. Sam can inspect the linked pull request and complete the review during the New York shift, then record the result in the same work item.

The All tab keeps their comments alongside recorded changes, including the move to In review and the assignment to Sam. Sam's reply confirms the feature is ready for QA. Activity shows the logged changes, while History shows previous and new property values, who changed them, and when. Contributors returning after a shift or planned leave can follow the progress without having to reconstruct the handoff.

Review changes and make decisions asynchronously

A feature review can bring together Engineering, Design, and Product across different working hours. The team needs a shared place to discuss options and record the agreed direction.

Connect conversations through Slack and Microsoft Teams

Emma, a product manager in London, suggests adding an import preview during onboarding in a Slack thread. Alex, a designer on the team, uses @Plane to create a work item in Product and assign it to himself. The work item gives reviewers a shared place to follow the proposal as they come online.

Engineering can assess showing the preview for every upload, while Design explores showing it when users map custom fields. With Thread Sync enabled on the work item, replies in the Slack thread and comments in Plane stay synchronized. Contributors can review the discussion and respond during their own working hours.

On self-hosted Plane Commercial Edition with Enterprise Grid, Microsoft Teams supports linked conversations too: replies in a thread become work item comments, and activity on the work item is posted back to the thread.

Record review outcomes in Pages

The product manager keeps the proposed import-preview behavior and its trade-offs in a Page rather than relying on the chat thread. Design can leave inline comments on specific requirements, while broader questions about scope stay in page-level discussions. Once the reviewers agree, the product manager records the selected behavior and rationale in the Page, then updates the linked work item with the approved acceptance criteria.

Keep delivery progress visible across time zones

A billing dashboard rollout involves contributions from several Engineering teams. A delivery lead in London needs to see what's reached review, what's with QA, and which work items the next regional team will take on.

Follow release work with Views

The delivery lead keeps a saved workspace View named Billing dashboard rollout, bringing together work from the Web App, Platform, and QA projects. It shows the dashboard UI, reporting endpoints, QA review, billing period filters, and data aggregation work, with their states, priorities, and assignees. The next regional lead can open the same View to review progress and pick up their part of the rollout.

Keep remote teams connected with Plane

When the next region comes online, the context is already there: Cloverquay Retail's request, the export review notes, and the agreed onboarding behavior. Contributors can see what's been decided, what has progressed, and where to pick up the work.

Get started with Plane to bring your remote team's requests, decisions, and delivery work into one workspace.