Tabellab

Campaign Request Intake: Requested Lead Time, Minimum Lead Time by Size and Rush Flags per Team

Lesson 1 of 20Lab

All lessons
  1. Campaign Request Intake: Requested Lead Time, Minimum Lead Time by Size and Rush Flags per TeamLabFree
  2. Triage Scoring: Weighted Priority Scores with SUMPRODUCT, Ranks and an Approve or Waitlist DecisionLab Locked
  3. Sprint Capacity: Available Days, Net Hours after Leave and Overhead, and Capacity per RoleLab Locked
  4. Utilisation and Load: Project Utilisation, Total Load and Overload FlagsLab Locked
  5. Sprint Planning: Plannable Hours, Running Totals, Commit or Carry Over and Carry-Over HoursLab Locked
  6. Sprint Velocity: Completion Rates, a Moving Average, a Linear Forecast and Sprints to Clear the BacklogLab Locked
  7. Turnaround SLAs: Targets per Request Type, Met or Missed, Days over the SLA and SLA AttainmentLab Locked
  8. Turnaround Distribution: Mean, Median, 90th Percentile and the Share within the SLALab Locked
  9. Approval Rounds and Rework: Hours per Round, Rework Hours, First-Pass Rate and Rework ShareLab Locked
  10. Campaign QA: Errors per 100 Checks, a Target Status, the Overall Error Rate and the Share of Clean LaunchesLab Locked
  11. QA Escapes: Escape Rate per Launch, the Overall Escape Rate and a Pareto Analysis of Defect CategoriesLab Locked
  12. QA Control Limits: Weekly Error Proportions, a Centre Line, Upper Control Limits and SignalsLab Locked
  13. Backlog Ageing: Age in Days, Age Bands with an Approximate Lookup, Counts per Band and Waiting TimeLab Locked
  14. Backlog Flow: Arrivals, Completions, Net Flow, Backlog Trend and Little's Law Waiting TimeLab Locked
  15. Tool Stack Costs: Cost per Active User, Seat Utilisation, Unused Spend and Low-Use FlagsLab Locked
  16. Seat Right-Sizing: Right-Sized Licences with ROUNDUP, Savings per Tool and a Renewal WindowLab Locked
  17. Cost Allocation: User and Request Shares, Allocated Tool Cost per Team and Cost per Active UserLab Locked
  18. Capacity vs Demand: Demand Hours by Request Type, Utilisation Needed and a Growth-by-Headcount Scenario GridLab Locked
  19. Load and Quality: Correlation, Regression Slope, R-Squared and a Forecast of Errors at a Higher LoadLab Locked
  20. Final Project: A Marketing Operations Scorecard with SLA, Utilisation, QA and Tool-Cost KPIsLab Locked

You are not signed in — the lab works, but your progress is not saved. Sign up

Lesson 1 of 20 is free. Unlock all 20 hands-on labs, the final exam and your certificate.

Buy course — $9.90
Loading the spreadsheet…

Why the request log comes first

Every marketing team has the same problem on a Monday morning: more people want things from it than it can build. The email for the autumn sale, a landing page for new boots, posters for a store opening, a banner for the loyalty app, they all arrive by chat, by email, in the corridor. Marketing operations is the function that turns this stream into a managed flow, and the first tool it needs is surprisingly plain: a request log, one row per request, with the date it arrived and the date it is needed.

Without a log you cannot answer basic questions. How many requests did we receive this month? Which team sends most of them? How many of them gave us only two days to react? How long do requests really take? Every later number in this course, from capacity to turnaround to backlog age, starts from rows of a log like this one. This free lesson shows the first and most useful number you can calculate from it, the requested lead time, and how to use it to flag rush requests in a fair and repeatable way.

The example company is Sedgewick Outdoors, a fictional outdoor retailer with an in-house marketing operations team. All requests, teams and numbers are invented for learning, and the minimum lead times are illustrative house rules, not industry standards. You will work with the same fourteen requests as in the lab above, received in October 2026.

What marketing operations actually does

Marketing operations (often shortened to marketing ops) is the group that runs the machinery behind campaigns: it takes in requests, plans the work, builds and checks campaign assets, manages the tools, and reports on how the whole system performs. It does not decide what the brand says; it makes sure that what the brand decides can be delivered on time, without errors and at a known cost.

