Features
CoreBIM capabilities fall into three areas of ISO 19650: workflow, information management and user management.
Workflow
How information moves between states, teams and approvals until publication.
CDE states
The container moves through the states Work in progress → Shared → Published → Archived as defined in ISO 19650. Each transition records who made it, the date and time, the reason and the approval result in a log that cannot be changed.
- Transitions configurable per project, including returns and exceptions
- Concurrency lock: no conflicting simultaneous approvals
- Version history kept, with no physical deletion
- Task teams with an isolated Work in progress area (ISO 19650-2 §5.3)
- Archived containers keep their full history
Multi-level approval workflows
The standard separates two gates: approval inside the appointed party (Work in progress → Shared) and authorisation to publish (Shared → Published). CoreBIM treats each as its own trigger, with the right approvers at each moment.
- Two ISO 19650 gates: check/review/approve and review/authorise
- Approval, rejection and return, with a mandatory comment
- Return to Work in progress with a recorded, traceable reason
- Queue of pending tasks per approver, inside each project
- Full history of approvals and returns per container
Information management
How each container is identified, classified, tracked and audited throughout the project.
ISO 19650-2 naming validation
Each container gets a unique identifier, checked against the project naming rules. The information manager defines segments by separator, order, whether they are required, length and allowed values.
- Structure: Project · Originator · Volume · Level · Type · Role · Number
- Three result levels: Compliant · Warning · Non-compliant
- Upload blocked or held when a name does not comply
- Batch validation of existing containers, with an error list
- Aligned with the Portuguese CT197 proposal
Metadata and project dictionary
Required metadata are Status, Revision and Classification. Each project adds the attributes it needs: Originator, Volume, Level, Discipline, Milestone and others, with a type, a default value and a list of options.
- Attributes configurable per project, with display order
- Data types: text, number, date, list and boolean
- Version and revision control per container (Pxx, Cxx and WIP sub-indexes)
- Several files per revision, for deliverables in several formats
- Attributes exposed through the API for integration
ProNIC items (coming soon)
ProNIC (the Portuguese protocol for standardising technical information in construction), developed by LNEC, is used in Portuguese state public works for technical specifications and measurements. It is optional and applies only to projects in Portugal.
- Today: link a ProNIC item code to a requirement item by hand
- In preparation: search items in the interface, without typing the code
- In preparation: batch import of items as requirement items
Immutable audit logs
Append-only log protected by a PostgreSQL trigger, tamper-resistant as ISO 19650-5 asks. Each event is stored with every field needed as evidence of compliance.
- Fields: event ID, UTC date/time, user, company, IP, object type, before/after, reason, result
- Audited operations: sign-in, approval, state transition, transfer, sharing, configuration
- Search and filters by type, user, object and period
- CSV export of evidence for external audits
- Retention period configurable per company
Operational reports
Visibility of submission status, compliance and approvals, at any time.
Submission status
A full map of the status of each submission by requirement, deadline and owner.
Overdue approvals
List of approval workflows past their deadline, by project and by approver.
Non-conformities
Containers with non-compliant naming or missing attributes, by project.
Revision history
Full timeline of revisions per container, with reasons and approvers.
Access to confidential information
Record of who accessed containers classified as Confidential.
Audit evidence
Chronological export for a selected set of objects, ready to hand to auditors.
User and access management
Who sees what, with which permission and under which sensitivity classification.
Usage profiles and ISO 19650 roles
Users pick a familiar label (Architect, Client, Site supervision) and the system records the ISO 19650 contractual role underneath: Appointing party, Lead appointed party or Appointed party.
- Familiar label for the user, ISO type for compliance
- Permissions by role: create, edit, change state, approve, archive
- Task teams with their own Work in progress area
- Multi-tenant: data isolated per company at database level
- Email invitations with acceptance and a preset role
ISO 19650-5 sensitivity classification
Classify information in three levels: Public · Limited access · Confidential. The method is the proportionate risk assessment of ISO 19650-5. The names are plain words, so anyone on the team can apply them consistently.
- Read, download and sharing permissions configurable per level
- External sharing by request and approval, with deadline, recipient and reason
- Enhanced audit logging on every access to sensitive information
- Download through a pre-signed URL that expires
- Cloudflare R2 storage with SHA-256 integrity check
Ready to try it?
Create a company, invite your team and start managing information containers today.
Start for free See plans and pricing →