Posting reconciliation matches each authorized publication request to a confirmed live post or an explicit unresolved outcome. It connects the content plan to execution evidence. The essential join is a stable publication identifier, supported by the destination account, approved asset version, caption, and publishing window.
What does a reconciliation sheet need?
Keep planned information and observed results in separate columns. Planned fields describe what should happen; observed fields describe what actually happened. If the operator overwrites the requested time with the actual time, the sheet loses the information needed to assess delivery.
Use the publication identifier as the primary reference and retain any job identifier from the posting tool. Add the public URL, observed account, completion time, media version, and exception category. A screenshot may support an investigation, but a screenshot alone is not a durable substitute for the destination reference.
Why is an accepted job not enough?
A submission can be accepted before a post becomes publicly available. Upload processing, account restrictions, review, connection failures, or an operator mistake can interrupt the remaining steps. Separate submitted from published so the report does not count attempted work as completed delivery.
Atlassian 2025 State of Teams found: Workers spent 25% of their week searching for information; 50% had unknowingly duplicated project work.
The research describes knowledge work broadly. Its relevance here is the cost of reconstructing missing context: stable identifiers and result fields make routine questions answerable from the record itself. They also make duplicate work easier to detect before someone retries an uncertain job.
How should exceptions be classified?
| Exception | What to investigate | Next action |
|---|---|---|
| Missing result | Submission and destination status | Confirm before retrying |
| Wrong account | Routing instruction and execution | Escalate to content owner |
| Wrong revision | Approved file and queued copy | Decide correction or removal |
| Duplicate publication | Original and retry job histories | Identify authorized final result |
| Late delivery | Requested window and blocker | Record cause and revised expectation |
Keep the categories small enough for operators to use consistently. Store the detailed explanation in a separate note. “Failed” without a cause is not a useful weekly report because it does not show which team can resolve the problem.
What does a worked reconciliation look like?
Suppose an agency requests a clip on its editorial and regional accounts. The editorial post has a confirmed URL; the regional submission has no confirmed outcome. Record the first as published and the second as awaiting investigation. Do not mark the entire asset complete or create another regional post immediately.
The operator checks the regional account and the original job. If the post exists, attach its URL. If the attempt conclusively failed, record that failure and create a linked retry after confirming the instructions are still valid. This preserves the distinction between recovery work and a new planned publication.
How often should reconciliation happen?
Reconcile around the operating cadence and the client’s need for evidence. Time-sensitive campaigns may require confirmation after each publishing window, while routine batches may use a scheduled review. Agree on who investigates unresolved jobs and when the client receives an exception report.
Separate delivery reporting from performance reporting. A correctly published post can perform poorly, and a viral post can still have been published with the wrong caption. Use the pilot metrics guide for audience outcomes after execution has been verified.
Record redirects or removed posts as later observations without overwriting the original publication evidence. This preserves a useful history for client reporting and corrections.
How Conbersa Fits Publication Reporting
Conbersa’s distribution service includes reporting around account activity. Agree on the evidence you need for client reconciliation, including destination references and exception handling. Start with the posting spreadsheet template so incoming instructions and outgoing results use compatible identifiers.