That makes it a service function, and service functions live or die by predictability. Colleagues forgive a longer turnaround if they know about it in advance. They do not forgive surprises. A request log with lead times is the first step towards predictability, because it makes the difference between what is asked and what is possible visible on day one, when something can still be done about it.

Everything in this course is about the team and its processes, never about judging individual colleagues. Use the numbers to fix the process: clearer briefs, better planning, fair capacity. A scoreboard of names tends to produce hidden work and gaming of the numbers.

What to record for every request

A log is only useful if every row is complete and comparable. For this lesson the minimum is nine fields. Keep the list short, because every extra field is one more thing people skip when they are in a hurry.

  • Request ID. A unique number, such as R-2101, so that everybody talks about the same item.
  • Received date. The day the request reached the team, not the day somebody started working on it.
  • Requesting team. CRM, E-commerce, Retail or Brand. It is the team that owns the budget and the priority, not a person.
  • Request type. Email send, landing page, banner set, social set, in-store poster, automation flow. It decides which skills are needed.
  • Size. S, M or L, estimated at intake by the operations team. A rough size is better than none, and you can correct it later.
  • Due date. The date the requester needs the finished work. This is the date that matters, so ask for it explicitly.
  • Requested lead time. Calculated: due date minus received date.
  • Minimum lead time. Looked up from a small table by size.
  • Intake status. Calculated: Rush or Standard.

The first number: requested lead time

The requested lead time is the number of calendar days between the day a request is received and the day it is needed: requested lead time = due date − received date. It answers a simple question: how much time are we being given?

In Excel this is one subtraction, because dates are stored as serial numbers, counting the days since the start of 1900. The received date of R-2104, 6 October 2026, is stored as 46301, and its due date, 13 October 2026, as 46308. The difference, =F7-B7, is 7 days. If you subtract the other way round, the result is negative, which is the quickest way to spot a reversed formula.

From request to sprint plan: where the lead-time check sits1 Requestarrives witha due date2 Logreceived date,team, size3 Lead-time checkrequested vsminimum4 Triagescore andrank5 Sprint plancommit withincapacityRequests shorter than the minimum are flagged Rush at step 3, before triage.
Figure 1. The intake flow of Sedgewick Outdoors. The lead-time check is the step this lesson builds in Excel.

A long lead time is not automatically good and a short one not automatically bad. A one-line social post can be built in two days. A campaign landing page with new photography cannot. The lead time only becomes meaningful when you compare it with what the request needs, and that is what the next step is for.

Minimum lead time by size

Every size of request needs a minimum lead time: the time the team needs to deliver the work properly, including briefing, building, checking and approval. In this example the house rules are short and written down in a small table:

SizeTypical contentMinimum lead time (days)
SSingle email send, social set, small change3
MBanner set, in-store poster, medium email7
LLanding page, campaign page, automation flow14

Three things make such a table useful. It is short, so that everybody can remember it. It is public, so that requesters can check it before they ask. And it is kept in cells, not typed into formulas. When the team gets faster, or when a new tool slows it down, you change one number and every flag in the sheet updates.

Do not set minimum lead times by wish. Take them from the data: after a few months of turnaround figures (lesson 8) use the 90th percentile of the real delivery times per size, plus a day for approval.

A request is a rush request when…

The rule is deliberately simple: a request is a rush request when its requested lead time is shorter than the minimum lead time of its size. A medium request needs seven days. If it comes with a deadline in five days, it is a rush request. If it comes with exactly seven days, it is not: the requester has given the team what it needs.

That last case is where beginners make the most common mistake. Writing G7<=H7 instead of G7<H7 flags every request that gives exactly the minimum. Your colleagues would see a rush label on requests that were planned properly, and the label would soon mean nothing. Strictly shorter means <.

The worked example: fourteen requests

Here is the complete log of October 2026 with all calculated columns. Check a few rows by hand before you trust the formulas.

