A completed form tells you that someone submitted information. A qualified enquiry tells you that the request fits the services you can provide. Use both counts so you can spot problems in the form as well as changes in lead quality.

Define qualification with sales

Choose two or three criteria the person handling enquiries can apply consistently. A web agency might use service fit, a viable project timeframe and a reachable contact. Keep a separate outcome for cases where there is too little information to decide.

Use explicit stages

Record accepted submission, valid enquiry, qualified enquiry and booked discussion. Give each record one current stage and retain the date it changed. Decide who records exclusions such as test data, vendors or duplicates.

Build a weekly review table

Use one row per source with submissions, valid enquiries, qualified enquiries and open cases. A hypothetical campaign with 20 submissions and four qualified enquiries deserves a different discussion from one with eight submissions and six qualified enquiries. Include the observation period so late decisions can be reconciled.

Look at reasons before changing spend

If a source brings many unsuitable requests, read the rejection reasons and compare them with its landing page promise. If decisions are missing because nobody followed up, repair the handoff before drawing conclusions about the channel.

A reporting template for the next meeting

Use a row such as source, accepted submissions, valid enquiries, qualified enquiries, awaiting review and top exclusion reason. Define each column under the table. Give the enquiry owner a deadline to clear unresolved cases before comparing channels. Review a small sample together to check that both teams apply the definitions consistently.

The growth metrics guide can help you choose the next metric to review. See our performance marketing services for work that connects campaign reporting to enquiry quality.