Contracting & Signing Authority

This policy explains who is allowed to sign agreements on behalf of TechAbout and the review that must happen before any signature. It applies to every employee and contractor; clients and vendors may also read it to understand how commitments with us become real.

Purpose

A contract binds the whole company, not the person who signs it. This policy makes sure that only authorised people commit TechAbout, that agreements are reviewed before signing, and that no one is exposed to obligations we never actually agreed to. It protects the company, our clients, and you.

If it is not in a signed written agreement, TechAbout is not bound by it.

Scope / Who This Applies To

• All employees and contractors, in every service line — web design and development, SEO, link building, cybersecurity, design, and Express.
• All agreement types: client contracts and statements of work (SOWs), vendor and supplier agreements, non-disclosure agreements (NDAs), partnerships, subscriptions, and renewals.
• Both PKR and international (USD/EUR/GBP/AED/SAR) engagements.

The Policy

Only authorised roles may sign

• Only roles named in TechAbout's delegation of authority may sign a contract or otherwise commit the company. Signing authority follows the role, not seniority or tenure. One person may currently hold this authority until the team grows.
• Authority is bounded — by value, by agreement type, or both. If a commitment exceeds your delegated limit, it must be escalated to the next authorised role before signing.
• If you are unsure who holds signing authority for a given agreement, or what the current thresholds are, ask ethics@techabout.com before you commit to anything.

Review before signing

• Finance reviews every agreement before signature — pricing, currency, payment terms, taxes, and billing must be checked and approved.
• Agreements that carry meaningful legal risk — new or unusual terms, indemnities, liability caps, IP assignment, data-protection clauses, or anything a counterparty drafted — must also go through legal review before signing.
• Never sign a contract you have not read in full, or one whose terms you cannot personally stand behind.

No side letters, no verbal deals

• No side letters. Every term lives in the main signed agreement. Do not create separate or "private" promises that sit outside it.
• No verbal commitments. A promise in a call, chat, or email does not bind TechAbout and must not be represented to a client or vendor as if it does. Put it in the contract or it does not exist.
• Do not agree to scope, discounts, deadlines, or refunds outside the signed document. If terms need to change, amend the contract in writing and route the amendment through the same review and signing steps.

Client SOWs and vendor agreements

• Client SOWs must state scope, deliverables, timeline, price and currency, payment schedule, and how change requests are handled. Vague scope is a risk to both sides — write it down.
• Vendor agreements (tools, subscriptions, subcontractors) must be reviewed and signed by an authorised role, not expensed or clicked through informally. Watch for auto-renewals, data handling, and long lock-in.
• If a vendor or subcontractor relationship could create a personal conflict of interest, disclose it first — see Conflict of Interest & Outside Work.
• Store every executed agreement in the official contract repository. An unsaved contract is a lost contract.

What To Do / How To Report

• If you are asked to commit to something and you are not the authorised signer, say so plainly and route it to the right role — do not sign just to be helpful.
• If a client or vendor pushes for a verbal "yes" or a side arrangement, decline politely and refer them to the written agreement process.
• If you believe a commitment was made without authority or proper review, report it to ethics@techabout.com promptly so it can be assessed and, if needed, unwound.

Consequences

Signing outside your authority, agreeing to side deals, or making binding verbal commitments exposes the company to real financial and legal risk, and may be treated as a disciplinary matter. Where a commitment was made without authority, TechAbout reserves the right to treat it as non-binding to the fullest extent permitted, subject to review by qualified local counsel and current law (including the Companies Act 2017).

Questions? Contact ethics@techabout.com.