The 30-Minute Weekly Operating Review: Cash, Expected Customer Payments, Projects, and Next Actions

A small team rarely needs another long status meeting. It needs a short habit that catches the changes capable of disrupting the next week: a stale account balance, a delayed customer payment, project costs moving faster than progress, or an important follow-up with no owner.

Those signals do not mean the same thing. A balance is a position at a point in time. A cash-flow chart summarizes recorded movement. An expected payment remains an expectation until money is recorded. A project margin may be a forecast built from budgets, progress, linked transactions, and time entries.

A useful review brings those signals together without flattening them into one misleading number.

The agenda below fits a 30-minute meeting. The team can use Figena for supported records and views while keeping an explicit external list when customer invoices and collections live elsewhere.

Key takeaways

• Review position, movement, expectations, and project economics separately before connecting them.
• Treat balance source and freshness as part of the number, not as optional metadata.
• Keep expected customer payments distinct from recorded actual-status income. Figena does not currently provide a complete accounts-receivable subledger or invoice-aging workflow.
• Review projects through progress, overdue and blocked work, linked income and costs, estimate at completion, forecast margin, and estimated unbilled time.
• End with a small decision log: one owner, one due date, and one next check for every material exception.
• Use AI as an optional, permission-aware briefing aid, not as proof that every record has been inspected.

What this review is—and what it is not

The weekly operating review is a decision meeting, not an accounting close. Its purpose is to identify what changed, decide what deserves attention, and make responsibility explicit before the team returns to daily work.

It should not attempt to certify financial statements, recreate a complete receivables ledger, or settle every project detail. If a balance cannot be reconciled, a payment is disputed, or a project forecast depends on missing inputs, the right outcome is a named follow-up—not a guess made to finish the agenda.

Use five distinct signal types:

This vocabulary prevents a common meeting failure: someone says “revenue,” another person hears “invoice,” and a third assumes “cash.” The review should make those differences visible every week.

Prepare the review before the clock starts

The meeting stays short only when the operating context is stable. Set these conventions once, then revisit them when the business changes:

1. Choose one workspace. Do not combine unrelated operating entities merely to create a convenient total.
2. Set a cutoff. Decide whether the review includes activity through the previous business day, the meeting start time, or another explicit boundary.
3. Confirm the reporting currency and time zone. They affect how periods and converted values are interpreted.
4. Name the meeting owner. This person moves the agenda and records decisions.
5. Bring the customer-payment source. If invoices and collection status are managed outside Figena, open that source beside the workspace. Do not recreate its values from project status.
6. Define materiality. The team should know which changes require discussion and which can be handled asynchronously.

Before the meeting, the owner should open the relevant accounts view, the filtered transaction view, the active project list, and the action or reminder queue. If an account depends on statement imports, unresolved matches, or manual updates, that context should be visible before anyone interprets the balance.

Minutes 0–3: establish the frame

Begin by stating the workspace, cutoff, base currency, and any known data gaps. This takes less than three minutes and prevents much longer arguments later.

A useful opening sounds like this:

We are reviewing the current workspace through Tuesday close in the workspace reporting currency. Two account balances were updated from the latest statement, one import still has unmatched lines, and customer payment dates come from the collection list maintained by operations.

Then ask one question: Is anything missing that would make today’s decisions unsafe?

Examples include a missing statement, a transaction in the wrong account, unsubmitted time, or an unconfirmed payment date. Record the gap; do not treat missing data as zero.

Minutes 3–8: review cash position and recorded movement

Start with position. Review bank, card, and cash accounts according to what each account represents. A credit-card liability is not spare cash. A physical cash count has different evidence from an imported bank balance. A converted home-currency total should not erase the original currency or the age of the underlying balance.

For each material account, check:

• the recorded balance;
• the balance source;
• the “as of” time or statement period;
• whether imported activity still needs review;
• whether a recent reconciliation supports reliance on the number.

If the source or update time is missing, downgrade confidence. A precise-looking number with uncertain provenance is still uncertain.

Next, review recorded movement for a consistent period. Thirty days is a practical starting point for many teams, while a shorter or longer range may fit the operating cycle. Compare recorded income, expense, and net movement, then open the transactions behind an unexpected change.

Keep the questions operational:

• Did the current position improve or deteriorate since the previous review?
• Which recorded income or expense explains most of the movement?
• Is a large change recurring, one-time, transferred between accounts, or incorrectly classified?
• Does the transaction belong to the account, client, vendor, or project currently attached to it?
• Is there an unresolved statement line that could change how the team reads the period?

