Work item and period
Identify the client or entity, accounting period, task and relevant account or return section. Avoid vague labels such as “pending” without context.
Who you speak to, what arrives and when, and what happens when something needs a decision — agreed in writing before the work starts.
Communication expectations are set during onboarding and recorded in the engagement workflow.
Each engagement defines who owns questions, how exceptions are raised, which decisions stay with your team and how work moves through preparation and review. A useful arrangement does not depend on a message being noticed by the right person; it gives each item an owner, a status and a next action.
Reporting cadence, escalation contacts and close-calendar handoffs are agreed before recurring work begins. We document the process rather than relying on assumed availability. How the offshore model works covers the wider delivery approach.
A status message should help the recipient decide what happens next, not simply announce that work is in progress.
Identify the client or entity, accounting period, task and relevant account or return section. Avoid vague labels such as “pending” without context.
Show whether the item is ready for review, being prepared, blocked by missing information or waiting for an authorized decision.
Link or refer to the source report, statement, invoice or workpaper. State the amount or discrepancy where relevant and explain what does not agree.
Name the person or role expected to act, what is needed and the agreed due date or next checkpoint.
Illustrative exception update
“March operating-account reconciliation: one bank debit does not match the ledger description. The statement line and current ledger entry are linked in the workpaper. Preparation is paused for this item; please confirm the correct coding or provide the supporting invoice. The remaining reconciliation items are ready for review.”
Example wording only; actual status, evidence and ownership should come from the engagement records.
The person preparing a schedule should identify the issue and assemble its evidence. The authorized reviewer decides how it is resolved.
A clear escalation path distinguishes a routine processing question from a blocker, a deadline risk or a matter requiring professional judgment. The engagement should say which issues can be resolved using documented instructions and which must return to the CPA firm, controller, property manager or other authorized contact.
For tax work, preparation notes can identify missing documents, inconsistent inputs and unresolved questions. Tax positions, advice, substantive review, approval and filing remain with the responsible tax professional. For accounting work, coding or posting outside the approved rules should be held for direction rather than guessed.
Record the affected file, period, amount or workpaper and the source evidence.
Mark the item as routine, blocked, deadline-sensitive or awaiting a professional decision.
Send it to the named contact through the agreed channel, with the requested action stated clearly.
Record the response, update the workpaper or task status and carry any remaining item into the next report.
The right frequency depends on transaction volume, deadlines and reviewer availability. The important part is agreeing it before the first recurring cycle.
| Checkpoint | What to communicate | Decision or output |
|---|---|---|
| Recurring task queue | New items received, work completed, blocked records and items waiting for approval. | Priorities and next actions for the agreed work period. |
| Weekly or agreed review | Open exceptions, ageing items, capacity constraints and upcoming deadlines. | Escalations, scope clarification and revised ownership where needed. |
| Month-end close | Reconciliation status, missing support, proposed adjustments and schedules ready for review. | Reviewer comments, approval decisions and the close items still outstanding. |
| Seasonal or deadline work | File readiness, missing documents, preparation status and items that could affect the agreed deadline. | A prioritized list for the responsible reviewer or client contact. |
A short written operating note prevents repeated questions about where work belongs, who can approve it and how a blocker is raised.
The plan should also explain what happens when the normal contact is unavailable, when a source record arrives after cut-off and when a requested task falls outside the agreed scope. The escalation route should not bypass the firm's own approval, client-consent or professional-review process.
For the wider operating sequence, see how onboarding sets the workflow, how review and quality checks are organized and the CPA-firm support overview.
Tell us your review points, handoffs and who needs to hear what, and we will describe the reporting rhythm we would set up.
Bring your review points, close calendar and escalation needs. We will describe the communication rhythm before you commit.