# Scope an implementation contribution

A proposed customer task, relevant experience and clear responsibility boundaries.

## Who this is for, and when

A consultant, a systems integrator or a fractional operations lead who helps companies adopt tools and wants to know where Elvina implementation work begins and ends. It begins when a client asks for help with a pilot. The risk is scope creep from source cleanup into system integration without an agreement.

## How it works in Elvina

An implementation brief separates discovery, source preparation, supported configuration, review, training and post-launch ownership.

- Describe the proposed customer task, your relevant experience and the responsibility boundaries you propose.
- Separate the phases: discovery, source preparation for Company Knowledge, supported configuration, review in the Web workspace, training, and post-launch ownership.
- State which phases you would own, which the customer owns and which need Elvina's involvement.
- Send the implementation brief through the contact channel and wait for an agreement before quoting fees or dates.

## A worked example

A fictional operations consultancy proposes to help a 40-location cleaning franchise pilot Elvina on its site inspection procedure. The brief assigns discovery and source preparation to the consultancy, configuration and review to the franchise's training owner, and post-launch ownership to the franchise. Customer system access is listed as requiring separate authorization.

- The brief shows six phases with an owner for each and a note on what needs Elvina's confirmation.
- The reply states whether an implementation partnership is planned or confirmed and what an agreement would define.
- No fee, delivery date or product capability is promised to the franchise before that agreement.

## What to check before relying on it

Do not promise product functionality, delivery times or fees without agreement. Customer system access and rollout require separate authorization.

- Each phase has a single accountable owner.
- Customer system access is called out as a separate authorization.
- No functionality, timeline or fee was promised before agreement.

## Where a person stays in charge

Do not promise product functionality, delivery times or fees without an agreement. Customer system access and rollout require separate authorization from the customer; Google Drive and Notion connect directly, and Dropbox and SharePoint are planned, not available today. This page is a program description; partnership status and terms are planned or confirmed per agreement.

## Questions people ask

**Q:** Can I configure the customer's workspace myself?

Only with the customer's authorization and within what your agreement covers. The customer's training owner approves what reaches learners.

**Q:** Is there a certification for implementation partners?

No certification is claimed on this page. Ask what the program offers when you send the brief.

No launch date is committed for planned features.