When evidence is incomplete, create a reconciliation follow-up. The resource guide on reconciling an account balance offers a useful sequence: match the same account and date boundary, investigate missing or duplicate items, document adjustments, and recheck the reports.

Capture each material exception, its consequence, and the person who will resolve it; do not repair every transaction in the meeting.

Minutes 8–14: review expected customer payments

This section replaces a vague “receivables” conversation with a more disciplined question: Which customer cash do we expect, what supports that expectation, and what must happen next?

Figena currently does not provide a complete accounts-receivable ledger, invoice-aging report, or automated collection workflow. If invoices are issued in another system, that system or a controlled collection list remains the source for invoice number, amount, due date, dispute status, and collection history.

Bring only the items material to the next operating period. Review them in five practical groups:

Figena can add useful operating context without pretending to be the invoice ledger. A project may show actual linked income and an estimate of unbilled time based on billable time value compared with recorded project income. Planning views can also represent expected recurring items and dated commitments with confidence or probability. Those are planning signals. They are not proof that an invoice exists, is due, or will be paid.

For every material expected payment, capture four fields in the meeting record:

• expected amount and currency;
• expected date or date range;
• evidence source and current confidence;
• owner and next customer-facing or internal step.

If the team cannot fill those fields, the item is not ready to support a confident cash decision.

Minutes 14–22: review project delivery and economics

Move from customer cash expectations to the work that creates or consumes economic value. Open the active projects view and focus on exceptions rather than narrating every project.

First review execution:

• weighted progress;
• overdue work items;
• blocked work items;
• the next meaningful milestone;
• changes in health or end date;
• unassigned work that could become a delay.

Then review economics where the current member has access. Figena’s project control center can combine budget lines, linked actual-status income and expense transactions, and permitted time-entry data. It can show actual income, external expense, labor cost, actual cost, estimated unbilled time, estimate at completion, forecast revenue, and forecast margin.

The formulas matter. Labor cost is the sum of paid minutes divided by 60 and multiplied by the available home-currency cost rate. Actual cost adds that labor cost to linked actual-status external expense. At weighted progress of 10% or more, estimate at completion is actual cost divided by the progress ratio; below 10%, it is the greater of actual cost or budget cost. Forecast revenue uses budget revenue when it is positive; otherwise, it is the greater of recorded project income or billable time value. Estimated unbilled time is the positive portion of billable time value minus recorded project income—not an invoice balance.

Ask these questions for any project with a material change:

1. Is progress credible? A forecast built on stale progress will look more precise than it is.
2. Are all relevant costs represented? Missing time, missing cost rates, or unlinked expenses can overstate margin.
3. Has labor been counted twice? External expense and calculated labor are separate; posting the same labor cost as an expense can duplicate it.
4. Does forecast revenue reflect the current commercial expectation? A budget is still a plan.
5. Is unbilled work operationally ready for billing? Delivery evidence and external billing terms still matter.
6. What changed since last week? Focus on the driver, not only the resulting number.

Use project risk signals as prompts. Overdue or blocked work and an estimate at completion above budget deserve investigation, but the signal should lead back to its evidence. It should not replace the project owner’s explanation.

The output of this section is not a longer project report. It is a short list of interventions: update progress, link a missing transaction, correct a budget, submit time, resolve a blocker, prepare external billing, or revisit the delivery plan.

Minutes 22–27: turn exceptions into next actions

Now convert the unresolved items into owned work. Figena’s Attention workspace separates action-required items, reminders, and notifications. It can surface project work-item events, including assigned, due, and overdue work, and it can summarize active and overdue reminders. Teams can filter by source and priority and snooze an item when deferral is intentional.

Use reminders for due-date work that should not depend on memory. Use project work items when the action belongs to delivery. Keep an external collection task in the system that owns customer communication if that communication must remain with the invoice record.

Every action should answer:

• What is the next observable step? “Investigate cash” is vague; “match the three unresolved statement lines” is observable.
• Who owns it? A team name is not an owner.
• When is it due? “Soon” cannot become overdue.
• What will count as done? Completion may require a reconciled balance, a linked transaction, an updated project input, or customer confirmation.
• Where will the evidence live? Do not bury the only proof in meeting notes.

Limit the meeting to actions that change a decision, remove a blocker, or improve the reliability of next week’s review. Routine work can remain in the normal queue.

Minutes 27–30: record decisions and close the loop

Use the final three minutes to read back decisions, not to reopen discussion. A compact decision log is enough:

These are templates, not fictional performance results. Replace them with the team’s real records.

