Connected project record

Marketing copy says Infrenta keeps one project record from estimate to field. This page states what that means in the product.

Infrenta aims to preserve identity and context across supported workflows so teams are not maintaining parallel copies of the same quantity, assumption, or cost.

Identities that should stay stable

When they are recorded, these objects keep a project-scoped identity:

• project identity — the root record other workspaces attach to
• source quantities — layout counts, takeoff values, or entered quantities
• assumptions — including foundation or attachment assumptions used commercially
• revision identifiers — estimate revisions, layout revisions, issued packages
• estimate lines — addressable cost items, not anonymous spreadsheet rows
• procurement references — RFQ and quote identities tied to a package
• commitments — selected supplier values Project Controls can see
• forecast states — expected final cost against the issued structure
• execution quantities — installed amounts that can be compared to the plan

If an identity is not issued, downstream workspaces should not treat a draft as the baseline.

Where context is carried

Some context is available because records share the project:

• project name, company scope, and files attached to the project
• links from a project into the five workflows
• permissioned access inherited from company membership

That is shared structure, not a guarantee that every field is copied into every workspace.

Where users issue, review, or select

These handoffs are intentional:

• a layout revision is selected or re-compiled into estimating quantities
• a GeoLab foundation assumption is accepted as a commercial assumption
• an estimate revision is approved before procurement uses it as a package baseline
• a quote is selected and becomes a commitment
• a budget inherits an issued commercial structure
• field quantities are entered against the current project context

Users review and select. The product does not silently rewrite an approved revision when someone edits a draft.

Where a workflow stores its own revision

Estimating revisions, layout revisions, and procurement packages each have their own history. Project Controls records budget revisions. Execution records dated field reports.

A revision in one workflow does not automatically create a matching revision in another. Teams name the issued revision that other groups should use.

What is not automatic

Do not assume:

• every layout edit updates the live estimate
• every GeoLab score becomes an estimate line
• every supplier email becomes a commitment
• every daily report updates forecast
• every workflow is synchronized in real time

Incomplete inputs stay incomplete. Infrenta does not invent missing geotechnical facts, supplier quotes, or installed quantities.

Practical rule

Treat the issued record as the one other teams may inherit. Drafts are for the team still working. If procurement is buying Rev 06 while estimating is editing an unnamed draft, the project is already split — even though both sit on the same project identity.

Related

• Creating a project
• Estimate revisions
• Procurement overview
• Project Controls overview