Posts
Four Categories
The Post isn't just a news feed; it’s a repository for the planning community. We move beyond the what to explore the how and the why. Our goal is to publish content that offers local insight with potential for application . Whether you’re writing about a micro-park in Bogota or a transit hub in Tokyo, your piece should provide "transferable knowledge" that a planner elsewhere can adapt to their own context.
Technical Specs
To help readers navigate our library, please tag your submission under one of the following four categories:
Perspective - Shape the Field
Thought-leadership on policy, ethics, or the future of the field. Challenge the status quo with a well-reasoned argument. This is your platform to be a provocateur or a visionary. Whether you're discussing the ethics of AI in zoning or the need for radical housing reform, we want informed opinions.
Discovery - The Planner’s Toolbox and Observation
Reviews of new datasets, mapping tools, or "street-level" observations of urban phenomena that others might have missed. Planning is often found in the details. Use this space to highlight a specific "win" in urban design, a new piece of software that saved you 20 hours of work, or a surprising trend in demographic data. Practicality is king. If you’re sharing a tool, include a link. If you’re sharing an observation, include high-quality photography or data visualizations.
Story - The Path to the Plan
Planning is a deeply human profession. We invite you to share the "lived experience" of being a planner. Focus on a specific "turning point" or "aha!" moment. While these are personal, they should still feel professional and relevant to the community.
-
Word Count: 500 – 1,500 words. (longer pieces can be allowed at the discretion of the editor).
-
Visuals: At least 1–2 high-resolution images, charts, or maps. You must have the rights to use these images or use Creative Commons/Open Source visuals with proper attribution.
-
Tone: Professional yet accessible. Avoid overly dense academic "planner speak." Write like you are talking to a high school students.
Writing Style
Our Voice:
Casual, creative, and human.
The Goal:
Be the person your peer wants to grab a beer with, not the textbook they want to sell back to the campus bookstore.
The Rules:
-
> * Keep It Simple: Use plain language that everyone can understand.
-
Make it personal: Share the 'why' behind the 'what.'
-
Get creative: Feel free to be poetic or inspirational. If it feels like you, it belongs here.
Promising Practices
Technical Specs
To provide a curated "Idea Bank" for planners. This section focuses on innovative methods, policies, and designs that have proven successful.
What Makes a Practice "Promising"?
We evaluate submissions based on three criteria:
-
Impact: Did it move the needle on a real-world problem?
-
Scalability: Can this be adapted by a city of a different size?
-
Clarity: Is the strategy explained clearly enough that it could be helpful other planners?
Submission Structure
To maintain consistency and ease of reading, all submissions must follow this standardized template:
-
Headline: A punchy, action-oriented title.
-
Project Identity: Name of the project/policy and its specific location (city and country).
-
An Overview: 3 – 5 sentence summary of the project and why it matters.
-
The Background: the context of the project, in terms of demegraphic, natural, cultural, hisotry, urban fabric setting.
-
Challenge: What specific urban planning issue was this designed to solve? (e.g., lack of green space, traffic congestion, inequitable housing).
-
The Strategy: The "How-To." Detail the steps taken, the tools used, and the stakeholders involved. Focus on the mechanics of the solution.
-
Transferable Lessons: What can other planners take away? Mention any "gotchas" or advice for replication in a different city.
Visuals are Essential
Since this is an "inspiration" section, visuals are key. Each submission should include:
One "Hero" Image: A high-quality photo or rendering that captures the essence of the project.
One Technical Graphic: A map, a diagram of the process, or a data chart showing the results.
-
Length: 400 - 1000 words limits, but keep it lean.
-
Language: Practical and direct. Use active verbs (e.g., "We transformed..." instead of "Transformation was achieved...").
-
Links: When applicable, include an external link to the official project page, the full policy text, or the final report.
Use of AI
AI is a co-pilot, not the captain.
We’re all for experimenting with new tools—AI can be a great spark for a stalled draft or a new perspective, or check editorial errors. But remember: at the end of the day, it’s your name on the page. We ask that you stand behind every word you share. Use AI to explore, but keep your hands on the wheel. For a deeper look at guidance of using AI for your work, check out the APA’s Planning Ethics and Generative AI.
Here are few general rules:
-
Never "set it and forget it." You are 100% responsible for every word, fact, and opinion in your post. If the AI gets a fact wrong or misinterprets a policy, that’s on you. Always do a final "human-pass" to ensure the piece reflects your actual thoughts. Don’t let a "hallucination" undermine your credibility as a planner.
-
Use AI to brainstorm outlines or find a tricky word, but don't let it rewrite your personal stories. If a sentence feels too "perfectly polished" and loses your voice, rough it up a bit. We want the "you" in the story.
-
If AI did the heavy lifting to structure the entire piece, just give us a quick "Heads up." A simple note at the bottom like, "I used AI to help brainstorm the framework for this post," keeps things honest and builds trust with your readers.
Please note that your article could be run
through https://www.zerogpt.com/ and if the content is mostly AI-generated your submission will not be considered.
The "No-Go" List
We want UPP to be a space for genuine connection. To keep the "vibe" right, we try to avoid content that feels like it belongs in an ad break. We generally won’t publish pieces that:
1. Lead with the Sales Pitch, Not the Lesson
We know that many of the best planning insights come from projects led by consulting firms or innovative new tools. That’s great! We love hearing about them. However, if a post feels like a brochure for a business, a course, or a specific program, it’s probably not for us.
The Rule of Thumb: If you're sharing a project you worked on, focus on the how and the why—the lessons that help other planners—rather than the "hire us" subtext.
2. Aim to “Bamboozle”
Planning can be complex, but our writing shouldn't be. We steer clear of anything written with the intent to confuse, over-complicate, or intentionally mislead the reader. If you can’t explain it simply over a coffee, it might need another pass. We’re here for clarity, not jargon-filled smoke and mirrors.
3. Chase Clout Over Contribution
There’s nothing wrong with building a reputation, but UPP is a place for community, not just a ladder for a social media presence. If a post feels like it was written solely to gain "clout" or build a "personal brand" without offering real value to the reader, it likely won't resonate here. Let the quality of your insights build your name, not the other way around.
4. Rely on “Machine-Borrowed” Expertise
AI is a brilliant assistant for smoothing out syntax or brainstorming an outline, but it shouldn't be the "brain" behind your piece. We ask that you don't use AI to write about concepts you don't already understand or haven't personally wrestled with. If you don't know the "why" behind a finding, a machine won't truly know it for you. We want hear your lived experience and your hard-earned knowledge.