Gate decisions and change requests, decided on the record.

Put each gate and each change request through the same steps: the evidence against the gate criteria, the options, the challenges and the steering committee’s approval, so the project’s history explains itself.

How it fits

Gate submission

Frame the gate as a decision: where the project stands, what is being asked and the options, including stopping.

Gate criteria

Record the evidence against each of your framework’s gate criteria.

Gate review

The PMO, finance and AI challenge the evidence, the plan and the risks before steering meets.

Gate decision

Steering members approve go, go with conditions, hold or stop, with the conditions on record.

Lessons learned

Gate decisions and change requests stay together, so closure reviews start from what was decided and why.

Questions

Can we use our own gate criteria?

Yes. Gate criteria are criteria on the decision; write the ones your framework uses.

Who signs off a gate?

The steering members you name as approvers. When every approver has approved, the decision closes.

How are change requests handled?

Each change request is a decision of its own, with the baseline it changes, the options and the approvals.

Does it replace our project tool?

No. Plans, tasks and timelines stay in your project tool; prorso holds the decisions that change them.

Explore example decisions · Read articles

prorso for other teams: Procurement · Software architecture · Product management · Finance & investment · People & HR · Operations & supply chain · IT, security & risk · Strategy & governance