RequestReceivedTeamTypeSizeDueLead timeMinimumStatus
R-21015 OctCRMEmail sendM14 Oct97Standard
R-21025 OctE-commerceLanding pageL16 Oct1114Rush
R-21036 OctBrandSocial setS12 Oct63Standard
R-21046 OctRetailIn-store posterM13 Oct77Standard
R-21057 OctCRMEmail sendS10 Oct33Standard
R-21068 OctE-commerceBanner setM13 Oct57Rush
R-21079 OctBrandCampaign pageL30 Oct2114Standard
R-210812 OctRetailEmail sendS16 Oct43Standard
R-210913 OctCRMAutomation flowL23 Oct1014Rush
R-211014 OctE-commerceSocial setS16 Oct23Rush
R-211115 OctBrandBanner setM26 Oct117Standard
R-211216 OctRetailLanding pageL30 Oct1414Standard
R-211319 OctCRMEmail sendM23 Oct47Rush
R-211420 OctE-commerceEmail sendS27 Oct73Standard

Out of 14 requests, 5 are rush requests: R-2102 (a large landing page with 11 days instead of 14), R-2106 (a banner set with 5 days instead of 7), R-2109 (an automation flow with 10 days instead of 14), R-2110 (a social set with 2 days instead of 3) and R-2113 (an email with 4 days instead of 7). That is 35.7 % of all requests. Look at R-2104 and R-2105 and R-2112: each gives exactly the minimum, and each is correctly Standard.

Requested lead time vs minimum lead time, 14 requestsStandardRushMinimum lead time for the size0510152025921011121026210372104321055210621210742108102109221101121111421124211372114Request number (R-xxxx)Days
Figure 2. Requested lead time (bars) against the minimum for the request size (dark ticks). A bar that ends below its tick is a rush request.

Step by step in Excel

  1. Enter the headers in row 3 and the fourteen requests in rows 4 to 17. Make sure the received and due dates are real dates, not text. Select them and switch the cell format to General: real dates turn into numbers like 46301.
  2. Requested lead time (G4): =F4-B4, copied down to G17.
  3. Minimum lead time (H4): =XLOOKUP(E4,$K$4:$K$6,$L$4:$L$6), copied down to H17. It finds the size in K4:K6 and returns the minimum from L4:L6. The dollar signs keep the table in place when you copy down.
  4. Intake status (I4): =IF(G4<H4,"Rush","Standard"), copied down to I17.
  5. Requests per team (L10): =COUNTIFS($C$4:$C$17,K10), copied down to L13.
  6. Average requested lead time per team (M10): =SUMPRODUCT(($C$4:$C$17=K10)*($F$4:$F$17-$B$4:$B$17))/L10, copied down to M13. The condition inside SUMPRODUCT returns TRUE or FALSE for each request, which Excel treats as 1 or 0 when multiplied, so only the lead times of the team survive the sum.
If you prefer helper columns, the average per team can also be written as =AVERAGEIFS($G$4:$G$17,$C$4:$C$17,K10) once column G is filled. Both formulas give the same result; the SUMPRODUCT version works straight from the dates.

Reading the result by team

The summary per team shows where the rush requests come from:

TeamRequestsRush requestsAverage requested lead (days)
CRM426.5
E-commerce436.3
Retail308.3
Brand3012.7

Requests per team: rush and standardRushStandardCRM224 requestsE-commerce314 requestsRetail33 requestsBrand33 requestsCounts of requests received in October 2026 (fictional data)
Figure 3. Rush and standard requests per team. Two teams account for all five rush requests.

E-commerce sends 4 requests and 3 of them are rush requests; CRM sends 4 with 2 rush. Retail and Brand send none, and Brand gives the most time, 12.7 days on average. Be careful with the conclusion. Four or three requests per team are far too few to say that E-commerce is badly organised. They are enough to start a conversation: are E-commerce deadlines driven by promotions that are fixed late? Could CRM requests be planned from the campaign calendar?

A rush flag describes the request, not the requester. Some rush requests are unavoidable, for example a supplier problem or a competitor move. Count them, discuss patterns, and leave room in the sprint plan for a few. What you want to avoid is a team that is surprised by its own plan.

