Bulk-upload and schedule many posts at once

An agency managing five retail clients' social accounts gets handed a month of pre-written festive content from one client's marketing team, sitting in a single spreadsheet — captions, image references, target dates for thirty-odd posts. Creating each one individually through a composer would eat an entire day the agency can't spare during a busy festive lead-up.

Bulk import accepts that spreadsheet or CSV directly, validates each row, and creates draft posts in bulk on the calendar for review before anything gets scheduled. A malformed row — a missing date, a broken media reference — gets flagged individually without blocking the rest of a valid batch. What it deliberately doesn't do is skip the normal checks a manually created post goes through: imported content still needs the same approval and platform-policy review, because bulk import exists to save typing, not to shortcut safeguards that exist for good reason.

Validation leniency is a real design tension worth understanding rather than assuming is handled correctly. A file-upload path that's too permissive can flood the draft queue with hundreds of malformed posts if checks let too much through, turning what should be a time-saver into a mess someone now has to clean up row by row — arguably worse than typing thirty posts by hand, since sorting a hundred bad imports takes longer than writing thirty good ones. Validation needs to be genuinely strict about what counts as a usable row.

Media references deserve particular attention, because a row referencing an image by filename only works if that exact file already exists in the media library. A row pointing at a photo never uploaded, or uploaded under a different filename, needs to surface as a clear per-row error — 'media reference not found for row 14' — rather than silently creating a draft with no image attached. A silent skip here is worse than a loud one, since nobody looks for a problem they don't know exists.

The safeguard worth repeating plainly: bulk import must never become a bypass route around the same approval and platform-policy checks a manually created post goes through. A festive campaign imported for a compliance-sensitive client still needs its wording reviewed the same way a hand-typed post would, and skipping straight to the schedule queue defeats the purpose of having approval at exactly the moment a mistake is most likely to slip through unnoticed.