UpCodes Projects

Keep compliance work aligned as projects evolve

Organize code research, assemblies, products, and decisions in one place, and keep everything aligned as you move across jurisdictions and code years.

‍

One place for project-specific context

UpCodes Projects give structure to everything you do in UpCodes.

Each project ties together:

Jurisdiction and adopted code years
Saved code sections, diagrams, assemblies, and products
Copilot conversations and notes
Checklists and specifications as work progresses

This keeps decisions consistent-even as teams, scopes, or timelines change.

Where project work happens

From quick bookmarks to full compliance checks

Projects mirror the way work actually happens—capturing what you bookmark, how you discuss it, what you reuse, and how you verify it before submission. From early research to collaboration, reuse across jurisdictions, and final checklists and calculations, Projects turn day-to-day effort into a workflow the whole team can build on.

Save context

Align teams

Reuse work

Validate decisions

Save context

Capture research as you go

As you research anywhere in UpCodes, Projects act as your anchor.‍

Bookmark code sections, diagrams, assemblies, and products
Add comments and context while decisions are fresh
Tag teammates to loop them in early

Research doesn’t live in isolation; it stays tied to the project that needs it.

‍

1/4

Align teams

Collaborate without losing context

Projects make collaboration clearer and more traceable.

See why something was saved-not just what was saved
Track discussion alongside the actual requirement or selection
Keep internal alignment across disciplines and offices

1/4

Reuse work

Reuse what already works

Projects don’t reset to zero every time.

Copy prior projects across jurisdictions or code years
Start from internal templates for common building types
Templates retain structure while updating code references to match the active jurisdiction and code year
Lock, archive, or share projects based on team needs

Past work stays relevant-even when jurisdictions or code cycles change.

1/4

Validate decisions

From research to validation

Projects are where requirements turn into confirmation.

Apply adopted requirements with local amendments considered
Generate Checklists to validate compliance
Use Code Calculators to verify quantitative requirements

Reference everything directly when drafting documentation or specs.

1/4

How it works

How Projects are structured in UpCodes

01. Set up shared workspaces

Workspace admins create team workspaces, then add the people who should be working together there. Most firms start by adding principals, project leads, and other decision-makers as editors, then layer in collaborators and viewers over time.

02. Assign roles and access

Editors control project creation and management in team workspaces. Collaborators can add bookmarks, comments, and updates inside projects, while viewers can see everything they’re invited to, but can’t change it. This keeps contribution open where it should be, and locked down where it shouldn’t.

03. Create projects in the right place

Editors can create team projects from any team workspace. Viewers and collaborators can only create projects in their personal workspace, which is ideal for early research or scratch-pad work before it’s ready to move into a shared space.

04. Collaborate with clear boundaries

Once a project exists, editors invite the right mix of collaborators and viewers so each person can work at the right level of control. The result: only a subset of users can spin up or restructure team projects, while the broader team can still contribute research, context, and review without risking accidental changes to the project framework.