Skip to content
New4D planning and Line of Balance are live

All of project controls. One platform.

Schedule, estimate, cost, resources and risk in one application, on one live project model. Change the plan and every number that depends on it moves.

  • Primavera XER in and out
  • What-if scenarios in seconds
  • AACE Class 5 → 1 estimates
  • Monte Carlo P10 · P50 · P80
  • DCMA 14-point
  • 4 forensic delay methods
  • 4D on the live schedule
  • AI drafts, you approve

Built for capital projects

  • 24

    modules in one application, every one in every plan

  • 14

    DCMA checks on the live model, failing activities listed

  • 4

    forensic delay methods, AACE-recognised, over your own updates

  • 5 → 1

    AACE estimate classes, versioned, with markup build-up

  • P80

    Monte Carlo over three-point durations: P10, P50, P80

  • 3

    exchange formats: XER, MSPDI and Excel, in and out

Built in-house

Activity CPM view

Our scheduling engine and Activity CPM interface are built from the ground up for connected project controls. Logic, calendars and constraints drive one live plan.

Everything on this page is in the product today. Bring your own schedule to a live demo and watch it run.

One umbrella

Everything that used to be five tools. One model.

The schedule, the estimate, the budget, the resource pool, the risk register, the DCMA score, the delay analysis, the 4D model and the monthly report all read and write the same project. Change a duration and every number that depends on it moves. No export, no re-key, no second licence.

Built for every seat at the table

Whatever your role, the whole platform is yours.

Planners, project managers, controls specialists, PMO managers, directors, engineering companies, consultants and owners work from the same model, and every seat includes every module. Pick your role.

Planners & schedulers

Build a schedule you can defend. Share it with your clients in XER.

Critical-path scheduling, efficient activity editing and schedule analysis in one workspace, so you can update the plan and check its consequences together.

  • Forward and backward pass with total and free float, calendars with per-day hours and holidays, eight constraint types, level-of-effort activities and inclusive end dates.
  • Edit activities with field-level undo and redo, fill down, and copy and paste to keep routine schedule changes quick.
  • XER in with constraints, calendars and the data date intact. The export is reconstructed from the verbatim source file, so the client recognises what comes back.
  • Run the DCMA 14-point assessment and trace float paths on the schedule you have open, before anyone else runs them on it.
  • Scenario mode: test a what-if against the plan in seconds, save it, or make it a project. Let the AI builder draft the first pass of WBS, logic, resources and risks for you to approve.

Review logic, run quality checks and exchange XER files from one workspace.

The tour

Nine stops. One application.

Scroll the whole platform, or jump to the part you came for.

01 · Schedule

A CPM engine, not a bar chart.

Forward and backward pass, total and free float, negative float where it belongs, on a Gantt that stays smooth at thousands of activities.

  • All four relationship types with leads and lags, and eight constraint types that hold their dates and warn when violated instead of moving silently.
  • Work calendars, global and per project, with per-day hours and holidays. Imported XER durations convert on each activity’s own calendar, so a 12-hour shift never inflates a duration.
  • Actuals drive the plan: record an actual start or finish and the dates, progress and status follow. Durations include the final working day.
  • Duration from production rate, quantity divided by crew output, calendar-aware. Line of Balance charts those quantities over time for repetitive work.
  • Keyboard editing with undo, redo and fill down, float-path tracing, saved and restorable baselines, and a scenario mode that reschedules against the live engine without touching the live project.
NetworkIllustrative
Activity-on-node, four layouts. Critical path in red, total and free float on every card.

02 · Scenarios

Ask what if. See the impact in seconds. Keep it as a project.

Switch the Gantt into scenario mode and change durations, logic and dates freely. The plan stays underneath as ghost bars, every number reschedules live against the real engine as you type, and nothing is written over the live project until you say so.

  • A late delivery, a re-sequence, a crash, a longer shutdown: change it and watch the critical path, the float and the finish date recompute against the baseline you choose.
  • Save it as a scenario, or turn it into a new, independently schedulable project in one click. The original stays untouched.
  • Critical-path crash and Monte Carlo hand their results into the same sandbox, so a recovery plan or a risk-adjusted plan is one more scenario rather than a spreadsheet.
  • Open the scenario project beside the live one and compare the two in one Gantt. Ctrl+Z reverses the whole experiment.
Activities · Scenario modeIllustrative
Ghost bars are the plan, solid bars are the scenario. The finish, the driving path and the cost move as you type.

