Access scope
Control visibility by portfolio, property, building, or roof.
Portal
Operate the portfolio, not the folder tree.
The public site explains the model. The portal is where the model runs. Baselines, event reviews, monitoring, findings, permissions, and decision outputs stay attached to the same roofs.
Portfolio view
Review queues
Decision outputs
Role-based access
The first screen should answer
- Which roofs have no baseline?
- Which event reviews are still open?
- Which findings need action this week?
- Which repairs still need closeout?
- Which buildings are due for monitoring?
Canonical object model
Portfolio
Property
Building
Roof
Baseline
Event
Artifact
Finding
Decision Pack
Action
Closeout
Representative command view
One view for status, queue, and action.
Active records
24Roofs currently managed inside the record model.Missing baselines
3Assets that still need the first fixed starting point.Open reviews
2Storm or repair comparisons waiting for review.Monitoring due
6Scheduled checkpoints due across active roofs.Action queue
Warehouse 04Storm review pending documentation package.
PendingRetail Plaza 9Repair closeout needs final upload.
In progressDistribution Center BQuarterly review due this week.
Due nowDecision outputs
Claim package ready7 roofs
Repair scope context ready4 roofs
Warranty follow-up open2 roofs
Capital review flagged5 roofs
Governance
Control is part of the product.
An enterprise record needs more than images and dashboards. It needs scope, permissions, state, and history.
Review states
Open, in review, approved, closeout pending, and monitored keep work visible.
Audit trail
Capture when artifacts, findings, and decision packs are added or changed.
Exports
Claim, repair scope, closeout, and capital packages should come from the same source.
Need to prove the model first?
Use the proof page to show the public workflow, then move live records into private walkthroughs and portal review.