Newforma vs Aconex 2026: Document Control Compared

Choose the record you need to control

Choose Newforma when your main problem is organizing your firm's project information across email, files, and connected applications. Choose Oracle Aconex when the project needs controlled document exchanges and correspondence across independent organizations. The deciding question is where the authoritative record should sit and who controls access to it.

Project information management is the organized capture, retrieval, and control of the files, communications, and decisions needed to deliver a construction project.

TL;DR: Newforma deserves the shortlist for firm-centered information management; Aconex deserves it for project-centered contractual collaboration. They overlap in document control and administration, but a feature match does not establish equivalent governance. If an owner already mandates a project environment, evaluate how your internal information system will connect to it before considering replacement.

The names also need clarification. Newforma is a company with distinct products, including Project Center and Konekt; a proposal labeled only “Newforma” is incomplete. Ethos Capital acquired Newforma in April 2023, according to Ethos Capital. Its current company page still identifies it as an Ethos portfolio company. Aconex remains an Oracle product. Neither comparison candidate should be treated as discontinued merely because ownership changed.

Key Takeaways

• Choose around information ownership first: organizing your firm's existing record and governing exchanges between project parties are different procurement jobs.

• Require the Newforma proposal to identify Project Center or Konekt, the selected edition or packages, and the connectors actually included.

• Favor Aconex when controlled cross-organization collaboration is central, subject to the project's requirements and participant acceptance.

• Treat both core subscriptions as Quote-based; compare migration, administration, integrations, and closeout alongside the license proposal.

• Keep formal approvals in the authoritative project system. Any surrounding automation should produce reviewable exceptions and preserve references to source records.

Who this is for

This guide is for a project information manager, design practice administrator, contractor document controller, or owner-side information lead making a purchasing decision. It is especially useful when information is fragmented internally while the project also requires formal external exchanges.

Red flags: the owner mandates a different environment that your shortlist cannot satisfy; nobody has authority to define the project record and approval process; required API or export access has not been confirmed.

A required environment is a constraint, not a preference that a comparison score can override. Similarly, neither system will repair disputed responsibilities on its own. Decide who registers documents, who reviews them, who authorizes issue, and who owns closeout before asking software to implement those decisions.

How we evaluated the buying decision

This is a public-information buyer's guide, not a hands-on product test. Official product and package pages establish advertised scope; help documentation establishes specific technical behavior; independent sources provide context. The recommendations below are our analysis of those sources, rather than vendor claims or a performance ranking.

The following weights are an editorial starting point, not researched market statistics. They total 100%. Adjust them before evaluating proposals, and attach a concrete acceptance task to every criterion. Mandatory contractual or access requirements remain disqualifiers regardless of the weighted result.

Do not award points merely because a feature appears in a brochure. Require the bidder to demonstrate your document numbering, a superseded revision, a restricted exchange, an overdue review, and an export. Record whether each task succeeds in the quoted configuration, needs additional scope, or remains unproven.

The relatively low commercial weighting assumes necessary governance comes first. It does not make affordability optional. A proposal outside your available budget fails procurement even if its features fit; a cheaper proposal that omits a mandatory process fails for the opposite reason.

Normalize the features before comparing proposals

Oracle describes private organizational workspaces, controlled sharing, a document register, configurable reviews, model coordination, and an unalterable audit trail; its public product page does not display a core subscription amount, according to Oracle. These are advertised capabilities, not evidence that your configuration or integration has been accepted.

The matrix separates product scope from buyer interpretation. “Confirm” means the proposal or acceptance exercise must resolve the detail. It does not mean the capability is absent.

The meaningful distinction is the operating model. An internal record can contain working conversations and material never issued externally. A shared project environment must establish what another party received and which process applied. Decide whether you need either boundary or both; do not merge them simply to reduce the application list.

Newforma: fit the product to the firm's information problem

Project Center is Newforma's on-premise PIM offering. Project Center editions: 3 according to Newforma. The published editions are Standard Edition, Contract Management Edition, and Enterprise Edition. Their scope progresses from information organization to contract administration and additional connectors, so the product name alone cannot establish entitlement.

Best fit: a design or engineering practice that needs staff to retrieve project email and files while retaining a firm-centered information structure. It also merits consideration where existing Newforma processes are useful and the immediate problem is an omitted connector or poorly configured handoff.

