Describe the project and required shift facts. Makeform creates a mobile-friendly foreman daily report form for labor, progress, conditions, equipment, delays, and issues.
Send daily reports to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a jobsite scenario, adjust the prompt, or use it in the builder.
Audience
Foremen coordinating several trades on an active building site
Format
End-of-shift report with trade breakdown and photos
Prompt size
306 chars
Example form structure
End-of-shift report with trade breakdown and photos
Project, date, foreman, and shift
Trades, headcount, and labor hours
Work completed and quantities
Delays, inspections, and safety events
Progress and issue photos
Suggested routing tags
Shift complete
Delay reported
Follow-up required
Separate headcount from crew hours so the office can spot labor changes quickly.
Step 1
Log
crew, hours, conditions, and locations
Step 2
Document
progress, quantities, photos, and deliveries
Step 3
Flag
delays, safety events, and needed decisions
Step 4
Plan
tomorrow's labor, equipment, and materials
A clearer end-of-shift record
Foremen enter phone-friendly details, giving the office a consistent view of production and obstacles.
Capture company, headcount, hours, task, and work area instead of burying labor in notes.
Record installed units, rooms, loads, or percent complete beside the day's work.
Conditional fields collect cause, duration, impact, action, owner, and photos for exceptions.
Useful across the jobsite
Choose a reporting pattern, then edit terms, quantities, and exception paths.
Track subcontractors, work areas, inspections, deliveries, visitors, issues, and next-day activities.
Add stationing, ground conditions, equipment hours, loads, installed lengths, tests, and utility conflicts.
Organize labor by cost code, floor, room, or task, with shortages and constraints separated.
Log job number, site time, completed scope, materials, requests, photos, and return work.
Build the daily reporting flow
Define required facts, refine the form, and route each submission to the project team.
List trades, cost codes, locations, quantities, shifts, and events needing detail.
Put shift facts first, repeat labor entries, and reveal issue questions when needed.
Share one daily link and require the fields needed for the project record.
Send reports to the team and tag exceptions that need a decision.
Choose a reporting method
A useful method makes routine facts quick while preserving exception details.
Field guide
Use six field groups for production and exceptions.
Report identity
Use identifiers the office needs to file reports. Project and shift dropdowns reduce naming variations.
Crew and hours
A repeating group keeps each trade distinct and connects hours with assigned work.
Progress and quantities
Pair an activity summary with the unit that matters, without forcing every trade into one metric.
Conditions and resources
Weather, access, deliveries, and equipment explain production changes. Add notes for unusual conditions.
Safety and quality
Ask about talks, inspections, hazards, and incidents. Exceptions open fields for location, action, owner, and attachments.
Delays and next steps
Capture cause, duration, affected work, response, owner, and tomorrow's needs outside general notes.
Related tools
Build focused forms when an item needs more detail than the daily log.
Summarize milestones, quantities, constraints, and upcoming work.
Open toolDocument safe practices, hazards, actions, and follow-up ownership.
Open toolCapture equipment condition, defects, and photos before work.
Open toolTurn repair or corrective work into an assigned request with location, priority, scope, and completion details.
Open toolGive crews a dedicated path to report a hazard, describe exposure, add evidence, and identify immediate controls.
Open toolCapture the reason, requested scope, schedule considerations, attachments, and reviewers for a potential project change.
Open toolFAQ
Practical answers for construction teams creating a consistent end-of-shift reporting process.
It is an end-of-shift record of crew hours, locations, weather, completed work, quantities, equipment, deliveries, inspections, delays, safety matters, photos, and the next day's plan.
Include project, shift, crew hours, work by area, quantities, weather, equipment, deliveries, inspections, safety observations, delays, incidents, extra work, photos, and planned activities. Remove fields your team will not use.
Use a repeating group for company, trade, headcount, hours, location, and activity. The foreman adds one entry per crew instead of navigating a fixed trade list.
Yes. Add uploads near progress, delivery, inspection, and issue sections. Ask for a location and short caption so the office understands each image.
Start with an exception check. If yes, reveal category, location, duration, affected work, impact, action, requested decision, owner, and photos. Routine reports stay short when nothing happened.
Yes. Edit trades, locations, cost codes, quantity units, inspections, and routing. Civil work may need stations and truck loads; interiors may need floors, rooms, and installed units.
Yes. Makeform offers unlimited free forms and responses. Generate, edit, publish, and collect daily reports without a response cap. The paid tier removes the Makeform badge.
Send it to the project team, organize fields in a sheet, and assign exceptions. Review missing details promptly and carry open constraints into the next planning conversation.
Replace scattered shift notes with one complete report.
