Lexington, Kentucky

Eli Hart

An early construction operator building toward ownership.

Based in Lexington, Kentucky, I’m building an early career across project management and field coordination — using project controls, documentation discipline, and private workflow systems to tighten how construction work moves from information to action.

Eli Hart
Based InLexington, Kentucky
Current StageConstruction Management
Operating EdgeProject Controls
DirectionHartwood Group
Scroll
Operator Brief

Stage, edge, and direction.

A concise operating brief on current stage, working edge, and long-term direction.

Current Stage

Construction management, field coordination, and project documentation — RFIs, submittals, meeting minutes, site walks, and schedule awareness.

Operating Edge

Disciplined project controls, correspondence tracking, and review gates, supported by private workflow systems built to reduce missed handoffs and memory-dependent follow-up.

Long-Term Direction

Hartwood Group — a deliberate path toward construction-informed development, ownership, and long-term project control.

01Method

Standard project controls, tightened through private workflow systems.

Most construction problems begin as information failures — an unanswered email, a submittal that sits too long, an RFI without a clear owner, a field note that never reaches the log, a schedule item that drops out of the next conversation. Project controls exist to make those gaps visible. Private workflow systems organize the correspondence, documentation, and follow-up those controls depend on. Human review gates keep judgment, confidentiality, and professional standards in front of every output. The point isn’t automation for its own sake — it’s tighter project execution.

In practice it runs as a simple loop — capture, organize, review, act — applied to the ordinary flow of a project.

  1. 01CapturePull every request, answer, and observation into one accountable place.
  2. 02OrganizeSort by owner, due date, and project area so status is something you check, not remember.
  3. 03ReviewA person checks each draft for accuracy, confidentiality, and judgment before it moves.
  4. 04ActSend, file, or track — with the next required step already defined.
Project Controls
The core of the work is disciplined document control and correspondence tracking: keeping RFI and submittal flow, change-order awareness, procurement logs, meeting minutes, and schedule lookaheads current and accounted for. The aim is a project where the status of any open item is something you can check, not reconstruct — so field coordination and office records stay in step.
Closed Workflow Systems
To support those controls, I build private, self-contained AI workflows that watch correspondence, organize action items, and draft routine documentation so nothing important sits unchecked. These systems are closed by design — project information stays in my own environment rather than being pushed into open public tools — and they assist the process rather than define it.
Human Review Gates
Automation organizes and drafts; it doesn’t decide. Every RFI response, submittal, log entry, and piece of correspondence passes a review gate before it goes anywhere. The workflow speeds up the routine handling so the judgment calls get more attention — not less — and nothing leaves without being checked by a person.
02Docket

Execution Docket

Confidential-safe examples of how I read everyday construction coordination items as control points — each tied to memory, owner, risk, action, review, and closeout.

01

Correspondence triage

Problem

Important decisions, approvals, and requests get buried across email threads, texts, calls, and meeting follow-ups.

Operator Method

I read correspondence as a stream of control items, not a list of messages — each tagged by source, owner, due date, project area, urgency, and required next move. The method separates true action items from noise and carries unresolved ones forward in a private control layer until they are closed, escalated, or formally parked.

Operating Difference

The aim is not inbox organization. It is decision preservation — making sure something casually agreed to in a thread or a hallway does not quietly disappear.

Why it matters

Missed communication is where cost, delay, and owner frustration usually begin.

02

RFI follow-up logic

Problem

Open questions create field uncertainty when responsibility, status, and impact are not made visible.

Operator Method

The method treats each RFI as a control item rather than a document — tracking what is being asked, why it matters, who owns the answer, what work it may affect, when it was raised, and what decision is needed to release action. Information questions stay separate from production-blocking ones.

Operating Difference

Attention follows exposure, not paperwork — the priority is knowing which unanswered item is putting schedule, cost, or field execution at risk.

Why it matters

A late answer is not always the problem; not knowing which open item is creating exposure is the bigger one.

03

Submittal tracking

Problem

Submittals lose value when review timing, distribution, procurement impact, and field readiness are not connected.

Operator Method

The workflow tracks submittals through a readiness lens — submitted, under review, returned, revise/resubmit, released, procurement-linked, and field-distributed — and treats returned information as something people have to act from, not just a status to file.

Operating Difference

The control point is whether the right field and procurement conversations can move from a returned submittal — not merely whether the document exists.

Why it matters

A returned submittal that never reaches the right field or procurement conversation can still create delay.

04

Meeting-minute capture

Problem

Meetings create obligations, but those obligations often disappear when minutes are treated as records instead of work instructions.

Operator Method

I convert meetings into a decision-and-commitment log: each item carries a responsible party, due date, carry-forward status, a related document where relevant, and whether it needs follow-up, escalation, or closeout.

