KordBlog
Kord vs Bentley ProjectWise for engineering document review
Bentley ProjectWise is the engineering common data environment (CDE) for EPC and infrastructure, handling controlled document management, versioning, and file references. Kord is the visual review layer for mixed-format submittal packages, with diffs across every format, structured review sessions, and AI cross-document consistency checks before release.
ProjectWise is the controlled CDE of record. Versioning, check-in/check-out, the file references that hold a large infrastructure program together. As the system of record, it’s earned its keep.
Kord is for the engineering team doing the actual review, which today happens in email, in Bluebeam, and in a conference room, because ProjectWise will tell you which revision is current but not what changed across the package. Kord shows the cross-format diff and flags where a value drifted across the set, all in one session.
When your engineers are moving fast and the review has quietly migrated everywhere except the CDE, run it in Kord instead. ProjectWise stays the archive; Kord is where the package actually gets looked at before it ships.
How Kord and ProjectWise compare
| Capability | ProjectWise | Kord |
|---|---|---|
| Primary unit of work | Controlled documents and drawing references | The whole engineering document set |
| Version control | Strong revision control, check-in/check-out, and reference management | Document-set history with forked deployments and release snapshots |
| Revision compare | Single-document/drawing compare via integrated viewer | Mixed-format package diff across PDF, Excel, STEP, text in one session |
| Cross-document consistency | Manual across referenced files | AI flags mismatches across specs and calculations |
| Review experience | Heavyweight, IT-managed CDE | Lightweight package-level review built for submittal cadence |
| Deliverables & transmittals | Formal deliverables management with transmittals | Review sessions grouping all files touched by a change |
| Best for | Project-wide engineering CDE and controlled records | Iterative submittal packages without content drift |
Typical ProjectWise workflow
- Check revised files into the managed workspace
- Versions and references update automatically
- Compare a document against its prior version in the viewer
- No mixed-format package diff, so referenced files are reviewed separately
- Deliverable released with cross-document drift unchecked
Kord workflow
- Edit files. Kord syncs and versions them automatically
- See exactly what changed, with visual diffs across PDF, Excel, STEP, and more
- AI cross-document consistency checks catch what humans miss
- Group a single change across every document it touches - excel, word, pdf, etc.
- Ship with full traceability, including a release snapshot and audit trail
Frequently asked questions
Is Kord a ProjectWise replacement?
No. ProjectWise should keep owning controlled document management, versioning, and references across the program. Kord is the review layer on top of it, where engineers see what actually changed across a submittal package, run the review, and catch drift before release.
We already use ProjectWise. Where does Kord fit?
Between your managed workspace and release. Kord syncs the changed files, groups them into a review session, and runs the mixed-format diffs and consistency checks; then the approved revision set gets checked back into ProjectWise.
Doesn’t ProjectWise already do version control?
It does, and Kord doesn't replace that. ProjectWise versions individual documents and manages their references. Kord works a level up: it treats a change, and every file it touched, as one review unit, and flags when a value drifts across the set. A document-by-document CDE was never built to do either of those.