Is the software suitable for PMPs without construction experience?

Yes. The construction-specific terminology of nomenclature, BOQ, progress acts, and schedules is learned in days — the PMBOK logic (baselines, variance, performance domains) is the same. The harder part for pure PMs is understanding country-specific construction regulations, not the system itself.

PMBOK 6, 7, or the upcoming 8th edition — which standard do you target?

The system covers all three. PMBOK 6 is process-oriented (10 Knowledge Areas, 49 processes in 5 Groups) — modules map directly. PMBOK 7 is a paradigm shift — from processes to 12 principles and 8 Performance Domains (stakeholders, team, development approach, planning, project work, delivery, measurement, uncertainty). Coverage is through real workflows, not just documentation. PMBOK 8 is upcoming — per PMI the focus is on adaptability and hybrid methods, which are already present in the workflow (change orders, iterative progress acts, parallel schedule types). Our architecture is built around the project lifecycle, not around a specific edition — transitioning to a new version requires no restructuring.

Is there integration with MS Project or Primavera P6?

Not directly. Schedules in Construction Hub have their own dependency engine with ES/EF/LS/LF and critical path. Excel and PDF export are available for exchange with external planners. Two-way .mpp / .xer integration is not a priority — most PMOs use it less than they expect.

How close is the EVM implementation to the standard PMI EVM?

Covers PV, EV, AC, SV, CV, SPI, CPI, EAC. Three PV distribution methods: LINEAR (uniform), S_CURVE (typical for the construction lifecycle), FULL (all at the end). EV is formed from signed progress acts directly linked to BOQ items. AC — from actually paid invoices.

How often should I review EVM metrics?

Weekly for active sites, monthly as a minimum. The system computes in real time — weekly review is a matter of discipline (15 minutes on the dashboard), not a technical limitation.

Do you cover PRINCE2 or IPMA practices?

Not explicitly as separate frameworks, but most PRINCE2 concepts (Stage Gates, Business Case, Tolerance) are covered through key dates, change orders, and budget alerts. The IPMA approach to individual competence is outside the scope of the software itself.

What from PMBOK do you NOT automate?

A formal Risk Register with response strategies (we have risk analysis as a metric, not a documented register), the PMI Stakeholder Engagement Assessment Matrix, a Quality Management Plan as a document, a structured Lessons Learned register. These remain in separate documents.

PMP in Construction — Applying PMBOK on Site with Specialized Software

You've passed the PMP. You know the PMBOK framework — 49 processes, 10 Knowledge Areas, and 5 Process Groups in the 6th edition; 12 principles and 8 Performance Domains in the 7th. You arrive at a construction project and find: Excel for the budget, email for communication, accounting software for invoices, phone calls for status. PMBOK in Excel doesn't work. Here — what PMBOK Construction Hub actually covers, and what it doesn't.

Why standard construction software doesn't speak PMBOK

Three types of software, three different problems for the PMP holder:

Excel — no integration management. Budget in one file, schedule in another, invoices in a third. Variance analysis means copying between sheets. Change tracking — versions in file names. EVM in Excel requires separate daily work.

Accounting ERP (SAP, QuickBooks, Xero) — focused on regulatory reporting. It knows how many invoices have been received, not how much work has been done. PV, EV, and AC don't exist in its vocabulary. Project performance is outside its scope.

MS Project / Primavera P6 — schedule-only. Produces an excellent Gantt, but doesn't know what completed work actually costs. SPI it computes, CPI — not. Cost integration requires separate implementation and constant manual reconciliation.

Universal PM tools (Asana, Jira, Monday) — good for tasks and communication, but they don't understand contractual progress acts, retainage, BOQ structure, or accounting logic. A standard PMBOK approach with zero construction specificity.

Construction Hub is built around the construction project lifecycle, not around a single performance domain.

Brief comparison on key criteria

Criterion	Excel	Accounting ERP	MS Project / P6	Universal PM	Construction Hub
Real-time EVM	❌	❌	Partial	❌	✅
Linked scope / cost / schedule	❌	❌	Schedule only	❌	✅
Construction specificity (acts, BOQ, retainage)	Manual	Partial	❌	❌	✅
Document chain and audit log	❌	Partial	❌	Partial	✅
Forecast EAC from current CPI	Manual	❌	❌	❌	✅