03 · Cost & estimating

The estimate becomes the budget. Once.

Versioned estimates from AACE Class 5 to Class 1, with a markup build-up, that push their line items straight into cost assignments. Idempotently, so pushing twice never doubles the budget.

  • Unit rates composed from resource components, so a rate is a build-up you can defend rather than a number someone typed.
  • Earned value, CPI and SPI on the same model as the schedule, read at the status date you choose.
  • One assignment solver: edit units, hours, rate or cost and the other three re-derive from whichever one you touched.
  • Capacity against demand, per resource. Over-allocation is never pooled away by averaging across the pool.
  • Multi-currency with an exchange-rate matrix, and S-curves from activity dates alone, before any cost data exists.
EstimatesIllustrative
A composed unit rate, the markup build-up, and one button that makes it the budget.
S-CurvesIllustrative
Baseline, planned and actual, read at the status date. CPI and SPI beside them.
Resource AssignmentsIllustrative
Capacity against demand, week by week. Over-allocation shown on the resource that carries it.

04 · Risk

Threats, opportunities, and a P80 you can defend.

A register that treats opportunities with the same rigour as threats, each on its own matrix, linked both ways to the activities they affect. Monte Carlo runs on the schedule you have open.

  • Probability and impact matrices for threats and for opportunities, with type-specific response strategies, owners, actions and residual scores.
  • Monte Carlo over three-point durations and per-activity probability: P10, P50 and P80 marked against the deterministic finish.
  • Risk scenarios feed P-level durations back into the CPM run, so you see the risk-adjusted plan rather than arguing about a percentile.
  • One Risk column on the Gantt opens the register entry, and the register points back at the activity.
Monte CarloIllustrative
Finish-date distribution with P10, P50 and P80, and the deterministic finish marked for contrast.
RisksIllustrative
Threats and opportunities, each on their own matrix, each linked to an activity.

05 · Forensics & schedule quality

The analysis that usually costs a second licence.

DCMA, forensic delay and critical-path crash, run against the model you have open. No bolt-on, no round trip, no claims consultant on retainer to find out what slipped.

DCMA ChecksIllustrative
Fourteen checks. Expand any one to the activities that failed it.
Delay DiggerIllustrative
Four updates compared. Slippage and its strongest root causes, attributed period by period.
CP CrashIllustrative
The crash cost curve, with the day the critical path changes over marked.
  • DCMA 14-point, on the live schedule

    All fourteen checks, run against the model you have open rather than an export of it. Expand any failing check to the activities behind it, and compare one revision against another.

  • Forensic delay analysis

    Four AACE-recognised methods — as-planned vs as-built, impacted as-planned, time impact analysis, collapsed as-built — over your own saved updates, backed by a standing delay-events register.

  • Critical-path crash

    Rank the secondary and tertiary float paths, build the crash cost curve, and find the day the critical path changes over as you compress. Then run Monte Carlo over the compression plan.

06 · 4D planning

Link the model to the schedule. Watch it get built.

Connect the IFC model to time. Link elements to activities, scrub the timeline, and review the build sequence as the programme changes.

  • IFC model elements linked directly to schedule activities. No separate 4D tool with its own copy of the programme to keep in sync.
  • Scrub the timeline and watch elements appear, stay in progress, or complete as their linked activities move.
  • Move an activity and the sequence it drives moves with it, because the link is to the live schedule, not a snapshot exported into a viewer.
  • A second colour mode shows how far each element has slipped against the saved baseline, directly on the building. Play the sequence back and export it as a video.
4D PlanningIllustrative
The model, driven by the live schedule. Built, in progress and not started, at the playhead.

07 · Reports

The monthly report writes itself from the model.

A block document whose tables and charts are bound to the schedule, cost and risk modules and re-read live at the report’s status date. Issue it and the numbers freeze as a numbered revision.

  • Data blocks bound to the modules — a progress table, an S-curve, a risk matrix, a lookahead — pull live figures at the report’s status date rather than being pasted in once.
  • Issuing a report freezes it as a numbered revision, so last month’s report still reads last month’s numbers after the schedule has moved on.
  • Monthly and executive formats come from the same model, so the board pack and the site team’s report never disagree.
ReportsIllustrative
Blocks bound to the modules, frozen as a numbered revision when you issue it.

08 · Data exchange

Primavera XER and Microsoft Project, in and out.

