These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Public Works Department
- Features
- Agencies and projects
Agencies and projects
Keep the agency, project counterparty and responsible people tied to each package.
OverviewMy Team Member Record×
Public Works Department · Agencies and projects
New
My Team Member Record
Team members
| Name | Role name | Organization | User | Active | |
|---|---|---|---|---|---|
| Member 332 | Role 939 | ORG-9252 | |||
| Member 254 | Role 845 | ORG-8307 | |||
| Member 355 | Role 717 | ORG-9689 | |||
| Member 811 | Role 199 | ORG-3192 | |||
| Member 409 | Role 665 | ORG-2802 |
6 of 6 records
Member 332Team members · TM-50843
Role nameRole 939
OrganizationORG-9252
Active✓
What you can do
Start with the responsible organization
A public works package needs a clear agency and counterparty before its owner plans tasks. The organization record carries the agency code, time zone, currency and active flag. The project record identifies the contracted counterparty, contact and address within that agency. When a manager opens a package, the organization and counterparty references keep the scope attached to the right parties.
A project name alone can be ambiguous across agencies. Agree how codes distinguish similarly named projects and which organization owns each project. An agency may work with several contracting organizations; preserve the selected relationship rather than putting a contractor name only in the package subject.
How the work is organized
- Agency identity. Admin maintains the organization code, active state, time zone and currency used for its work.
- Project context. Public Works Manager checks the project contact, address and organization before it becomes the counterparty on a package.
- People and ownership. Team members link to an organization and platform user, while the package owner links to a specific team member.
The separate team-member record matters when responsibilities move. A person’s name and role can be reviewed against the organization without changing the package’s historical counterparty. The manager can find who owned a delayed package and which project was in scope.
What to agree during setup
Set a code convention for agencies and projects, decide who may change an inactive record, and identify the team member who owns each live package. Confirm the time zone used when reading due and inspection dates. Match existing project contacts to the right agency before importing work packages; a wrong organization reference can make an otherwise complete package misleading.
If a contractor contact changes, update the project record and review open packages. Keep completed work tied to the counterparty recorded for that work. Admin and the Public Works Manager should rehearse a transfer of ownership so overdue items remain visible during staff changes.
Check the handoff on an actual case
Take a road repair project serving one agency and a named contractor. Create its project record with contact and address, assign an active team member, then open a package for the repair. Check that the package points to the intended organization and counterparty. Change the project contact and confirm that its package still shows the same project identity. Ask the manager to locate the package from the open-work list and confirm the owner.
What your team sees
- All Organizations — Agency identity and active state for work selection.
- All Projects — Contractor and project context under each agency.
- All Team Members — People available to own or review public work.
Follow the work through
Continue with package planning and the data model.
What it keeps track of
Data model- Organizations
- Public works agencies and contracting organizations
- Projects
- Public works projects and contracted counterparties
- Team members
- Staff and contractor personnel linked to an organization and platform user
- Users
- Users
- Work packages
- Baseline work packages with lifecycle, budget hours and counterparty scope
Who uses it
Permissions- Admin
- Maintains identity and access; Public Works Manager checks project scope; Package Owner confirms the correct counterparty before planning.
Set up Public Works Department your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.