Asset revisions

Keep creative review and build references attached to each asset revision. The team uses asset type, revision number, build reference, and review date to keep that context together. Use a pilot package to check the record links and each role’s handoff.

• Submission. Contributor ties an asset revision to a package and organization and records its type, revision number, and build reference.
• Creative decision. Asset Reviewer inspects the submitted revision and its creative evidence before approving or rejecting it.
• Build check. The build reference identifies the version whose QA evidence must be checked before the asset is complete.

Pending Asset Reviews is the working queue for submitted assets. A rejected revision stays distinguishable from an approved one. A later submission needs its own current revision and evidence so an earlier approval is not mistaken for approval of new work.

Agree how the asset type and build reference identify the artifact the reviewer actually saw. Define which attachments count as creative evidence and which demonstrate build QA. Keep the asset’s organization aligned with its parent package. Asset Reviewer should be independent of the person preparing the revision. Choose how a rejected asset returns to Contributor and how a fresh submission is distinguished from the rejected one.

Asset Reviewer decides on creative evidence for the submitted version. Project Coordinator then checks build QA evidence and its reference before the approved asset becomes complete. A rejected submission returns to Contributor for a new revision; the earlier outcome remains visible.

Consider a character model submitted again after creative review rejects the first version. Contributor opens the parent package, records the new asset revision and build reference, and attaches the creative and build evidence under that package. Asset Reviewer inspects the submitted version and either approves or rejects it. The review date and status show the outcome; the package context gives the team the supporting files.

Repeat with an old package revision or a build reference that identifies a different artifact. The action should remain with the coordinator or contributor for correction. Do not treat a creative approval alone as a completed asset: the build check and current evidence also matter before the package proceeds.

• Pending Asset Reviews — Find submitted assets by parent package, type, revision, and build reference.
• Evidence Register — Inspect the attachments associated with the parent package.

Follow planning, execution, and delivery review for the handoffs that connect these records. The data model shows the exact references to migrate and verify. Set up a pilot through implementation before broadening the team.