How to reply to a freelance data project brief
First identify whether the client needs data entered, cleaned, analyzed or turned into a report. Name that task in your reply, then show evidence of the relevant work. Ask about the input and the expected output before estimating. A listing that says "data specialist" may describe spreadsheet cleanup or an analytical project; the title alone isn't enough to scope either.
An example: responding to an analysis request
This illustrative brief is not a real listing or a named company's dataset.
Brief: "We have monthly sales spreadsheets from several stores. Need them combined and a dashboard showing revenue by store and product category. Some category names differ across files. We'd like the process to work again next month."
Weak reply: "I work with Excel, Python, SQL and Power BI. Please send the files and let me know when you need the dashboard."
Example reply:
Your dashboard depends on combining the store files and resolving category names consistently, so next month's refresh follows the same rules. My relevant example is a spreadsheet cleanup I can walk through, including the mapping rules and validation checks. I'd agree on the category mapping, reconcile the combined totals with the inputs, and document the refresh process. Can you share a redacted sample of the file layouts, and how should returns or cancelled sales affect revenue? That would help me scope both the report and the recurring update without guessing at the definitions.
The sample assumes you have completed a spreadsheet cleanup; change that evidence to match your own work. Don't claim experience with a tool solely because it appears in the listing. If your example uses a different tool, explain which part of the task transfers and which part you would need to establish.
Resolve the reporting rules before building
Inspect file layouts and changing headers
Ask about file count, approximate row count, column layouts and delivery format. One consistent spreadsheet is different from dozens of files with shifting headers. Use a redacted sample when possible; don't ask a prospective client to send sensitive customer records in an initial reply.
Define revenue and category mapping
"Revenue" might refer to booked sales, paid orders or net amounts after returns. Ask about the specific ambiguity in the brief. A polished dashboard can still answer the wrong question when its underlying definitions were never agreed.
Describe reconciliation and exception checks
For this project, describe reconciling totals, checking duplicates and reviewing unmatched categories. Name the checks rather than promising perfect accuracy. Confirm who can resolve unfamiliar category names; some decisions require business knowledge that the dataset doesn't contain.
Plan the recurring refresh handover
A one-time report and a repeatable refresh need different handover work. State whether the scope includes import instructions, a mapping table, error checks and documentation. Ask whether someone will run the process manually or whether an automated schedule is expected.
Respond differently to a record-entry task
If the task is entering invoice fields, focus on the number of records, required columns, validation rules and handling unreadable values. Show a small relevant example of careful structured work. Don't pitch forecasting or dashboards unless the client requests them. A sensible question is how ambiguous entries should be flagged, rather than silently guessed.
Distinguish reporting work from record entry
The current snapshot for data work supplies current figures for the field. Read each brief to distinguish entering records, preparing files and analyzing results; a category label cannot choose that service for you. When comparing an offer, check the payment basis as well as the amount. Currency conversion and separation of hourly from project amounts are absent from the budget bands. For a recurring dashboard, the source layouts, business definitions and refresh owner are more useful scoping inputs than a combined distribution.
End with a useful scope question
Ask for the sample layout or definition that determines the work. Once those are clear, your quote can describe the deliverables and assumptions instead of putting a fixed price on an unknown dataset.