Frequently asked questions.

SHERPA is an integrated FF&E execution system that governs a controlled process and takes responsibility for controlled outcomes from design intent through installation.

SHERPA governs design intent, cost, schedule, quality, procurement, logistics, installation, and closeout through one accountable execution system.

No. SHERPA is not defined as a software platform, marketplace, or passive tool. SHERPA may use technology where appropriate, but the value is the governed execution system behind it. The system governs the work; the tool supports visibility, records, communication, and control.

Because platforms support participation, while systems govern execution and create accountability for controlled outcomes.

SHERPA is not another participant in the process and not a passive tool directed by fragmented workflows. It is the governed execution system through which the FF&E process operates. The spokes connect to the system; the system does not reshape itself around each spoke.

Greater execution confidence, improved budget discipline, stronger schedule control, preserved design intent, transparent governance, and clearer accountability.

Because SHERPA replaces informal, disconnected decision-making with disciplined governance, clear accountability, structured execution, and repeatable controls.

Governance ensures every significant decision is controlled, traceable, accountable, and aligned with the project's intended outcome rather than individual interpretation.

SHERPA replaces informal, disconnected decision-making with disciplined governance. Its value is accountable execution: defined inputs, clear outputs, documented approvals, controlled communication, schedule visibility, risk control, and decision accountability across the governed FF&E lifecycle.

Yes. SHERPA combines governance with practical FF&E experience to guide execution decisions that support project objectives.

Owners, developers, operators, hospitality groups, golf clubs, designers, architects, and project teams executing complex FF&E projects where execution confidence, traceability, and risk control matter.

No. SHERPA is most valuable where FF&E complexity, cost exposure, schedule pressure, stakeholder coordination, or execution risk matters. Smaller projects may use a lighter governance model or standalone SHERPA Procurement.

No. SHERPA preserves the designer's intent and governs how that intent is translated into FF&E specifications, procurement, logistics, installation, and closeout.

No. Architectural responsibilities remain with the architect. SHERPA governs FF&E execution within its defined scope.

No. Contractors execute their work. SHERPA governs the FF&E execution pathway and coordinates the governed scope.

SHERPA establishes a governed execution framework that existing teams can plug into through defined inputs, outputs, responsibilities, approvals, and decision points. Each participant keeps responsibility for its own professional scope, while SHERPA governs how FF&E-related information, decisions, procurement, logistics, installation, risks, and accountability move through the project.

No. Designers, architects, contractors, vendors, and other project participants remain responsible for their own professional scope. SHERPA does not dictate how each spoke performs work within its independent scope unless SHERPA is specifically engaged for that scope. SHERPA governs how FF&E-related information, approvals, schedules, risks, and decisions move through the execution process.

SHERPA works with existing teams, but it does not reshape the governance system around unmanaged workflows. Participants connect to SHERPA through defined inputs, outputs, responsibilities, approvals, and decision points. This makes the system usable without requiring massive change, while still protecting accountability and control.

No. SHERPA does not require massive change to be useful. It creates a controlled structure that participants can plug into through defined information, approvals, responsibilities, and decision points. The goal is not to disrupt the team; it is to prevent FF&E execution from being controlled by informal, disconnected, or undocumented workflows.

No. SHERPA is not the entire project management system for the project. SHERPA governs the FF&E execution pathway within the larger project environment and connects to the owner, project manager, designer, architect, contractor, vendors, and installers so FF&E decisions and dependencies remain controlled, visible, and accountable.

No. SHERPA does not compete with the project manager. The project manager may oversee the broader project, while SHERPA governs the FF&E execution system within the project. SHERPA gives the project manager clearer FF&E visibility, controlled decision records, schedule awareness, risk tracking, and accountability within the governed FF&E scope.

SHERPA fits into the larger project team as the governed FF&E execution layer. It does not replace the owner, project manager, designer, architect, contractor, vendor, or installer. It connects their FF&E-related inputs and outputs into one controlled process so decisions, approvals, procurement, logistics, installation, and closeout do not operate in isolation.

A project manager may coordinate tasks across the broader project. SHERPA governs the FF&E execution system itself: design-intent translation, specification control, procurement alignment, logistics coordination, installation readiness, decision records, risk control, and accountable closeout within the governed FF&E scope.

A purchasing agent typically focuses on sourcing, quoting, ordering, and vendor coordination. SHERPA Procurement can perform those functions, but SHERPA Governance goes further by controlling how procurement connects to design intent, budget, schedule, approvals, logistics, installation, risk, and accountability.

No. SHERPA reduces the burden on owner oversight by creating structured visibility, decision controls, and accountable reporting. Owners still retain approval authority where required, but they are not left to manage disconnected details without a governed system.

