Question and scope

This protocol measures the elapsed time between the moment a cross-team request is accepted and the moment someone reserves calendar time to work on it. Acceptance is the point at which an owner and a deliverable are agreed, as described in the request acceptance checklist. The first scheduled work block is a dated interval assigned to a named person, not a due date and not an intention. The result is a median lag in working days, a distribution, and a list of requests with no block at all.

The gap matters because it sits between two events most teams already measure. Intake volume is tracked, and delivery dates are tracked, but the quiet period in between is usually invisible. A request can be accepted on Monday, sit unassigned for two weeks, and still look healthy on a dashboard that only compares due dates. By the time the date slips, the cause is far behind the current reporting period.

Scope is one coordination team and a defined set of accepted requests. Include requests accepted during the window even if work has not started. Exclude requests that were rejected, withdrawn, or returned to the requester before acceptance. Record the sources for both timestamps and the calendar system used for scheduling so another analyst can rebuild the measurement.

Defining the two timestamps

Define the intake timestamp as the moment the request record shows an accepted owner, deliverable, and due date. Do not use the moment the request arrived, because that measures triage speed rather than scheduling speed. If the team accepts requests in a meeting, use the meeting date; if acceptance happens in a ticket, use the status transition. Store the field name and system so the definition is auditable.

Define the first scheduled work block as a calendar event or capacity-plan entry with a date, a duration, and a named person assigned to this request. A block can be an hour or a full day, but it must be time someone has reserved. An entry that only repeats the due date does not qualify. A block assigned to a team queue without a named person is weaker evidence and should be flagged separately.

Unit of analysis and exclusions

The unit is one accepted request with one owner and one deliverable. Split a bundled request when each part could be scheduled independently, such as two reports for two audiences with different reviewers. Keep one unit when the parts must be produced and reviewed together. Use the record as it stood at the cut-off rather than a cleaned version rewritten during the audit.

Exclude requests accepted but later cancelled before any work was needed. Exclude duplicate records created when a ticket and an email describe the same request, but count the pair once and note the overlap. Exclude requests whose first block predates acceptance, which usually means work began before the paperwork caught up. Report each exclusion category with a count so the denominator is defensible.

Include requests accepted near the end of the window that are still waiting. Those are not missing data; they are censored observations, and dropping them will make the lag look shorter than it is. Record the observation date and days elapsed so far. Report the censored view alongside the completed-request view and explain the difference.

Building the request inventory

Start with the request tracker if one exists, then add accepted requests that live only in email or chat. Search for acceptance language such as confirmed, assigned, or agreed, and check the commitment log for items promised but never entered in the tracker. The inventory should reflect the work the team actually took on, not only what followed the formal path. A request that arrived by chat and was accepted in a call still belongs in the population.

Record the requester, receiving team, owner, acceptance date, due date, and system of record. Mark requests that arrived through an informal channel, since those are the most likely to lack a scheduled block. Freeze the list before reading the calendar so the sample is not biased toward requests that were easy to schedule. Assign a stable identifier to each unit.

Check for requests accepted twice, such as a reopened ticket with a new owner. Treat a transfer as a new acceptance only if the deliverable or scope changed. Otherwise keep the original acceptance date and note the transfer. Reopened requests with a new due date are a common source of artificially short lags, because the clock appears to restart.

Reading the calendar evidence

For each request, search the calendar of the named owner for events that reference the request or its deliverable. Record the earliest qualifying block and its duration. If the calendar shows only a recurring team meeting where the item might be discussed, do not count it as a work block. Discussion is not reserved production time, and counting it would flatter the result.

Check capacity plans and project schedules when the calendar is empty. Some teams reserve time in a planning tool and create calendar events later. Record which system provided the evidence so the analysis can show how many blocks exist in only one place. A block that lives only in a planning tool is still a commitment, but it is easier to lose when the plan changes.

Handling reschedules and cancellations

Record every move of the first block, not just the final date. A block that moved twice before happening has a different operational meaning from one scheduled once and kept. Capture the reason when the calendar or planning tool records one, and group reasons into categories such as capacity conflict, dependency wait, or requester change. The categories explain more than the raw count.

