1. Company Details
- Business
- Webapps Software Solutions
- GSTIN
- 19CRLPP7937D1Z7
- Address
- 128, Jodhpur Gardens, Lake Gardens, Kolkata, West Bengal 700045, India
- support@webappssoft.com
- Phone
- +91 97••••0291
2. Purpose and Application
This Policy explains the standard process for approving project scope and accepting deliverables. The accepted proposal, SOW or signed agreement may specify different criteria, review periods or milestone rules and will prevail where clearly stated.
“Deliverable” means an item expressly included in the written scope. “UAT” means user acceptance testing performed by or for the Client.
3. Project Acceptance Before Work Begins
A project begins after the Client accepts the proposal or SOW, confirms the authorised contact, pays the required advance and provides necessary information. Acceptance may occur by signature, authorised email, purchase order, online confirmation or payment where the proposal clearly states that payment confirms acceptance.
The Client must review the scope, assumptions, exclusions, fees, milestones, technologies, ownership, dependencies and support terms before approval. Informal discussions do not add to the scope unless recorded in writing.
4. Acceptance Criteria
Acceptance will be measured against objective written criteria in the proposal, requirements, approved designs, user stories or SOW. If detailed criteria are not stated, a deliverable is acceptable when it materially performs the functions expressly described in the approved scope in the agreed test environment.
Minor cosmetic issues or non-material defects that do not prevent intended use will not normally justify rejection of the entire milestone, but will be logged for correction where in scope.
5. Milestone Review
Projects may be divided into discovery, design, prototype, development, testing, deployment and handover milestones. Approval of a milestone authorises reliance on that milestone for later work.
Reopening an approved milestone because of changed preferences, business decisions or new information may affect fees and timelines. Webapps will identify the change before proceeding where reasonably practicable.
6. User Acceptance Testing
Unless the project document states another period, the Client should complete UAT and provide consolidated written feedback within 7 business days after a deliverable is made available for acceptance.
The Client should test normal workflows, agreed devices/browsers, user roles, calculations, content, integrations and data handling relevant to the scope. Testing should use authorised, safe and appropriately backed-up data.
Webapps may provide reasonable testing instructions. The Client remains responsible for deciding whether the deliverable is suitable for its business, users and legal or regulatory requirements.
7. Reporting Issues and Feedback
Feedback must be submitted through the designated email, issue tracker or project channel and should be consolidated by the authorised Client contact. Each reported issue should include:
- the relevant requirement or acceptance criterion;
- steps to reproduce the issue;
- expected and actual result;
- screenshots, recordings or logs where available;
- device, browser, account or environment details; and
- severity and business impact.
Fragmented, contradictory or late feedback may extend delivery and may require additional fees.
8. Defect, Preference Change and New Scope
A defect is a reproducible failure of the deliverable to materially meet an agreed requirement in the agreed environment. A defect does not include:
- a new feature or workflow not in the approved scope;
- a change in design preference after approval;
- new content, data migration or integration not included;
- a third-party platform change, outage or restriction;
- an issue caused by unauthorised modification or misuse; or
- support for an environment not agreed in scope.
Items that are not defects will be assessed as change requests, with their effect on cost and schedule provided before work begins.
9. Correction and Re-Testing
Webapps will review timely reported issues, reproduce them where possible and correct verified in-scope material defects within a reasonable period based on severity and complexity. The corrected item will be returned for focused re-testing.
Re-testing should confirm the correction and affected related functions. It is not a new opportunity to expand scope or reverse unrelated approvals.
10. When a Deliverable Is Accepted
A deliverable or milestone is accepted when any of the following occurs:
- the authorised Client representative approves it in writing;
- all material acceptance criteria are satisfied and remaining items are minor;
- the Client deploys, publishes, commercially uses or instructs Webapps to launch it, except where expressly designated as a limited test;
- the Client pays an invoice expressly linked to accepted completion without reserving a documented material issue; or
- the review period expires without a written report of a material non-conformity, after at least one reminder from Webapps.
Deemed acceptance will apply only to the extent permitted by law and will not remove an express defect warranty or rights that cannot be excluded.
11. Production Launch
Production deployment occurs only after required approvals, credentials, content, backups and payments are received. The Client should nominate an authorised person to approve launch.
Urgent launch at the Client’s instruction despite known non-critical issues constitutes acceptance of those recorded issues for launch purposes, without cancelling any agreed plan to address them.
12. Final Handover and Ownership
After final acceptance and full payment, Webapps will provide the handover items stated in scope, which may include source code, repository transfer, documentation, design files, deployment information and Client-owned credentials.
Ownership is governed by the NDA & Code Ownership Policy and the project agreement. Open-source, third-party and reusable Background Materials remain subject to their respective rights and licences.
13. Post-Acceptance Defect Warranty
Any warranty or free defect-correction period will be stated in the proposal. If no warranty period is stated, acceptance does not create an unlimited maintenance obligation. New features, content updates, third-party changes, security monitoring, hosting and ongoing support require a maintenance agreement or separate approval.
Warranty coverage excludes misuse, unsupported environments, unauthorised changes, compromised credentials and external platform failures.
14. Client Delay or Non-Response
Late feedback, approvals, content or access may pause the schedule and cause resource reallocation. Webapps may send a reminder and, after reasonable notice, mark the milestone accepted, archive the project or provide a revised restart schedule as allowed by the contract.
Delay by the Client does not delay invoices tied to completed work where the contract states that payment is due upon delivery or availability for review.
15. Rejection and Dispute Resolution
A rejection must identify the material written criterion not met and provide reasonable evidence. The parties will first attempt to resolve the issue through their project leads, then authorised management representatives.
Undisputed deliverables and invoices remain accepted and payable while a specific issue is reviewed. If resolution is not reached, the dispute provisions in the signed agreement apply; otherwise Indian law and competent courts in Kolkata, West Bengal apply, subject to mandatory forums.
16. Contact
Webapps Software Solutions
128, Jodhpur Gardens, Lake Gardens, Kolkata 700045
support@webappssoft.com
+91 97••••0291