Common mistakes and how to spot them

  • Reversed subtraction. =B4-F4 returns negative lead times. If a whole column is negative, swap the dates.
  • Dates stored as text. Data pasted from a chat tool or a form often arrives as text. The subtraction then returns a #VALUE! error or silently a wrong result. Convert the column to real dates first.
  • Counting the received day and the due day. Adding 1 to the difference makes every lead time one day longer and every rush flag harder to trigger. Keep to the plain difference and write the rule down.
  • Using <= for the rush test. A request that gives exactly the minimum is not a rush request. Use <.
  • A lookup table without dollar signs. =XLOOKUP(E4,K4:K6,L4:L6) copied down becomes K5:K7, then K6:K8, and soon finds nothing. Lock the table with $K$4:$K$6.
  • Typing the size into the formula. =IF(G4<7,...) uses seven days for every request. Look up the minimum for each size instead.
  • Dividing by the wrong count. The average lead time per team divides by the requests of that team, not by all fourteen.

Checks before you trust the log

A few quick checks save embarrassing meetings.

  • Count the rows. =COUNTA(A4:A17) must equal the number of requests you expect (14), and the counts per team in L10:L13 must add up to the same number.
  • Look for impossible dates. A due date earlier than the received date gives a negative lead time. =MIN(G4:G17) should be zero or more.
  • Look for gaps. A missing size makes XLOOKUP return #N/A. Filter the column for errors before you summarise.
  • Compare with a hand calculation. Pick two rows, count the days on a calendar and compare with the sheet.

Quick reference: functions and shortcuts in this lesson

Function / shortcutWhat it does hereExample
Date subtractionCalendar days between two dates=F4-B4
XLOOKUPFinds the size and returns its minimum lead time=XLOOKUP(E4,$K$4:$K$6,$L$4:$L$6)
IFRush or Standard label=IF(G4<H4,"Rush","Standard")
COUNTIFSRequests per team=COUNTIFS($C$4:$C$17,K10)
SUMPRODUCTAverage lead time of a team without helper column=SUMPRODUCT(($C$4:$C$17=K10)*($F$4:$F$17-$B$4:$B$17))/L10
F4 / Cmd + TAbsolute reference$K$4:$K$6
Ctrl + Shift + ~General format, shows a date as its serial numberCheck what Excel stores

Real-world uses

  • A visible intake form. Most project and ticket tools can ask for a due date and a size at submission. The same two columns, due date and size, give you the lead-time check automatically.
  • Weekly intake review. Sort the log by status and talk through the rush requests. The conversation is about what could have been planned earlier, not about who asked.
  • Planning conversations with requesting teams. Show a team its average requested lead time next to the minimum. Teams that see the numbers usually start planning earlier on their own.
  • Input for capacity planning. The count of requests per team and size is the demand side of the capacity plan you will build in lesson 18.
  • A service menu. The minimum lead time table is the start of a service menu: what we deliver, how long it takes, what we need from you.

Where the course goes from here

This lesson built the entry gate of the process. The remaining nineteen labs follow a request through the system and measure every step. The next lessons score and rank requests (2), calculate the capacity of the team (3), compare logged hours with that capacity (4), plan sprints and forecast velocity (5 and 6).

Then the course turns to delivery. You measure turnaround against service level agreements and read its distribution with the median and the 90th percentile (7 and 8), count approval rounds and rework (9), and track the quality of launches with QA error rates, escapes and control limits (10 to 12). Lessons 13 and 14 deal with the backlog: its age, its flow and what Little's law says about waiting time.

Lessons 15 to 17 turn to the money in the tool stack: cost per active user, right-sizing seats at renewal and allocating shared costs to teams. The last block tests demand against capacity in a scenario grid (18), relates team load to quality with correlation and regression (19) and ends with a scorecard that brings the key numbers onto one page (20).

Open the lab above and fill the first column of the sheet before you read on. Seeing the first Rush label appear next to the right request makes the rest of the course much easier to follow.

Summary

A request log with a received date and a due date gives the requested lead time. A small table of minimum lead times by size gives the benchmark. A strict less-than test turns the two into a rush flag, and COUNTIFS and SUMPRODUCT summarise the flags per team. The method is simple, but it makes planning problems visible on the day a request arrives, which is the cheapest day to deal with them.

