The weekly report an event agency owner should actually read

On Thursday night or Friday morning, someone in the agency builds the weekly report. A producer or the finance lead copies figures out of the budget Excel (three tabs, two versions), the supplier sheet, the accounting software, a few email threads and the approvals that happened on WhatsApp. The owner gets a long summary on Friday afternoon. Most of it says what the team did, and very little of it says what the owner needs to decide.

A weekly report worth reading is shorter. It answers five questions for every live project: what we can still win, where margin is drifting, which collections are due, what we are about to spend, and which decisions are waiting on the owner. For each of them, the answer already sits in eventIQ's Business Engine, so the weekly review becomes reading and deciding instead of assembling.

Key takeaways

• Report what needs deciding. "Catering quotes are in" helps nobody decide anything.
• Five questions cover most of what an owner needs: pipeline, margin drift, collections, money about to leave, decisions waiting.
• In eventIQ each answer lives on the project or opportunity record, so nobody copies it into a new Excel every Friday.
• Collections and unapproved spend are the items owners need earliest and most often miss.
• Drop task lists, raw exports and slides rebuilt from scratch.

Why most weekly reports fail

They fail because they are rebuilt by hand from sources that don't agree. The budget lives in one Excel with several tabs and versions, supplier costs sit in another sheet, invoices are in the accounting software, and approvals are scattered across email and messages. Whoever builds the report picks a version of each, and two people asking the same question can get two different margins.

They also report the wrong thing. "Site visit done, catering quotes received, AV brief sent" is a record of effort. The owner can't act on it. Margin usually shows up only at project close, when nothing can be changed.

And they arrive late. By the time a summary built on Thursday is read on Friday, a supplier invoice has landed and a client has asked for one more change.

eventIQ's Business Engine is built around the opposite idea: the proposal, budget, suppliers, expenses, approvals and invoices stay connected on one record per project. The weekly report then becomes a short list of questions you read from those records.

1. Pipeline: what can we still win, and what should we park?

Start with work that isn't won yet, because it decides next quarter's revenue. For each open opportunity the owner needs three things: its stage, the next critical date and whether the client is engaging.

In eventIQ's proposals and lead management, every opportunity is a record with its meetings, notes, files and next actions. Stages follow how your company sells, such as creative, budgeting, revision, negotiation and confirmation. Critical dates and next actions stay visible, and open notifications show when the client has opened the proposal page.

So the pipeline section of the report reads like this: which opportunities moved stage this week, which have a deadline coming, and which proposals the client opened but hasn't answered. Then the owner decides: chase, reprice or park. If a proposal has been through several rounds, our guide to event proposal revisions covers keeping those versions on one record instead of Excel tabs.

2. Margin drift on live projects

This is the section owners most want and least often get. The question is simple: is each live project still on course for the profit we planned, and if not, which lines moved?

In eventIQ's budget and finance module, suppliers are assigned directly to budget lines, so a venue or AV change shows up on the line that carries that cost. Project expenses go through approval and are monitored against a defined amount or share of the budget, so you can step in when spending or expected profitability starts to drift. Planned and actual profitability are compared on the same underlying data, and scenarios let you see what happens to revenue and profit if attendance, supplier cost, scope or selling price changes.

For the report, that means a short line per project: planned margin, where it stands now, and the two or three lines that moved it. If the client has made changes in the client area, they show up on the same record instead of in an Excel that came back by email. For the habit behind this section, see real-time budget control.

3. Collections and expected payments

Overdue collections are easy to leave out of a weekly report because they feel like finance's job. They belong near the top. An agency often pays venues and suppliers before the client pays its invoice, so a late collection on one project can tie up cash that every other project needs. The owner is usually the one who can make the call that gets it paid.

eventIQ tracks what should be billed, what has been invoiced, what has been paid and what still needs collection on the project record. Sales-invoice requests are prepared from that record, and you can send reminders for outstanding collections before they become a closing problem. Through the accounting integrations, with ready-made connections for Paraşüt, Xero and QuickBooks or a custom integration, invoices, payments and collections come back into project control.

In the report: per project, what is invoiced and unpaid, what is due to be billed, and which collections need a reminder or a call from the owner.

4. Money about to leave

The fourth question looks the other way: what are we committed to paying, and does it match what we agreed?

eventIQ checks purchase invoices against the intended supplier and amount, so an invoice that doesn't match its budget line stands out before it is paid. Expense, advance, payment and credit-card requests run through approval workflows, and the integration sends payment and advance requests to finance with the project context attached.

For the owner, this section lists the larger pending requests and any supplier invoice that differs from what was budgeted. Our guide to event supplier management covers keeping quotes, invoices and payments on one supplier record.

5. Decisions waiting on the owner

The last section is the one that should take the owner's time. It lists everything that can't move until they say yes or no.

In eventIQ's approval workflows, each stage is assigned to a role or a named person, with monetary limits so smaller requests finish with fewer approvals. Paths can differ by department and transaction, and every decision is recorded. So the requests that reach the owner are the ones above their limit or assigned to their stage, which is exactly what this section should show: project and budget approvals, larger expense or payment requests, and purchase or sales invoices waiting on them.

Scope changes belong here too. When a client asks for something new on the client proposal page, which supports review, comments and approval, the owner should see it alongside its effect on margin while there is still time to respond.

What to leave out of the weekly report

• Activity lists. What the team did this week belongs in project meetings.
• Every task. The owner needs the exceptions.
• Raw exports. A 400-row export moves the work to the reader.
• Slides rebuilt from scratch. If the numbers live on the records, read them there.

If a section has nothing to flag, one line saying so is enough.

A suggested routine for a 20-minute review

This is a suggested routine; we haven't measured it across agencies:

1. Open the pipeline and note which opportunities need a decision to chase, reprice or park.
2. Go through live projects for margin drift and pick the ones to look at more closely.
3. Check unpaid invoices and collections, and decide which need a reminder or a call.
4. Scan pending spend and mismatched supplier invoices.
5. Clear the approvals waiting at your stage.

Because the answers sit on the project records in Business Engine, the person preparing the review reads them from eventIQ instead of copying them into a new Excel each week.

FAQ

Which KPIs should an event agency track weekly?

Keep it to pipeline movement, margin drift per live project, collections and expected payments, committed spend and pending approvals. Add more only if the owner acts on them.

Should the weekly report include every project?

Include every live project, but give a line only to those with something to flag. A project on budget with no overdue collections needs a single "no change".

Who should prepare the weekly report?

Whoever owns the commercial record, usually the finance lead or a senior producer. With the numbers already on the records, the job is checking and flagging.

Try it on one live project

Pick one live project and ask the five questions about it. Then bring it to a Business Engine demo and walk it through as an opportunity, a budget with suppliers on its lines, approvals and collections, so you can see your next Friday review on the record. The platform tour and our page for event agencies show how the pieces connect.