Projects and organizations

Keep each work package within an active studio organization and eligible game project. The team uses project and organization codes, contact, and eligibility note to keep that context together. Use a pilot package to check the record links and each role’s handoff.

• Studio scope. Admin keeps each organization code, active state, currency, and time zone clear before project work is assigned.
• Project eligibility. The project contact and eligibility note give Project Coordinator a reason to choose a counterparty for a package.
• Membership. A team member links a user to an organization; an active member still needs the right project and package assignment to act.

Project Directory Cards gives the coordinator a starting point for eligible project work. The package then links back to its organization and project. Compare those links before baselining so work from another studio or project is not folded into the wrong delivery.

Admin and Project Coordinator should agree who maintains project codes, contacts, eligibility notes, and membership. Check that the project’s organization matches the one chosen for a new package. Set a convention for active and inactive projects and for a member on leave. Decide who corrects a mistaken project link before task work begins; changing it after review also changes what the reviewer must inspect.

Admin checks active state, currency, and time zone with the coordinator before assigning a package. If a contact or eligibility note changes, revisit the package counterparty before the team baselines tasks.

Consider a new game project entering production while an older project remains active. Admin records the new project under its studio organization and gives it a distinct code and contact. Project Coordinator chooses it as the counterparty for a new package, then checks that the package owner is a member of the same organization. A project from the older studio should fail that scope check, even if its name looks similar.

Repeat with an inactive project and with an owner whose membership is on leave. Correct the source records first, then inspect the package links again. The eligibility note explains why the project is in scope; it is not a substitute for the organization and active-state checks.

• Project Directory Cards — Find active projects by code, contact, organization, and eligibility note.
• Planned Work Packages — Check which planned packages use the project before execution begins.

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.