All names, teams and numbers in this article are fictional and the minimum lead times are illustrative. Replace them with your own data and your own house rules when you use the method at work.

Frequently asked questions

What is a good lead time for a marketing request?

There is no universal number. A good lead time is one that is at least as long as the time the team needs for that type and size of work, including briefing, building, quality checks and approval. Measure your real delivery times, then set a minimum lead time per request size and keep it in a table.

How do I calculate the lead time between two dates in Excel?

Subtract the received date from the due date, for example =F4-B4. Excel stores dates as serial numbers, so the result is the number of calendar days. DAYS(F4,B4) gives the same result. If the numbers come out negative, the dates are in the wrong order.

What is a rush request?

In this course a rush request is a request whose requested lead time is shorter than the minimum lead time of its size. A request that gives exactly the minimum is not a rush request. The label describes the request and its timing, not the person or team who sent it.

How do I look up a value for each row from a small table in Excel?

Use XLOOKUP(lookup value, lookup range, return range), for example =XLOOKUP(E4,$K$4:$K$6,$L$4:$L$6). INDEX with MATCH does the same in older versions. Lock the table with dollar signs before copying the formula down.

How do I count requests per team with COUNTIFS?

Write =COUNTIFS(team_range, team) and lock the range, for example =COUNTIFS($C$4:$C$17,K10). Add more range and criterion pairs to count only the requests that also match another condition, such as the status Rush.

Should I include weekends in the lead time?

For intake it is common to use calendar days because requesters think in dates. For delivery promises many teams count working days instead. Whichever you choose, write it down and use it consistently. Later lessons use working days for turnaround and calendar days for backlog age.

Keep going: Marketing Operations: Request Intake, Sprint Capacity & Utilisation, Turnaround SLAs, Campaign QA Error Rates, Tool-Stack Cost per User & Backlog Ageing

This free lab is lesson 1 of 20. Unlock the other 19 hands-on labs, the final exam and your certificate for a one-time $9.90.

  1. Triage Scoring: Weighted Priority Scores with SUMPRODUCT, Ranks and an Approve or Waitlist Decision
  2. Sprint Capacity: Available Days, Net Hours after Leave and Overhead, and Capacity per Role
  3. Utilisation and Load: Project Utilisation, Total Load and Overload Flags
  4. Sprint Planning: Plannable Hours, Running Totals, Commit or Carry Over and Carry-Over Hours
  5. Sprint Velocity: Completion Rates, a Moving Average, a Linear Forecast and Sprints to Clear the Backlog
  6. Turnaround SLAs: Targets per Request Type, Met or Missed, Days over the SLA and SLA Attainment
  7. Turnaround Distribution: Mean, Median, 90th Percentile and the Share within the SLA
  8. Approval Rounds and Rework: Hours per Round, Rework Hours, First-Pass Rate and Rework Share
  9. Campaign QA: Errors per 100 Checks, a Target Status, the Overall Error Rate and the Share of Clean Launches
  10. QA Escapes: Escape Rate per Launch, the Overall Escape Rate and a Pareto Analysis of Defect Categories
  11. QA Control Limits: Weekly Error Proportions, a Centre Line, Upper Control Limits and Signals
  12. Backlog Ageing: Age in Days, Age Bands with an Approximate Lookup, Counts per Band and Waiting Time
  13. Backlog Flow: Arrivals, Completions, Net Flow, Backlog Trend and Little's Law Waiting Time
  14. Tool Stack Costs: Cost per Active User, Seat Utilisation, Unused Spend and Low-Use Flags
  15. Seat Right-Sizing: Right-Sized Licences with ROUNDUP, Savings per Tool and a Renewal Window
  16. Cost Allocation: User and Request Shares, Allocated Tool Cost per Team and Cost per Active User
  17. Capacity vs Demand: Demand Hours by Request Type, Utilisation Needed and a Growth-by-Headcount Scenario Grid
  18. Load and Quality: Correlation, Regression Slope, R-Squared and a Forecast of Errors at a Higher Load
  19. Final Project: A Marketing Operations Scorecard with SLA, Utilisation, QA and Tool-Cost KPIs

Buy course — $9.90 See the full course