Engagement and Remuneration Policy

1. Purpose and scope

This policy describes how Orvion World engages the people who work with it and how they are paid. It applies to engineers, designers, AI specialists, project leads, sales and partnership contributors, and to any other role unless a written agreement says otherwise.

Our default model is performance based: a person commits to a defined output, the remuneration for that output is fixed in advance, and payment follows acceptance of the output. Full-time salaried employment is used where a function needs continuous presence; see section 9.

2. Definitions

Output: a result that can be checked. A feature shipped, a module live, a model deployed, a website launched, a client onboarded, a sales target met, a document delivered.

Acceptance criteria: the written, checkable conditions that decide whether an output is complete.

Engagement: one agreed output, or a set of milestones, with its remuneration, timeline, acceptance criteria and penalty terms.

Engagement document: the written record of all of the above, agreed by both sides before work starts. An email thread that both sides have confirmed counts.

3. How an engagement is formed

Anyone may propose an engagement: Orvion World may ask for one, or a contributor may propose one unprompted.

Before work starts the engagement document must state: the output and its acceptance criteria; the delivery date or milestone dates; the remuneration for each milestone; the penalty terms for a miss; who accepts the output on behalf of Orvion World; and anything Orvion World must supply (access, data, decisions) and by when.

Work that starts without an engagement document is at the contributor's risk and is not payable until one is agreed.

4. Remuneration

The remuneration for an output is fixed in the engagement document. It does not change with the hours taken, the location worked from or the seniority of the person, only with the output.

Larger projects are split into milestones, each with its own acceptance and its own payment, so that money moves as value is delivered.

Payment is made within the period stated in the engagement document after acceptance. If no period is stated, it is paid in the next payment run after acceptance.

Repeat contributors are offered larger outputs and larger amounts over time. The basis stays the same.

5. Acceptance

An output is accepted when it meets the acceptance criteria in the engagement document. The person named in the document decides, against those criteria only.

If the criteria are ambiguous, the ambiguity is resolved in the contributor's favour and the criteria are rewritten for next time.

Minor defects found after acceptance are fixed by the contributor within the warranty period stated in the engagement document; they do not reopen acceptance or payment.

6. Commitments and penalties

A commitment is a commitment. If an output is delivered late, or does not meet the agreed criteria, a penalty applies. The penalty is stated in the engagement document before work starts.

Penalties are set per engagement because different work carries different impact: a late internal tool and a late client launch are not the same. There is no blanket rate. Typical forms are a reduction of the remuneration for the affected milestone, a deferral of payment until the output is corrected, or, for a repeated or serious miss, termination of the engagement.

Penalties apply to Orvion World as well. If we delay the work by failing to supply access, data or decisions on time, or by changing the scope without a revised agreement, the contributor's dates move accordingly and the remuneration is not reduced.

A contributor who sees a miss coming must say so early. Early notice does not remove a penalty, but it is taken into account, and it allows the scope or date to be renegotiated before the deadline rather than after it.

7. Changes to scope

Scope changes only through a revised engagement document agreed before the extra work is done. Additional work done without a revision is not payable.

Either side may propose a change at any time. Until it is agreed, the original document stands.

8. Where and when the work is done

Contributors may work from the Orvion World office in Nashik, remotely, or at a client site when the engagement requires it. Hours are planned by the contributor around delivery and the meetings the work needs.

There are no timesheets and no location-based pay adjustments for output-based engagements.

9. Salaried employment

Where a function needs continuous presence rather than a defined output, Orvion World employs full-time salaried staff for it. Such positions are opened when required and announced on the careers page.

Salaried staff have performance expectations recorded in their employment terms. The output model in this policy does not replace those terms, and this policy does not limit how Orvion World may choose to staff any role.

10. Confidentiality and ownership

Work produced under an engagement, and the code, designs, data and documents that go with it, belong to Orvion World or its client as stated in the engagement document, from the moment they are paid for.

Client information, source code and business data are confidential during and after the engagement. Contributors may describe their work in general terms in a portfolio unless the engagement document says otherwise.

11. Disputes

Any disagreement is first settled against the engagement document. If the document does not answer it, the parties agree a reading in writing and apply it going forward.

Nothing in this policy limits rights under the laws that apply to the engagement or employment contract.

12. Changes to this policy

This policy may change. Engagements already agreed are governed by the version in force when their engagement document was signed. The current version is always at this address.

Questions about this policy: info@orvionworld.com. To propose an engagement, use the careers page.