Map decisions rather than software permissions
In this invented project, sponsor Kai approves scope, operations lead Mei supplies booking rules, accounts lead Jo verifies invoice rules, and delivery lead Ren estimates implementation. These names and responsibilities are synthetic.
| Decision | Supplies facts | Reviews result | Approves or escalates |
|---|---|---|---|
| Booking cancellation rule | Mei | Jo checks invoice effect | Kai approves scope impact |
| Additional export feature | Mei states task; Ren estimates | Mei reviews sample | Kai decides inclusion |
| Invoice total definition | Jo | Jo reviews worked amounts | Unresolved business rule returns to Jo |
A reviewer is not automatically an approver
Mei likes the export demo. Can Ren treat that as approval to add the feature?
Show the worked answer
No. Mei reviews the result, while Kai decides inclusion. Record Mei’s feedback and ask Kai for the scope decision using Ren’s estimate.
This sheet assigns project decisions; it does not grant application access. Keep the existing role-permission matrix for account capabilities, and use the authority actually agreed for your project.