Google Sheets: checklist
A sample file and a description of what you want the sheet to do are enough to start a conversation. Use sample data; no passwords are needed. Document layouts, initial data and notification rules can follow. Seeing your calculation method and a correct result early helps me define the scope, price and delivery date accurately.
What to know before we talk
This helps me recommend a package and estimate the cost.
Tasks you want to automate
Examples include totalling sales across tabs, deducting outgoing stock, issuing quotes or emailing reminders when something is due. Describe it in your own words. I will explain whether spreadsheet formulas are enough or Apps Script is needed.
Calculation rules and a correct result
Send your current formulas or calculation method, along with a result you know is correct, such as a quote with the right totals. I use this to check the calculations before delivery.
Who enters, views and edits the data
Tell me how many people will use it, what each person does and whether customers need to view their own data. Separate permissions or customer status lookups usually require a web interface.
Entries per day
Estimate the number of entries per day and how many people will use the system at the same time. I check these against Google service limits before starting.
Your Google account and target go-live date
Tell me whether you use Gmail or Google Workspace so I can set up the files and permissions in the right account. Include your budget and when you want to start using the system so I can recommend a suitable package.
What to send before work starts
These materials are needed to build and test the system. You can send them through the chat as they become ready.
The sheet or Excel file you use now
Send a copy with sample names and figures. I need the table structure, formulas and workflow, not real customer data.
Document layouts you need
Send a sample of each quote, invoice or receipt format you use. Explain whether you need PDF exports or delivery by email as well.
Initial data
List the products, customers or opening balances to import, with approximate record counts. Large data migrations are assessed and quoted separately before work starts.
Notifications and integrations
For LINE OA notifications or data from another system, explain the rules, such as sending an alert when stock falls below a set level. These are add-ons, which I quote before starting the work.
File access
Do not send passwords in the chat. I build with sample data, send the system for you to test, then help set up the files and code in your account at delivery.
Can we talk before everything is ready?
Yes. Send a sample file and explain what you want the sheet to do. I will list anything else needed. The delivery period starts once I have all the required information and we have confirmed the start date.
What happens after you send the details?
- Tell me how you work now and what you need the system to do.
- We agree on the deliverables, price, start date and delivery date in the Fastwork chat.
- I build the system with sample data, send it for you to test, and make revisions within the rounds included in your package.
- I hand over the files and code, help with setup, and fix bugs within the original scope as covered by your package.
Copy this project brief into the chat
Copy this into the Fastwork chat. Fill in what you know, leave the rest blank and do not include passwords.
My business: What I want the sheet to do: What I use for this now (paper / Excel / Google Sheets): Who uses it, and what each person does: Approximate entries per day: Gmail or Google Workspace: Documents or notifications needed: Budget: Target go-live date: