Change Request Management and Pricing Policy

TechViUs
Version: 1.0
Legal review notice: This policy is a business template and is not legal advice. Provisions concerning contract formation, electronic approvals, taxes and withholding, invoice-dispute deadlines, deemed acceptance, late-payment charges, suspension of services, withholding of deliverables or source code, cancellation fees, limitation of liability, governing law, and termination should be reviewed by qualified counsel in each relevant jurisdiction before use. This is particularly important if TechViUs or its clients are located in Bangladesh or another jurisdiction with mandatory consumer, commercial, tax, employment, data-protection, or electronic-transactions rules.

1. Purpose

This Change Request Management and Pricing Policy establishes the process for requesting, evaluating, approving, performing, invoicing, and delivering work that falls outside the scope of an existing project agreement.

The policy is intended to clarify:

  • When a requested change is treated as a Change Request;
  • When a Change Request becomes binding;
  • How charges and minimum fees are calculated;
  • When invoices may be issued and when payment is due;
  • How disputes, late payment, cancellation, and suspension are handled; and
  • How approved changes may affect project schedules and deliverables.

2. Application and Order of Precedence

This policy applies to software-development and technology services provided by TechViUs, including:

  • Web applications;
  • Mobile applications;
  • Backend and API development;
  • Administrative panels and dashboards;
  • UI/UX development;
  • Database development;
  • Third-party integrations;
  • Cloud and server-related development;
  • Maintenance and enhancement services; and
  • Modifications to existing applications.

This policy applies only to the extent that it is incorporated into, or otherwise made applicable by, a written agreement, quotation, proposal, Statement of Work ("SOW"), Change Request proposal, or other contract between TechViUs and the client.

If this policy conflicts with a signed agreement, SOW, quotation, proposal, or other governing contract, the governing contract controls to the extent of the conflict.

Jurisdiction-specific review flag: Confirm whether this policy can be incorporated by reference and whether the client must expressly acknowledge it before it becomes contractually binding. Some jurisdictions impose special requirements for online terms, consumer contracts, or amendments to existing agreements.

3. Definition of Change Request

A Change Request ("CR") means any new requirement, modification, addition, deletion, or alteration requested by the client that is not expressly included in the applicable original scope, quotation, proposal, SOW, requirements document, or other governing agreement.

Examples include:

  • Adding a new feature;
  • Modifying an existing feature beyond the approved requirements;
  • Adding screens, pages, workflows, or user journeys;
  • Changing business logic;
  • Adding user roles or permissions;
  • Adding an API or third-party integration;
  • Changing database structure or functionality;
  • Adding reports, dashboards, or analytics;
  • Making material UI/UX changes;
  • Changing an approved design;
  • Adding platform, browser, operating-system, or device support; or
  • Requesting changes after a feature has been completed, delivered, or approved.

A request will not be treated as a CR merely because it requires ordinary correction of a defect or non-conformity in an agreed deliverable, provided that the correction is necessary to make the deliverable conform to the approved requirements.

4. Work Included in the Original Scope

TechViUs will perform the features and requirements expressly included in the applicable original scope and approved project documents.

A correction required to make an agreed feature operate materially in accordance with the approved requirements will generally be performed without a separate CR charge.

A request may be treated as a CR if it:

  • Changes an approved requirement;
  • Introduces new functionality;
  • Requires additional development, design, testing, deployment, or project-management effort;
  • Requires work to be repeated because the client changed an approved requirement; or
  • Results from a change in the client's business rules, preferences, content, assets, systems, or instructions.

5. Change Request Procedure

5.1 Client Request

The client must submit each requested change through an agreed communication channel.

The request should contain sufficient information for TechViUs to understand the requested outcome, relevant requirements, dependencies, and desired timing.

A request is not an authorization for chargeable work.

5.2 Review

TechViUs may review the request and assess:

  • Technical requirements;
  • Development effort;
  • UI/UX implications;
  • Backend and API implications;
  • Database implications;
  • Testing and quality-assurance requirements;
  • Third-party dependencies;
  • Risks to existing functionality;
  • Security, hosting, deployment, or infrastructure implications; and
  • Potential effects on the project schedule.

TechViUs may decline a request, request additional information, or determine that the request should be handled under a separate agreement.

5.3 Proposal or Estimate

