The Contractor's Question

So here's a thing that nobody thinks about.

You're a general contractor. You've got crews, equipment, scheduling, bids to manage. A potential client mentions a big industrial project coming to the area—data center, maybe, or distribution, or something else heavy.

You want the job.

But you also want to know: how long is this actually going to take?

Not because you're curious.

Because you need to know if your crews are going to be tied up for six months or three years.

Because that changes everything about whether you can even bid on it.

Because that's how you plan your business.

So you do what any contractor would do.

You look for the timeline.

Finding the Answer That Might Not Be Final

A few weeks back, Panattoni—the developer behind Project Shelby—said in a local media interview that construction would take approximately 2.5 years.

I logged that into the Project Shelby dossier as a tracked finding.

Here's the thing, though: I marked it exactly the way it should be marked.

Developer's claim.

Not independently verified.

Source: Panattoni, August 2026.

That matters.

Because "approximately 2.5 years" is what one person said one time in one interview.

It's not a permit filing.

It's not an engineering report.

It's not a contract with a known penalty for delay.

It's an estimate.

The contractor asking that question—the one who needs to actually plan a business around the answer—has to know the difference between "the developer said this" and "this is documented in a filed permit with enforceable terms."

They're not the same thing.

And honestly?

I don't even know if 2.5 years is the right number to look for.

Construction timelines slip.

Weather happens.

Supply chains break.

Permitting takes longer than expected.

I've watched enough software projects miss their ship dates to know that "estimated completion" is often more of a hope than a promise.

But I'm a tech nerd, not a heavy construction guy.

So I don't know what's typical for industrial builds in Ohio.

I just know what was said.

The Whole Stack of Unknowns

Here's what I'm realizing, though.

A lot of what matters about a development project isn't in a single finding.

It's in the pattern.

The contractor wondering about timeline also wants to know: who's the general contractor on this job? (I don't have that yet.) What equipment is going to be needed? (Not logged.) Are there union requirements? (No idea.) Will permits slow things down? (Haven't seen the full permit stack.) Who else is bidding?

What's the actual economic picture?

Because right now, the contractor has one sentence from a developer, and that's it.

Everything else they need is scattered across permit filings, zoning approvals, utility assessments, maybe a news article here and there—if they can find it.

It's all public, technically.

But it's not exactly next to each other.

And a person running a business doesn't necessarily have ten hours to hunt for it the way I do.

They have a job to bid on, or they don't.

Why That Matters to Me

This is where my own conflict sits.

I'm trying to build a tool that makes it easier for people to see what's happening.

For contractors, for real estate people, for residents, for anybody who has a stake.

And one of the ways that tool works is by tracking what's been claimed—and being really clear about what's been verified versus what's just been said.

The contractor needs to know that timeline came from the developer's mouth, not from a regulatory filing.

The resident needs to know the difference too.

So does the city planner, or the utility company, or anyone else making a decision.

Transparency isn't just "here's the information."

It's also "here's where this information came from, and here's whether it's been verified yet."

Because the source matters.

The credibility matters.

And if I don't track that difference, then I'm not actually being transparent.

I'm just pointing people at a pile of claims.

Why We're Tracking This

That's what the Project Shelby dossier is for.

Everything we've logged—the timeline estimate, the developer, the date, the verification status—sits in one place where a contractor or a resident or anyone else can see it, compare it against what they're hearing from other sources, and decide what to do with it.

One estimate isn't a secret.

But ten different sources all claiming different timelines?

That's useful information.

That's a pattern.

That's something worth noticing.

Right now we're still in the early phase of tracking this project.

But as more filings come in—permits, utility requests, zoning materials, meeting minutes—the picture gets bigger and more detailed.

The contractor gets a better answer to their question.

The resident gets a clearer sense of what's coming.

And everyone can see how the pieces fit together.

That's the whole point.