Content calendar CSV validator
Choose the contract your calendar actually uses, then validate the pasted CSV. Match the column names in its header rather than assuming every template uses the same wording. Repeated scheduling keys can be allowed when several assets belong on the same day.
Select the actual checks
| Setting | What it checks | When to change it |
|---|---|---|
| Required columns | Their presence and non-blank values | Use Post brief when that is the real header, rather than Brief |
| Scheduling key | The chosen column and its values | Choose Day, Date or the actual identifier; leave blank to skip |
| Key format | Text, positive day number or real YYYY-MM-DD date | Choose text for weekday names or another non-date key |
| Unique keys | Repeated values under the selected key | Allow repeats when multiple assets share a date |
| Expected records | The non-blank data-row count | Use 0 when no expected count is required |
Read record-specific issues
Column matching ignores case and outer whitespace, but different names remain different. An empty required value, inconsistent field count, repeated header or invalid selected key is reported with its logical CSV record number. A quoted multi-line cell stays inside one record.
The parser handles quoted commas, doubled quote escapes, ordinary line breaks and an initial UTF-8 text marker. Fully blank records are excluded from the data count. It accepts up to 1000000 text characters and 10001 logical records including a header.
A passing structural check does not establish that the creative brief, permissions, dates or business facts are ready. Use the receiving team's actual review for those decisions; a row count alone does not prove that every day in a period is covered.
Before handing off the calendar
- Use the actual header names.
- Choose the correct uniqueness and key-format rules.
- Correct malformed quoting before judging other issues.
- Review the complete briefs, assets and responsibilities separately.