Draft project framework
This page is a discussion framework, not an executed contract. Each project must have a signed statement of work or proposal with the commercial details completed. Do not rely on this placeholder page as a substitute for a reviewed client agreement.
1. Parties and project documents
Provider: Symmetric Code, Muslim Town, Hyderabad, Sindh, Pakistan. Client: {{CLIENT LEGAL NAME AND ADDRESS}}. The project consists of this agreement plus the signed statement of work, approved change requests and any specifically named schedules. Identify which document prevails if terms conflict.
2. Scope and delivery
The statement of work must define deliverables, exclusions, assumptions, dependencies, milestones, acceptance criteria, client review periods and the target schedule. Changes to scope, timing or fees require written approval from both parties.
3. Fees and payment
Complete the project fee, currency, deposit, milestone invoices, due dates, taxes, late-payment handling and expenses in the signed statement of work. Do not start paid work until the agreed initial payment condition is met. These terms are placeholders and do not set a price.
4. Client responsibilities
The client provides timely decisions, accurate content, authorized brand assets, system access and a project contact. The client confirms it has the rights and permissions needed for materials it supplies. Delays in these items may affect the schedule and should be handled in the signed scope.
5. Revisions and acceptance
Specify the included revision rounds, how feedback is consolidated, what counts as acceptance, and what happens if no response is received. Extra work must be approved and priced in writing before it begins.
6. Ownership and third-party materials
The signed scope must state when ownership of custom deliverables transfers, what rights are retained until payment, and how pre-existing tools, open-source software, fonts, stock media and third-party services are licensed. No IP transfer rule is final until these terms are completed and reviewed.
7. Confidentiality, data and security
Identify confidential information, permitted use, protection duties and exclusions. If the project processes personal data, define the parties’ roles, instructions, security controls, subprocessors, breach handling, retention and any required data-processing addendum before work begins.
8. Support, termination and refunds
Set out any warranty period, post-launch support, maintenance, service levels, termination notice, payment for work completed, deposits and refund rules in the signed statement of work. These are currently placeholders.
9. Liability and disputes
Define remedies, liability limits, exclusions, escalation process, governing law and dispute forum only after legal review for Pakistan and the client’s jurisdiction. Nothing here overrides non-excludable rights or liabilities under applicable law.
10. Signatures
A project agreement should be signed by authorized representatives of both parties and include the applicable statement of work. Contact symmetriccode01@gmail.com to discuss a project.
