Workplace Policy

1. Purpose and scope

This policy explains the general working principles used by EnvisionStudio when coordinating remote, project-based work with independent professionals. It is intended to support clear communication, dependable delivery, and respectful collaboration.

The policy is a general guide and is not, by itself, an employment offer or a complete contractor agreement. The written terms agreed for an individual project or engagement take precedence where they address a specific commercial or delivery matter differently, subject to applicable law.

2. Remote work and flexibility

Work is generally coordinated remotely. Unless a project agreement states otherwise, there are no fixed daily login or logout times. Team members are expected to manage their work responsibly, meet agreed deadlines, and be available during any collaboration overlap agreed for the project.

Engagements are project-based and non-exclusive, subject to confidentiality obligations, conflicts of interest, and any commitments already accepted. EnvisionStudio does not guarantee a minimum number of projects or ongoing assignments.

3. Project briefs and assignments

Before work begins, the project coordinator and assigned professional should confirm the key details in writing. Depending on the project, these may include:

• Project scope, responsibilities, and deliverables
• Acceptance criteria, milestones, and deadlines
• Compensation, invoicing requirements, and payment conditions
• The designated coordinator and communication channels
• Any agreed collaboration hours, meetings, and reporting needs
• Revision limits and the process for approving scope changes

If a brief is unclear or important details are missing, raise the questions with the coordinator before proceeding where practicable.

4. Communication and meetings

Team members should respond to project-related messages within 24 business hours, Monday through Friday, excluding applicable public holidays. This is a response standard, not a requirement to work continuously or remain online throughout the day. A project brief may set a different response time for a genuinely time-sensitive task.

Meetings are arranged as needed for project planning, reviews, handovers, or issue resolution. Any recurring meetings or specific availability requirements should be agreed in advance. Use the designated project channels and keep important decisions, approvals, and changes in a written record.

5. Availability and planned absences

If a planned absence may affect an accepted deadline, milestone, meeting, or other project commitment, notify the coordinator in advance and obtain agreement on any necessary adjustment. If an unexpected situation affects availability, communicate it as soon as reasonably possible and explain any impact on delivery.

There is no general paid-leave entitlement or fixed leave quota created by this policy. Any time away, rescheduling, or project-specific arrangements should be discussed in the context of the relevant engagement and applicable law.

6. Quality, deadlines, and delivery

Professionals are expected to review their work before submission, follow the agreed brief and relevant professional standards, and deliver files or work products in the agreed format. Raise blockers, dependencies, risks, or likely delays early rather than waiting until a deadline has passed.

If a deadline is at risk, contact the coordinator promptly with the reason, current status, and a realistic proposed next step. Changes to milestones or deliverables should be agreed in writing.

7. Reviews, revisions, and scope changes

Work will be reviewed against the agreed brief and acceptance criteria. Reasonable corrections needed to bring a deliverable into line with the agreed scope should be handled according to the project terms.

Requests that add new features, substantially change approved direction, introduce new deliverables, or exceed the agreed revision scope should be raised with the coordinator. Any change to scope, timeline, or compensation must be agreed before the additional work proceeds.

8. Compensation and payment

Compensation and payment conditions should be confirmed in writing before work begins. Unless the project agreement states otherwise, payment is processed after the relevant deliverables have been reviewed and approved in accordance with the agreed process.

The applicable agreement should specify any review period, approval process, invoice or documentation requirements, payment timeline, and treatment of disputed or incomplete deliverables. This policy does not establish a universal payment deadline or guarantee approval of work that does not meet the agreed requirements.

9. Confidentiality and information security

Protect all confidential information received through EnvisionStudio or its clients, including business information, customer data, project files, designs, source code, credentials, pricing, and internal communications. Use that information only for the authorized project and share it only with people who are authorized to receive it.

Use reasonable security practices: keep devices and accounts protected, avoid sharing passwords or access tokens, use approved storage and communication channels, and promptly report suspected unauthorized access, loss, or disclosure. Do not copy, publish, reuse, or retain confidential project materials beyond the permissions and retention requirements that apply to the engagement.

Confidentiality obligations may continue after a project or engagement ends, as set out in the relevant agreement and applicable law.

10. Client communication and representation

EnvisionStudio manages the client relationship, project coordination, commercial commitments, and delivery oversight. Unless expressly authorized, team members should not independently promise pricing, deadlines, scope changes, refunds, or other terms to a client, nor present themselves as having authority to bind EnvisionStudio.

Where direct client interaction is required, the coordinator should clarify the purpose, permitted scope, and communication channel. Escalate requests or concerns that may affect scope, cost, deadlines, or client expectations.

11. Professional conduct and conflicts of interest

Treat clients, colleagues, and collaborators respectfully. Harassment, discrimination, intimidation, abusive conduct, deliberate misrepresentation, and misuse of access or project information are not acceptable. Raise concerns with EnvisionStudio so they can be reviewed appropriately.

Disclose any actual or reasonably foreseeable conflict that could affect a project, including competing obligations or use of confidential information. Independent professionals may work with other clients, provided they honour accepted commitments, confidentiality requirements, intellectual-property obligations, and any agreed conflict restrictions.

12. Intellectual property and portfolio use

Ownership, licensing, transfer of rights, use of third-party materials, and portfolio permissions are governed by the applicable written project or professional agreement and relevant law. Do not publish client work, display project materials in a portfolio, or reuse assets before receiving the required written permission.

13. Concerns, changes, and ending an engagement

Raise project concerns, delivery risks, payment questions, or conduct issues with the designated coordinator or contact EnvisionStudio at contact@envisionstudio.in. EnvisionStudio may review concerns, clarify expectations, and agree on reasonable corrective steps where appropriate.

Notice periods, suspension, termination, handover duties, outstanding payments, and access removal are governed by the relevant written agreement and applicable law. This policy does not create a universal notice period or replace any agreed termination terms.

14. Policy updates and interpretation

EnvisionStudio may update this policy as its processes evolve. The version published on this page is the current general guidance; project-specific requirements should be confirmed in writing. If you are unsure how a provision applies to your engagement, ask the project coordinator before relying on an assumption.