The limitation is scope ambiguity. Project Center and Konekt are separate offerings; do not assume identical functionality or interchangeable implementation requirements. An internal information hub also does not automatically satisfy an owner's prescribed external exchange process. Require explicit evidence for that boundary rather than accepting a general collaboration claim.

Implementation should begin with a representative project archive. Ask staff to retrieve a document from its number, find the associated correspondence, explain the current revision, and distinguish working material from issued records. Map security groups before indexing or migrating material. A search result that exposes restricted information is an implementation failure even when retrieval is fast.

Konekt: confirm the cloud package separately

Konekt deserves separate evaluation when cloud access and connected information are the intended purchase. Konekt listed storage: 500 GB per seat according to Newforma. Its package page lists Info Track, BIM Track, and CA Track. Treat storage as a stated allowance, not a substitute for confirming retention, connector rights, and the quoted package combination.

For a proposed US Tech Automations workflow, an authorized Newforma export or supported API read would trigger a comparison between recorded review assignments and an approved responsibility register. The workflow would normalize project identifiers, flag missing owners or inconsistent statuses, and output an internal exception queue with source references. Prerequisites include confirmed access for the selected product, an agreed schema, and permission to process the records. A document controller would review exceptions before any formal response or source-system change.

This proposed layer would address the handoff around the record. It would not replace Newforma's document control, confer access the vendor has not granted, or establish that an existing deployment supports the required operation. An export-driven design is a reasonable fallback if it preserves the necessary metadata and has an accountable refresh owner.

Aconex: evaluate the rules between project parties

Best fit: an owner, contractor, or project information team whose central requirement is controlled collaboration among separate organizations. The case strengthens when the project needs participants to maintain their information boundaries while exchanging documents through agreed processes.

The limitation is adoption and process ownership. A platform selected for a shared project cannot achieve the intended record if participants continue conducting consequential exchanges elsewhere. This is an operating risk to test, not a claim that Aconex lacks email-related functionality.

Implementation should define organizational responsibilities, document metadata, correspondence conventions, approval routes, and administrator access. Use the actual project information requirements as the acceptance baseline. Have representatives of the participating organizations perform the same exchange from their own permitted views.

Test exceptional paths as carefully as normal ones. Ask what happens when a recipient lacks access, an approver is unavailable, a revision arrives during review, or a record needs correction. The project team must understand how to preserve evidence while resolving mistakes. Broad configuration options make that design work necessary.

A proposed US Tech Automations design could run an authorized Aconex document-register query on a schedule, compare returned identifiers and revision metadata with an approved downstream register, and produce a reconciliation report for the information manager. Prerequisites are approved API access, project visibility, documented field mappings, and a supported downstream destination. The controller would review unmatched records and conflicting revisions; the design would not automatically issue contractual correspondence or approve documents.

This approach is most useful when the pain sits between applications. If the missing task is already supported inside the project's configured workflows, use that capability first. Adding another queue without a clear ownership rule can increase ambiguity about which status people should trust.

Pricing and TCO: compare identical scope

Pricing checked October 10, 2026.

The public Newforma product/package pages and Oracle's Aconex product page checked for this guide do not publish core subscription amounts. The pricing entries therefore read Quote-based. No reseller estimate, review-site starting price, or mobile-app subscription is substituted for a core platform quote.

Normalize proposals around the same information requirements and project boundaries. State which organizations participate, what records must migrate, which integrations are mandatory, and what closeout must deliver. Ask vendors to separate included work, optional scope, and work your team must perform.

Whole-life cost includes internal administration and the exit path. An apparently smaller quote can create more work if migration preparation, metadata repair, permission management, or record reconciliation falls to your staff. Conversely, a broader package adds little value if the owner requires a different exchange environment.

Require an export acceptance exercise before committing. Inspect whether the delivered material preserves document identity, revisions, relevant relationships, and understandable metadata. A folder of files may be insufficient for your agreed record, even if every file opens. Ask how access and archives behave when the subscription or project ends.

Separate documented mechanics from illustrative math

Illustrative scenario: a project information manager needs to reconcile 500 matching Aconex document-register records. The documented page_size default is 25, the example request uses 100, and the maximum is 500, according to Oracle. For this hypothetical fixed result set, the math is 500 ÷ 25 = 20 pages, 500 ÷ 100 = 5 pages, or 500 ÷ 500 = 1 page. Those are initial search-page counts, not measured runtime, total integration calls, or a customer saving. The manager would reconcile the returned count and inspect exceptions before accepting the downstream register.

