Business tool builder

Your roofing scheduler knows which jobs
the rain just pushed to next week.

Tell the agent how your crews, job stages and material drops work. It builds a web app with a crew board, weather holds and a foreman day sheet, on a live preview you can steer.

Starter prompt

Build a roofing scheduler web app for a residential roofing company with four crews. Track jobs with the address, access notes, squares, pitch, layers to tear off, stage and a customer contact, and crews with a daily squares capacity. Schedule each job as one or more crew days and flag a day whose squares, after a difficulty factor for steep pitch and extra tear-off layers, pass that crew’s capacity. Foremen open their crew’s day sheet on a phone, log squares installed, add photos and mark weather holds. Track shingle and roll-off deliveries with drop and pickup dates, and warn me when a job starts before its material lands.

Build it in Netiva Paste the prompt into a new workspace and adjust it to your business.
Overview

Who this roofing scheduler is for

Most roofing companies schedule from a whiteboard, a shared calendar and a run of phone calls the night before a storm. The office knows a job is sold; the foreman finds out at 6 a.m. that the shingles never left the yard. A roofing scheduler built with Netiva keeps jobs, crew days, material drops and permit dates together, so you can see how many squares each crew is carrying this week, put a day on weather hold and move the rest of that job without losing the roll-off pickup.

Key features

What your roofing scheduler can do

  • A crew board built from days

    A roof is rarely one date. Every job is booked as crew days, and the board shows each crew’s week, squares weighted by a steep-slope labor factor and a tear-off allowance against their daily capacity, and which days are still open.

    • Squares from the measured footprint times the slope factor for the pitch
    • A flag when a day’s labor-weighted squares pass the crew’s capacity
    • Multi-day jobs drawn as a run of days across each crew’s week
    • Saved views for this week, next week and jobs waiting to be booked
  • Weather holds that move the job

    Mark a crew day as a weather hold with a reason and the app offers the crew’s next open date for the days that were left, so the rest of the job travels with it instead of being rebooked one day at a time.

    • Hold reasons kept on the day: rain, wind, frost or heat
    • The remaining days of a held job moved together
    • A hold list the office clears every morning
    • Forecast per job address through a weather provider’s API
  • Material drops, roll-offs and permits

    Shingle loads, underlayment, membrane and roll-off containers each get a record with a drop date, a pickup date and where it goes. The app flags any job booked to start before its material lands or without a permit number.

    • Rooftop load or ground drop noted on every delivery
    • Container drop-off and pickup dates beside the crew days
    • Permit number and the inspection stage held on the job
    • A morning email listing today’s drops, holds and starts
  • A day sheet for the crew on site

    Foremen sign in on a phone, open their crew’s day sheet, read the pitch, layers and access notes before the truck is unloaded, then log squares installed and photograph the deck while it is still open.

    • Address, squares, pitch and layers on one phone screen
    • Deck, dry-in and finished photos saved on the crew day
    • Squares installed entered before the crew leaves
    • Each foreman sees only their own crew’s days
Data model

The collections behind it

Netiva keeps your records in built-in collections. Here’s a starting structure — the agent adapts it to your prompt, and you can change it any time.

Jobs

Every sold roof, from the measurements to the final inspection.

  • Address (required) Text
  • Access notes Where the roll-off goes, driveway limits, lawn and landscaping to protect Paragraph
  • Stage (required) Sold, Measured, Permit, Ready, Scheduled, In progress, Punch list, Inspection, Closed Text
  • Squares Roof area in squares (100 square feet each); blank until the roof is measured Number
  • Pitch Rise over 12, such as 6:12; blank until the roof is measured Text
  • Layers to tear off 0 for new construction or a planned layover Number
  • Permit number Blank until the building department issues it Text
  • Customer contact Name and phone for the homeowner or property manager Text

Crews

