SHERPA Governance Portal + Service Spokes
HCG and CREVOX are building the SHERPA Governance Portal: a full client-facing system for FF&E project governance — decisions, approvals, evidence, budget, and schedule visibility — with service spokes that scope the portal to individual offerings such as Procurement.
Primary reader question: How can an FF&E execution company give clients role-based visibility into project decisions, evidence, budget, and schedule?
What this HCG + CREVOX project established
The portal gives owners, operators, designers, and project managers role-based visibility into governed project state — who owns each decision, what evidence supports it, and where budget, schedule, or quality risk is accumulating — and can be adopted as the full system or as a single service spoke such as Procurement.
The condition that required a controlled system response
FF&E clients experience their projects through scattered emails, spreadsheets, and vendor portals, so governance value stays invisible; SHERPA needed a client-facing system that exposes decisions, evidence, and status without forcing every client into the full platform on day one.
Constraints that governed the work
- Preserve the controlled SHERPA operating model as the portal's single source of truth.
- Support full-platform clients and single-spoke clients on one underlying architecture.
- Give each role visibility appropriate to its responsibilities without duplicating project data.
- Keep decision ownership, approvals, and evidence auditable.
Why this work matters beyond the technology.
Makes governance visible and billable by exposing decisions, evidence, and status to clients directly.
Lets clients start with one service spoke, such as Procurement, and expand into the full system.
Reduces status meetings, email archaeology, and duplicated reporting through shared project data.
How the work was structured to reduce uncertainty and execution risk.
- 01
Model FF&E projects as governed objects: decisions, approvals, specifications, quotes, evidence, budget, and schedule.
- 02
Define role-based views for owners, operators, designers, and project managers.
- 03
Design service spokes — starting with Procurement — that expose a scoped slice of the same architecture.
- 04
Stage delivery so dashboards, approvals, and client communication build on shared project data.
What the system contains and how the parts work together.
A governance portal architecture with role-based project visibility.
Decision, approval, and evidence workflows tied to accountable owners.
Budget, schedule, and risk dashboards built on shared project data.
Spoke-scoped portal experiences for individual services such as Procurement.
Controlled outputs created, implemented, or formally defined
What is materially different because of the work
The statements below reflect the documented project state. They do not convert an active, defined, or conceptual project into a completed implementation or claim unsupported financial results.
- SHERPA's governance model now has a defined client-facing product rather than existing only in documents and process.
- Spokes let clients adopt a single service with a portal experience that can expand to the full system.
- Portal requirements are shaping how project data, evidence, and decisions are captured across the SHERPA ecosystem.
Artifacts that can substantiate the work
Public evidence depends on client permission and confidentiality. HCG can use approved public, controlled, or anonymized artifacts without presenting confidential material as open proof.
Direct answers for readers evaluating a comparable need.
What business problem does the SHERPA Governance Portal address?
It replaces scattered emails, spreadsheets, and vendor portals with role-based client visibility into governed FF&E project state: decision ownership, supporting evidence, approvals, budget, schedule, and accumulating risk.
What did HCG and CREVOX create or define?
A portal architecture with role-based views, decision and approval workflows, evidence and status structures, dashboards on shared project data, and service spokes — beginning with Procurement — that scope the portal to individual offerings.
What is the current status of the SHERPA Governance Portal?
Active development. The architecture, role model, workflows, and Procurement spoke are defined and being built on the SHERPA platform, with dashboards and client onboarding staged next.
Lessons carried into future HCG and CREVOX work
- A governance operating model becomes commercially tangible when clients can see decisions, evidence, and status directly.
- Spokes expand adoption without diluting the core system definition.
- Role-based views must draw from one project record, or the portal recreates the fragmentation it exists to solve.
Ranked against the same business context.
CREVOX AI-Native FF&E Digital Twin
CREVOX / SHERPA ecosystem · FF&E + Design
The CREVOX FF&E Digital Twin extends SHERPA into an AI-native platform connecting project objects, specifications, decisions, quotes, vendors, logistics, installation, evidence, and status.
SHERPA FF&E Governance + Execution System
SHERPA FF&E · FF&E + Design
HCG and CREVOX developed SHERPA as a governed FF&E execution system that connects design intent, sourcing, procurement, logistics, installation, evidence, budget, schedule, and accountable decisions.
CREVOX Outcome Delivery Platform
CREVOX · Technology + AI
CREVOX is an outcome-delivery platform and service ecosystem designed to combine AI intake, reusable capabilities, specialist workflows, tools, verification, and human review around finished business results.