Getting started

Creating a project

How Infrenta uses a governed project record as the shared context for engineering, commercial, procurement, and delivery work.

Updated 2026-08-23

A project in Infrenta is the shared record that other workspaces attach to. Creating a project is less about filling a form and more about establishing the object that estimates, layouts, procurement packages, budgets, and field records will reference.

What the project record holds

The project is designed to keep:

  • identity and portfolio context
  • files and drawing revisions
  • team access scoped to the company
  • health and open-decision signals
  • links into GeoLab, layout, estimating, procurement, controls, and execution

Exact field labels can change as the product evolves. Do not treat this page as a click-by-click UI script.

Conceptual workflow

  1. Create the project in the authenticated application so the record is company-scoped.
  2. Attach source information — drawings, geotechnical reports, BOMs, and supplier documents belong on the project, not in a side folder that only one estimator can see.
  3. Run the workspaces that apply — GeoLab and layout inform quantities and foundation assumptions; estimating consumes those quantities; procurement inherits approved scope; Project Controls and Execution consume the commercial and field picture.
  4. Revise in place — layout revisions, estimate revisions, and procurement packages should point at the same project rather than creating parallel “v3 final FINAL” files.

See Connected project record for what is issued versus automatic.

Access and tenancy

Infrenta is multi-tenant. Project data is company-scoped. Role-based permissions control which modules and records a user can see or change. A project is not a public marketing object; it lives in the authenticated application, not on the public website.

See Accounts and access.

What not to expect from this page

This documentation does not list every required field, every validation message, or every button name. Those details belong in in-app guidance. If your organization is being onboarded, Infrenta can provision sample project context during implementation.

Related