SHERPA supports designers by preserving design intent and translating approved selections into governed specifications, budget alignment, procurement readiness, logistics planning, installation coordination, and issue control. SHERPA does not replace the designer's creative or professional role unless separately engaged for that scope.

SHERPA supports architects and contractors by making FF&E-related information, decisions, schedules, site requirements, and installation dependencies visible and controlled. SHERPA does not assume architectural, engineering, code, permit, or contractor responsibilities unless expressly included in scope.

Yes. SHERPA provides FF&E procurement. Within SHERPA Governance, procurement operates as one governed function inside the broader FF&E execution system. SHERPA Procurement can also be used as a standalone procurement service or as a procurement workstream within another approved governance structure. In that model, SHERPA governs only the procurement pathway, not the full project.

SHERPA Governance is the full governed FF&E execution system. It controls how FF&E information, decisions, approvals, procurement, logistics, installation, closeout, risk, and accountability move through the project. SHERPA Procurement is a procurement-focused spoke. It may operate inside SHERPA Governance, as a standalone procurement service, or as a procurement workstream within another approved governance structure.

Yes. SHERPA Procurement can be used without full SHERPA Governance. In that model, SHERPA governs only the procurement-related pathway: sourcing, quoting, purchasing, vendor coordination, production tracking, logistics coordination, procurement approvals, procurement visibility, and procurement-related closeout. It does not govern the full project unless the broader governance system is engaged.

Yes. SHERPA Governance can govern FF&E execution even when procurement is handled by another approved party. In that model, SHERPA governs visibility, approvals, coordination, scheduling, risk control, and accountability around the procurement pathway, but does not act as the purchasing party unless separately engaged.

SHERPA provides the accountable execution structure for the FF&E scope it governs, subject to the defined scope, decision authority, approvals, and controls established for the engagement.

Governed FF&E scope means the portion of the project that SHERPA is formally responsible for controlling through defined inputs, approvals, schedules, responsibilities, records, and decision pathways. SHERPA accountability applies only to the scope placed under SHERPA governance.

If an activity, decision, vendor, purchase, or workflow sits outside SHERPA governance, SHERPA may provide visibility or coordination if contracted, but it does not assume accountability for outcomes it does not control.

The rim-and-spokes model means SHERPA Governance provides the controlled FF&E execution framework, while functions such as design coordination, procurement, vendor communication, logistics, installation, reporting, and closeout operate as spokes. Each spoke keeps its own purpose, but connects to SHERPA through defined inputs, outputs, responsibilities, approvals, and decision points.

Yes. Design coordination, procurement, vendor coordination, logistics, installation, reporting, and closeout can all function as spokes within SHERPA Governance. Each spoke performs its own work, while SHERPA governs how information, approvals, schedules, risks, and decisions move between them.

Governing a spoke means SHERPA controls how that function connects to the broader FF&E execution process. Performing a spoke means SHERPA is directly hired to execute that function. For example, SHERPA may govern procurement performed by another party, or SHERPA may provide SHERPA Procurement directly if engaged for that scope.

Yes, if that function is placed within SHERPA's governed scope and the required information, authority, approvals, and decision pathways are established. SHERPA may govern how a function connects to FF&E execution without directly performing that function.

SHERPA works with each spoke, but it does not reshape the governance system around unmanaged workflows. A governance system must protect accountability, which requires defined inputs, outputs, responsibilities, approvals, and decision points. The system is designed to be easy to plug into, but it cannot remain accountable if every spoke operates through its own uncontrolled process.

Procurement is important, but it is only one part of FF&E execution. A product can be correctly purchased and still create project risk if design intent, approvals, budget, production timing, logistics, site readiness, installation, or closeout are not governed. SHERPA Procurement governs the procurement pathway; SHERPA Governance governs the broader FF&E execution system.

If a spoke is outside SHERPA Governance, SHERPA may coordinate with it if contracted, but accountability for that spoke remains outside SHERPA control. SHERPA can only govern outcomes connected to the agreed scope, authority, information, approvals, and controls.

Yes. SHERPA Procurement can operate as a procurement workstream inside another approved project governance structure. SHERPA governs only procurement-related scope and connects to the other system through defined data intake, approvals, communication, schedule requirements, and reporting expectations.

Yes. SHERPA can operate inside another approved project governance system when roles, authority, data intake, communication rules, reporting expectations, approval paths, and decision records are clearly defined. In that structure, SHERPA governs the assigned FF&E execution layer or procurement pathway.

SHERPA increases execution confidence by governing decisions before they become execution risks, protecting design intent, budget, schedule, quality, and coordination within the governed scope.

Design intent is translated into governed specifications and managed through every execution stage to final installation.