Treat a cancelled block as unscheduled unless another block was created at the same time. A cancelled block with no replacement is the clearest signal that the request lost its place in the queue. If the block was cancelled because the request was completed early, exclude the request from the reschedule analysis and note it. Context matters, and a mechanical count of cancellations will mislead.

Evidence standards

Accept an acceptance timestamp only when it appears in a system the team uses to operate. A date in a personal note is weaker than a status change in the shared tracker. Accept a scheduled block only when it has a date, a duration, and a named person. A verbal agreement to "get to it next week" is not a block until it appears where the owner will see it on Monday morning.

Do not create a block during the audit and then count the request as scheduled. That changes the population instead of measuring it. If the team starts scheduling while the review runs, record the new block in a separate field and report it as a post-audit change. The original state is what the headline describes, and the change is what the team did in response.

Record gaps in the evidence rather than estimating them. If a request has no acceptance date, mark it unknown and report the count. If it has an acceptance date but the owner's calendar is unavailable, mark it unverified rather than assuming no block. A visible unknown is more useful than a guessed value, because it shows where records are weak.

Sampling and verification

Use a census when the inventory is small enough, which is common for a single coordinator handling a few dozen requests a quarter. Above roughly one hundred and fifty requests, draw a random sample and publish the method. Stratify by receiving team and by month so one busy period does not dominate. Freeze the sample before reading the calendar.

Have a second reviewer recode at least ten requests and compare the results. Resolve disagreements by returning to the tracker and the calendar, not by debating which date seems more likely. Record the resolution so later reviewers apply the same interpretation. If disagreement is high, rewrite the definitions and recode the full sample before reporting.

Check for timezone and working-day errors. Two systems may record the same event on different dates if one stores UTC and the other stores local time. Count working days using one calendar and state which holidays were excluded. A lag reported in calendar days without that note will not be comparable to the next period.

Decision rules before coding

Decide whether a block scheduled before the acceptance date counts. The practical answer is no, because the request had not been accepted and the block belongs to earlier planning. Note those requests separately, since they indicate work started before the paperwork. That is a different finding and may be healthy in an emergency.

Decide whether a partial block counts, such as a fifteen-minute calendar hold. A hold is not reserved production time unless the team treats it that way. Set a minimum duration before coding and apply it consistently. Record the threshold so a later reviewer can compare periods, because a low threshold produces a short lag that does not reflect capacity.

Analysis and reporting

Report the median lag in working days, the interquartile range, and the share of requests with no block at all. Show raw counts beside every percentage. A median alone hides the tail, and the tail is where requests that damage trust usually sit. Add the share of first blocks that fell after the due date and the share rescheduled at least once.

Break the result down by receiving team, owner, and request type. Suppress groups with fewer than five requests so one unusual item does not look like a pattern. Pair the lag with estimated effort, because a two-week wait for a one-hour task is a different problem from a two-week wait for a two-week project. The capacity check before handoff is the natural control for the first case.

Report the trend rather than a single period. Lags move with holidays, staff changes, and large launches, so one month is rarely enough to judge. Show at least three periods, or state clearly that the result is a baseline. A baseline with a stated method is more useful than a comparison against an invented target.

Limits and sources of error

The sources cited here describe internal control and project scheduling practice in general terms; they do not provide a benchmark for intake-to-scheduling lag. A short lag may mean the team schedules quickly, or that it only accepts work when capacity is already free. The measure cannot distinguish those cases without acceptance volume and available capacity. Report both alongside the lag before drawing a conclusion about scheduling discipline.

Calendar data is incomplete by nature. Some work happens in small gaps that never appear as a block, and some blocks are aspirational. A request may be worked on before its first formal block, which makes the lag look longer than the lived experience. Check a sample of requests against progress notes to estimate that gap and report it as a limitation.

Review cadence

Review the result at a fixed point and end with one change, one owner, and one check date. A practical first change is to require a scheduled block before a request can move to accepted status. Repeat the measurement after two full cycles before setting a target, because one period may reflect a holiday or a hiring gap. Keep the definitions with the result so the next reviewer can compare like periods.

Retire the measure when most accepted requests have a block within the team's stated service level and the tail stops moving. If the team keeps it, publish the no-block share and the late-block share together, because a short median can hide a growing tail. Link the result to the dependency standup when unscheduled work waits on another team. The purpose is to make the quiet delay visible while it is still cheap to fix.

Sources