Where appropriate, TechViUs will provide a written CR proposal or estimate containing some or all of the following:

  • Description of the requested change;
  • Scope, assumptions, dependencies, and exclusions;
  • Estimated hours or fixed price;
  • Applicable hourly rate and minimum charge;
  • Third-party costs, if known;
  • Applicable taxes;
  • Estimated or agreed delivery schedule;
  • Payment and invoicing terms;
  • Urgent-work charges, if applicable; and
  • Any special acceptance, support, or deployment conditions.

For hourly work, an estimate is an estimate only and is not a fixed price, guaranteed maximum, or spending cap unless TechViUs expressly states otherwise in writing.

5.4 Client Approval

The client must approve the applicable CR proposal before TechViUs begins chargeable work.

Approval is valid only if it is provided by an authorized client representative through one of the following methods:

  • A signed CR document;
  • An email sent from the representative's business email address;
  • Approval recorded in an agreed project-management system under the representative's authenticated account; or
  • Another written electronic method expressly approved by TechViUs in advance.

The approval must clearly identify the applicable CR or proposal and expressly confirm acceptance of its scope, pricing method, and payment terms. Silence, receipt of an estimate, verbal discussions, or informal expressions of interest do not constitute approval.

5.5 Formation, Binding Effect, and Advance Payment

A CR becomes binding only when:

  1. TechViUs has issued or communicated the applicable CR proposal or terms;
  2. An authorized client representative has approved those terms using an authorized method under Section 5.4; and
  3. TechViUs has received and acknowledged that approval.

The binding CR consists of the approved proposal or terms, any written approval that modifies or clarifies them, and the applicable governing agreement and this policy. Approval binds the client to the approved scope, pricing method or fixed price, minimum charge, approved third-party costs, applicable taxes, schedule, payment terms, and other stated conditions.

TechViUs may require full or partial advance payment as a condition of scheduling or commencing the CR. If advance payment is required, the CR may be binding upon approval, but TechViUs is not required to begin, schedule, reserve resources for, or deliver work until the required amount has been received as cleared funds.

A request to begin work before formal approval constitutes approval only if it is made in writing by an authorized client representative, clearly identifies or reasonably refers to the applicable CR proposal, and expressly accepts its scope, pricing, and payment terms. Otherwise, TechViUs is not authorized to perform chargeable work.

Jurisdiction-specific review flag: Review whether the specified electronic approval methods satisfy applicable signature, electronic-transactions, evidentiary, and contract-amendment requirements. Confirm how client representatives are authorized and whether advance payments are subject to mandatory refund or consumer-protection rules.

5.6 Scheduling and Commencement

After a CR becomes binding, TechViUs may schedule and begin the approved work.

TechViUs is not required to begin work until any required advance payment has been received as cleared funds.

5.7 Testing and Delivery

TechViUs will test and deliver the completed change in accordance with the approved CR, subject to the client's timely cooperation, access, feedback, approvals, and payment.

6. Pricing

CR charges may be calculated on an hourly or fixed-price basis.

6.1 Hourly Pricing

Where the required effort cannot reasonably be determined in advance, TechViUs may charge for actual time spent.

Standard hourly rate: BDT 1,000 per hour.

Billable time may include reasonable time spent on:

  • Requirement analysis;
  • Planning and estimation;
  • Client communication;
  • Design and UI/UX work;
  • Development;
  • Testing and quality assurance;
  • Deployment;
  • Troubleshooting;
  • Documentation; and
  • Project-management activities directly related to the CR.

Unless expressly agreed otherwise in writing, an hourly estimate is not a fixed price or maximum fee.

6.2 Fixed Pricing

For sufficiently defined requirements, TechViUs may provide a fixed price.

The fixed price will be based on the scope, assumptions, complexity, risks, dependencies, and resources identified in the approved CR.

A fixed price applies only to the scope expressly described in the approved CR. Any additional requirement, changed assumption, client-requested rework, or third-party dependency outside that scope may be treated as a separate CR.

6.3 Third-Party Costs

The client is responsible for third-party costs required for or reasonably related to an approved CR, including:

  • API usage fees;
  • Cloud and hosting services;
  • SMS and email services;
  • Payment-gateway fees;
  • Maps and location services;
  • Software licenses;
  • App Store and Google Play fees; and
  • Other external services.

