How 670 Construction Jobs Got Connected to a Tax Deal Nobody Explained

So I'm digging through the Faircrest Data Center dossier.

You know the project—the one in Perry Township that's been filing permits and zoning stuff for the last couple of years.

And I'm trying to catalog what we actually know about it versus what we're just guessing at.

One of the things that came up early was jobs.

Construction jobs, specifically.

About 670 of them, according to reporting from the Canton Repository back in June.

That's not a small number for Stark County.

But here's where it got interesting.

Those 670 trade workers weren't just a prediction somebody made up.

The number came from somewhere official.

And it connected to something else: a tax abatement discussion.

And IBEW Local 540—the electrical workers union—was apparently in the conversation about why that tax deal made sense.

All of that seemed like it should connect somehow.

So I started trying to figure out what the actual connection was.

Tracing the Jobs Back to the Paperwork

This is the part where I got a little lost.

And I'm going to be honest about it, because it's genuinely confusing to track.

The 670 number appears in Grace Springer's reporting, and that's the source we've verified in the dossier.

But the number itself—where did it come from originally?

A project estimate.

A bid from a contractor.

Some kind of county or township study.

I don't actually know.

And I'm not going to guess.

What I do know is that the construction employment projection got connected, in public conversation, to the discussion about whether the tax abatement made sense.

The union's support apparently hinged on job opportunities for members.

That's a real thing that happened.

But the actual documents that laid out the tax abatement details, the conditions, the timeline, the exact numbers being discussed—those are sitting in township or county files somewhere.

And honestly, I haven't found them yet.

Which is either because they're not online, or because I'm looking in the wrong place, or both.

Welcome to my life.

Why This Actually Matters

Here's the thing about development projects of this scale:

Money flows.

Jobs get created.

Infrastructure changes.

Communities notice.

But the conversation about whether any of that is actually a good trade-off usually happens somewhere between a permit filing and a public meeting and maybe a local news story.

And different people in that conversation are looking at completely different questions.

A construction worker cares about 670 jobs for the next however many months.

A union rep cares about those being good jobs with union pay.

A township wants the tax revenue or the infrastructure improvement or both.

A neighbor wants to know if power lines are going up in their backyard.

An accountant wants to see if the tax abatement actually pencils.

And all of those conversations are happening.

But they're not necessarily happening in the same room, at the same time, looking at the same numbers.

Because the documents that pin down those numbers are scattered across different files, different offices, different meetings.

What I'm Actually Wrestling With

I'm building a tool that's supposed to help people see what's actually happening here.

But I can only show people what I can actually find and verify.

And that creates a weird position for me.

If the 670 jobs number is real, but the justification for the tax abatement is sitting in a filing I haven't located yet, then someone reading the dossier might think I've done a complete job when I actually haven't.

Or worse—they might think the jobs and the tax deal are the same thing when they're actually two separate questions that just happen to overlap.

That's different from having the wrong answer.

That's having an incomplete picture.

And the more complex a project gets, the easier it is for an incomplete picture to feel complete.

Especially when an AI is helping organize the documents and I'm probably the only person reading the original files to verify anything at all.

Which means I'm the one responsible for knowing the difference between "we found this" and "we still don't know."

And I take that seriously.

Because if people are going to use this site to understand what's actually happening in their county, they need to know what we actually verified and what we're still hunting for.

That's What the Dossier Is For

The project dossier isn't a finished report.

It's a living tracker.

We found 670 construction jobs connected to Faircrest, and we verified it came from a real news source.

We know the union was part of the conversation about why the tax abatement happened.

We've got those as confirmed facts.

But we're also tracking what we still need to find—the actual tax abatement documents, the specific terms, the full timeline.

That stuff matters too.

Because it's the difference between knowing that something happened and understanding why.

The more projects we're tracking here in Stark County right now, the easier it is for all these documents to blur together.

That's exactly what Stark Civic Monitor is supposed to prevent—putting all the filings, all the news coverage, all the meeting minutes in one place so people can actually see what connects to what instead of accidentally confusing two separate things.

We're not done hunting yet.

But the hunt itself is part of what you're seeing.