Operating Difference

Minutes are not passive summaries; they are a continuity tool that ties conversation back to actual project movement.

Why it matters

A clean meeting record protects accountability and reduces repeat conversations.

05

Procurement / lookahead awareness

Problem

Material and equipment issues compound when documentation, approval, lead time, and schedule windows are tracked separately.

Operator Method

The control layer ties procurement concerns into one connected record — required approval, submittal status, lead-time exposure, needed-on-site window, responsible party, and current blocker — and flags the line between “not urgent yet” and “about to affect the field.”

Operating Difference

This is lookahead protection: watching the exact point where a paperwork delay turns into a sequencing delay.

Why it matters

Procurement problems become expensive when they are noticed only after the field is ready.

06

Site-walk observation notes

Problem

Field observations lose value when they stay in a notebook, camera roll, or memory instead of entering the project record.

Operator Method

I log each observation by location, trade, condition, reference photo, required follow-up, and closeout status — distinguishing a simple observation from a quality concern, a coordination issue, an owner decision, or a schedule-sensitive item.

Operating Difference

The site walk becomes field-to-office continuity — a feedback loop between what is happening on site and what the record shows — not a visual check-in.

Why it matters

Good field notes keep small issues from becoming undocumented disputes later.

07

Review-gate discipline

Problem

Fast communication without review creates risk: wrong recipient, unclear wording, incomplete record, or premature commitment.

Operator Method

Before anything leaves the loop it passes a review gate — draft, verify context, confirm owner, check attachments and references, weigh risk, then send, file, track, or escalate. The private workflow supports memory and drafting; the review gate keeps judgment human.

Operating Difference

Speed comes from control, not impulse. Nothing meaningful moves forward without review before action.

Why it matters

Professionalism is not just moving fast. It is moving cleanly.

03Experience

A deliberate progression — from materials and quality control, to project engineering, to project management — each role moving closer to how a job is planned, coordinated, and controlled. Kept general here: no confidential project, client, or company details.

Summer 2026

Project Management Intern

Gray Construction — Lexington, KY

  • Support project managers with subcontractor coordination, documentation, and daily field operations.
  • Help keep RFIs, submittals, meeting minutes, and project records accurate and current.
  • Conduct site walks to monitor progress, safety, quality, and schedule.

ToolsProcore · Bluebeam · Microsoft Office

Fall 2025

Project Engineer Co-Op

Messer Construction — Lexington, KY

  • Coordinated with subcontractors and trade crews to keep schedule and workflow on track.
  • Organized submittals and project documentation for accuracy and timely review.
  • Performed on-site observations and documented progress against milestones.

ToolsProcore · Bluebeam · MS Project

Summer 2025

Quality Control Intern

Hinkle Construction — Stanton, KY

  • Conducted lab testing on asphalt and concrete materials to verify specification compliance.
  • Prepared and analyzed hot-mix asphalt samples for quality and performance.
  • Documented and reported daily quality control results to project teams.
Education

B.S., Construction Management

Eastern Kentucky University — Richmond, KY · Expected May 2027

Associate of General Studies — Bluegrass Community & Technical College (2024–2025).

What this is building

Field familiarity
Understanding how work actually moves on site — not only how it appears in the documents.
Documentation discipline
RFIs, submittals, meeting minutes, correspondence, and project records kept accurate and current.
Project-control awareness
Schedule, procurement, cost exposure, open-item tracking, and follow-through.
Ownership perspective
Learning construction through the lens of future development and long-term project control.
04Thesis

Where construction goes from here.

Construction stayed under-digitized while the work itself grew bigger and more complex. AI can close part of that gap — but the data-risk concerns firms raise about open, public tools are legitimate. The real opening is controlled, closed-loop systems a company actually owns. My interest is in learning that early, from inside the work, before it becomes the standard.

01Productivity gap

Construction is among the least-digitized major industries, and it shows: labor productivity has grown roughly 1% a year for two decades while the broader economy grew closer to 3%. Large projects still run about 20% past schedule and as much as 80% over budget.

02Adoption gap

Interest is near-universal; adoption isn't. In a 2025 RICS survey of more than 2,200 professionals, close to half had no AI in place and roughly another third were still in early pilots — and Dodge's 2025 data shows fewer than one in five firms actually changing how they work.

03Data-risk barrier

The barrier isn't cost or stubbornness — it's data. Around half of firms cite privacy, security, and IP risk, and they're right to: bids, owner agreements, subcontractor pricing, and NDA-held drawings don't belong in a public model the firm doesn't control.

04Closed-loop opportunity

