Covered deliverable
Confirm that the affected function is part of the accepted scope and was released or handed over as described.
Plain-language warranty guide
Separate a defect from a change—and assess it against the agreement.
Any project warranty, its coverage period, start point and available remedy are determined by the applicable written agreement and governing law. This page explains the assessment path but does not create or extend a warranty. Nothing here excludes, restricts or replaces rights and remedies that cannot lawfully be excluded or limited.
Clearscope and responsibility
Usefulsystems people can operate
Durableownership after launch
Why it matters
Covered deliverable
Confirm that the affected function is part of the accepted scope and was released or handed over as described.
CHAPTER 01 / Start with the contract
Coverage comes from the accepted terms for the actual work.
Locate the proposal, scope, acceptance record, change approvals and any support or warranty schedule. Those documents identify the delivered behaviour, responsibilities, dependencies and relevant period, if one applies.
Applicable period
Use the start point and duration stated in the written agreement. No generic period is promised on this page.
Acceptance and changes
Review accepted limitations, later modifications and approved changes that may affect expected behaviour.
Legal rights
Mandatory statutory rights continue to apply according to the relevant law, regardless of this explanatory guide.
CHAPTER 02 / Defect or enhancement
The key question is whether agreed behaviour failed or new behaviour is wanted.
Possible defect
The delivered function does not operate in a material respect as specified and accepted, within the applicable environment and responsibilities.
Enhancement
The function operates as agreed, but a new option, workflow, design, integration or broader behaviour is now desired.
Content or configuration change
Words, images, products, users, settings or business rules need updating after the accepted release.
External change
A browser, device, API, hosting platform, supplier, policy or connected system has changed or become unavailable.
Use or access issue
The reported result depends on permissions, credentials, unsupported use, supplied data or a step outside the agreed workflow.
CHAPTER 03 / Evidence to provide
Show the expected behaviour, the actual behaviour and the context.
Project reference
Identify the agreement, deliverable and affected production system.
Reproduction steps
List the authorised steps, inputs and role that lead to the issue without including secrets.
Timing and frequency
State when the issue began, whether it is consistent and what changed nearby in time.
Sanitised evidence
Provide exact messages, screenshots or logs only through an approved route and remove unnecessary personal or confidential information.
Environment
Identify relevant browser, device, account role, integration or third-party status where known.
CHAPTER 04 / Assessment path
Confirm, contain, classify and communicate.
1. Confirm receipt
The request should receive a reference through the functioning support channel.
2. Review applicability
The report is compared with the scope, acceptance, applicable period, responsibilities and subsequent changes.
3. Reproduce or inspect
Available evidence and authorised access are used to determine whether the behaviour can be confirmed.
4. Classify
The outcome may be a covered defect, change request, content/configuration item, external dependency, access issue or unresolved investigation.
5. Propose the next step
Any remedy, workaround, further investigation, external referral or separately scoped work is communicated under the applicable agreement and law.
CHAPTER 05 / Dependencies and exclusions
Responsibility can change when the environment changes.
The applicable agreement determines exclusions. Relevant considerations can include unauthorised changes, unsupported environments, misuse, client-supplied content or data, external services, expired licences, compromised credentials, hardware, connectivity and failures outside GA Applications' control. These factors do not override non-excludable legal rights.
Third-party services
External supplier terms, availability and product changes may affect diagnosis and remedy.
Browsers and platforms
Assessment considers the supported environments identified by the project and material platform changes since acceptance.
Modifications
Changes by another party may need to be isolated before responsibility for the reported behaviour can be determined.
CHAPTER 06 / Security, backups and continuity
A warranty is not a substitute for operational care.
Security updates, account management, backups, monitoring, content administration and recovery are ongoing responsibilities that exist only within the scope allocated to each party. A warranty does not imply uninterrupted service, continuous monitoring or recovery of data where those services were not agreed.
Access control
Keep authorised users and credentials current and report suspected compromise through the designated route.
Backup ownership
Confirm who operates, verifies and retains backups for each relevant system.
Supplier continuity
Know which domains, hosting, APIs, subscriptions, devices or licences are required for operation.
CHAPTER 07 / After any stated period
The system can still be supported through an agreed pathway.
An issue outside an applicable warranty period may be handled through an active support arrangement, a scoped repair, a maintenance review or a wider improvement project. Assessment comes before commitment so the cause, risk and responsibility can be understood.
Support request
Use for an issue under an active care or support arrangement.
Scoped repair
Use where investigation or remedial work needs a separate commercial authorisation.
Modernisation
Use where the affected system or dependency should be redesigned rather than repeatedly patched.
Continue through the ga applications system.
Each route answers a different operating question while retaining the same standards for evidence, responsibility and a usable next step.
Route 01
About
See how GA Applications approaches websites, business systems, automation and responsible digital design as one connected project.Route 02Process
Follow GA Applications' eight-phase path from diagnosis and scope through design, build, launch, handover and measured improvement.Route 03Pricing
Understand how scope, content, integrations, risk and support shape a GA Applications estimate without misleading one-size-fits-all packages.Route 04Faq
Direct answers about GA Applications services, delivery, pricing, ownership, SEO, AI, support, locations and independent concepts.Route 05Support
Report an issue, request a controlled change or find the right support path for a GA Applications website or connected system.Route 06Refunds Cancellations
Understand how a cancellation or refund request is reviewed against completed work, commitments, third-party costs, written terms and law.Route 07Chinkara Maven
Explore Chinkara Maven as GA Applications' guided assistance layer for approved knowledge, clear permissions and human-reviewed action.Questions worth resolving
What to clarify before committing.
What warranty period applies to my project?
Use the period and start point, if any, stated in the applicable written agreement. This general page does not create a standard period.
Is every problem a warranty defect?
No. The issue may be a defect, enhancement, content change, access issue, external-service change or behaviour outside the agreed environment. It must be assessed against the actual scope and evidence.
What remedy will be provided?
Any remedy depends on the applicable agreement, confirmed cause and governing law. It should not be assumed before assessment.
Does this page limit consumer rights?
No. Nothing on this page is intended to exclude, restrict or replace rights and remedies that cannot lawfully be excluded or limited.
Request an assessment
Bring the agreement, the expected behaviour and safe evidence.
The issue can then be classified against the accepted scope, applicable responsibilities and law before a remedy or next step is proposed.