Google Workspace

Google Drive Contract Management for Indian Teams: Setup, Limits and When to Move

Owen LarkfieldContract technology writer10 min read

Written by Owen Larkfield Plenty of Indian companies run contract management in Google Drive, and for a team with a few hundred agreements it can work for years. It fails in predictable ways: an executed PDF gets overwritten, a renewal reminder script dies when the person who wrote it leaves, or nobody can say which version of the vendor agreement was actually stamped and signed. This guide is for the founder, finance lead or company secretary who wants to set Drive up properly, and who wants to know in advance which symptoms mean it is time to move. Every Google feature named below was checked against Google's own help pages. Several depend on your Google Workspace edition, so confirm with your admin before you design around one. ## Put contracts in a shared drive, never in someone's My Drive The most common Drive failure is ownership. A contract uploaded to an employee's My Drive belongs to that employee's account, and when the account is suspended after they leave, finding and transferring those files becomes an admin task that often happens too late. Use a shared drive instead. Google's shared drives help page explains that content contributed to a shared drive created in your organisation is owned by the organisation, and it sets out five access levels: Manager, Content manager, Contributor, Commenter and Viewer. A layout that works for most Indian companies: - Contracts: Executed. Final signed and stamped copies only. Legal or the company secretary hold Content manager; everyone else who needs access is a Viewer. Contributors cannot delete files, which is exactly what you want here.

  • Contracts: In negotiation. Working drafts. Business owners can be Contributors.
  • Contracts: Templates. Approved templates, with Viewer access for the business so they copy rather than edit the master. Keep the number of Managers small. A Manager can delete the shared drive and permanently remove files from the Trash. ## A folder tree and file name your auditors can follow Folders should answer the question an auditor or due diligence counsel will ask first: show me every agreement with this counterparty. Organise by contract type at the top level and counterparty below it, for example Customers, Vendors, Employment and contractors, Leases and property, Group and related party, Financing. File names do the rest. A rule such as 2025-04-01_Acme-Logistics-Pvt-Ltd_Vendor-MSA_Executed.pdf sorts by date, shows the exact legal name of the counterparty, and makes the status visible. Use the counterparty's registered name, including Private Limited or LLP, because a trade name in the file name will not match the name on the stamp paper. Indian execution adds two items that must sit next to the agreement: - The stamp evidence. The e-stamp certificate or franking record, with its certificate number noted in your register. An instrument that should have been stamped and was not can be refused in evidence under the Indian Stamp Act, 1899 until the duty and penalty are paid, so the stamp record is part of the contract file, not an afterthought.
  • Board or authority approval. The resolution or delegation under which the signatory acted, where one was needed. ## The Google Sheets register that does the real work Drive stores files; it does not know that a vendor contract renews on 1 April unless someone tells it. That someone is a register in Google Sheets, one row per agreement. | Column | Example entry | Note | |---|---|---| | Contract ID | VEN-0142 | Also written in the file name or a label | | Counterparty (registered name) | Acme Logistics Private Limited | Must match the signature block | | Our contracting entity | Your company's exact legal entity | Matters for groups with several companies | | Type | Vendor MSA | Use a dropdown, not free text | | Effective date and end date | 01-04-2025 to 31-03-2026 | Date-formatted cells, never text | | Renewal mechanism | Auto-renews for 12 months | Fixed, auto-renewing, or evergreen | | Notice period (days) | 60 | Read from the clause, not assumed | | Notice deadline | Formula from end date and notice period | The column reminders run on | | Stamp duty paid and certificate number | Yes, certificate number noted | Blank means a follow-up task | | Owner (business) | Head of operations | Gets the reminder | | Drive link | Link to the executed PDF | One click from register to file | For the notice deadline, =END_DATE - NOTICE_DAYS is the basic formula, written with your own cell references. Two refinements are worth adding. If the clause counts business days, use WORKDAY with a holiday range that lists the relevant state's public holidays, since Indian holidays vary by state. And if notice must be given "not less than" a number of days before the end date, set the reminder a week earlier than the computed date to leave time for courier delivery. Use data validation for dropdown columns and protect the formula columns so a well-meaning colleague does not paste over them. ## Drive labels: metadata that stays with the file A register can drift away from the files it describes. Drive labels reduce that drift by attaching structured fields to the file itself. According to Google's admin help page on classification labels, an admin can create up to 150 labels with up to 10 fields each, and fields can be option lists, numbers, dates, short text or people. Label permissions decide who can view a label, apply it, edit its values and search by it. A practical contract label might carry: contract type (options), our entity (options), end date (date), stamp status (options) and business owner (person). Users with permission can then search Drive for every vendor agreement ending before a given date without opening the register. Two cautions. Labels are created by admins, so your Workspace admin becomes part of your contract process. And edition support differs, so check that your plan includes labels before you build on them. ## Renewal reminders with Apps Script Drive and Sheets do not send renewal reminders on their own. The usual fix is a short Apps Script attached to the register: once a day it reads every row, finds notice deadlines 90, 60 and 30 days out, and emails the owner and legal. Google's installable triggers documentation describes time-driven triggers as working like a cron job, and warns that the run time may be slightly randomised: a trigger set for 9 a.m. can fire at any point between 9 and 10. That is fine for a renewal reminder. What breaks these scripts is not timing but ownership and silence: - The script runs as the person who installed the trigger. If their account is suspended, reminders stop, and nothing tells you they stopped.
  • A renamed column or sheet tab breaks the lookup. The script fails quietly until someone notices a missed renewal.
  • Nobody reviews the code. It becomes a black box in the middle of a legal control. If you use this approach, install the trigger from a role account that does not belong to one employee, add a weekly "reminders ran" summary email so silence is noticeable, and keep a second calendar reminder for any contract above a value threshold. ## Version history and approvals: read the limits closely For native Google Docs, version history is detailed and easy to restore. Most executed contracts, however, are PDFs or Word files, and Google's version management page says that for these non-Google files a past version might be permanently deleted after 30 days or once there are 100 newer versions, unless you mark it Keep forever. The safe rule for executed contracts is simple: never upload a new version over a signed file. Upload amendments as separate files and link them in the register. Drive also has a built-in approvals feature. Google's approvals help page says it is available only for Enterprise and Education Plus accounts, and that the approval banner and approval history apply to Docs, Sheets and Slides files. If your company is on a Business plan, you will be routing approvals by email or chat, so save the approval email as a PDF in the contract folder. ## Signals that Drive has run its course | What you notice | What is really happening | Fix inside Drive? | |---|---|---| | A renewal was missed although it was in the register | Reminders depend on one script and one person | Partly: role-owned trigger and weekly heartbeat email | | Nobody can find every contract with a change-of-control clause | Drive searches words, not clause meaning | No | | Diligence for a funding round takes weeks | Register fields are incomplete or out of date | Only with a clean-up project | | Two "final" versions of the same agreement exist | Drafts and executed copies mixed | Yes: separate shared drives and naming rule | | Stamp duty status is unknown for older contracts | Stamp evidence was never filed with the agreement | Yes, but it is manual work | | Legal reviews counterparty paper clause by clause by hand | Drive has no contract review layer | No | Two or more "No" rows that matter to your business usually mean it is time to add a contract tool. If you are comparing Drive with Microsoft's equivalent, our SharePoint contract management guide covers the same decision on that side, and why contracts end up scattered across email and drives explains how the mess forms in the first place. ## Using Adira next to a Drive setup Adira, made by Clausio LLP on Anthropic's Claude, is a contract drafting and review workspace with Indian law as its home ground. Its pricing page lists storage integrations by plan; whether Google Drive is one of them, and how it behaves, is something to confirm with Adira before you plan around it. Documents are uploaded into Adira, and finished contracts come out through export to PDF or Word, which you then file in your shared drive under the same naming rule. What it adds on top of a Drive setup is the review and drafting layer that Drive lacks. The Document Intelligence Dashboard reads a contract and marks each position favourable, neutral or unfavourable to your company, and lists red flags, missing clauses, key dates, obligations and compliance items including Companies Act points, Section 42 and PAS-3, SEBI, FEMA and stamp duty. Clause-Level Editing applies plain-English changes and shows a diff, and Files, Cases and the Activity Timeline keep a version history of the work. Pricing is public at adiralaw.com: Practice is USD 89 per seat per month billed annually with a three-seat minimum, and there is a 7-day free trial. Where Adira is not the right fit: if your goal is to keep every contract inside Google Drive with metadata and reminders running there automatically, look elsewhere, at tools built to work inside Google Workspace. Adira will not replace your Sheets register either. The Firm plan adds a docket for obligations, renewals and key dates; test during the trial how the dates it surfaces land there for your own contracts. ## A one-afternoon checklist 1. Create the three shared drives and set access levels.
  1. Move executed contracts out of personal My Drive folders.
  2. Agree the file naming rule and rename the top fifty contracts by value.
  3. Build the Sheets register with the columns above and protect the formula columns.
  4. Ask your admin whether your edition supports labels; if it does, create one contract label.
  5. Install the reminder trigger from a role account and add a weekly heartbeat email.
  6. Mark every executed PDF as Keep forever, or simply never overwrite one.

