A numbered line in an RFP response checklist is not one task. It can ask for a narrative answer, a document, a completed form and a signature, and each has its own owner and state. A tracker that counts lines counts the labels, not the work.
What does one checklist line actually ask for?
Read a line the way the evaluator will. The headline is one sentence, and behind it sit up to four different kinds of ask.
A narrative. The issuer wants to know how the firm thinks: the approach to this financing, the plan for distribution, the reasoning behind a structure. Prose answers this, and the prose has to be about this issuer.
A document. A certificate, an audited statement, a rating letter, a sample of a prior official statement, a copy of a policy. The document exists or it does not, and its contents are not a summary.
A form. A fee schedule in the issuer's format, a references table, a conflicts disclosure, a pay-to-play questionnaire. The form has fields, and an empty field is an incomplete answer even when the narrative beside it is strong.
A signature. An authorized signer attests to the response. That is a separate act with a separate person behind it, and it is not done until it is done.
A single line can carry all four. "Provide your firm's approach to the financing, a sample official statement from a comparable issue, the attached fee schedule and a signed certification" is one numbered item and four pieces of work.
GFOA's guidance for issuers on selecting an underwriter shows the same compression from the other side. It asks issuers to put the evaluation criteria, the fee format and at least three references into the solicitation. Each of those becomes a line in the response, and each line carries a narrative, a form or a named reference behind it.
Why does a line count understate the response?
Because a status assigned to a line is a summary of several asks that can disagree.
Mark the line done when the narrative is written and the certificate is missing, and the tracker says finished while the response is not. Mark it open when the narrative, the form and the signature are in place and one referenced document is outstanding, and the tracker hides work that is nearly finished. Either way the row moves in a step that is larger than the work, and the person reading the tracker cannot see which ask is the one holding it up.
The chase list inherits the same error. "Please send the certificate" is a request for one thing when the line asked for three jurisdictions, and a reply with one certificate resolves the row without resolving the ask. The denominator was wrong when the chase was written, so the chase cannot fix it.
Why is the ask the right unit of work?
Because an ask has one deliverable, one owner and one state.
The narrative and the form might belong to the banker. The certificate might come from the issuer's counsel. The signature belongs to whoever the firm authorizes. Those are different people with different queues, and a line-level status cannot tell you which queue is stuck. An ask-level status can.
An ask is also small enough to be honest about. Answered, answered in part, open, or not applicable are real states for a certificate covering three jurisdictions. Two of three is partial, and partial is useful: it tells the reviewer that one call closes the gap. At the line level, partial has nowhere to sit, so it turns into done or open and loses the information either way.
The test is the deliverable. If two things can arrive separately, they are two asks. If one thing answers both, it is one. A fee schedule and a signed certification are two. A narrative about distribution and a distribution plan attached as evidence might be one ask with two parts, or two, depending on what the issuer asked for. Read the line, then decide.
How should a desk read a new checklist?
Decompose before estimating.
The first pass over a new RFP or RFQ is where the response gets its shape. Read each numbered line and write down the asks behind it: the narrative, the document, the form, the signature, the reference. Name the owner for each one. Note the evidence that already exists and the evidence that has to be produced. Only then estimate the work.
That pass costs a fraction of the drafting and it changes what the drafting looks like. A response that looked like forty lines can be a hundred and twenty asks, and the schedule that assumed forty lines was never going to hold. Doing the decomposition first is how a group finds that out while there is still time to ask the issuer a question, rather than in the last week when the only option is to work later.
The second pass is the delta. For each ask, the question is not "do we have something like this" but "do we have this, for this issuer, current". A prior response gives the shape of the narrative and the format of the form. It does not give the certificate, the signature or the reference the issuer asked for.
What should a public finance group change in its tracker?
One row per ask, filed under the line it belongs to.
The sections still read the way the checklist reads, so nothing is lost in navigation, and the count underneath is the same count the work is done in. Each row carries its own state, its owner and the evidence attached to it. A partially answered ask earns partial credit. A line rolls up from its asks, so a line with three answered asks and one open one shows as partial rather than done.
None of this requires a new system. A spreadsheet holds one row per ask as easily as one row per line, and a group that keeps its tracker in Excel is not wrong to. The denominator is a choice inside the tool.
The workflow on the software side runs the same arithmetic. RFP automation reads the solicitation, builds the response from the group's closest precedent and routes each section to a named reviewer. The checklist is the part that changes slowly; the asks behind it are the part that decides whether the response is ready. On a public finance desk the unit of work is the ask, and the tracker should say so.
What else is worth asking?
What is a parenthetical on an RFP checklist?
The bracketed part a numbered line carries: the documents, entities, periods or jurisdictions that each have to be produced separately. It is where one line turns into several deliverables.
Does one line ever really carry four asks?
Often it carries at least two, and the four kinds are the useful way to see them: a narrative answer, a document, a completed form and a signature. A line can ask for one of the four or for all of them.
Can a spreadsheet hold one row per ask?
Yes. A spreadsheet holds one row per ask as easily as one row per line. The denominator is a choice inside the tool, not a reason to change the tool.