DocumentationStart here
2 min readUpdated 16 August 2026

How PIWOT℗ works

A practical map of requests, active capacity, your matched designer, and delivery.

Inside PIWOT℗
PIWOT℗ request board with Backlog, Active, Needs Input, and Done columns

The request board keeps upcoming work, active work, questions, and completed delivery visible together.

Where this fits

01

Set up

02

Add context

03

Invite people

04

Send request

01

The basic workflow

  1. 01Add a request to your backlog with a clear brief, files, and a target date.
  2. 02Move the request to Active when you want work to begin and capacity is available.
  3. 03Use the request for comments, files, decisions, and review. The context stays with the work.
  4. 04Move work through Needs Input and Done as decisions are made and delivery is approved.
02

Active capacity

Your plan controls how many requests can be Active at the same time. The backlog behind those active lanes is unlimited, so you can prepare upcoming work without losing context.

More Active Requests can be added from Billing when your team needs parallel work.

03

Where the work lives

  • Briefs and requirements
  • Files, references, and links
  • Comments, mentions, and decisions
  • Status, priority, target dates, and request members
  • Billing, agreements, and workspace settings
04

Who owns each part

  • Your team owns the goal, source material, decisions, and timely feedback
  • The matched designer owns the craft work and raises questions inside the request
  • The design manager keeps priorities, scope, and context coordinated across the workspace
  • Workspace Admins own team access, settings, billing, and Active Request capacity
05

When the direction changes

Discuss the change in comments, then update the brief with the accepted direction. If the work changes service category, the current designer match can be reviewed. If the change creates a separate outcome, create another Backlog request so approval and delivery remain clear.

FAQ