Who is installing, and how much roof each crew puts on in a normal day.

  • Name (required) Text
  • Foreman email (required) Matches the foreman’s sign-in so the day sheet finds their crew Text
  • Crew size Number
  • Squares per day (required) Your own average on a walkable pitch; the board compares against it Number
  • Type In-house or subcontracted Text
  • Active Yes or no; keeps last season’s crews off the board Text

Crew days

One crew, one job, one date — the block the board draws.

  • Job (required) Relation to Jobs
  • Crew (required) Relation to Crews
  • Date (required) Date
  • Work (required) Tear-off, dry-in, install, membrane, metal or cleanup Text
  • Status (required) Planned, On site, Weather hold, Done Text
  • Hold reason Rain, wind, frost, heat or a late delivery Text
  • Squares installed Number
  • Photos Image

Deliveries

Shingle loads, membrane, underlayment and roll-offs, with the dates each lands and leaves.

  • Job (required) Relation to Jobs
  • Kind (required) Shingles, underlayment, membrane, insulation, metal or roll-off container Text
  • Supplier (required) Text
  • Drop date (required) Date
  • Pickup date Roll-off collection; blank for a material drop Date
  • Placement Rooftop load, ground drop or driveway, and which elevation to load Text
  • Status (required) Ordered, Confirmed, Delivered, Picked up Text
  • Contact Yard dispatcher or container company, for rebooking a drop Text

Required field. Types are Netiva collection field types.

Screens

Pages and screens to start with

A typical first version. Ask the agent for more, or annotate the preview to change any of them.

  • Crew board

    Each crew’s week in a column, with the address, the work for that day, squares booked against capacity and every hold marked.

    Your team
  • Day sheet

    The phone screen a foreman opens on site: address and access notes, pitch and layers, squares installed and photos of the deck.

    Signed-in users
  • Job

    One roof end to end — measurements, access notes, stage, permit number and the customer to call, with every crew day and delivery attached to it.

    Your team
  • Deliveries

    Shingle loads, underlayment, membrane and containers by drop and pickup date, with anything landing after its crew day at the top.

    Your team
  • Weather holds

    Held days and the jobs behind them, so the office can rebook each one onto its crew’s next open date.

    Your team
  • Pipeline

    Sold jobs by stage, showing which still need a measurement, a permit or a material order before they can reach the board.

    Your team
How it works

From prompt to a live roofing scheduler

  1. Describe how you book work

    Tell Netiva how many crews you run, what a normal day of squares looks like and which stages a job passes through before it can start. The agent drafts collections for jobs, crews, crew days and deliveries.

  2. Load the crews and this season’s jobs

    Enter crews and sold jobs in the collection grid, or ask the collection assistant to draft rows from your notes and tidy addresses, then set capacities, stages and permit numbers.

  3. Book a test week in the preview

    Put a week of crew days on the board in the live preview, hold one for rain and open the day sheet at phone width. Annotate anything that reads wrong and the agent changes it while you watch.

  4. Publish before the next storm

    Publish in one click on your own domain, with SSL and hosting handled for you, so foremen can sign in from the truck. Custom domains start on the Starter plan. Every later change is checkpointed and easy to roll back.

Why Netiva

Netiva vs a traditional build

Building a roofing scheduler with Netiva compared with a traditional build
Criterion With Netiva Traditional build
Rescheduling a rained-out day The held day and the days still to come moved onto the crew’s next open date Calls the night before, then the whiteboard redrawn on Monday morning
Crew capacity Booked squares compared with each crew’s daily capacity as you schedule A feel for how much a crew can install, argued about once the day is lost
Getting started Describe what you need in chat and watch it take shape in a live preview Hire developers, or stitch together templates, plugins and a hosting plan
Content and data Built-in collections with nine field types, bound straight to your pages Set up and connect a separate database or CMS
Making changes Ask the agent; every change is checkpointed and reversible File a ticket, wait for a sprint, redeploy
Hosting and domain Global hosting and automatic SSL; connect a custom domain from the Starter plan Buy hosting, then install and renew SSL certificates yourself
Code ownership Clean production code you own and can export Locked into a template, plugin or agency setup
Examples