TechViUs may invoice third-party costs in advance, when incurred, or with the related CR charges. TechViUs may require the client to contract directly with or pay the relevant third-party provider.

Unless otherwise agreed in writing, TechViUs is not responsible for changes to third-party pricing, availability, functionality, policies, or service levels.

7. Minimum Charge

TechViUs may apply a minimum charge to each CR, even if the actual development time is less than the minimum.

Minimum CR charge: BDT 3,000.

For hourly CRs, the minimum charge generally represents three hours at the standard hourly rate. The minimum charge applies to each separate CR unless TechViUs agrees otherwise in writing.

The minimum charge may cover requirement analysis, communication, preparation, development, testing, deployment, and related activities.

8. Taxes and Withholding

Unless expressly stated otherwise in the applicable quotation, proposal, invoice, or written agreement, all prices and charges exclude applicable taxes.

The client is responsible for applicable VAT, sales tax, withholding tax, source tax, duties, levies, and similar governmental charges relating to the CR, except taxes imposed on TechViUs' net income.

If the client is legally required to withhold tax from a payment to TechViUs, the client must:

  1. Notify TechViUs before making the deduction;
  2. Deduct no more than the amount legally required;
  3. Remit the withheld amount to the relevant authority within the required period; and
  4. Provide TechViUs with an official withholding-tax certificate or equivalent evidence of remittance.

Unless prohibited by law, the parties may agree that payments will be grossed up so that TechViUs receives the full net amount stated on the invoice.

Jurisdiction-specific review flag: Tax treatment, VAT, withholding, gross-up provisions, invoicing requirements, and the allocation of tax liability must be reviewed under the laws applicable to TechViUs and the client. A gross-up obligation may be unenforceable or subject to specific statutory rules.

9. Invoicing

9.1 Invoice Timing

Unless the applicable CR proposal or governing agreement states otherwise:

  • Fixed-price CRs: TechViUs may invoice the full approved price upon approval, before work begins, or according to agreed milestones.
  • Hourly CRs: TechViUs may invoice monthly, upon completion, at agreed milestones, or when the minimum charge or accumulated work reaches an amount reasonably determined by TechViUs.
  • Third-party costs: TechViUs may invoice third-party costs in advance, when incurred, or with the related CR charges.
  • Cancelled CRs: TechViUs may invoice work performed and non-refundable costs incurred through the effective cancellation date.

Each invoice will identify the relevant CR and may include applicable taxes, third-party costs, and other approved charges.

9.2 Advance Payment

TechViUs may require full or partial advance payment before beginning a CR.

If advance payment is required, TechViUs is not required to schedule or begin the CR until the required amount has been received as cleared funds.

An advance payment will be applied to the relevant CR. It is non-refundable to the extent that TechViUs has performed work or incurred non-refundable costs, except where a refund is required by applicable law or expressly agreed in writing.

Jurisdiction-specific review flag: Review whether advance payments may be characterized as deposits, retainers, prepaid fees, or penalties, and whether mandatory refund or consumer-protection rules apply.

9.3 Invoice Disputes

The client must notify TechViUs in writing of any genuine invoice dispute within five calendar days after receiving the invoice.

The notice must:

  • Identify the disputed invoice and amount;
  • State the specific basis for the dispute; and
  • Provide reasonable supporting details.

The client must pay all undisputed amounts by the due date.

If the client does not submit a dispute within the stated period, the invoice will be treated as accepted, except for errors that could not reasonably have been identified earlier or rights that cannot legally be waived.

Jurisdiction-specific review flag: A five-day dispute period and deemed-acceptance provision may be restricted or unenforceable in some jurisdictions, particularly for statutory claims, consumer transactions, fraud, latent defects, or mandatory accounting requirements.

10. Payment Terms

Unless a different period is stated in the applicable CR proposal, invoice, or governing agreement, each invoice is due within seven calendar days after the invoice date.

Payment must be made in the currency and through the payment method specified by TechViUs.

The client is responsible for bank charges, payment-processing fees, currency-conversion costs, and similar charges unless otherwise agreed in writing.

Payment is received only when cleared funds are available to TechViUs.

11. Late Payment and Non-Payment