The following table restates that illustrative calculation. It assumes full pages, an unchanged result set, and successful responses; retries, additional metadata calls, and file downloads are excluded.

Pagination is a useful procurement test because it exposes a common integration mistake: accepting a successful request as proof that every record was collected. Confirm termination, stable identifiers, revision handling, and reconciliation. If access fails, the output should report an unavailable read rather than an empty register.

Keep the approval process above the technology choice

CDE information states: 4 according to NBS (2019): work in progress, shared, published, and archived. Its explanation distinguishes the information workflow from the technology supporting it. That distinction matters more than a claim that a product is a complete environment.

Your acceptance exercise should show how information moves between the project's required states and who authorizes each transition. Ask where suitability, revision, and classification appear, how receiving parties interpret them, and what evidence remains after approval. Software availability alone does not establish that the agreed process is implemented.

Independent reviews need similar discipline. G2's seller-level Newforma page displayed 4.2 out of 5 across 186 reviews when opened for this guide, according to G2. That is a seller-level snapshot, not a product-specific score for Project Center or Konekt. Do not transfer it to a particular edition or compare it with a differently scoped review sample.

Ask for references that resemble your information boundaries and selected product. Have the reference describe configuration work, ongoing administration, participant adoption, and exports. A reference with different scope can still inform questions, but it cannot validate your required workflow.

Buy orchestration only when the handoff warrants it

Zapier, Make, n8n, or an in-house integration may be sufficient for straightforward, authorized exchanges. These approaches can support run histories, retries, error branches, and audit evidence when configured. Their suitability depends on available access and the actual workflow, not their labels.

The buyer still must design and own observability, idempotency, escalation, access controls, and maintenance. Decide how repeated reads avoid duplicate work, how failed runs become visible, who handles exceptions, and how schema changes are detected. Establish whether logs may contain confidential project information and who can inspect them.

A proposed US Tech Automations design could configure explicit reconciliation, source-record references, duplicate suppression, and an internal human review queue across the selected applications. That difference would be a documented design and support responsibility, not an inherent capability advantage over DIY tools. Require access prerequisites, acceptance evidence, and named review owners before relying on it.

For adjacent examples of evaluation structure, the membership-platform comparison and SaaS tool-selection guide illustrate different buying contexts. The campaign exception workflow provides a separate example of turning a condition into a review queue. These articles do not establish construction-product capabilities.

Questions to settle before procurement

Is Newforma a direct replacement for Aconex?

Only when the selected Newforma product satisfies the project's required information boundary and exchange process. Compare the quoted configuration against the owner requirements rather than assuming that shared document-management features make the products interchangeable.

Which Newforma product should be in the proposal?

The proposal should explicitly name Project Center or Konekt and identify the included edition or packages. Request connector scope and implementation responsibilities alongside that selection; a brand-level proposal leaves too much unresolved.

Which vendor has the lower subscription price?

Public core pricing does not establish a cheaper vendor. Both are Quote-based in this guide, so the answer requires comparable written proposals and a clear account of internal administration, integration, and closeout work.

Can a firm use Newforma while a project uses Aconex?

Yes, that is a possible architecture if authorized access and a governed handoff are established. Define which system controls issued records and which supports internal retrieval, then test identity and revision reconciliation before adding automated synchronization.

When NOT to use US Tech Automations?

Use the existing tool when its native workflow already resolves the task, a controlled export meets the reporting need, or access restrictions prevent a reliable cross-system process. In those situations, another orchestration layer adds administration without resolving the underlying constraint.

What should decide a close comparison?

Choose the configuration that satisfies mandatory governance and lets the responsible users complete representative tasks. Use the weighted criteria to distinguish acceptable candidates; do not let a convenient interface compensate for a failed record or access requirement.

Make the choice with a project-shaped acceptance test

Choose Newforma if firm information organization is the primary problem and the selected product fits your operating environment. Choose Aconex if controlled exchanges among project organizations are the primary requirement. Retain both only when their separate boundaries have a purpose and the handoff can be governed.

Before committing, require a representative retrieval, controlled issue, review exception, and closeout export in the quoted configuration. Assign responsibility for every unresolved item. If the remaining problem is the movement of authorized information between systems, see how US Tech Automations could configure that handoff with explicit prerequisites, reconciliation, and human review.