The most-cited objection is also the most solvable. Closed-loop, file-based workflows keep everything inside an environment the firm owns — the AI works over its own files, with nothing pushed to a service it doesn't govern. Advisory guidance already points proprietary project data toward closed, self-contained tools.

Read the full thesis

Construction is one of the least digitized major industries in the world — by McKinsey’s Global Institute index, it sits near the very bottom. The cost of that shows up in the numbers: construction labor productivity has grown roughly 1% a year for two decades, while the wider economy grew closer to 3%. Large projects still run, on average, around 20% past schedule and as much as 80% over budget. The work got bigger and more complex; the way it’s managed barely moved.

AI is the first thing in a generation with a real shot at closing that gap, and the industry knows it. But knowing isn’t doing. In a 2025 RICS survey of more than 2,200 professionals, close to half had no AI in place and roughly another third were still stuck in early pilots. Dodge Construction Network’s 2025 contractor data tells the same story — fewer than one in five firms are actually changing how they work. The interest is nearly universal. The adoption isn’t.

The reason isn’t stubbornness, and it isn’t cost. Survey after survey lands on the same barrier: data. Around half of firms name privacy, security, and intellectual-property risk as the thing holding them back — and they’re right to. A bid, an owner agreement, subcontractor pricing, a drawing held under NDA — none of that belongs in a public model you don’t control, where it can leak or quietly train someone else’s tool. The caution is rational. It’s also where most of the industry has decided to stop.

Here’s the part the wait-and-see posture misses: that exact objection is the most solvable one on the list. Closed-loop, file-based workflows keep everything inside an environment the company owns — the AI works over your own files, on your own terms, and nothing is pushed out to a service you don’t govern. This isn’t a fringe view. Advisory firms like RSM already tell construction clients that anything involving client data, financials, or proprietary project information belongs in closed, self-contained tools rather than open public ones. The wall most firms are standing behind has a door in it. Few have walked through it.

And industries don’t wait for the cautious. Innosight’s corporate-longevity research shows the average company now lasts about 15 years on the S&P 500, down from over 30 a generation ago, with a large share of today’s index projected to turn over within the decade. The pattern behind that churn is consistent: incumbents treat a structural shift as optional right up until it isn’t, and by the time the proof is undeniable, the new standard has already been written by whoever moved earlier. Resistance doesn’t stop the evolution — it only decides which side of it a company ends up on.

Construction won’t be the exception. The firms treating closed-loop AI as a careful, in-house engineering problem today are the ones who will set how projects run a decade from now — tighter coordination, cleaner records, faster turnaround, without ever surrendering control of the data. The firms waiting to watch the results will spend that decade adapting to a standard they had no hand in setting. I’d rather help write it than inherit it. That’s the bet the rest of my work is built on.

Sources — McKinsey Global Institute (Reinventing Construction, productivity & digitization indices); RICS AI in Construction survey, 2025; Dodge Construction Network contractor survey, 2025; RSM US AI adoption guidance, 2025; Innosight corporate-longevity research.

05Market

Kentucky market conviction.

Hartwood’s long-term direction is being shaped around Kentucky growth corridors where housing movement, household income, industrial expansion, and fragmented project execution needs overlap.

This is the market logic shaping my long-term platform direction — a working thesis, not a development plan. I read five Kentucky corridors through the same operator lens I bring to a project: where population, permits, household income, housing movement, and industrial expansion overlap with real project-execution needs, and where there is room for disciplined small-company entry over time.

1 2 3 4 5
Strategic region map — simplified, not survey-grade GIS.
01

Bluegrass Core / Lexington Ring

Fayette · Scott · Jessamine · Madison · Woodford · Clark

The home-base region. It gives proximity, credibility, relationship density, and a practical starting point for residential project work, owner-side coordination, and long-term market learning.

  • Fayette County had about 329,800 people in 2025.
  • Fayette County had 152,488 housing units in 2025.
  • Fayette County had 1,052 building permits in 2025.
  • Scott County median household income was $85,158.

OpportunityPremium residential upgrades, small-scale residential coordination, owner-side project discipline, and long-term market learning.

02

Northern Kentucky / Cincinnati Edge

Boone · Kenton · Campbell

A higher-income suburban and logistics-connected corridor tied to the Cincinnati metro edge.

  • Boone County median household income was $99,414.
  • Boone County mean travel time to work was 25.0 minutes.
  • Boone County transportation and warehousing receipts were $1.87B in 2022.
  • Campbell County median household income was $77,567.

OpportunityOwner-occupied residential improvements, infill coordination, and housing demand supported by logistics and cross-metro employment.

03

Louisville East / Oldham–Shelby Corridor

Jefferson · Oldham · Shelby · Bullitt

