Meeting of the Minds Submission Guidelines: Publishing Urban Innovation Analysis

Key Takeaways

• Meeting of the Minds, a San Francisco nonprofit focused on urban innovation since 2009, publishes short applied analysis on urban technology, mobility, climate resilience, energy, and local governance for city staff, planners, utility professionals, and funders.
• Drafts that clear editing usually run 600 to 900 words, name a specific place and project, quantify results with citable sources, and close with a lesson another jurisdiction can act on.
• Editors reject promotional copy, anonymous case studies, and essays without evidence. Budget lines, agency reports, and published evaluations carry the argument.
• The outlet fits mid-career practitioners and applied researchers with one concrete project. It fits poorly for purely theoretical modeling, partisan commentary, or product promotion.
• Before pitching, confirm exclusivity terms, clear internal approvals if you work in government, and prepare images with captions and credits.

1. Introduction

Urban practitioners generate knowledge that rarely travels. A city negotiates data-sharing terms with a scooter operator, a utility phases in time-of-use rates across three neighborhoods, a planning department rewrites its permit workflow and cuts review times. The record of what worked, what it cost, and what broke in year one usually ends up inside procurement files and consultant decks. Meeting of the Minds built its editorial model around moving that record across city lines.

Most rejections at practitioner outlets follow a pattern the writers never see coming. The draft reads like a press release. The case study hides the city's name and the budget. The essay asserts that cities should embrace innovation and stops there. An author who fixes these defects in advance moves to the top of the queue, whatever the topic.

This article translates the Meeting of the Minds submission guidelines into a working process: what the editors accept, how to structure an urban innovation analysis that clears editing, which defects trigger rejection, and where the outlet sits relative to trade press, think tanks, and commentary sites. The intended readers are city staff, planning and sustainability professionals, utility analysts, civic-tech founders, and applied researchers choosing where to place their next piece.

2. What the publication accepts and who reads it

The outlet publishes applied analysis: how a specific place adopted a technology, changed a process, or funded infrastructure, and what the result measured. Since 2009 the organization has run the publication alongside a regular newsletter and an annual summit, and its topic list follows the operating questions of city government: mobility and electrification, climate adaptation, energy systems, data governance, housing, and civic engagement. Contributors are mostly practitioners. Municipal staff, utility analysts, nonprofit directors, consultants, and researchers with field projects write most of the bylines.

The readership leans professional. City officials deciding what to buy, planners weighing code changes, sustainability officers tracking grant deadlines, and the vendors and foundations that finance this work all read the same pieces. That mixture sets the register. A vendor reader wants to know how cities buy. A city reader wants to know what the product cost and how it failed. Both get served when the piece states numbers, actors, and constraints plainly.

Read five to ten recent pieces on your topic before drafting, and note how quickly they reach a named decision and a number. If your subject is flood sensors, write so a stormwater manager in another region could repeat the procurement: unit costs, funding source, contract vehicle, staffing, and the measured outcome. A piece that stops at "the city deployed smart infrastructure" has nothing for either reader.

3. Formatting the submission: length, structure, evidence

The guidelines ask for roughly 600 to 900 words, and the constraint does real work. That length holds one project, one decision, and one lesson. A comparison of four cities' programs, or a literature review, needs a different outlet or an editor's approval for a longer format.

A structure that holds up in editing:

1. A headline that states the finding, with the subject in it, rather than an abstraction such as "The future of parking."
2. An opening paragraph with the place, the problem, and the stakes.
3. Two or three body sections under subheads: the decision and its options, the cost and funding, the measured result.
4. A closing lesson with conditions attached: where the approach transfers, where it does not, and what the author would change.
5. Links to primary sources: budget lines, council agendas, agency reports, or published evaluations.

Two process notes improve acceptance odds. Write the closing lesson first; if you cannot state it in two sentences with numbers attached, the piece needs more reporting. And have a chart or project photo ready with caption and credit, since the publication runs illustrated pieces and editors will ask.

A pre-submission checklist:

• Word count between 600 and 900
• The city or agency named in the first paragraph
• At least three quantified claims, each with a source
• One stated limitation or failure, with what changed as a result
• Author bio of two or three sentences with your role and organization
• Images with captions, credits, and permissions
• A note on exclusivity and any funder reporting obligations

