1. Gaming Studio Project Mgmt
  2. Process
  3. Execute work
Process · Execute work

Execute work

After a package is active, Contributor records task effort and completion evidence against the current plan. Asset revisions have their own submission and review states. Keep the parent package and organization clear so creative approval applies to the version the reviewer actually saw. Build QA evidence then supports completion as a separate step.

Step by step

  1. Execute tasks Contributor

    Contributor records actual hours and completion dates on scoped tasks. Project Coordinator checks that dependencies and task revisions still agree with the package baseline.

    • Record work and completion against package scope
    • Updates Tasks, Work packages
  2. Submit asset revisions Contributor

    Contributor records the asset type, revision number, build reference, and parent package, then submits the draft asset for review.

    • Move asset from Draft to Submitted
    • Updates Asset reviews, Work packages
  3. Review asset evidence Asset Reviewer

    Asset Reviewer checks the submitted revision and creative evidence. The reviewer approves or rejects the submission independently.

    • Move submitted asset to Approved or Rejected
    • Updates Asset reviews, Record attachments
    ApprovalA person approves before the work moves on.
  4. Confirm build QA Project Coordinator

    Project Coordinator checks the build reference and QA evidence for the approved version before completing the asset review.

    • Move approved asset to Completed only with build evidence
    • Updates Asset reviews, Record attachments
Contributor
Records work and submits revisions; Project Coordinator checks task scope; Asset Reviewer decides on submitted assets; Project Coordinator confirms build QA before completion.

Set up Gaming Studio Project Mgmt your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started