Import the schedules you already have, work on them here, and hand back a file your client’s P6 opens. Bulk edits round-trip through Excel.

  • The import carries what usually gets lost

    Activities, relationships with leads and lags, the WBS, constraints, calendars including 12-hour shift and holiday calendars, and the data date. Durations convert on each activity’s own calendar rather than an assumed 8-hour day.

  • The export is your file, updated

    The XER you imported stays on the project record. The export is reconstructed from it with your changes applied, so what your client opens in P6 is recognisably the file they sent you.

  • Bulk edits in Excel, safely

    Export the activities, edit a thousand rows in a spreadsheet and bring them back. The whole file is validated before anything is applied, and your export templates are kept for next month.

The retained-source round trip is the P6 XER path. Microsoft Project MSPDI reads a schedule in fully, constraints and calendars included; the export writes dates, progress and logic back, not constraints.

09 · AI assistant

AI that drafts the plan. You approve it.

Describe the scope and choose the level of detail. The assistant drafts the WBS, the activities, the logic and the durations, staffs and prices the plan from your library, and lists the risks against the activities they threaten. AI Check then reviews whichever module you are in against the whole project. Nothing is written until you approve it.

  • WBS, activities, relationships and durations, including durations from production rates, at the level of detail you choose. Big programmes build in stages, a branch at a time.
  • Resources and roles assigned to activities with units, so work and cost derive from the schedule. Cost types and cost assignments priced from your library.
  • Risks drafted and linked to the activities they threaten. AI Check then reviews the register for gaps in coverage, weak responses and missing owners.
  • Logic verification on demand: open ends, leads and lags, constraints and unusual float, beside the DCMA findings. Then the deterministic CPM engine does the scheduling.
AI Assistant · BuildIllustrative
One scope statement in, one staged proposal out: WBS, activities, logic, resources, assignments, costs and risks.
AI CheckIllustrative
Review as well as build: proposals staged row by row, with the before and after on each one.

What you should know

  • Runs on Anthropic’s Claude models, on an API key you or your organisation supply. With no key entered, the assistant does nothing.
  • Your key is encrypted, resolved only on the server, and never sent back to your browser.
  • Using it sends project data to the AI provider. If that is not acceptable on your project, do not use the module.
  • An administrator can hide the module role by role, so an organisation can switch it off entirely.

Why GETSEVEN

Six reasons teams move the whole discipline onto it.

Not a scheduling tool with extras bolted on, and not a task tracker that grew a Gantt. A project controls platform, built as one thing from the start.

  • One model, every discipline

    There is no export step between the schedule and the DCMA score, the estimate and the budget, the register and the activity. There is no second database.

  • Every module in every plan

    Risk analysis, DCMA, forensic delay, crash, 4D and AI are not add-ons or tiers. A Solo seat has the same modules as an Enterprise seat.

  • Project data that travels with you

    Import XER files with constraints, calendars and the data date. Export your changes using the retained source file to preserve the detail your project partners need. Exchange schedules through MSPDI and round-trip bulk edits through Excel.

  • What-ifs in seconds, kept as projects

    Scenario mode reschedules against the real engine as you type, with the plan underneath as ghost bars. Save it, or make it a project in one click.

  • An AI builder with a review gate

    It drafts the WBS, schedule, resources, assignments, costs and risks; you approve. Runs on Claude, on your own API key, and never writes on its own.

  • Enterprise access when you need it

    SSO through SAML or OIDC, SCIM provisioning, five roles with per-module permissions, an append-only audit log, and a database you can point at your own server.

Bring a real schedule. We will run it live, not a demo project.

Book a demo

Pricing

Every module. Every plan. Per named seat.

Risk analysis, DCMA, forensic delay, 4D and AI are included at every tier. Billed annually; the tier changes who can share what, never which modules you get.

  • Solo

    $175per user / month

    One planner or consultant. Every module.

  • Most popular

    Team

    $165per user / month

    Shared library, roles and permissions. Every module.

  • Enterprise

    from $249per user / month

    SSO, SCIM, audit log, your own database server. Every module.

Questions

The things people ask first.

Planners and schedulers, project managers, project controls specialists, PMO managers, project directors, engineering companies and EPC contractors, consultants and claims analysts, and project owners. Every seat includes every module, so the planner and the director are looking at the same model. The "Built for every seat" section on this page walks through each role.
45 minutes · no slides

Bring your worst schedule.

An XER goes in, the full DCMA assessment runs against your real schedule, and every connected module responds. Not a demo file.