Frequently asked questions

Is Google Drive good enough for contract management?
For a few hundred agreements with one person maintaining a disciplined register, often yes. It stops being enough when you need clause-level search, reliable reminders that do not depend on one script, or fast diligence answers.
How do I get renewal reminders from Google Drive?
Drive has no renewal reminders of its own. Most teams compute notice deadlines in a Google Sheets register and run a daily Apps Script time-driven trigger that emails owners. Install it from a role account and add a weekly summary so a stopped script is noticed.
Can Drive keep every version of a signed PDF?
Not by default. Google says past versions of non-Google files may be deleted after 30 days or 100 newer versions unless marked Keep forever. Never overwrite an executed contract; upload amendments as separate files.
Where should stamp duty records go in a Drive setup?
In the same folder as the executed agreement, with the e-stamp certificate or franking number recorded in the register. An unstamped or under-stamped instrument can be refused in evidence until duty and penalty are paid, so the record belongs with the contract.
Does Adira integrate with Google Drive?
No. You upload documents to Adira and export finished contracts as PDF or Word to file them in Drive. Teams that want everything to stay inside Google Workspace should choose a tool built for that.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free

Book a demo

See Adira on your own contracts

A 30-minute walkthrough with our team. Tell us a little about you, then pick a time that suits you.

Prefer email? [email protected]