The Louisville region provides scale, while Oldham/Shelby-style suburban wealth creates a higher-value residential improvement and ownership-learning corridor.

  • Oldham County median household income was $122,497.
  • Oldham County owner-occupied housing rate was 87.1%.
  • Oldham County median owner-occupied home value was $393,100.
  • Oldham County had 24,896 housing units in 2025.

OpportunityHigh-value owner-occupied residential work, additions, renovations, disciplined contractor coordination, and long-term development exposure.

04

South Central / Bowling Green–Warren

Warren · Barren · Simpson · Allen

A high-permit, manufacturing-supported growth market with more room for disciplined small-company entry than Kentucky’s largest urban centers.

  • Warren County population was 149,375 in 2025.
  • Warren County population increased 11.0% from the 2020 estimates base to 2025.
  • Warren County had 1,453 building permits in 2025.
  • Warren County median owner-occupied home value was $258,000.
  • Warren County median gross rent was $1,002.
  • ValorFlex announced a $23.4 million Bowling Green facility creating 82 jobs.
  • AKFA announced a Bowling Green manufacturing facility creating 331 Kentucky jobs.

OpportunityGrowth-market residential work, project coordination, site-readiness awareness, and practical development learning.

05

Richmond / Madison–I-75 Southeast Gateway

Madison · Estill · Garrard · Rockcastle · Laurel

A lower-cost, I-75-connected corridor with university influence, industrial-site positioning, and practical residential/project execution needs.

  • Madison County median household income was $63,351.
  • Madison County mean travel time to work was 25.2 minutes.
  • Richmond Industrial Park South III received $500,000 in Kentucky Product Development Initiative funding.
  • Richmond Industrial Park South III is a CSX Select Site.

OpportunityEntry-level deal flow, renovation and repair coordination, smaller residential projects, and long-term market learning before larger development activity.

How I read the map

This is not a claim of market control. It is a working thesis: start close, learn the work, understand housing movement and permitting pressure, build execution discipline, and expand only where the data and relationships justify it.

Source ledger

The figures in this section are directional public-market signals, not underwriting assumptions.

U.S. Census Bureau QuickFacts
County population, housing units, building permits, income, commute time, owner-occupied housing, home value, and rent metrics.
USAFacts population summaries
County population summaries where applicable.
Kentucky Cabinet for Economic Development
Industrial expansion announcements and job-creation references.
Kentucky Product Development Initiative / state site-readiness announcements
Site-readiness and product-development references.

Metrics should be rechecked before investor-facing, lending, underwriting, or legal use.

06Ventures

Ventures.

Commercial and civic work being built alongside my construction track — with Hartwood Group as the primary long-term platform.

Primary platform

Hartwood Group.

Hartwood Group is the long-term platform behind the direction I am building toward — construction-informed development, disciplined project execution, residential project work, and eventual ownership.

Hartwood Group began as a project between my brother and me, originally founded as Tankersley Contracting & Advisors, LLC. The early, hands-on work was straightforward and done one job at a time — residential fencing, residential and storefront blacktop sealing, and barn remodels — closer to a contractor and service-work model than to what we are building toward now.

The posture today is more deliberate. Rather than scaling that early service model, my brother and I are each building real footing in our own industries first, and treating Hartwood as a platform to grow on purpose rather than in a hurry.

The long-term direction is construction-informed development — residential project work, disciplined project control, and eventual ownership of what we plan and build. It is early-stage, and deliberately so: the early work taught us how things get built; the next chapter is about applying that on our own terms.

StageEarly-stage platform
BaseLexington, Kentucky
OriginTCA → Hartwood Group
DirectionDevelopment + ownership
Sitehartwood.group — launching soon
07Systems

Private workflow discipline.

The systems I am building are not meant to replace construction judgment. They are private workflow layers that help preserve correspondence, project records, task memory, review gates, and follow-through — the quiet parts of project execution that create exposure when they are left to memory alone.

Correspondence memory
Emails, meeting items, and informal follow-ups are captured and carried forward until they are resolved — instead of scattering across threads and apps where they quietly fall off.
Documentation follow-through
RFIs, submittals, field notes, and procurement concerns only matter if they stay connected to the action they require, with status held in view until each is closed out.
Review before action
Private systems help draft and organize, but meaningful communication still passes a human review before it leaves the loop. Judgment stays with a person.

The goal is not automation for its own sake. The goal is cleaner coordination: a private record-to-action loop that supports judgment, protects the project record, and keeps the next move visible.

08Profile

Diligence / Profile

A cleaner view of the materials someone may want before a serious conversation.

Operating Brief
Available on request
09Contact

Get in touch.

Open to opportunities and conversations across construction, project management, and development. Feel free to reach out.

LinkedInin/eli-hart
LocationLexington, Kentucky