Our working method

Understand. Scope. Deliver. Review. Support.

A structured approach to turn a need into an understandable project, organise responsibilities and progress towards handover.

Present my project Explore our expertise

Illustration representing the five phases of COREVIA International’s working method.

A shared method adapted to each service

Structuring the project without imposing an unnecessarily rigid process

The projects supported by COREVIA International can be very different: solar installation, website, logistics operation, car rental, language assignment, book, printing or civil engineering intervention.

Our method provides a shared structure for understanding the need, identifying constraints, defining the scope, organising responsibilities, reviewing deliverables and preparing handover.

This structure is adapted to the nature of the service, the scale of the assignment, the delivery mode, the available information and the conditions accepted in the proposal.

A small assignment may use a simplified version of the method. A complex project may require more documentation, validation points, contributors and controls.

The project journey

Five phases from the initial request to handover

01Listening and discoveryUnderstand the need, objectives, users, location and initial constraints.
02Assessment and scopingAssess feasibility, define the scope and identify risks, dependencies and required expertise.
03Proposal and planningPresent the services, deliverables, responsibilities, schedule, conditions and estimate.
04Delivery, monitoring and quality controlCarry out the work, share important information, manage validation and review deliverables.
05Handover, approval and supportProvide the deliverables, complete final approval and organise the support included in the proposal.

Objective

Listening and discovery

Understand the need before defining a solution.

This first phase is used to gather essential information, identify the people involved and understand the desired result.

Possible activities

Gather a description of the need.
Identify the relevant service or services.
Understand the objectives and users or beneficiaries.
Gather the location when the project requires it.
Understand the desired deadline and indicative budget when it can be provided.
Review available documents.
Identify initial constraints.
Determine whether further discussion is required.

COREVIA’s responsibilities

Ask the necessary questions.
Restate the need.
Identify missing information.
Guide the client towards relevant expertise.
Explain the next steps.

Client responsibilities

Provide accurate information.
Describe the objectives.
Provide available documents.
Identify known constraints.
Appoint a contact person when necessary.

Possible outputs

Summary of the need.
Information received and information still missing.
Direction towards one or more services.
Decision to continue to assessment or request clarification.
Decision not to proceed when the need does not match the services or is not feasible.

Objective

Assessment and scoping

Assess feasibility and define what should actually be delivered.

This phase turns a general request into a more precise scope. It helps identify constraints, assumptions, dependencies, resources and required expertise.

Possible activities

Analyse available information and technical requirements.
Assess the location and delivery mode.
Review volumes, formats, quantities, documents or existing infrastructure.
Identify dependencies and any required permissions.
Identify known risks.
Clarify deliverables and scope limits.
Distinguish included and excluded elements.
Determine the required expertise.
Determine feasibility remotely, on-site or through a hybrid approach.

COREVIA’s responsibilities

Analyse the provided information and identify insufficient information.
Identify constraints, assumptions and dependencies.
Propose a coherent scope.
Recommend a delivery mode.
Decline or postpone an assignment when conditions do not support reliable or safe delivery.

Client responsibilities

Provide access to necessary information.
Confirm priorities.
Allow a visit or technical access when required.
Clarify internal constraints and identify third parties.
Respond to requests for clarification.

Possible outputs

Assessment and preliminary scope.
Lists of deliverables, exclusions and assumptions.
List of risks and recommendations.
Decision to prepare a proposal or request an additional assessment.
Reasoned decision not to proceed.

Objective

Proposal and planning

Formalise the conditions of delivery before work begins.

This phase presents how the project may be delivered. The proposal should enable the client to understand the scope, deliverables, responsibilities, schedule, conditions and estimate.

Possible activities

Summarise the need and objectives.
Define the included scope, exclusions and services involved.
Present deliverables, assumptions and responsibilities.
Define expected contributions and validation points.
Present the indicative schedule and expected response times.
Clarify the delivery mode and travel conditions.
Present the applicable estimate, price and payment terms.
Explain change rules and included support.

COREVIA’s responsibilities

Present an understandable proposal.
Explain assumptions and identify exclusions.
Clarify responsibilities and validation points.
Present applicable costs.
Explain the change process.
Answer questions relating to the proposal.

Client responsibilities

Review the proposal and request necessary clarification.
Confirm information.
Approve or reject the scope and accept the conditions.
Provide required permissions or materials.
Make required pre-start payments when applicable.

Possible outputs

Accepted proposal or proposal requiring revision.
Postponed or declined project.
Delivery plan.
Indicative schedule.
Authorisation to begin.

Objective

Delivery, monitoring and quality control

Produce the deliverables while maintaining the required coordination, communication and controls.

This phase corresponds to carrying out the assignment. Its organisation depends on the service, number of contributors, dependencies, validation points and delivery mode.

Possible activities

Confirm contacts and organise tasks.
Produce deliverables on-site or remotely according to the project.
Coordinate expertise and monitor dependencies.
Perform interim checks.
Present versions and collect feedback.
Correct issues and communicate difficulties.
Update the schedule when necessary.
Process change requests.
Prepare handover.

COREVIA’s responsibilities

