# Partner Portal decision sheet

Worked example companion. Fictional scenario; no measured results.

A partner portal works when progression, attribution, and ownership are part of the same process.

## How to use this sheet

Replace the example rules with your own. Keep each acceptance decision linked to its owner and evidence. Use the blank CSV to record your actual process; the example CSV contains teaching material.

| Situation to test | Expected behavior | Review and ownership |
| --- | --- | --- |
| Incomplete certification | Explain the prerequisite | Partner completes the required step |
| Existing opportunity | Flag an ownership review | Program owner decides attribution |
| Revoked access | Deny protected operations | Program administrator handles reinstatement |

## Workflow

1. **Learn** (Partner): Complete the required program steps.
2. **Refer** (Portal): Create a traceable referral route.
3. **Register** (Partner): Submit the opportunity with source evidence.
4. **Review ownership** (Program owner): Resolve conflicts and assign the next step.

Exception: An ownership conflict enters review. The portal does not silently award a deal based only on the latest submission.

## Measurement

Measure incomplete registrations, time to ownership decisions, and administrator follow-up per registration. These are proposed evaluation measures rather than demonstrated program results.

## Limitations

- This worked example is a proposed design, not access to a production application.
- Implementation depends on source data, access rules, and policies agreed with the responsible team.

Source page: https://www.opsautomators.com/work/partner-portal
Prepared September 16, 2026.