COREVIA International is a multidisciplinary company organised around four pillars: energy and infrastructure, digital and growth, mobility and logistics, and languages, publishing and printing.
Loading...
Loading...
Frequently asked questions
Search common questions about services, quotes, delivery, privacy, projects and future features.
General knowledge base
Answers follow already established public rules. Service-specific questions remain on the relevant detail page.
Published questions
Priority questions
24 questions available
COREVIA International is a multidisciplinary company organised around four pillars: energy and infrastructure, digital and growth, mobility and logistics, and languages, publishing and printing.
The public catalogue includes solar energy, civil engineering, information technology, digital marketing, car rental, logistics, language services, book writing and printing.
Yes. A request may concern a single area of expertise. Coordination across several services is proposed only when the need justifies it and after assessment.
An integrated solution is a scenario in which several official services may be coordinated under one scope. Its final composition depends on context, feasibility and the accepted scope.
Use the quote request page or contact COREVIA International with the need, location, desired schedule and known constraints. The team may request clarification before any proposal.
No. Requests are assessed before pricing because price and scope depend on the available information, constraints and actual delivery conditions.
Pricing considers scope, resources, quantities, timing, location, dependencies and identified constraints. Relevant criteria vary by service.
No universal price is presented for services assessed to order. Applicable conditions are those in the accepted proposal and may be adjusted if the scope changes under the agreed process.
The schedule is established after assessing scope, required information, approvals, availability and dependencies. It is confirmed only together with the corresponding delivery conditions.
Some services may be delivered fully or partly remotely. The delivery mode is defined according to the nature of the need, available information and safety or coordination constraints.
Yes, when the service and feasibility require it. On-site work remains subject to assessment of location, access, safety, schedule and required resources.
Each request is assessed according to the service, location and delivery conditions. See the Areas of operation page to distinguish official locations from areas assessed case by case.
Availability is confirmed only after checking dates, location, resources and service-specific conditions. Sending a request therefore does not constitute automatic confirmation.
Information is limited to what is useful for handling the request. Confidential, private or unauthorised material is not published in the website’s public content.
A change is described, assessed and approved before being incorporated. Any effect on scope, schedule, responsibilities and cost is communicated under the agreed framework.
Yes, when compatible with the scope. Interfaces, responsibilities, prerequisites and limits must then be clarified before delivery.
Deliverables and approval criteria are defined in the accepted scope. Handover may include a review, checks and confirmation depending on the service.
The Projects page presents only work whose information is verified and approved for publication. The absence of a public record does not mean a private reference can be disclosed.
The Shop is a future feature. Its products, prices, payments, deliveries and terms will be presented as available only after the relevant module has been implemented and approved.
Use the details and channels shown on the Contact page. To help route the request, specify the required service, your location and the objective.
No. No public payment journey is presented as active at this stage. Payment terms applying to a service are stated in the approved commercial documents.
Support, maintenance or follow-up may be included when stated by the service and accepted scope. It should not be assumed outside those conditions.
Prepare the objective, context, location, desired timing, relevant users, useful quantities or dimensions, and any known constraints and available documents.
Contributions are first identified separately, then organised around a shared scope, responsibilities, dependencies and approval points.
Present the context, objectives and constraints to receive an appropriate response.