Blockers and capacity collisions

Pro Navigator and Squad feature. A blocker in OrgBearings is not a ticket — it exists to answer one question: who do I need to unblock this, and will they be there?

Projects and blockers

Create projects with a status (planning, active, blocked, at_risk, completed) and a deadline, then link the people working on them. Each blocker carries:

• Title, severity (low to critical) and status (open, in_progress, resolved)
• A deadline — or it inherits the project's
• Resolvers — the named people who hold the keys: the approver, the SME, the vendor contact
• Resolution notes — how it was fixed, kept for next time

The capacity collision warning

This is the feature no org chart, ticket system or spreadsheet gives you. If a blocker's deadline lands on a day a resolver is on leave, at an external event or off-shift, OrgBearings flags it before it bites:

Capacity collision: Sarah is unavailable on the deadline. Contact delegate: Marcus.

The warning considers the effective deadline — the blocker's own date, else the project's — and it checks the delegate's status too, so it never points you at someone who is also away.

Why it matters

Most deadline slips are not engineering problems; they are "the one person who could approve it was on holiday" problems. A rose badge in March beats a missed deadline in May.