Questions, answered

Click Get started, then use Proto to configure Gaming Studio Project Mgmt for your business. Begin with one active organization, one project, a coordinator-owned package, its task plan, and an independent delivery review.

A Work Package holds the project, owner, budget hours, due date, revision, and lifecycle status. Tasks, asset reviews, attachments, decisions, and operation receipts connect to it.

Yes. Tasks hold planned and actual hours, due and completion dates, and dependency text. Review the task rows within their package when comparing effort with the original plan.

The asset review records a revision, asset type, build reference, and status. An Asset Reviewer checks a submitted revision and records its decision against the work package context.

Attach files to the work package with a title, evidence type, uploader, upload date, and Internal or Shared visibility. Agree the visibility policy before the team starts adding files.

An Independent Reviewer records the source revision, decision, reason, and review date. The Project Coordinator uses that decision and the package evidence when moving work toward acceptance.

The coordinator addresses the reason, updates the package or supporting evidence, and requests another review of the current revision. The earlier decision remains part of the record.

Operation Receipts record the action key, expected revision, result state, and failure reason. Operations Reviewer compares that receipt with the linked work package and effects before recording a verified result.

Yes. Projects link to Organizations, and each Work Package links to a project counterparty and an organization. Agree the access and ownership rules for each project during setup.