A Family Office Reporting Calendar That Survives Late Data

A family office can promise a report by the 14th and still leave the most important dates unstated. Which sources had to arrive by the 2nd? Which figures reflect September 30, and which still carry a June valuation? When does a reviewer have to decide whether a missing file changes the report or its release date?

A useful family office reporting calendar connects those decisions. It names the source cutoff, the handoff between preparation and review, the final approval window and the recipient date. It also says what happens when an input is late. The example below is a fictional quarter-end schedule, not a claim that every office should close on these dates.

01Give Each Report More Than One Date

For each output, distinguish four clocks:

• As-of date: the period the report is meant to describe, such as September 30.
• Source effective date: when each underlying statement or valuation actually measures the asset or transaction.
• Receipt cutoff: the last time an input may enter the planned close without an explicit exception decision.
• Release date: when an approved version reaches named recipients.

The four dates may not match. A bank statement can cover September and arrive October 2. A private-fund value in the same pack may still be dated June 30. Sage's family-office reporting guidance notes that alternative-asset values can lag and that their as-of dates need to be clear. The Asora investment-reporting template also recommends one cutoff time per report and explicit valuation timing and preliminary/final status. Neither source sets a universal deadline for a particular family office.

Start with the actual decisions the recipients make. The principal may need a cash and exposure summary; the investment committee may need a performance pack; the controller may need reconciled entity figures. A single delivery date should not hide different source dependencies or authorize a dashboard to substitute for a reviewed report.

02A Copyable Calendar for One Reporting Cycle

For every recurring output, record period end, audience, source register, cutoff, preparation owner, review owner, approver, planned release, exception route and version location. Put the exception route and version location on the calendar record itself: [escalate to role/channel by time] and [approved pack + source-register location]. The next cycle can reuse those fields while changing dates and owners where the process changes.

The following example is entirely illustrative. North Quay Family Office plans a principal-facing Q3 pack for Wednesday, October 14, 2026, covering a period ending September 30. The office sets its own source cutoff at 5 p.m. on Friday, October 2. It has agreed that the latest approved private-fund NAV may carry an earlier effective date if it is labelled. These are office choices, not industry standards or external filing deadlines.

This is a dependency chain, not six isolated reminders. If the controller's work is incomplete on October 6, the CIO does not inherit an apparently finished set of numbers. If the CIO has not approved an affected section by October 9, the CFO cannot treat the planned October 13 sign-off as automatic. The calendar should specify the latest decision time for a revised release, not simply show an overdue task in red.

The sample pack has an internal source register. A compact entry for each input looks like this: Custody A | Sep 30 positions | received Oct 2, 10:14 | owner: operations | reconciled Oct 6 | pack sections: allocation, return. The point is not the pipe format. The reader must be able to move from a released figure to the source version, the receipt date and the person who reviewed the exception.

03Plan for a Fund NAV That Will Arrive Later

North Quay's private-fund administrator will not deliver a September 30 NAV by the October 14 release. The latest approved mark is June 30. That is a planned timing difference, not a missing file that the controller discovers on release day. The office can still show the holding with a June 30 valuation label if its policy and reviewers permit it. It separately records capital calls, distributions and other activity effective through September 30 when supported by source files received by the October 2, 5 p.m. cutoff; it does not admit October activity into Q3 or silently transform those transactions into a new September NAV.

In PACK-Q3-v1, the private-fund line should therefore state something like: “Latest approved NAV: June 30, 2026. September 30 valuation pending from manager. September capital activity is shown separately. This figure is not a September 30 manager mark.” The disclosure belongs beside the figure and in the source register, not only in a footnote far from the decision it affects.

The ILPA reporting template concerns quarterly GP-to-LP reporting. It does not set North Quay's recipient date or prove when this particular fund's statement will arrive. The office must use the manager's actual schedule. In this fictional case, the September statement arrives November 16. The reporting lead logs its receipt and asks whether a separately approved supplement is needed or the value should enter the next cycle. Nobody edits the already released October pack without a versioned correction and recipient notice.

04Replan an Essential Source That Misses Cutoff

Now change one fact: a custody positions file due October 2 has not arrived. This is different from the planned fund-NAV lag. The missing custody file affects allocation and performance figures that the October 14 pack promised to cover. Entering zeros, copying an old positions file without a dated label or letting the report move silently through review would create a false picture.

The exception record needs a decision, not merely a reason for lateness:

If the file still has not arrived by the new decision point, the office must replan again. October 19 is an illustrative target, not a guarantee. The FOS reporting warning-signs guide covers how to diagnose a recurring exception; this calendar shows who changes the schedule and what recipients are told in this one cycle.

05Make the Release Record Reusable Next Quarter

After release, save the approved pack version, source register, open-exception decisions, approval record, recipient list and send timestamp together. For each missed gate, capture the planned date, actual date, owner, reason and decision. This lets the reporting lead distinguish a one-off provider delay from a cutoff that the office sets too early every quarter.

The calendar does not replace review of the figures. The FOS investment-performance reporting guide owns the return and release tests. Here the calendar makes space for those tests before the report is promised to readers.

Before the next cycle begins, the office should be able to answer: Which input determines the earliest credible release? Which review window protects the recipient from an unreconciled figure? Which known lags can be labelled, and which missing sources require a new promise? A calendar that answers those questions can survive a late file without presenting a late or incomplete report as though nothing changed.