Comparable project memory
Structures project, portfolio, proposal and document data in a shared vocabulary so options can be evaluated against consistent criteria.
Preserved decision provenance
Shows which document, version, assumption and owner support a result; later data changes do not erase the original decision context.
Visible exceptions and approvals
Missing documents, conflicting data and authority-dependent steps move into structured review instead of disappearing in personal follow-up.
Continuity from portfolio to operation
The same project identity and state history persists from initial evaluation through proposal, approval and follow-up.
Project and portfolio context
Proposal and comparison criteria
Document and information source
Decision, owner and follow-up state
Make visible which evidence and responsibility support the progress of a project or portfolio option.
Project and portfolio context
Proposal and comparison criteria
Document and information source
Decision, owner and follow-up state
The system underneath the interface.
Propos treats project and portfolio data as schema-controlled entities, versioned documents and state machines rather than a loose collection of files. A comparison output is not a temporary view of mutable data; it is a reproducible decision snapshot stored with its sources.
Canonical project schema
Project, portfolio, stakeholder, proposal, criterion, document and decision objects have separate identities; free text cannot silently replace critical fields.
Document and version relation
File content, metadata, source, version and related decision are stored separately so current documents are not confused with historical evidence.
Comparison engine
Criteria, weights, missing data and evaluation time are recorded; scores and rankings are never presented without rationale.
Workflow and approval
State transitions are bound to roles and prerequisites. Missing records, unauthorized changes or conflicting information enter a review queue.
Integration and search
External project, CRM and document sources connect through adapters; normalized metadata supports filtering and relationship-aware search.
Cross-cutting contracts that make the architecture trustworthy
- Role- and project-scoped access
- Versioned document metadata
- Reproducible decision snapshots
- State-machine approval prerequisites
- Immutable audit trail
Propos does not infer substitutes for measured plans, contracts, official records or expert verification. Missing or conflicting sources remain explicit; verified facts and user assumptions are never presented at the same confidence level.
We explicitly design where the system must stop.
The system structures information and comparison without inventing substitutes for measured plans, contracts or official records.
Operational need
Keeping project, proposal and portfolio information across separate files and channels delays decisions and makes comparison difficult.
The Corixo approach
Propos structures construction and real estate workflows around more consistent data, explicit workflows and traceable decision points.
The goal is not to create more screens. It is to form the right decision inside a more visible, explainable system with clear responsibility.
Intended value
Faster comparison, more visible project information and more controlled progress.
Questions we address
- How can project information become comparable?
- Which data standards do portfolio and proposal workflows need?
- How can decision points remain traceable?