Creator review

A review decision records the decision value, reviewer, decision date, source revision and reason. It links to an opportunity and can also link to a creator attribution. The independent flag records whether the decision was made separately; the team must check the reviewer against the submission owner. This gives an Attribution Reviewer a place to record the reason for approving, rejecting or returning a submission. The attribution record retains its own status and decision date.

The coordinator marks a draft attribution Submitted. The reviewer opens the submitted record, checks its order reference and supporting attachment, then records the decision. Approve and Reject are decision values; Return is available when the submission needs work. The reviewer should compare the source revision on the decision with the attribution revision so a later edit is not mistaken for an earlier approval.

• Named owner. Attribution Reviewer decides and records the reason. Creator Coordinator prepares evidence and corrects returned work. Admin assigns access.
• Linked record. Keep the work tied to its parent opportunity and organization so a later reviewer can follow the case.
• Decision trail. Keep the reviewer, date, source revision and reason together so a changed count gets a fresh decision.

Agree who can review attributions, what independence means for your organization and what evidence is enough for a decision. Require the reviewer to compare the order reference with the attachment before recording a decision. Decide who checks that the decision points to the current revision and who updates the attribution status afterwards. Decide whether a returned item goes back to Draft or is corrected under a new revision. Set the rule for recording a reason. Rehearse the reviewer seeing only the records assigned to the organization they serve.

A coordinator submits an attribution with a creator name, quantity and order reference. The reviewer sees that the attached source does not match the quantity. They record Reject and explain the discrepancy. The coordinator corrects the quantity and revision, attaches the updated source, and resubmits. The next decision names the later revision and reviewer. An old approval should never be applied silently to the changed count. The reviewer checks the parent opportunity again before deciding, since a familiar creator may have worked on another drop for the same partner.

• Attribution review queue — Submitted creator records waiting for a reviewer.
• Reviewed attributions — Decided records with the status and decision date visible.

• Attribution to review: Follow the related decision and record changes.
• Review the data model: Check references before importing records.