I'll never forget the email that came through in September 2022. The subject line was polite: "Re: Playground Installation – Some Issues." The attached photos showed a half-installed spinner that was six inches off the designated spot. The concrete base had already cured. Wrong spot. Wrong spec. Wrong everything.
That mistake cost us $3,200 in redo—demolition, new concrete, replacement parts—plus a three-week delay for a school that had already scheduled its opening.
I've made plenty of mistakes in my eight years handling playground equipment orders. But the ones that sting the most? They always happen on the small, seemingly straightforward projects.
The Small Project Trap
When you're dealing with a $150,000 playground structure for a municipal park, everyone pays attention. There are meetings, site surveys, multiple approvals. But ask me about the $15,000 school playground add-on or the two-piece fitness station for a community garden—those are the ones where corners get cut.
Here's the assumption I made back in 2022: "It's just a small project. How much can go wrong?"
I assumed the site was flat. I assumed the specs from the general contractor were current. I assumed the KOMPAN installation manual was straightforward enough that we could skip the pre-install walkthrough. What I mean is, I assumed simplicity meant forgiveness.
It doesn't.
The Real Cost of Small-Project Shortcuts
Let me break down what happened on that $15,000 order. We saved $300 by skipping the site survey—figured we could rely on the contractor's drawings. We saved $150 by not ordering a concrete inspection. We saved about two hours on the planning call.
The result: a spinner installed on a base that was 3 inches too high for the safety fall zone. The fix required:
- Breaking out the concrete pad: $1,200
- New pour and cure time: $1,500
- Lost labor for two crew members on standby: $500
- Expedited shipping for a replacement part (the original was damaged during demolition): $0 (KOMPAN replaced it, but the lead time was the issue)
Net loss: $3,200. I saved $450 in upfront costs and spent $3,200 fixing the problem. That's the "penny wise, pound foolish" math I've now built my entire process around avoiding.
Looking back, I should have insisted on a site visit. At the time, the client was eager to move fast, the budget was tight, and everyone wanted to avoid another meeting. I let schedule pressure override process discipline.
The Deep Cause: Why Small Projects Fail
Here's what most people get wrong about small playground installations. They think the risk is proportional to the budget. It's not. Small projects have three specific vulnerabilities that large projects don't:
1. Incomplete Specifications
On big projects, specs get written and reviewed by multiple stakeholders. On small ones, you get a single email with a drawing from someone who may have never ordered playground equipment before. Key details—like the type of surfacing, the required fall height, the exact model number of the spinner—get omitted because "it's just a small piece."
I once ordered a KOMPAN carousel for a community garden based on a verbal description. Assumed it was the standard model with the standard base. The client wanted the in-ground mount. I ordered the surface-mount. (Oh, and I should add: the in-ground mount requires a different concrete spec. That was a separate lesson.)
2. The "Friendly" Handoff
Small projects often skip formal handoffs. The information travels through three people: the client tells the facility manager, who emails the contractor, who calls you. By the time it reaches you, the "corner of the playground near the bench" has become "the southeast quadrant adjacent to the existing structure." And nobody checked because everyone assumed it was simple.
3. The Budget Squeeze
Small projects have small budgets. The margin for error—financially and logistically—is near zero. Yet the same number of steps is required: site prep, foundation, assembly, inspection. You can't skip steps just because the dollar amount is smaller.
To be fair, I get why clients want to simplify. A $15,000 installation feels like it should be less complex than a $150,000 one. The reality? The complexity is in the details, not the dollar amount.
The Cost of Getting It Wrong
Beyond the direct redo costs, small-project mistakes have a multiplier effect that I didn't fully appreciate until I'd made them a few times:
- Credibility damage: A small project error looks like carelessness, not complexity. The client doesn't see a complicated install—they see you didn't pay attention.
- Lost referrals: Small projects are often the first project with a new client. That community garden job could have led to a school contract. Instead, we spent the next year rebuilding trust.
- Internal morale: My crew hated rework. It's demoralizing to tear out something you just installed, especially when it was an avoidable mistake.
I want to say those were the only mistakes I made that year, but I'd be lying. We had two other small-project failures in the same quarter. One was a surfacing depth issue. The other was an incorrect fall zone calculation. Each cost between $800 and $2,000 to fix.
That's when I created our pre-install checklist. In the 18 months since, we've caught 47 potential errors using it—yes, I keep count. Small projects are finally going smoothly.
The Fix: A Simple Pre-Install Checklist
I'm not going to lay out a fifty-step process. The point of this article isn't the solution—it's understanding why small projects need the same rigor as large ones. But here's the framework I use now, which takes about 30 minutes per project:
- Verify the spec yourself. Don't rely on third-hand information. Call the client or visit the site. Confirm model numbers, mounting types, and surfacing requirements.
- Check the site against the manual. KOMPAN's installation manuals include specific requirements for base dimensions, concrete specs, and fall zones. Print them. Take them to the site. Compare.
- Photograph everything. Before you pour concrete, before you install anything, take photos of the site with measurements visible. It's the only way to prove what you found.
- Build in a buffer. Small projects often have tight timelines. Add a day for unexpected issues. If nothing goes wrong, you look efficient. If something does, you have breathing room.
That's it. Four checks. Thirty minutes. It would have saved me $3,200 and a lot of embarrassment.
Why I'm Writing This
When I was starting out in this industry, I approached KOMPAN with a $2,000 order for some replacement parts and a small fitness station. I was nervous—I expected to be treated like a small fish. Instead, the team walked me through the spec sheet, asked about the site conditions, and offered to connect me with an installer.
They treated that $2,000 order with the same seriousness as a $200,000 one. That's the approach I now take with every project, regardless of size.
Small doesn't mean unimportant. It means potential. And the way to protect that potential is to treat every project—no matter the budget—with the same planning and respect. Your future large projects depend on it.
— A playground equipment specialist who learned this lesson the expensive way.