Supported
Submitted evidence materially supports the defined capability assertion under the recorded review scope.
Partner capability evidence
OceanHub treats every partner capability as a discrete assertion: one canonical capability, the evidence offered to support it, and an explicit review state. The system does not turn organization-level marketing claims into scores or blanket endorsements.
Review workflow
The organization has selected a canonical capability, but no supporting evidence packet has been submitted.
Capability-specific evidence has been submitted and is waiting for review.
The assertion and submitted evidence are being checked against the defined capability scope.
A review has been completed and carries an explicit outcome, reviewer provenance and review date.
Review outcome
A reviewed outcome does not imply that every service offered by the organization has been assessed. Scope, reviewer and review date remain part of the record.
Submitted evidence materially supports the defined capability assertion under the recorded review scope.
Evidence supports part of the claimed scope, but important limits or gaps remain.
The submitted material does not yet support the capability assertion to the required review standard.
Evidence packet
The first intake asks for one primary evidence item per capability. Additional material can be requested during review.
reference-project
Reference project / client case
field-asset
Field asset / equipment
dataset-deliverable
Dataset / delivered technical output
procedure-method
Procedure / method statement
certification-accreditation
Certification / accreditation
personnel-credential
Personnel credential
publication-paper
Publication / technical paper
third-party-assessment
Third-party audit / assessment
Profile boundary
A future partner profile can expose organization identity, canonical capability assertions, operating regions, evidence freshness and review provenance. OceanHub will not create public capability profiles from registration alone.