The summer window is fixed
Work inside occupied buildings often has to land between the last day of school and teacher return. A late submittal on hardware or MEP equipment can push a classroom handover past the first bell.
Construction management for education facilities
Every school project has a deadline. The academic calendar won't move.
Jet.Build connects budgets, drawings, RFIs, submittals, change orders and reporting for K–12 and campus capital programs — with one dedicated account contact who sets it up with you and stays.
Book an Industry Demo (opens jet.build in a new tab)Explore education construction on Jet.Build (opens in a new tab)
Photo: AI-generated illustrative image, not an actual Jet.Build project.
The reality
School construction runs on someone else's calendar.
The problems are rarely the building itself. They are timing, visibility and coordination across many parties.
Bond reporting is defined by the owner
Capital-program teams report to boards, oversight committees and the public in formats the district or institution sets. Rebuilding those numbers from spreadsheets each month invites drift.
Occupied campuses add coordination
Phasing, access routes, shutdowns and noise windows have to be agreed with principals, deans, facilities and IT — and the decisions need to be findable later.
Many hands on one program
Owners, owner's reps, architects, CMs, GCs and trade partners all touch the same RFIs, changes and drawings. Email threads do not show who is holding the ball.
What Jet.Build connects
One record for every project in the program.
Project controls that typically live in separate spreadsheets, inboxes and drives, kept together.
Budgets & cost forecasting
Track budgets, commitments and change orders per project so program staff can see where a bond package stands before the next board update.
Drawings & documents
Keep drawings, specs and project documents organized and versioned, so field and office teams work from the same set.
RFIs & submittals
Log, route and follow up on RFIs and submittals with clear ownership and due dates — useful when long-lead items drive a summer schedule.
Change orders & approvals
Route change requests through approval steps you define and keep the decision trail attached to the project record.
Reporting
Pull project and portfolio status into reports structured around the owner-defined categories your program already uses.
Milestones & project teams
Set milestones such as substantial completion before move-in, and give internal and external stakeholders access to what they need.
Summer capital program — status
12
Projects
18
Approved changes
2
At-risk turnovers
- Lincoln Elementary — ModernizationTurnover Aug 14On track
- Westview MS — HVAC ReplacementTurnover Aug 21Submittal late
- Oak Ridge HS — Science WingSubstantial Jun 30Open RFIs: 6
Workflows
How different teams use it on education work.
Example workflows, written from the buyer's side. Your configuration is set up around your own process.
K–12 capital-program manager
Twelve summer projects, one board meeting in August
- Each modernization is set up as its own project under the program
- Budgets and approved changes roll into one status view
- Milestones flag which schools are at risk of missing turnover
- The board packet starts from current data, not last month's spreadsheet
University construction manager
Lab renovation in an occupied science building
- Shutdown and access decisions are logged against the project
- RFIs from the GC route to the architect with due dates
- Submittals for fume hoods and controls are tracked against need-by dates
- Facilities and department contacts see the documents relevant to them
Owner's representative
New elementary school, bond-funded
- Change orders move through owner approval steps you configure
- Cost forecast updates as commitments and changes are entered
- Drawings and specs stay versioned for each issue
- Monthly owner reporting follows the district's own categories
General contractor
Summer HVAC and finishes package across three campuses
- One project per campus with shared reporting
- Long-lead submittals are visible to the owner and design team
- Open RFIs are reviewed in weekly OAC meetings from one list
- Closeout documents are collected in one place for handover
Project types
Built for the range of work a capital program carries.
- K–12 modernizations and additions
- New school construction
- Occupied-campus renovations
- Summer-window MEP, roofing and finishes work
- Bond-funded multi-site capital programs
- Higher-ed residence halls, labs and academic buildings
- Athletic and auxiliary facilities
- Deferred-maintenance and infrastructure packages
Implementation & support
Your dedicated partner from kickoff to closeout.
Every account gets the same dedicated contact for setup, training and support. No ticket queue, no rotating reps. The setup is tailored to your program's project requirements.
- Step 1
Account setup
Your account contact configures the workspace, permissions and workflow structure around how your program actually runs — projects, phases, approval paths.
- Step 2
Data import & onboarding
Existing project records and documents are brought in as scoped in your agreement, and office, field and external partners are onboarded together.
- Step 3
Go-live
The same person stays close during launch to answer configuration and workflow questions as your first projects move into the system.
- Step 4
Weekly training
Recurring live training keeps new staff, consultants and trade partners current. Training is part of the relationship, not sold separately.
- Step 5
Ongoing support
Workflow adjustments, new projects, new team members and account changes go to the same contact who already knows your setup.
Evaluation checklist
Questions worth asking any platform you evaluate.
A neutral list to bring to vendor conversations, including ours.
- Can each school or building be tracked as its own project while rolling up to a program-level view?
- Can reporting follow the categories your board, oversight committee or institution already requires?
- How are RFIs, submittals and change orders assigned, routed and closed — and who sees what?
- How will external partners (architects, CMs, GCs, trades) be onboarded and supported?
- What does data import cover, and how are integrations and onboarding scoped in the agreement?
- Who is your day-to-day contact after go-live, and how often does training happen?
- How is pricing structured as the number of active projects changes over the program?
- What does your own procurement, IT and records process require before adoption? Confirm these directly with your organization.
FAQ
Implementation, fit and limits.
Is this the same as Jet EDU at edu.jet.build?
No. Jet EDU is a teaching platform for student learning. This page is about Jet.Build construction management software for teams that plan, build and renovate school and campus facilities.
Who is Jet.Build a fit for in education construction?
District capital-program teams, university and college facilities and construction departments, owner's representatives, construction managers and general contractors who need one place for budgets, documents, RFIs, submittals, change orders, approvals and reporting.
How does implementation work?
A dedicated account contact helps set up your account and workflows, supports data import and onboarding as scoped in your agreement, stays with you through go-live, and runs weekly training. The specific setup is tailored to your program's requirements.
Will the same person support us after launch?
Yes. Jet.Build's model is one dedicated account contact who continues as your point of contact for workflow changes, new projects and new users after go-live.
How is pricing structured?
Pricing is generally based on active projects rather than per-seat fees, so you can bring in your whole team and partners. Integrations and onboarding are scoped per agreement. Your demo is the place to get specifics for your program.
Does Jet.Build replace our procurement, safety or compliance processes?
No. Jet.Build is project management software. It does not certify school safety or regulatory compliance and does not replace your organization's procurement approvals. Confirm those requirements with your own procurement, legal and IT teams.
What should we bring to an industry demo?
A representative project or program, your current reporting format, the approval steps you use for changes, and the list of internal and external parties who need access. The walkthrough focuses on those workflows.
Plan next summer's work with the calendar in view.
Bring one real project. We'll walk through it in Jet.Build and show how setup, training and support would work for your team.