If an invoice is not paid by its due date, TechViUs may, without waiving any other rights or remedies:

  • Suspend development, testing, deployment, support, or access to related services;
  • Remove the CR from the active development schedule;
  • Withhold delivery of source code, credentials, files, documentation, or deployment;
  • Require advance payment for future work;
  • Require a revised estimate or payment arrangement;
  • Recover reasonable collection, legal, banking, and administrative costs to the extent permitted by law;
  • Charge late-payment interest or fees only if permitted by applicable law and stated in the applicable invoice or agreement; and
  • Treat the non-payment as a material breach of the applicable agreement.

A suspension may affect the delivery schedule. TechViUs is not responsible for delays caused by the client's late payment or non-payment.

If an invoice remains unpaid for fourteen calendar days after its due date, TechViUs may cancel the CR or terminate the related services by written notice. The client remains responsible for completed work, approved charges, applicable taxes, third-party costs, and reasonable costs incurred before cancellation or termination.

Suspension, cancellation, or termination does not release the client from payment obligations that accrued before the effective date of suspension, cancellation, or termination.

Jurisdiction-specific review flag: Review statutory limits on interest, collection costs, suspension of services, withholding of deliverables, termination rights, and access to data or systems. The right to withhold source code, credentials, or client data may be limited by the governing agreement, professional obligations, data-protection law, or insolvency law.

12. Urgent Change Requests

If the client requests completion ahead of the normal development schedule, TechViUs may classify the request as an Urgent Change Request.

An Urgent Change Request may be subject to additional charges based on:

  • Required delivery time;
  • Developer availability;
  • Additional resources;
  • Impact on existing work;
  • Work outside normal working hours; and
  • Scheduling or opportunity costs.

TechViUs will communicate any additional urgent-work charge before beginning the urgent work. If the client does not approve the additional charge, TechViUs may process the request under the normal schedule or decline the requested accelerated delivery.

13. Changes After Approval

After a CR has been approved, any additional modification that requires additional effort may be treated as a new CR.

For example, if the client approves Feature A with Requirement X and later requests Requirement Y, Requirement Y may be separately estimated and charged.

TechViUs is not required to begin work on the additional modification until the new CR has been approved in accordance with this policy.

14. Design and Requirement Changes

Changes to approved designs, requirements, workflows, business logic, content, or assets may result in additional charges.

This includes changes requested after:

  • UI/UX approval;
  • Development has begun;
  • Development has been completed;
  • Testing has begun;
  • Client approval; or
  • Production deployment.

The additional charge will reflect the work required to modify, repeat, retest, redeploy, or otherwise address the change.

Work already completed may remain chargeable even if the client later changes the relevant requirement.

15. Effect on Schedule

An approved CR may extend the original project schedule.

Where a CR materially affects the schedule, TechViUs will provide an updated estimated timeline or milestone schedule.

The revised schedule may depend on:

  • Complexity;
  • Available resources;
  • Client feedback and approvals;
  • Required content, assets, or access;
  • Third-party dependencies;
  • Testing and acceptance time; and
  • Receipt of required payments.

A delivery estimate is not a guaranteed deadline unless TechViUs expressly agrees in writing to a guaranteed deadline and identifies any applicable conditions or remedies.

16. Client Responsibilities

The client must provide, in a timely manner:

  • Clear and complete requirements;
  • Required content and assets;
  • Design references, where applicable;
  • Business rules and other necessary information;
  • Access to required third-party services;
  • Timely feedback, testing, and approvals; and
  • Timely payment of invoices and advance-payment requests.

Delays in providing information, assets, access, approvals, or payments may extend the schedule and may result in additional charges for rescheduling, resource reallocation, repeated work, or other resulting effort.

17. Testing and Acceptance

TechViUs will test the CR against the approved requirements.

If the delivered functionality materially fails to conform to the approved requirements, TechViUs will address the relevant non-conformity without treating the correction as a new CR.

The client must report any material non-conformity in writing within seven calendar days after delivery or after TechViUs makes the CR available for review. The notice must describe the issue and identify the relevant approved requirement.

If the client does not report a material non-conformity within that period, the CR will be deemed accepted, except for defects that could not reasonably have been identified during that period or rights that cannot legally be waived.

Requests that introduce new requirements, change approved functionality, or result from a change in the client's preferences will be treated as separate CRs.

Jurisdiction-specific review flag: Review the seven-day acceptance period and deemed-acceptance language for enforceability, especially where statutory warranties, consumer protections, latent defects, or mandatory acceptance procedures apply.