Why Construction Hub specifically for a PMP holder

Four concrete differences that make the system useful for certified PMs:

1. EVM is built-in, not bolted on. In a typical ERP or accounting system EVM is done in a separate Excel — data is copied manually. Here Earned Value is computed from actually signed progress acts linked to BOQ items. Actual Cost — from actually paid invoices. No double entry, no monthly reconciliation.

2. Single source of truth for project data. Scope (BOQ), schedule, cost, quality (acts), procurement (contracts, tenders), and stakeholders (partners) are in one system with shared references. A change to the BOQ automatically reflects in the schedule and in EVM. This eliminates the main friction in applying PMBOK — constant reconciliation between disconnected tools.

3. Real-time data, not a month-end snapshot. Most construction systems give a report when accounting closes the period — 40-60 days delay. Here SPI and CPI are computed at the moment of inquiry. This turns EVM from a retrospective report into an early-warning system.

4. Built specifically for construction. Universal PM tools (MS Project, Asana, Jira) don't understand progress acts, retainage, BOQ hierarchy, proformas, or contractual dependencies between general contractor and subcontractors. Construction Hub is designed around these concepts — they are not a configuration, they are the data structure itself.

The result: PMBOK discipline works in practice, not just on paper.

The 10 Knowledge Areas → modules in Construction Hub

Knowledge Area	Concrete coverage in Construction Hub
Integration Management	Document chain offer → contract → progress act → invoice → payment; audit log for every change
Scope Management	BOQ with hierarchy of groups and subgroups, change orders with traceability to the original, baseline versions
Schedule Management	Schedules with dependency engine (FS, SS, FF, SF), automatic date propagation on shifts, schedules derived from BOQ, contract, or offer
Cost Management	Real-time plan vs actual budget, full EVM, burn rate analysis, configurable budget overrun alerts
Quality Management	Acceptance progress acts, completed work certificates, inventory revisions
Resource Management	Users, departments, warehouse stocks, serial numbers for scarce items
Communications Management	Share links for offers, contracts, and documents (no login required for the recipient), in-app notifications and email alerts
Risk Management	Per-site risk analysis, overdue tracking, burn-rate alerts, per-counterparty limits
Procurement Management	Tender procedures with competing bids, subcontractor contracts, AI matching of bids to BOQ items
Stakeholder Management	Partners with roles (client / investor / subcontractor / supplier), specialties, share links for external parties

All ten areas have real implementation. Not a single row in the table is a future development.

Earned Value Management — full implementation

EVM is PMI's gold standard for objectively measuring project performance. Most PMP holders know it theoretically; few apply it in practice — it requires real-time data that manual collection doesn't provide.

In Construction Hub EVM is a built-in function in budget analysis — no separate Excels, no manual data gathering:

PV — Planned Value — the value of planned work as of a given date. Three distribution methods:

LINEAR — uniform across project duration (useful for maintenance, repetitive operations)
S_CURVE — the standard distribution for a construction lifecycle (slow start, mid-project acceleration, slowdown towards the end)
FULL — full value at the end date (for fixed deliveries)

EV — Earned Value — the value of work actually completed. Computed from signed progress acts linked directly to BOQ items. Not an estimate — a real value.

AC — Actual Cost — actually paid invoices for the site. From the payments module, not an approximation.

Derived metrics:

SV (Schedule Variance) = EV − PV — are we ahead of schedule?
CV (Cost Variance) = EV − AC — are we within budget?
SPI = EV / PV — schedule performance index (1.0 = on plan; <1 = behind)
CPI = EV / AC — cost performance index (1.0 = on plan; <1 = over)
EAC (Estimate at Completion) = BAC / CPI — forecast of the final budget at the current trend

A weekly review of the EVM dashboard takes 15 minutes. It gives a more accurate picture of project health than monthly Excel reports.

The 5 Process Groups → workflow in Construction Hub

