Most rework in recurring reports traces back to a vague intake. If contributors do not know exactly what is required, when, and in what format, the report owner spends the cycle chasing rather than producing. A fixed intake process removes the ambiguity and is one of the cheapest improvements available.

This guide covers how to run report intake so inputs arrive right first time. It is the companion to The Reporting Workflow and How to Produce Recurring Reports on Schedule.

A report is late long before it is written. It is late the moment an input was unclear.

What a good intake does

Report intake is a request, a brief and a deadline. A good intake does three things:

  • Specifies the inputs – precisely, by name and format.
  • Names the supplier – one accountable person per input.
  • Sets the deadline – ahead of the data freeze, with a reminder.

Everything else is refinement. When these three are clear, inputs arrive on time and usable; when they are not, the report owner becomes a chaser and the cycle slips.

The intake template

A fixed intake template is the mechanism that makes intake consistent. It asks each contributor for:

  • The specific inputs required, listed by name.
  • The format and source expected – system, workbook or narrative.
  • The deadline for submission, ahead of the freeze.
  • The contact to resolve questions.
  • Any assumptions the contributor is making.

Sending the same template every cycle teaches contributors the shape of the request. By the third cycle, most inputs arrive clean without a reminder.

Briefing for recurring reports

A recurring report does not need a full brief each cycle, but it needs the deltas:

  • What changed since last cycle – new sections, new metrics, new emphasis.
  • The key questions this cycle’s report should answer.
  • Any known issues – a restated figure, a delayed data source.
  • The audience and any changes to it.

For a brand-new recurring report, the brief is fuller: the audience, the decision it informs, the structure and the definitions. After the first cycle, the brief becomes a short delta note attached to the intake.

Chasing without damaging relationships

Chasing inputs is unavoidable; doing it well is a skill.

  • Chase the owner, not the group. A broadcast reminder reaches everyone and is owned by no one.
  • Escalate on a schedule, not on frustration – for example, a reminder at minus two days, an escalation at minus one.
  • Make the ask small and specific so it is easy to comply with.
  • Close the loop. Tell contributors what their input changed, so the next request is taken seriously.

The intake is a relationship as much as a process.

Measuring intake quality

Intake is measurably improvable if you track a few numbers:

  • On-time input rate – the share of inputs received by the deadline.
  • First-pass usability – the share received in the right format without a rework request.
  • Chase effort – how much of the owner’s time goes to chasing.

A falling on-time rate signals a scheduling or clarity problem; a low first-pass usability rate signals a template problem. Both are fixable, and both are invisible without measurement.

A worked intake request

A concrete request shows what good intake looks like. For a monthly management report:

  • Subject: Management report – [month] inputs required by [date].
  • Attachments: the intake template and last month’s report.
  • For each input: what is needed, in what format, from which system, and who owns it.
  • Deadline: the date and time, ahead of the data freeze.
  • Escalation: who to contact if the input will be late.

A request like this, sent the same way every cycle, teaches contributors the shape and reduces chasing within a few cycles.

Intake for different report types

The intake varies with the report, but the principles hold.

  • Management and board packs: financial and operational inputs, plus commentary on variances.
  • Client reports: delivery data, results and account context.
  • Compliance reports: rule-defined data, with evidence and sign-offs.
  • Status reports: progress, risks and blockers, usually short and frequent.

The template changes; the discipline does not. Every intake names its inputs, its owners and its deadlines, and every intake is sent the same way each cycle.

Common mistakes

  • Vague requests. “Send the numbers” produces late, wrong-format inputs.
  • No named supplier. Requests sent to a group are owned by nobody.
  • No deadline ahead of the freeze. Inputs due at the freeze arrive after it.
  • Chasing the group. Broadcast reminders are easy to ignore.
  • No intake template. Each cycle reinvents the request and repeats the mistakes.

Frequently asked questions

What is report intake?

The stage where inputs and data are requested from contributors against a brief and a deadline. It is the first stage of the reporting workflow and the most common cause of lateness when it is done poorly.

What should a report intake include?

The specific inputs required, the format and source expected, the deadline, the contact for questions, and any assumptions the contributor is making.

How do you get contributors to deliver on time?

Name one owner per input, send a consistent template, set the deadline ahead of the data freeze, and chase the owner directly with a scheduled reminder and escalation.

Should the intake be the same every cycle?

Yes, for recurring reports. The same template, updated only for the deltas, teaches contributors the shape of the request and makes inputs faster and cleaner over time.

How do you measure intake quality?

Track the on-time input rate, first-pass usability, and the time spent chasing. A falling on-time rate signals scheduling or clarity problems; poor usability signals a template problem.

What if a contributor consistently delivers late?

Escalate the pattern, not just the instance. A chronic late input is a scheduling or accountability problem to solve in the post-cycle review, not a fact to work around each cycle.

Should the intake request go to individuals or a group?

Individuals. A request sent to a group is owned by nobody, and chasing a group is ineffective. Name one person per input and send to them.

How far ahead of the freeze should inputs be due?

At least one day, ideally two, so a late input has somewhere to land before the freeze. Inputs due at the freeze arrive after it.

What should an intake request not do?

It should not be vague, sent to a group, or due at the freeze. Those three mistakes account for most late inputs. Be specific, name a person, and set the deadline early.

How do you onboard a new contributor to the intake?

Send them the template, last cycle’s report, and a one-line explanation of what their input feeds. A contributor who understands why the input matters delivers it more reliably.

Should the intake template change each cycle?

Only slightly. Send the same template with the deltas updated – new metrics, changed owners, a known issue – rather than rebuilding it. Familiarity is what makes contributors fast.

What if a contributor does not know the answer?

Have them flag it by the deadline rather than going silent. An early “I cannot provide this” is manageable; a silent no-show on the freeze date is not.

How do you handle an input that arrives in the wrong format?

Return it once with the expected format and a short explanation, and note it in the intake metrics. Repeated format errors usually mean the template is unclear, not that the contributor was careless.

How do you get senior contributors to prioritize the intake?

Give them the smallest possible ask, the earliest possible deadline, and the context for why it matters. Senior contributors respond to a clear, short, well-prepared request far better than to a chase.

How many reminders should an intake send?

Two: one at the deadline minus two days, and one escalation at minus one. More reminders dilute their effect; fewer let the deadline pass unnoticed. Route both reminders to the named owner, not to the group, so the chase has somewhere to land without a broadcast.

How do you handle an input that is needed from outside the firm?

Build the external deadline with more buffer, name a single contact, and agree the format in advance. External inputs are the least controllable, so they get the most schedule protection – and the earliest chase, because there is no internal owner to escalate to.

Next step

Fix intake before you fix anything else. A consistent template, named suppliers and a deadline ahead of the freeze will remove most recurring-report lateness within two cycles. Download the Reporting Calendar Template to schedule the deadlines, and see The Reporting Workflow for how intake fits the wider process.

Sources

  • APMP, Body of Knowledge: requirement analysis, kickoff and content plans, applied to recurring report production.
  • Onetribe Advisory (2026), citing industry research: mapping reporting activity is the first step to reducing manual effort.

Good-practice claims are cited from their sources; no statistic in this article is invented.