4. What gets rejected, and the fix for each pattern

Rejections cluster into five patterns.

Vendor copy praises a product without a named client or independent numbers. The fix is structural: get the city on record, report cost and an outcome metric, and shrink the vendor to a one-sentence role.

Anonymous case studies ("a mid-sized city recently implemented...") leave readers unable to verify anything. Editors pass on them. Name the city and the year, or place the piece elsewhere.

Unmeasured claims such as "dramatically improved efficiency" give an editor nothing to publish. Replace each with a metric, a baseline, and a source: "cut permit review from 21 to 14 days, per the department's 2024 report."

Unexplained jargon ("digital twin-enabled predictive governance") reads as padding to a practitioner audience. Use plain verbs and define the one term you cannot avoid.

Missing failure modes matter most. A piece that reports only wins reads as advertising to anyone who has run a pilot, editors included. One paragraph on what underperformed and what you changed restores credibility.

One caution sits outside the editor's view: if you work for a public agency, route the draft through your communications office before you submit, and check disclosure rules with the department that owns the data. Procurement terms still under negotiation should stay out of the piece entirely. Internal review can take longer than the edit itself, so start it before you pitch.

5. Where Meeting of the Minds fits among other outlets

Choose an outlet by format, audience, and speed, in that order. The table compares the realistic options for someone with an urban innovation story to tell.

Reading the table against a concrete case clarifies the choice. A postmortem of a bus electrification pilot, with cost per bus and maintenance data, belongs in Meeting of the Minds, whose readers sign procurements and write grant applications. A reaction to a federal grant announcement due next week fits a commentary outlet, which turns pieces around in days at the cost of reach. A two-year study with a methods appendix belongs with the think tanks, which trade speed for depth and institutional credibility.

Three logistical questions deserve answers before you pitch anywhere:

• Exclusivity: contributed outlets differ on whether a piece can run elsewhere. Ask in your first message and state any funder obligations that require parallel publication.
• Timing: attach the pitch to a live hook, such as an open grant program, a pending council vote, or the period around the outlet's annual summit, when reader attention concentrates.
• Rights and images: confirm who owns the photos and charts, and get written permission from any vendor or agency whose material you reproduce.

6. FAQ

Q1. How long should a submission to Meeting of the Minds be?

Plan for 600 to 900 words. Editors cut longer drafts or ask for trims, and a piece under about 400 words rarely carries enough operating detail for a practitioner audience. If the evidence genuinely needs more room, propose the longer format in your pitch and let the editor decide before you write it.

Q2. Can I publish the same analysis somewhere else?

Ask about exclusivity in your first message to the editors rather than after acceptance. State any commitments that already exist, such as a grant report that will become public. After publication, if you want to circulate the piece internally or on professional networks, share a short excerpt with a link and confirm the outlet's republishing terms instead of assuming them.

Q3. Do I need a city or university affiliation to contribute?

No. Contributor lists at the publication include nonprofit directors, utility analysts, consultants, and founders alongside municipal and academic authors. First-hand involvement is the requirement: write about work you ran, funded, evaluated, or supervised. Second-hand knowledge works when you report it as such and cite the people who did the work.

Q4. What should public employees clear before submitting?

Route the draft through your communications office, and check disclosure rules with any department whose data or contracts appear in the piece. Leave out terms still under negotiation. Start the clearance process before you pitch, because internal review can take longer than the editing cycle.

7. Conclusion

Meeting of the Minds is the right placement when three conditions hold: you took part in the work, the results can be quantified from documents you can cite, and the reader you want is someone who can copy the approach in their own jurisdiction. Under those conditions the working order is fixed. Draft the closing lesson first, keep the piece between 600 and 900 words, name every actor, cost, and source, and include one admitted limitation. When the piece is a fast policy argument, a commentary outlet offers a quicker path with a smaller audience; when it is a data-heavy study, a think tank or journal offers the room it needs. For the project postmortem that city hall needs to read, the next step is a pitch email containing the budget line, the outcome number, and two sentences on what another city should do differently.