Live execution state tied to the property.

​

 

What This Is

Active Projects is the layer that represents work in motion.

It tracks projects that have been approved and are currently underway, tying execution status, documentation, and decisions to the property rather than to disconnected timelines or messages.

This is not a task list.
It is an execution state model.

 

Why This Exists

Once work starts, information usually fragments.

Details live in texts.
Photos live in phones.
Status lives in someone’s head.

When something goes wrong, there is no shared reference point.

Active Projects exists to keep execution visible, structured, and anchored to the home.

 

What Is Tracked

Each active project maintains a clear execution footprint.

This includes:

Approved scope and pricing
Assigned providers
Material selections and dependencies
Current status and phase
Photos and video tied to locations
Notes and exceptions as they occur

Nothing is detached from the original plan.

 

Relationship to the Property Model

Active Projects operate directly on the property’s spatial data.

Work is associated with:

Specific rooms or zones
Defined surfaces or systems
Known materials and quantities

Execution references the same structure used during planning.

 

Execution Transparency

Progress is visible without constant check ins.

Photos, updates, and documentation are captured as work occurs and attached to exact locations.

This creates verifiable records instead of narrative updates.

 

Change Management

When conditions change, the impact is contained.

Scope adjustments are compared against the approved baseline.
Material substitutions are explicit.
Exceptions are documented in place.

Change is tracked, not absorbed quietly.

 

Operational Effects

Active Projects reduces friction during execution.

Fewer status calls
Less interpretation by providers
Clear accountability when issues arise

Oversight becomes structured rather than reactive.

 

Continuity After Completion

When a project finishes, it does not disappear.

Its data rolls forward into service history, material records, and lifecycle planning.

Execution strengthens the system instead of leaving residue.