BC
Brad CodyAdministrator

Company governance

Decision Queue

One company-wide register for choices that need evidence, discussion and an accountable conclusion. Each item states the actual question, a recommended starting point, what evidence closes it and the source that created it.

Open decisions31Across 9 departments
Critical P010Resolve before dependent work
Ready to discuss14Recommendation is prepared
Blocked1External evidence or advice needed
Departments9One shared company queue
01

Frame

Agree on the exact decision—not merely the surrounding topic.

02

Challenge

Review the recommendation, risks, alternatives and missing evidence.

03

Decide

Name the accountable decision-maker, decision and effective date.

04

Propagate

Update the source document, roadmap, owner and dependent work.

Clear

3 of 31 decisions shown

P0DR-015
OperationsReady to discuss

Approve Provider quality standards by category

What minimum evidence, insurance, service standards and review cadence are required for each Provider Category?

Open brief
Why this matters

The Registry promise depends on a vetted network, yet qualification cannot be one generic checklist across vendors, storage, delivery, trades and creative services.

Recommended starting point

Create a global trust baseline plus category-specific qualification, expiry and suspension rules; do not mark a Provider active until both pass.

Evidence required to close

Approved matrix for all nine categories, application mappings and re-verification cadence.

Decision owner
Provider Operations
Required timing
Before approving production Provider accounts
P1DR-016
OperationsReady to discuss

Set cross-party service levels

What response and update standards apply to Offers, quotes, receiving, damage, storage release, delivery and installation?

Open brief
Why this matters

Designers will only trust the shared system if Provider status is current and exceptions are handled predictably.

Recommended starting point

Define category-specific response targets, automatic reminders, escalation owners and visible exception states rather than one generic SLA.

Evidence required to close

Provider-reviewed SLA table and two real workflow simulations.

Decision owner
Provider Operations
Required timing
Before Provider pilots
P1DR-017
OperationsEvidence required

Define damage, claims and service-recovery ownership

Who records, investigates, communicates and financially resolves damage or failed delivery at each handoff?

Open brief
Why this matters

Receiving, storage, delivery and installation evidence crosses several independent businesses and can expose the Registry brand.

Recommended starting point

Use timestamped condition evidence and chain of custody, with one Registry case owner and contract-defined commercial responsibility by handoff.

Evidence required to close

Counsel-reviewed claims workflow, required insurance and a simulated damaged-Item case.

Decision owner
Operations + Legal + Finance
Required timing
Before physical-goods workflows go live

Closure standard

A discussion is not a decision until the source changes.

01Decision and rationale recorded02Named accountable owner03Effective date and review date04Source document updated05Roadmap or budget impact applied06Affected people notified07Evidence or assumptions attached08Superseded choice preserved