Project context

App Administrator maintains the organization and project records that give a work package its operating context. An organization has a name, code, active flag, time zone and currency. A project has its own name, code, active flag, contact, address and eligibility note, and belongs to an organization. These details let the Project Coordinator pick the right project when opening a work package. The project address also helps the team distinguish sites with similar names.

A practical setup starts with one organization and one active project. Confirm the organization’s time zone and currency with the people who will review dates and certified values. Check the project contact and site address with the delivery lead. If the organization manages several sites, give each project a distinct code so the package’s parent project is clear in daily review.

• Organization. App Administrator maintains the organization that owns projects, people and work packages.
• Project. Each project records the client site and its contact, address and eligibility note.
• Membership. team members connects a named staff member to an organization and a platform user, with an active flag and role name.

Agree which organization owns each project and which people should be active team members. The App Administrator should check that the team member’s organization agrees with the organization on the package they will own. Establish a naming rule for project codes before importing site work. The eligibility note should be a useful operational cue for the Project Coordinator selecting a project; it should be maintained when the project’s working conditions change.

The project context is part of every package review. A certificate points to an organization and to a package, and that package points to a project. Reviewers should compare those relationships when reading a certificate. An organization setting alone cannot tell the reviewer whether a certificate relates to the intended site; the package and its project complete that context.

Suppose a coordinator starts a work package for a school renovation. The App Administrator first creates the organization’s record and a project with the correct site address and contact. The coordinator then chooses that project as the package’s counterparty and assigns an active team member from the same organization as owner. The Project Reviewer opens the package before looking at a certificate and can see which site, organization and named owner stand behind it.

If a second renovation has a similar name, the project code and address distinguish the records. Correct the project selection before carrying task hours and certificate values forward. Once a package has review decisions and attachments, a change of project context deserves the same care as a change in scope.

• Active Work Packages — Packages with their project, owner and due date for day-to-day checks.
• Submitted Certificates — Certificates whose package and organization context needs review.

Continue with project setup and package delivery.