Implementation
Prepare Wegiel.io around the work people do
Choose a fuel collection or delivery and follow the information from the first request through the team to the document and payment check. Agree scope, source data and responsibility before confirming a start date.
From agreements to independent work
From choosing a process to support after launch.
We agree the proposed workflow for the company's configuration — its modules, data and team responsibilities. For each stage, we agree the information needed, the outcome and how to check it.
The offer confirms the scope and charges for configuration, data preparation or transfer, training and support after launch. The module list alone does not define the scope of these services.
-
01
Process and responsibility
Outcome: An agreed initial area, required modules and a responsible person on the company's side.
Responsible: The company's decision-maker and the person coordinating implementation arrangements.
Information needed: A description of day-to-day work, the first process and the roles involved.
Completion condition: Both parties must confirm the scope and identify who resolves questions and accepts the trial results. -
02
Company, access and configuration
Outcome: Agreed data access, module parameters and connections between work areas.
Responsible: The process owner, role representatives and the person responsible for configuration.
Information needed: Branches, warehouses, workstations, users and the rules for the selected process.
Completion condition: The team must confirm its tasks and access. Selected devices and integrations must be checked within the agreed scope. -
03
Data for the trial and launch
Outcome: A list of data to prepare and a method for checking completeness.
Responsible: A person familiar with the company's data and the person agreeing its preparation.
Information needed: A data sample, required master records, opening balances and archive scope.
Completion condition: The company must identify who checks the data. We verify transfer feasibility before agreeing the launch. -
04
Trial of the shared workflow
Outcome: A checked workflow from input data to handover to the next person, and a list of feedback.
Responsible: Users in the participating roles and the process owner.
Information needed: An agreed configuration and a fictional example reflecting how the business works.
Completion condition: Each role must be able to identify its outcome. Gaps must have a responsible person and an agreed way to resolve them. -
05
Training by role
Outcome: Each role learns its own operations, data checks and how to hand a case on.
Responsible: Users and the person providing training within the agreed scope.
Information needed: Tasks for each role, trial results and the team's questions.
Completion condition: Users must be able to complete the agreed example and know where to ask a question. We record further training needs. -
06
Readiness and launch plan
Outcome: An agreed go-live plan with responsibility for the first documents and checks.
Responsible: The company's decision-maker and those responsible for data, configuration and initial operations.
Information needed: Trial results, team preparation, opening data and the list of open cases.
Completion condition: Both parties must confirm readiness and how open cases will be handled. Only then do we agree when to move into operational work. -
07
Support after launch
Outcome: An agreed approach to requests, explanations and agreeing further changes.
Responsible: A designated company contact and a request recipient specified in the offer.
Information needed: User questions, feedback on initial operations and the agreed support scope.
Completion condition: Before launch, we must confirm the channel, hours and handling terms in the offer. The team must know who manages the request and how its completion is agreed.
Preparing Wegiel.io
Let's start with the data and the people responsible.
A description of how you work is enough for the conversation. We agree fictional data for the trial; do not send actual documents or customer data through the website form.
What we will prepare to discuss
- Choose a fictional solid-fuel product, unit and sample certificate data.
- Prepare the parameter table scope and identify who checks sources and product assignment.
- Agree the sales document, certificate handover and office checks.
Opening data and archive
The transition plan covers products and units, customers, warehouses, opening data and quality documents. Agree which open matters continue in the new system and where history is archived. Check transfer feasibility and register scope before staff begin work.
Who to invite to the joint trial
- Quality-documentation staff
- Identifies product and parameter data needing substantive verification.
- User preparing the document
- Discusses access scope and certificate handover for review.
- Office and process owner
- Agree the recipient, how missing data are clarified and separate register checks.
Trial and review scope
Let's follow one agreed example.
The questions below help agree the trial workflow with the team. They do not confirm that all actions have already been completed or optional modules enabled.
What we will check together
- Does the chosen product match the certificate, and is the parameter-table reviewer identified?
- Which missing information must be resolved before the document is prepared for handover?
- Can staff identify fuel-parameter sources, the correct product and sales document?
Who takes over the next step
Agree who prepares the certificate and passes it to the named quality-documentation owner. The office arranges register checks; the process owner assigns missing-data clarification.
Boundaries of the example configuration
Transport and CRM automation follow the agreed scope. Before calculated excise can be used, the known product-setting gap must be repaired, then applicable fuel parameters, periods and resulting documents verified and accepted.
Let's agree the initial setup scope.
Let's discuss the team's tasks, the areas needed and the people responsible. We agree the trial scope and how to transition to operational work before planning the launch.