18. Cancellation

If the client cancels an approved CR after it becomes binding, the client must pay for:

  • Work completed through the effective cancellation date;
  • Design, analysis, planning, testing, and deployment preparation;
  • Third-party costs;
  • Non-refundable expenses; and
  • Other reasonable costs incurred or commitments made in reliance on the CR.

If cancellation occurs before development begins, TechViUs may invoice analysis, planning, scheduling, advance work, reserved resources, and non-refundable costs.

Cancellation does not affect payment obligations that accrued before cancellation.

Jurisdiction-specific review flag: Review whether any cancellation charge could be characterized as a penalty or unenforceable liquidated damages provision. Charges should be tied to actual work performed, costs incurred, or a reasonable pre-estimate of loss where required by law.

19. No Automatic Authorization to Develop

A client request does not authorize TechViUs to begin chargeable work.

TechViUs will review the request and, where appropriate, provide an estimate or CR proposal.

Chargeable work will begin only after the CR becomes binding under Section 5 and any required advance payment has been received, unless TechViUs expressly agrees otherwise in writing.

20. Communications and Records

CRs, approvals, estimates, invoices, payment notices, disputes, and cancellation notices should be documented through an agreed communication channel.

The parties should retain records of:

  • The requested change;
  • The approved scope;
  • The applicable hourly rate or fixed price;
  • Minimum charges;
  • Taxes and third-party costs;
  • Payment terms;
  • Delivery or acceptance requirements; and
  • Any subsequent amendments or approvals.

Electronic records, including email and project-management-system records, may be used as evidence of communications and approvals, subject to applicable law and the governing agreement.

Jurisdiction-specific review flag: Confirm applicable electronic-signature, record-retention, privacy, cybersecurity, and evidentiary requirements. Avoid retaining unnecessary personal or confidential information in project-management systems.

21. Exceptions and Waivers

TechViUs may, at its discretion, provide minor changes without additional charge.

An exception, courtesy, discount, delayed-payment arrangement, or waiver applies only to the specific instance for which it is granted and does not create an obligation to provide similar treatment in the future.

Any waiver or exception must be confirmed in writing by an authorized representative of TechViUs.

22. Policy Updates

TechViUs may update this policy from time to time.

An updated version applies only to CRs approved after the updated version's effective date, unless the parties expressly agree otherwise in writing.

An update will not retroactively change the pricing, scope, payment terms, or other rights and obligations of a CR that became binding before the updated version took effect.

23. Client Acknowledgement

By approving a CR, the client acknowledges and agrees that:

  1. The requested change may fall outside the original project scope;
  2. The CR becomes binding only after approval by an authorized client representative through an authorized method and TechViUs' receipt and acknowledgment of that approval;
  3. TechViUs may require full or partial advance payment before scheduling or beginning work;
  4. Hourly charges, fixed prices, minimum charges, third-party costs, taxes, and other approved charges may apply;
  5. Invoices are due within the period stated in the applicable invoice, proposal, or agreement, or within seven calendar days if no other period is stated;
  6. The client must promptly raise genuine invoice disputes and must pay undisputed amounts by the due date;
  7. Late payment or non-payment may result in suspension, withholding of deliverables, cancellation, additional costs, and other lawful remedies;
  8. An approved CR may affect the project schedule;
  9. Additional changes to an approved CR may require a separate estimate and approval; and
  10. If an approved CR is cancelled, the client remains responsible for completed work and costs incurred.

24. Recommended Governing Contract Terms

This policy should be used together with a governing agreement that addresses, as applicable:

  • Legal entity names and authority to contract;
  • Governing law and dispute resolution;
  • Confidentiality;
  • Intellectual-property ownership and licensing;
  • Data protection and information security;
  • Warranties and disclaimers;
  • Limitation of liability;
  • Indemnification;
  • Force majeure;
  • Termination;
  • Ownership and release of source code and credentials;
  • Support and maintenance;
  • Export controls and sanctions; and
  • Notices and service of legal process.
Jurisdiction-specific review flag: These provisions should be drafted or reviewed for the jurisdictions in which TechViUs and its clients operate. This policy does not itself establish governing law, jurisdiction, dispute resolution, intellectual-property ownership, confidentiality obligations, data-processing terms, or liability limits.

© TechViUs — All Rights Reserved

Back to Home