Budget alignment begins early and remains governed throughout execution so commercial decisions support project objectives rather than react to them.

Manufacturing, logistics, approvals, and installation are planned as one governed execution pathway rather than separate activities managed in isolation.

Every material decision follows defined authority, documented approvals, and controlled governance within the SSOT.

All changes are evaluated for cost, schedule, design, and execution impact before approval through formal change governance.

SHERPA evaluates changes for cost, schedule, design, procurement, logistics, installation, and closeout impact before approval. Approved changes are documented in the controlled record so the project team understands what changed, why it changed, who approved it, and what impact it creates.

SHERPA continuously governs assumptions, risks, issues, decisions, and changes using controlled registers and defined escalation pathways.

If a participant's process creates risk, SHERPA identifies the issue, assigns responsibility, documents the decision path, and controls the escalation before the issue becomes unmanaged project risk. SHERPA works with each participant, but it protects the governed execution framework from undocumented decisions, incomplete information, misalignment, or uncontrolled process gaps.

The SSOT is the controlled project record containing the authoritative information governing every decision, item, approval, and execution activity.

The SSOT should contain the current controlled record for governed FF&E scope, including approved specifications, item data, decisions, approvals, quotes, procurement status, schedules, risks, issues, changes, logistics details, installation readiness, closeout documentation, and version history.

SHERPA identifies the missing information, assigns responsibility, documents the risk, and prevents uncontrolled release where missing information could create cost, schedule, quality, procurement, logistics, or installation issues.

No. SHERPA governs the decision process, presents controlled information, identifies risks, documents approvals, and manages execution impact. Final owner-side decisions remain with the designated client authority unless decision rights are expressly assigned to SHERPA in the engagement.

SHERPA reduces confusion by defining responsibilities, decision rights, approval paths, communication rules, schedules, issue ownership, and the single source of truth. Each participant knows what information is required, where it belongs, who must approve it, and what happens next.

Substitutions are reviewed against design intent, performance requirements, budget impact, lead time, availability, quality, warranty, logistics, and installation implications. No substitution should move forward without documented review and approval through the governed decision process.

SHERPA manages vendor and manufacturer coordination through controlled communication, quote tracking, production visibility, lead-time validation, issue escalation, logistics coordination, and documentation. Vendors remain responsible for their own products and commitments, while SHERPA governs the pathway through which their work affects the project.

Late approvals are documented as execution risks because they can affect budget, schedule, procurement release, production, logistics, and installation. SHERPA identifies the impact, assigns responsibility, escalates when required, and updates the controlled record so consequences are visible.

Success is measured by disciplined execution, budget control, schedule management, preservation of design intent, quality, documented decisions, and accountable execution within the governed scope.

SHERPA governs closeout through verification, documentation, warranties, turnover, lessons learned, and archival of the controlled project record.

SHERPA provides structured visibility through governed reporting, project status, decision tracking, risk management, and milestone reviews.

SHERPA reporting may include project status, open decisions, approval needs, procurement status, vendor updates, production risks, logistics timing, installation readiness, budget variance, schedule risk, issues, and next required actions. Reporting is tied to the governed scope.

As early as project definition. Early involvement allows design intent, budget, schedule, and execution strategy to be aligned before downstream decisions are constrained.

Every governed SHERPA engagement begins with Charter activation, project definition, stakeholder alignment, and establishment of the governed execution framework.

SHERPA needs timely decisions, access to current project information, defined authority, approved scope, accurate budgets, schedule expectations, stakeholder participation, and use of the agreed decision and documentation process. Governance works when required inputs and approvals are provided.

Yes. SHERPA can enter an active project, but value depends on how much scope can be brought under control. The first step is usually a governance review to identify current information, open risks, undocumented decisions, procurement status, schedule constraints, and immediate control gaps.

No. SHERPA does not guarantee specific savings, acquisition-cost reductions, schedule outcomes, or risk elimination. SHERPA provides a governed execution system designed to reduce avoidable risk, improve control, and protect capital within the governed scope.

No. SHERPA does not guarantee schedule certainty. SHERPA improves schedule control by identifying dependencies, tracking approvals, coordinating procurement and logistics, managing risks, and making schedule impacts visible before they become unmanaged problems.

SHERPA pricing depends on scope, complexity, project phase, service model, governance requirements, procurement involvement, reporting needs, and level of accountability. SHERPA Governance and SHERPA Procurement may be priced separately or together depending on the engagement.

The first step is to define the intended scope: full SHERPA Governance, SHERPA Procurement, or procurement operating within another governance structure. From there, SHERPA reviews project information, confirms authority and responsibilities, and defines the controls required for the engagement.