When delivery work gets busy, business development often disappears. When a project ends, the pipeline suddenly feels urgent again. A weekly 90-day review helps you see that gap while you still have choices.

The review is simple: list what could happen in the next 30, 60, and 90 days; check the evidence behind each opportunity; compare the pipeline with your available capacity and cash needs; then choose three actions for the coming week. You do not need a sophisticated CRM or a pretend-precise forecast. You need an honest view of what is real, what is uncertain, and what needs attention.

This worksheet complements our guide to pipeline coverage, which explains how to think about future work relative to business needs. Here the focus is the weekly operating habit that keeps the picture current.

Set up three horizons

Use the next 30 days for decisions that can affect near-term work: active proposals, client renewals, scoped introductions, and available delivery capacity. The 31–60 day horizon includes buyer planning cycles, expected project starts, and relationships that need a specific follow-up. The 61–90 day horizon is where you nurture promising accounts and build future sources without pretending those conversations are current revenue.

The windows are planning tools, not sales-stage labels. A proposal may sit in the 60-day horizon if procurement will take that long. A former client might be a 30-day opportunity if a new need has already been discussed. Record the date when a decision could happen and why you believe it.

Also list committed work separately. Signed projects and retained clients affect capacity and cash, but they should not be mixed with uncommitted possibilities. Keep unpaid invoices separate too. A client promising to pay is a different fact from cash received.

Build a worksheet with only useful fields

One row per opportunity is enough. Include the client or organization, source, problem, proposed service, current stage, evidence for that stage, approximate value or range, likely decision date, potential start date, capacity required, last meaningful interaction, next action, and next-action date. Add a short note for the largest uncertainty.

You can use a spreadsheet, notebook, or CRM. If you already have a system, resist adding fields merely because the software supports them. A field earns its place when it changes a decision. Keep contacts and opportunities distinguishable without turning the review into data entry.

Be strict about stages. “Qualified” should mean you understand the client problem, who can decide, why the work matters now, and why your offer fits. “Proposal sent” means a proposal reached the people involved in the decision. “Verbal yes” is not a signed agreement. If a record lacks a next action, either add one or move it out of the active pipeline.

Inspect the evidence, not just the total value

Many pipeline dashboards invite you to multiply every deal by a standard probability. That can be useful in a mature business with enough of its own outcome data, but a solo practice often has too few comparable deals for a stable rate. A large weighted total may look reassuring while the underlying work depends on one client, one agency, or one unconfirmed deadline.

Instead, ask three questions for every important item. What has the buyer actually done? What must happen next? What could prevent the work from starting? A scheduled stakeholder meeting is stronger evidence than an enthusiastic first call. A clear purchase process is stronger than a promised “quick decision.” Record facts and your interpretation separately.

If you do have reliable historical data, use it cautiously and segment it. Referrals, inbound inquiries, and cold outreach may behave differently. So may small projects and long procurement cycles. Any probability you use should be your editable assumption, not a general claim about what freelancers convert.

Put capacity beside demand

Future revenue means little if you cannot deliver the work responsibly. For each potential start date, estimate the weekly hours and review burden the engagement would require. Compare that with committed delivery, meetings, administrative work, time off, and the business-development time you intend to protect.

This may expose a useful tension. You can have a thin pipeline but no near-term capacity, or a full pipeline made up of work that would all start in the same month. In the first case, invest in longer-horizon relationships and better-fit offers. In the second, discuss start dates, phased scopes, or trusted partner support before making commitments. Make the accept, wait, or refer decision against your real delivery capacity.

Do not count every tentative opportunity as if it will fill the calendar. Create a low, middle, and high scenario instead. In the low case, only signed work lands. In the middle case, one well-supported opportunity starts. In the high case, several do. Ask whether each scenario is manageable and what decision you can make now to reduce its downside.

Choose three actions for the week

A review is complete when it changes your calendar. Pick one action that protects a live opportunity, one that develops the next horizon, and one that improves your future pipeline or positioning. Examples include confirming a decision date, sending a relevant case example to a buyer, asking a former client about a known upcoming planning cycle, or refining an offer that repeatedly attracts the wrong inquiries.

Make each action specific enough to execute without reopening the whole worksheet. “Follow up with prospects” is not specific. “Send the audit scope question to Maya on Tuesday and ask who will approve the budget” is. Add an owner and date even if you work alone; you are distinguishing an intention from a commitment.

Limit the list deliberately. If there are ten equally urgent actions, your stage definitions or prioritization may need work. Small, consistent movement is easier to sustain alongside delivery than a heroic burst once a quarter.

A sample 20-minute review

Imagine you have a signed engagement ending in five weeks, a proposal awaiting procurement, an agency introduction with no end-client conversation, and two past clients who mentioned work later in the year. First, update the signed project’s completion and invoice dates. Then mark the proposal’s real decision milestone: procurement review next Thursday, not “probably closing soon.” Ask the agency when you can speak with the client and what rate range is approved. Give each past client a relevant future trigger rather than treating both as open deals.

Your next three actions might be to confirm procurement timing, request the agency’s decision process, and prepare a concise update for one past client. Notice that none requires writing a new proposal. The review directs effort toward the decisions currently holding the pipeline back.

Learn from what actually happened

At month end, review opportunities that moved, stalled, or disappeared. Which source produced qualified conversations? Where did scope or authority remain unclear? How long did a proposal stay open before a real decision? Which opportunities were delayed by your own capacity? Record outcomes without assigning blame. This is operational evidence for improving your process.

Keep the 90-day view rolling. Move the windows forward each week, close dead records, and adjust your actions when evidence changes. SmartBid’s opportunity and outcome tracking can help you connect pursuit decisions with what followed. The point is a calmer, more accurate next decision, not a larger-looking pipeline.