The consent discovery questionnaire agencies should send before the build starts
October 1, 2026 · CookieAegis
Consent work goes wrong in the scoping phase, not the build phase. By the time anyone opens the tag manager, the decisions that matter, which regions the site serves, who owns sign-off, what the marketing stack actually loads, have already been made by default. A short discovery questionnaire sent before the build starts surfaces those decisions while they are still cheap to make, and it turns consent from surprise rework into a priced line item.
Why consent gets missed in scoping
Agencies scope what the client asks about: design, content, integrations, launch date. Consent is nobody's line item, so it gets handled the way unscoped work always gets handled: quickly, at the end, by whoever has time. The result is a banner bolted onto a finished site, configured around whatever the tag manager already loads, with categories invented on the spot.
The rework that follows is predictable. The client's lawyer sees the banner after launch and asks who approved the category definitions. Marketing discovers their new analytics tool fires before consent. A regional manager points out the site sells into a jurisdiction nobody scoped for. Each of these is a discovery failure, and each one costs the agency unbillable hours to fix.
The questions that matter
The questionnaire does not need to be long. It needs to ask the questions whose answers change the build:
- Which countries and states does the site sell to or collect data from? Name them, not just our main markets.
- List every marketing, analytics, advertising, chat, video, and social tool that will be on the site at launch, including the ones marketing plans to add in the first quarter after launch.
- Who signs off on the banner text and the category definitions: the client, their lawyer, or the agency?
- Does the client already have a consent platform, and if so, which contract and configuration carries over?
- Are there subdomains, apps, or checkout flows on other domains that share visitors with this site?
- Who at the client can approve a tag manager change, and how fast do they usually respond?
The second question is the one clients answer worst and the one that matters most. Ask for the marketing stack in writing, and ask what is planned, not just what is live. The tool added two weeks after launch is the one that breaks consent, and it is always a tool the client knew about during discovery.
Turning answers into a scope line item
Answers become scope. A client selling into three regulated regions with fourteen marketing tools and a lawyer who must approve the banner text is a different project from a brochure site with analytics and a contact form. The questionnaire gives you the evidence to price them differently: consent configuration, banner copy rounds, legal review cycles, and post-launch monitoring each get their own line.
Put the client's answers in the statement of work as assumptions. When the client adds a new ad platform mid-build, the questionnaire response is the document that makes the change order a conversation instead of an argument. Agencies that skip this step do the same consent work for free that their competitors charge for.
Red flags in client answers
Some answers should raise the price or at least the attention. We are not sure what marketing uses is a red flag: it means the tag manager is a mystery and the first task is an audit, not a banner. Legal will look at it later means the banner text will go through unknown rounds of revision, so quote the rounds. Our last agency handled it means there is an existing configuration with unknown quality, and inheriting it without an audit inherits its problems too.
Keeping the questionnaire current
Review the questionnaire twice a year. Privacy rules change, client stacks change, and the questions that caught everything last year miss the new patterns this year. The agencies that do consent well treat discovery as a living document, not a form they wrote once. Five questions updated beats twenty questions stale.