Clarify the office role
Annual report production is usually led by investor relations, corporate communications, or the corporate secretary, with legal, finance, and the printer contributing. The executive office supports the CEO and board sections, the review calendar, and the final approval evidence. It does not own the whole document.
Write the role down before the cycle starts. Which sections does the executive office draft? Who approves the CEO letter?
Who coordinates the board portraits? Who is the single point of contact for the printer? A clear role prevents the assistant from becoming the de facto project manager for content outside their authority.
Identify the decision-makers for the cover, the theme, and the executive quotes. These choices often attract late opinions. A short approval list, agreed at the kickoff, reduces the number of review rounds.
Build the production calendar backwards
Start from the publication and filing dates. Work backwards through printer proofs, legal review, audit committee review, board approval, executive sign-off, design, and content drafting. Mark the dependencies, not just the deadlines.
Add slack before the legal and board reviews. Those stages rarely compress, and a late draft that reaches counsel on a Friday will not be reviewed by Monday. A calendar with no slack is a plan to miss the date.
Share the calendar with every contributor and name the person accountable for each milestone. A calendar without owners is a wish list. Review it weekly, and flag slips as soon as they are known rather than at the deadline.
Run a single content tracker
Use one tracker for every section, image, approval, and data point. Each row should show the owner, the status, the due date, the version, and the evidence of approval. Multiple trackers create conflicting versions and duplicated reminders.
Track the dependencies between sections. The CEO letter may depend on the financial highlights; the board section may depend on the governance disclosures. A section that is “done” but waiting on a number is not done.
Keep the tracker visible to contributors without giving everyone edit access. A read-only view with a named editor per row reduces accidental changes and makes the status trustworthy.
Coordinate review rounds without version drift
Number every review round and every file. Use a naming convention that includes the section, the round, and the date. A folder of files called “final,” “final2,” and “final review” is a version-control failure waiting to happen.
Consolidate comments into one review log. Each comment should have an owner, a disposition, and a link to the change. Do not let reviewers send comments in separate email threads; the editor will miss one.
Freeze the content before the final proof. After the freeze, changes should be limited to corrections and legally required edits, each recorded in a change log. A late design change can invalidate the printer’s proof and the board’s approval.
Manage disclosure and approval evidence
Confirm which sections require legal, audit, or board review. Keep the approval evidence with the final version: who approved, when, and which draft. A verbal approval is not enough for a document that will be published.
Check the forward-looking statements, the executive quotes, and the board biographies against the approved source. A biography that omits a current role or a quote that promises a result can create a disclosure problem. Route the question to counsel rather than editing for style alone.
Keep a secure archive of the final files, the approvals, and the printer’s proof. If the report is challenged or corrected, the archive shows what was approved and what was published.
Support the printer and digital release
Confirm the print specifications, the file format, the color profile, and the proof deadline. The printer should have one named contact and one approved file. A last-minute file from a different contributor is a recipe for a wrong cover or a missing page.
Check the digital version separately. Links, alt text, reading order, and file size matter for the website and for accessibility. A print-ready PDF is not automatically a good web document.
Plan the release sequence: the filing, the website posting, the internal announcement, and the media or investor distribution. Give each step an owner and a time, and confirm who is allowed to speak publicly if the report draws questions. The executive office may only handle the CEO’s message, but it should know when the report goes live.
Capture lessons after publication
After the release, hold a short retrospective with the core team. What arrived late? Which review round added the most delay?
Which approval was unclear? Record the answers while the details are fresh.
Update the calendar and the tracker template for the next cycle. If a section consistently needs two extra weeks, build that into the plan rather than repeating the scramble. If a reviewer consistently misses the deadline, escalate the pattern with evidence.
Archive the final package and close the tracker. The next cycle should start from a proven template, not from a search through last year’s email. The executive office’s contribution is continuity, and continuity is built after the report ships, when the loose ends are written down rather than remembered.
Background sources consulted for this workflow: Division of Corporation Finance; Staff Guidance; Audit and Assurance Resources; Governance Resources.