| Which jobs need attention today? |
Yes Project rows show Work On actions, favorites, phase and status, client, PM and super, late RFIs, open COs, punch, missing daily reports, crew activity, toolbox and safety, and compliance gaps. |
| Where is the actual job page? |
Yes Work On keeps the job number, customer, location, PM and super, pulse, blockers, map, weather, the estimate it came from, and project navigation together. |
| Where are the current project files? |
Yes Project files handle folders, uploads, previews, downloads, protected files, internal backup, external package material, and project-specific file actions. |
| Which drawing or spec version are we using? |
Yes Drawing/spec logs track issued sets, sheet logs, revisions, specs, directives, correspondence, verification, and downloadable history. |
| Who owes the RFI answer? |
Yes RFIs carry the official question, drawing/spec reference, recipient, due date, response count, distribution, ball-in-court, PDF, and closeout action. |
| Did the reviewer open the submittal packet? |
Yes Submittals track item, revision, generated cover sheet, compiled packet, reviewer workflow, distribution, opened status, decision, release state, and history. |
| What scopes still need buyout quotes? |
Yes Project RFPs build scope packages after award with invited vendors/subs, opened/downloaded status, no-bids, quote amounts, and coverage gaps. |
| Can vendors quote without creating an account? |
Yes The public RFP planroom gives vendors a secure no-login page with the files, project details, acknowledge and no-bid buttons, response status, and quote upload. |
| Where do meetings, permits, and inspections live? |
Yes Management records keep agencies, permit status, inspection results, meeting notes, dates, attendees, and follow-ups attached to the job. |
| Did the super finish the daily report? |
Yes Daily reports capture date, weather, manpower, work completed, work in progress, safety notes, inspection status, and final report state. |
| What is happening in the field this week? |
Yes Lookahead, safety, deliveries, toolbox talks, and punch lists carry owners, due dates, assignments, status, exceptions, and field commitments. |
| Who is scheduled on this job? |
Yes Manpower shows who is scheduled, field coverage, crews, where labor is short, and how it ties to timeclock. |
| Is the extra work approved or still floating? |
Yes Change orders track RFC/CO scope, status, reviewer ball-in-court, labor/material/sub pricing, markup, attachments, packet state, and approvals. |
| Is the T&M work signed, priced, and billable? |
Yes T&M tickets track field extra work, labor, materials, signer status, pricing status, packet status, and whether the ticket is ready to bill. |
| Can we build the pay app from the project? |
Yes AIA-style billing builds schedules of values, includes approved COs, tracks current due, retainage, invoice number, package generation, delivery, and review. |
| What has been billed and what is still unpaid? |
Yes A/R shows project invoices, open balances, paid balances, aging, payment status, receive-payment actions, and Stripe payment links where enabled. |
| What subcontractor exposure sits on this job? |
Yes Subcontractor records keep commitments, billing, vendor and sub relationships, what is owed on the job, and supporting documents close to the job. |
| Does the schedule reflect the work changing around it? |
Yes Schedule provides task grid, Gantt, dependencies, baseline, lookahead, workdays, health, critical path, calendar, and PDF/print controls. |
| Can closeout start before the last week? |
Yes Closeout builds packages from cover sheets, warranty letters, O&M items, as-builts, custom deliverables, section breaks, and generated output. |
| Who gets project updates? |
Yes Team and distribution manage project roles, contacts, outside recipients, distribution lists, sent/opened status, and who receives project records. |
| How does this project want records routed? |
Yes Settings and workflows control module behavior, submittal setup, numbering, routing, review expectations, and project-specific access behavior. |