Projects and organizations

An Admin starts with the organization name, code, time zone and currency. The Project Coordinator then creates the event project with its contact name, address and eligibility note. These details give the team a stable place to attach work packages, rather than using a project name as an informal label. A package points to a Projects row through Counterparty and to the owning organization through Organization.

• Organization. Admin maintains the owning organization, its code, time zone and currency so projects have a consistent home.
• Project. Project Coordinator records the event contact, address and eligibility note under that organization.
• Package link. A package names both the organization and project; the coordinator checks that they describe the same engagement before planning tasks.

Agree who may create a new organization, how project codes are assigned and when an eligibility note calls for a human decision. Confirm which time zone governs due dates when the client and operating team work in different locations. Use the contact name as a coordination detail; it is not an approval decision or an identity record.

Before assigning work, decide who can create project codes and who resolves a disputed eligibility note. Record the time zone that the team will use when discussing due dates with a client in another location. Keep the project contact current so a worker can reach the right person about venue access without treating that contact as an approver.

Open one real event project and trace a package back to both the project and organization. Check that the contact and address belong to the intended engagement. If a coordinator selects the wrong project, correct that link before work begins so later task hours, evidence and acceptance are read in the right client context.

Give the Event Worker the package record number for a venue visit. Have the worker open its project, verify the address and contact, and trace the project to the owning organization. If the package points to another event, the Project Coordinator corrects the project link before the worker logs hours. The Operations Lead can then group package progress by the intended project instead of mixing work from two engagements.

• Project Directory — See each event project with its code, contact, address and owning organization.
• Work Packages — Check the parent scope, owner, due date and current status before deciding.

Follow Register the project for the related decision path. Review the data model when mapping existing records, and use implementation to rehearse the first event cycle.