Deliver the accepted scope and organise contributions.
Share important information and communicate difficulties.
Request required validation.
Review deliverables.
Document accepted changes.
Protect information according to agreed commitments.

Client responsibilities

Provide the required access, content and decisions.
Respect agreed validation deadlines.
Consolidate feedback when required.
Communicate changes promptly.
Not request out-of-scope execution without an impact assessment.
Facilitate site or stakeholder access when necessary.

Possible outputs

Interim deliverables and validation versions.
Progress reports and documented decisions.
Change requests.
Quality review reports.
Deliverables ready for final handover.

Objective

Handover, approval and support

Provide the deliverables, confirm receipt and organise the next steps included in the scope.

This phase closes the main delivery work. It includes handing over the agreed elements, presenting them, final approval and, when included, documentation, training, assistance or maintenance.

Possible activities

Complete the final internal review.
Prepare and hand over files, equipment or other deliverables.
Present deliverables and explain their use.
Provide the included documentation and training.
Collect and address reservations within the scope.
Confirm final approval and closure.
Start the included warranty, maintenance or assistance.
Collect feedback.

COREVIA’s responsibilities

Provide and explain the included elements.
Provide the included documentation.
Address reservations within the scope.
Distinguish corrections from new requests.
Clarify post-handover support conditions.
Document closure when necessary.

Client responsibilities

Review deliverables and identify reservations within the agreed conditions.
Confirm receipt.
Meet any remaining payment conditions.
Use deliverables in accordance with recommendations.
Identify people to be trained when training is included.
Retain and back up transferred elements when this responsibility belongs to the client.

Possible outputs

Final deliverables and receipt confirmation when necessary.
Included documentation or training.
Included maintenance plan or support period.
Reservation list and closure.
Additional proposal for a new request.

Shared responsibility

A project moves forward more effectively when everyone understands their role

COREVIA organises delivery, but the assignment may also depend on information, validation, access and decisions provided by the client or other parties.

COREVIA’s responsibilities

Organise the assignment and comply with the commitments defined in the proposal.

Understand and restate the need.
Identify missing information.
Propose an appropriate scope.
Explain assumptions and exclusions.
Organise contributions.
Communicate important information.
Request required approvals.
Review deliverables.
Report identified difficulties.
Document accepted changes.
Hand over the included elements.
Comply with the commitments defined in the proposal.

Client responsibilities

Provide the contributions, decisions and access within the client’s responsibility.

Provide accurate information and required documents.
Appoint relevant contacts.
Obtain permissions within the client’s responsibility.
Provide required access.
Approve within agreed timeframes.
Consolidate feedback when requested.
Communicate changes promptly.
Comply with payment terms.
Review deliverables.
Retain transferred files or equipment.
Use deliverables in accordance with applicable recommendations.

Responsibilities of potential third parties

Contribute according to the nature of their involvement and applicable commitments.

Provide their contributions under the agreed conditions.
Respect dependencies and validation points.
Communicate constraints.
Provide the information or access within their responsibility.
Comply with applicable confidentiality commitments.
Report difficulties that may affect the schedule.

A third party’s responsibility depends on the nature of its involvement and the commitments applicable to it.

The applicable proposal or agreement defines the responsibilities retained for the project.

Preparing the project

Information that supports more accurate scoping

Not all information is required for every service. The following elements may nevertheless help assess a request more efficiently.

01
The need
An explanation of the problem, objective or desired result.
02
The relevant service
The main area and any complementary expertise being considered.
03
The location
Address, site, city, origin, destination or remote mode when applicable.
04
Users or beneficiaries
People, teams, clients, readers or audiences concerned.
05
Available documents
Plans, texts, files, data, specifications, photographs, inventories or references.
06
Desired schedule
Start date, deadline, dependent events and availability constraints.
07
Indicative budget
Available range when the client is able to provide it.
08
Constraints
Access, safety, permissions, confidentiality, infrastructure, format, volume or dependencies.
09
Contacts
People responsible for decisions, approvals and information.
10
Success criteria
Elements used to determine whether the deliverable addresses the need.

You may submit a request even if some information is not yet available.

Communication adapted to the project

Sharing important information at the right time

Frequency, channels and participants depend on the assignment. They should be defined in the proposal or at project start.

A primary contact

Identify the person consolidating communication on the client side and the main COREVIA contact.

Defined channels

Clarify the channels used for decisions, documents, urgent matters and routine communication.

Appropriate progress checkpoints

Determine a frequency consistent with the duration, complexity and dependencies of the project.

Documented decisions

Maintain an understandable record of important choices, approvals and changes.

Sufficiently early alerts

Report a difficulty as soon as it may affect the scope, schedule, budget or quality.

Consolidated feedback

Combine comments to reduce contradictions and repeated corrections.

COREVIA does not promise permanent availability or immediate response. Response times depend on the conditions defined for the project.

Review before handover

Checks adapted to the nature of the service

Quality control does not take the same form for software, translation, solar installation, printed material or a logistics operation. Criteria should be defined according to the deliverable.

Technical and functional review

Review the operation, characteristics, configuration, integration or agreed performance according to the service.