> ## Documentation Index
> Fetch the complete documentation index at: https://docs.concord.ad/llms.txt
> Use this file to discover all available pages before exploring further.
# Validation checks
> What Concord verifies before an action reaches you, and what it fixes on its own.
Every platform action is validated before you are asked to approve it. The point is that the thing you review is already coherent and already accepted by the platform's rules — so approving is a decision about intent, not a proofreading exercise.
## What gets checked
**Required fields** — every field the platform requires for that object type and campaign type, at every tier of the tree.
**Coherence** — budgets against flight dates, start dates against end dates, child objects against their parent's configuration.
**Platform rules** — allowed objectives, valid bid strategy and budget combinations, formats and character limits, values that exist for that account and that country.
**Quotas and limits** — anything the platform caps, such as the number of targeting criteria on an object.
**Your conventions** — the naming rules and checklists carried by your [Skills](/features/skills/understanding-skills).
**Availability for this account** — targeting values are resolved against what your advertiser can actually target, rather than assumed. A country or interest your account cannot target is reported, not silently swapped for a neighbour.
## What Concord fixes on its own
Some corrections are unambiguous, so Concord applies them and tells you:
* Forcing a newly created object to a non-active status
* Renaming a duplicated object so the name stays unique
* Completing a field the platform derives from another one you set
* Dropping a targeting value that is not available in every country you are targeting, and naming what it dropped
## What Concord comes back to ask
When a fix would be a guess about your intent, it asks instead of choosing:
* A required field the brief does not cover and your rules do not default
* A budget or date that contradicts one of your Skills
* A platform rejection that has more than one reasonable resolution
## When a check fails
The action is not submitted. The failure names the object and the field, so the fix is a message away: correct it in the conversation and Concord prepares the action again.
The most common source of avoidable failures is a rule that lives in someone's head. Once a check fails for the same reason twice, put it in a Skill — Concord will apply it before you see the action next time.