How Long Does 2.5 Years Actually Mean?

So I was digging through the Project Shelby dossier earlier this week, and I found something that seemed like it should be straightforward.

A timeline.

The developer says the whole thing takes about 2.5 years to build.

That's a number.

Numbers are supposed to be clear.

And yet.

I realized I had no idea what that actually meant, or where it came from, or whether it would hold up, or what happens if it doesn't.

So naturally I started wondering how I would even verify something like that.

Finding the Estimate

The number comes from Panattoni—the development company working on Project Shelby—according to a report from WHBC dated August 18th, 2026.

2.5 years.

That's specific enough to sound like an informed projection.

Specific enough that someone reading it might think, okay, so construction wraps up in mid-2028 or so, depending on when they break ground.

But here's the thing.

That's what the developer said.

Not what an independent source verified.

Not what a third-party timeline analysis confirmed.

Not what a permit application documented with engineering specifics.

What the developer said.

And I have absolutely no way to know—just from reading that number—whether it's based on detailed project scheduling, whether it's a conservative estimate, whether it's optimistic, whether similar projects in similar conditions actually hit that timeline, or whether it's the kind of projection that changes on week three of the project when somebody discovers something unexpected.

The Question Nobody Asks Until It Matters

Here's what fascinates me about timelines.

We use them all the time.

The highway construction will take three years.

The factory renovation will be done by spring.

Your software project will ship in two quarters.

And then life happens.

Materials get delayed.

Weather happens.

Supply chains do weird things.

You discover the foundation has a crack.

The code takes longer to debug than anyone expected.

Suddenly that 2.5 year estimate becomes 3.2 years.

Or 2 years.

Or nobody really knows anymore because the goalpost moved and now you're just trying to remember when they said it would be done.

I don't know much about construction timelines.

I know plenty about software timelines, though.

And let me tell you: every engineer in the world will tell you the same thing about deadlines.

They're imaginary until they're not.

What I Actually Don't Understand

Here's my honest gap in knowledge.

For a project like this, is that 2.5 year estimate something a county would verify independently before approving the project?

Does somebody check the developer's math?

Does someone with actual construction experience review the timeline and say, "Yeah, that pencils out" or "No, that's wishful thinking"?

Or does the number just go into a file and everyone moves forward on the assumption that yes, sure, that's probably about right?

I genuinely don't know.

And I'm not going to guess and sound like I do.

But I know it matters.

Because if a project is supposed to be done in 2.5 years and then it's still running in year four, that affects traffic, noise, dust, local businesses, property values, everything downstream.

The longer it runs, the longer the impact runs.

And if nobody ever confirmed whether 2.5 years was realistic in the first place, well.

That seems like it might have been worth asking.

That's What the Dossier Is For

This is exactly why I built the Project Shelby dossier the way I did.

One item—one estimate—gets logged with its source clearly marked.

Not as gospel.

Not as verified fact.

But as: here's what was claimed, here's when it was claimed, here's who claimed it.

That way, when someone else files a revised timeline six months from now, you can see it side by side with the original.

When news reports mention the project, you can cross-reference what they're saying against what actually got filed.

When people are talking about this project—and they will be—you can point to what was actually said and when, instead of relying on memory or rumors.

2.5 years is a claim.

Not a guarantee.

And keeping track of the claim is a lot more useful than pretending we never heard it.