Process Group	PMI Processes (examples)	Implementation in the system
Initiating	Develop Project Charter, Identify Stakeholders	Create site with initial budget framework, define investor / client / general contractor roles, subcontractor specialties
Planning	Create WBS, Define Activities, Estimate Costs, Plan Procurement, Develop Schedule	BOQ as WBS (groups → subgroups → items), schedule with dependencies and critical path, unit prices from price lists, subcontractor contracts, tender procedures for new procurements
Executing	Direct Work, Manage Communications, Conduct Procurements, Manage Stakeholder Engagement	Progress acts for work performed, invoices and proformas to subcontractors, payments (incl. retainage), share links to stakeholders, warehouse movements
Monitoring & Controlling	Monitor & Control Work, Perform Integrated Change Control, Control Costs, Control Schedule, Control Quality, Monitor Risks	Real-time dashboard, full EVM (PV, EV, AC, SPI, CPI, EAC), change orders with approval and financial impact, document chain for traceability, audit log, per-site risk analysis
Closing	Close Project or Phase, Close Procurements	Final progress act, retainage release on schedule, archived document chain, contract performance analysis for lessons learned

The workflow is linear by nature, but change orders and phases allow iteration without breaking the baseline. This matches the hybrid approach that PMBOK 7 establishes as primary — plan-based and adaptive elements in a single project.

What PMP practices add on top

The system covers the mechanics. PM discipline determines the result. Specifically for PMP holders on a construction project:

1. Establish and lock the BOQ baseline — the first signed version is the baseline. After that, every change goes through the change orders module with approval. Without this discipline, variance analysis loses meaning — you're comparing against a moving target.

2. Weekly EVM review cadence — look at SPI and CPI once a week, not at month-end. EVM is an early-warning system, not a quarterly report.

3. Partner roles as input for RACI — the partners module has roles client / investor / subcontractor / supplier. Maintain a separate RACI matrix in the project document — the system gives the roles, not the matrix itself.

4. Change orders as scope creep control — every allegedly "small" additional item goes through a change order with financial impact. This stops the practice of "we'll catch up later".

5. Audit log as a source for lessons learned — at project end, review the audit log for the site. Which change orders were a recurring pattern? Which overdue alerts were ignored? This is the basis for a documented Lessons Learned register.

What the system does NOT have — honestly

PMI standards include elements that Construction Hub does not formally cover or covers only partially:

Risk Register with response strategies — we have risk analysis as a performance metric (probability of overrun, supplier exposure), not a documented register on the probability × impact × response scheme.
PMI Stakeholder Engagement Assessment Matrix — we have partners with roles and specialties, not an engagement plan with the unaware / resistant / neutral / supportive / leading gradation.
Quality Management Plan as a document — we have acceptance acts and certificates (the mechanics of quality control), not QMP documentation per PMI template.
Structured Lessons Learned register — there is an audit log as raw source, not a separate interactive lessons learned asset.
Two-way integration with MS Project / Primavera P6 — Excel/PDF export only.
Integration with PMI Talent Triangle development tracking — out of scope.

These elements remain in separate documents. For most practical projects this is not a blocker — formal Risk Register documentation takes more time than it adds value on a medium-sized construction site. For very large projects with an investor committee — supplement with standard PMI templates.

What changes for a PMP on a construction project

The typical weekly rhythm of a PM without specialized software: maintaining a budget Excel, manually consolidating the schedule, gathering status data from sites, preparing a report for the investor. By observation, the hours for such "data synchronization" usually take a significant portion of the week — without management value, just mechanical work.

With a system in which EVM, scope baseline, schedule dependencies, and actual costs are in one place, these tasks reduce to:

Weekly management report — review of a ready dashboard, PDF export
Status meeting preparation — charts are already current, focus is on interpretation
Change order approval — the system computes cumulative impact on budget and schedule
Investor report — share link, one click, no separate presentation preparation

The freed time goes to the real PM work: stakeholder management, risk anticipation, team coaching. What you are certified for.

A concrete first step

The standard advice "register and try it" doesn't work for PMP holders — a concrete validating experiment is needed.

Recommended first week:

Import the BOQ of one active site (Excel import or manual)
Link a signed contract and one or two existing progress acts
Activate EVM analysis for the site
Compare SPI and CPI data with the last monthly Excel report you prepared manually

The result can be one of three things:

The numbers match → the system saves you the time for the monthly report
The numbers differ → your current manual calculation misses data (the more likely scenario)
The numbers surprise you → you have a real indicator of project health you haven't seen before

Register free — 14 days without a credit card. For corporate clients with more than 5 parallel projects we recommend a pilot deployment on 1 project (4-6 weeks) before rollout. Contact us for personalized PMO onboarding.