Outlook
How to Audit Social Media Scheduling Procurement Notices
Audit UK social media scheduling procurement notices with clear scope, stage and inclusion rules, then state what the records can and cannot support.
Public procurement notices can show what buyers sought or awarded for social media scheduling. Audit them by defining the record, searching the stated services, applying one inclusion rule and logging each decision so another researcher can check it. The method describes the records found within a stated search, not every UK buyer or supplier; the wider outlook stays cautious too.
Define the record before searching
A notice, an award and a later contract change may belong to one procurement episode. They are not automatically three purchases. Give the episode a stable reference and keep each notice beneath it, so a reviewer can follow the sequence without counting each stage as a separate buyer.
Set the subject boundary before reviewing results. A contract that mentions social media might cover advertising, content production, monitoring, publishing or several services together. Include it as scheduling evidence only when the published requirement supports that classification. Keep mixed or unclear contracts separate rather than treating the whole contract as a scheduler purchase.
Record the geography stated for the requirement, not just the contracting authority's location. An England-based authority may procure a UK-wide service; those are not equivalent descriptions. Record the relevant period too, distinguishing the notice date, award date and date of any contract change.
A procurement award records a procurement event, not the communication outcome; that is a separate question for social media scheduling attribution methods.
Search the public procurement trail
Search each public service according to its stated scope. Contracts Finder search guidance says users can search for government and agency contracts worth over £12,000 including VAT. It directs users to Find a Tender for high-value UK contracts, usually above £139,688 including VAT. These are search routes, not a guarantee.
For procurement processes starting on or after 24 February 2025, the notices specified by the Procurement Act 2023 must be published. Exceptions cover Scottish rules, certain below-threshold Northern Irish contracts, and frameworks, dynamic purchasing systems or qualification systems established under earlier legislation. Check the applicable Find a Tender notice rules.
Record the notice type and stated procurement route. A missing result in a search is not, by itself, evidence that no purchase occurred. Search several descriptions, such as "social media publishing", "social media management", "content scheduling" and "digital communications". Treat these as discovery terms, not tests for inclusion: a phrase in a search result is only a lead.
Open the underlying record and save its exact title, reference, contracting authority, notice type, dates, lot description and any named supplier. Log the date of the search, the terms used and the service searched so that the process can be repeated, as a review methodology would require.
Apply an inclusion rule consistently
Write the inclusion rule before coding records. For example, classify a record as confirmed scheduling evidence only when the notice or award explicitly identifies scheduling or publishing software, or describes a requirement that clearly includes that function. Save the supporting wording and the reason for each decision.
Use a small set of statuses, applied consistently:
- Confirmed:the record explicitly identifies social scheduling or publishing software as part of the procured requirement.
- Mixed:scheduling is named, but the contract also covers substantial other services or products.
- Potential:the published description may be relevant but does not establish the scheduling scope.
- Excluded:the record describes another service and provides no substantiated scheduling requirement.
- Unresolved:the available material is not enough to decide.
Do not infer a scheduler from a supplier's name, a broad service label or a general reference to social media. Where a supplier is named, record the legal entity shown in the procurement material separately from any product or edition stated there. Supplier marketing can show what an offer claims to include; it does not establish a purchase.
Keep the procurement stage visible. An invitation or tender is a demand signal of a proposed procurement, not a completed award. An award is evidence of a documented decision. Record a later contract change against the same episode unless the documents establish a separate purchase.
Market evidence register rules
- Separate supplier and buyer sides
- Record legal entity and edition
- Accept documented procurement or buyer interview
- Log geography, period, unit, evidence type
- Set acceptance rule before collecting
- Log non-response and missing coverage
Make each coding decision reproducible
Keep one row for each notice or formal record and use a shared episode reference to connect related records. A useful register includes these fields:
| Field | What to record |
|---|---|
| Record identity | Episode reference, notice reference, source and retrieval date |
| Buyer and geography | Contracting authority and the geography expressly stated for the requirement |
| Stage and period | Notice type, relevant dates, and whether it is a tender, award or change |
| Scope | Exact wording supporting the scheduling classification, plus lot or service detail |
| Supplier | Named legal entity and any product or edition wording in the record |
| Coding decision | Status, inclusion rule applied and reason |
| Search coverage | Search terms, missing documents, unresolved questions and follow-up action |
If the available record does not establish the scheduling function, supplier, geography or stage, mark the field unknown or the record unresolved. Keep excluded and unresolved records in the register: that makes the classification boundary visible and reduces the risk of a later reader mistaking an omitted record for a confirmed non-purchase.
Log where the search took place, when it was run, the terms and filters used, and whether a relevant document was unavailable. This gives a reviewer a way to distinguish "not found in this search" from "checked and excluded under the rule".
Retain the wording used to support decisions rather than relying on a summary written from memory. Counts built on that log can feed a market size estimate only with those limits stated.
Scenario evidence tests
Does a defined buyer study show review events?
continued replacement buying
scenario not supported
Use a decision-tree view only after classifying the underlying record. Its branches can organise questions about what a procurement record supports; they do not turn a tender into an award or an unverified description into confirmed scheduling scope.
State what the records can support
A carefully bounded report can describe the procurement records found for a specified geography, period, category and search method. It can distinguish tenders from awards, and explicit scheduling requirements from mixed or unresolved contracts.
It cannot, on its own, establish total demand, supplier revenue or how many organisations use a scheduler. Search results are not a complete count of purchasing. When reporting a count or comparison, explain how related notices were grouped, how mixed contracts were treated and whether tenders were kept separate from awards.
State the search services, dates, terms and inclusion rule. If those limits do not support a broader claim, narrow the claim rather than filling gaps with assumptions. For guidance on reporting boundaries and exclusions, see social media scheduling measurement.
Before publication, check that every included record has a source reference, a dated trail and a stated reason for its classification.
Ask a second reviewer to apply the saved wording and rule to a sample of decisions. If they cannot reproduce a classification, clarify the rule or leave the record unresolved. Describe each result by its actual stage and scope; do not present a procurement opportunity as a completed purchase.