Ways teams use it

  • A residential roofer with four crews

    Most jobs are a day of tear-off and install, some are two. The production manager books a week at a time, and when a crew finishes by lunch the board shows the next job whose shingles are already sitting on the roof.

  • A storm-season contractor with a permit backlog

    After a hail event the pipeline runs into the hundreds. Jobs stay at the permit or material stage until both clear, so only work that can genuinely start that week reaches a crew’s column on the board.

  • A commercial re-roof run in phases

    A large flat roof goes on in sections over several weeks — tear-off, insulation, membrane — with an inspection between phases and some work done after hours. Each section is its own run of crew days and the deliveries screen keeps the drops in step.

Good to know

Before you build

  • The forecast comes from a provider you choose

    Netiva builds the app; weather data doesn’t come with it. Pick a weather API, add your key and describe what you want shown — the chance of rain at each job address on the day it is booked, for example.

  • Your local code still decides the install

    Building and residential codes allow asphalt shingles on slopes of 2:12 and greater, with double underlayment from 2:12 up to 4:12, and states amend both. The app records the pitch and layers you tore off, not whether the job meets the code or the manufacturer’s instructions.

  • Photos are proof of work, not safety records

    OSHA requires fall protection for residential construction work 6 feet or more above a lower level. A picture on a crew day shows what the deck looked like — keep toolbox talks, harness checks and inspections wherever your safety program already keeps them.

  • Estimating and invoicing stay where they are

    Netiva doesn’t pull jobs out of your estimating software or push invoices into your accounting tool. Enter sold jobs in the grid, or ask the agent to call your provider’s REST API if it offers one, and bill from the system you already use.

FAQ

Questions about building a roofing scheduler

Can foremen open the day sheet on a phone?

Yes. Netiva builds web apps that run in the browser, so a foreman opens the link on a phone in the truck and signs in with their own account — there is nothing to install. The day sheet shows their crew’s job for that date, with the pitch, layers and access notes, and photos taken on the phone are saved against the crew day.

How does the app handle a day lost to rain?

You set the crew day’s status to weather hold and pick a reason. Because a job is stored as a run of crew days, the days that had not started yet move together onto that crew’s next open date, and the app offers to push that job’s material drop and roll-off pickup by the same number of days. Rebooking those is still a phone call — the yard’s number sits on the delivery — and the customer can be emailed the new date from the job.

How does the scheduler know how much a crew can install in a day?

Each crew record carries a squares-per-day figure you set from your own history. Squares are the roof’s real area — the measured footprint times the slope factor for the pitch, divided by 100. On top of that the board applies a separate difficulty factor for steep pitch and for each extra layer to tear off, adds the result up per day and flags the days over that crew’s figure. A steep three-layer tear-off asks for its extra day while you are still scheduling.

Can it show the forecast for each job address?

Apps built with Netiva can call any REST API with the key stored securely, so you can describe a weather provider’s forecast endpoint to the agent and have the next seven days shown on the board. You bring the account and key. Check the provider’s terms for how often you may call it and how long you may cache what comes back.

Can subcontracted crews work from the same board?

Yes. Mark a crew as in-house or subcontracted and give it a foreman email. A signed-in foreman opens the day sheet and sees only the days booked to their own crew, so a sub sees their work without reading the rest of the schedule. Capacity works the same way, whichever kind of crew is installing.

Do I own the roofing scheduler once it is built?

Yes. Netiva writes clean, framework-standard code that you can read, edit and export whenever you want, with no proprietary runtime. Every change the agent makes is checkpointed, so you can branch, compare versions and roll back if a change to the board doesn’t work the way your office expected.

Drafted with AI assistance from Netiva’s product pages and reviewed by the Netiva team. Example data models, screens and prompts are illustrative starting points, not customer projects.

Build your roofing scheduler today

Describe it in a sentence and watch Netiva’s agent build it. Free to start — no credit card required.