If a decision belongs to a project, Figena supports project activity types such as status updates, risks, and decisions. That can keep the operational rationale close to the work. The weekly review itself, however, is a team practice assembled across views; it is not a one-click statutory report.

Close with three statements:

1. the current cash position the team is willing to use, including any qualification;
2. the expected customer payments that materially affect the next period, with confidence and owners;
3. the project or action exceptions that could change those expectations.

An optional AI briefing step

Cilila AI can produce an evidence-backed, read-only brief from workspace sources available to the current member. It can help identify an initial place to look across projects, transactions, reminders, and other accessible modules. Its answer is constrained by permissions, source availability, AI configuration, and the records retrieved for the question.

Use it to form hypotheses, then inspect the relevant source records in their owning modules. The brief is not an exhaustive inspection or evidence that an action was completed. If AI or a source is unavailable, deterministic views and the team’s review remain authoritative. The guide to using AI safely provides additional review principles.

Common failure modes

Combining every number into “cash”

Recorded income, recognized revenue, forecast revenue, billable time value, expected customer payments, and bank balances answer different questions. Preserve the label and source of each number.

Treating unbilled time as an invoice

Estimated unbilled time can identify work worth investigating. It does not establish that the work is billable under the agreement, that an invoice has been issued, or that payment is due.

Letting the meeting become data entry

Correct a simple, consequential error when it is safe. Otherwise assign the repair and move on. The meeting’s job is to direct work, not absorb it.

Carrying actions without owners

If an exception remains important enough to discuss next week, it is important enough to have one named owner and one due date now.

Weekly review checklist

Before the meeting

• [ ] Confirm workspace, cutoff, time zone, and reporting currency.
• [ ] Review account balance sources and “as of” dates.
• [ ] Identify unresolved statement or transaction issues.
• [ ] Prepare the external expected-payment list, if applicable.
• [ ] Confirm that project progress, time, budgets, and links are reasonably current.

During the meeting

• [ ] Separate cash position from recorded cash movement.
• [ ] Separate expected customer payments from recorded income.
• [ ] Review only material project and action exceptions.
• [ ] Open the evidence behind unexpected changes.
• [ ] Assign one owner, due date, and completion condition per action.

After the meeting

• [ ] Place each action in the appropriate project, reminder, reconciliation, or external collection workflow.
• [ ] Record material project decisions close to the project.
• [ ] Correct data at its source rather than only in the meeting summary.
• [ ] Carry unresolved confidence limitations into the next review.

Frequently asked questions

Does Figena provide a complete accounts-receivable report?

No. Figena can connect projects with recorded finance transactions, calculate project operating signals such as estimated unbilled time, and include expected recurring items or commitments in planning. It does not currently provide a complete customer invoice subledger, aging report, DSO workflow, or automated collections process. Use the authoritative invoice source for those facts.

Is the cash-flow view a forecast?

The standard cash-flow series summarizes recorded actual-status income and expense transactions for the selected period. Figena also has separate planning views based on expected recurring occurrences and dated commitments, which may be weighted by confidence or probability. Keep historical actuals and planning forecasts visibly separate.

Should every active project be discussed?

Usually not. Review projects with material movement, overdue or blocked work, forecast pressure, uncertain inputs, or an upcoming decision. A complete list can remain available without becoming a spoken status report.

What if a balance is stale or cannot be reconciled before the meeting?

State the limitation, reduce confidence in decisions that depend on it, and assign reconciliation. Do not replace the missing evidence with an estimate unless the estimate is clearly labeled and appropriate for planning.

Can Cilila run the meeting automatically?

No. Cilila can generate a permission-aware, citation-backed read-only brief when AI and relevant sources are available. It does not guarantee exhaustive coverage, certify the numbers, or complete follow-up actions merely by describing them.

Who should own the review?

Choose the person best positioned to keep the agenda moving and maintain the decision log. That may be a founder, finance owner, operations lead, or project lead. Individual follow-up should still go to the person who can perform and verify the work.

Make the review repeatable before making it elaborate

A weekly operating review becomes valuable through consistency. Use the same definitions, the same order, and the same standard for evidence. Let the underlying records change; keep the review logic stable.

Start with position. Explain recorded movement. Review expected customer payments without calling them cash. Examine project economics without calling a forecast audited profit. Convert exceptions into owned work. Then stop at 30 minutes and let the team execute.

That rhythm gives a small team something more useful than a larger dashboard: a shared way to distinguish what happened, what is expected, what is uncertain, and what someone will do next.