Organizations and projects

A delivery lead creates the organization with its name, code, active state, time zone and currency. A project then records its contact, address and eligibility note under that organization. This relationship gives every work package an unambiguous client and project context. The lead checks that the project belongs to the organization selected on the package. A familiar project name alone is not enough to establish that link.

• Organization identity. Agree on codes and time zones before staff and project records are imported.
• Project ownership. Name the contact who can answer questions about scope and delivery location.
• Assignment boundary. Keep staff, project and package under the intended organization.

Decide which organization codes identify the client and delivery teams. Check the project contact and address with the people who will use them. Agree how an inactive project is handled before a coordinator assigns new work. Add team members with their organization and user identity, then confirm that the package owner belongs to the delivery context.

A delivery lead opens a client project with a known contact and an eligibility note. A coordinator prepares a work package for that project and chooses the same organization. Before planning tasks, the lead checks the project link and owner. If a similar project exists under another organization, the coordinator uses the correct record instead of relying on a matching name. The project remains a durable parent for later package reporting.

Before the first package is opened, walk the organization and project list with the people responsible for delivery. Confirm which code identifies the client, which contact receives questions, and which team member will own the package. Then follow the relationships from a sample project to a sample package. This makes a mistaken assignment visible while it is still easy to correct. If a client has several projects, keep each package on the specific project that will receive the work. The lead can use that relationship when comparing active and accepted packages. An accurate parent record also makes later review decisions and evidence easier to find without depending on names that may be similar.

• Active work packages — See the linked project, owner and current work status.
• My team member record — Check the signed-in person and organization before assigning a package.

Follow organizations and projects in the operating process. Review the data model when mapping project, package and evidence records.