Stop rebuilding the submittal register by hand.
SubmittalPulse turns project specs, spreadsheets, folder exports, RFIs, and order logs into a register-health packet that shows what is required, what is missing, what is blocked, and who owns the next move.
Sample output
Submittal 042: door hardware
Required by spec. Folder file stale. Approval blocked by RFI-014. Owner missing before Thursday PM meeting.
Narrow customer
PMs and project engineers at small general contractors or specialty contractors.
They run active jobs without a fully adopted CM system and still rely on Excel, folders, email, and memory for submittals, RFIs, approvals, and orders.
Paid problem
Manual register work creates schedule risk and PM fire drills.
The cost is not only data entry. Missing attachments, stale approvals, and unclear owners turn into delayed materials, rework, payment-app friction, and avoidable meeting churn.
Validation test
One active project package, one register-health packet.
The waitlist tests whether small contractors will share a redacted package and pay for a practical preflight before a full product exists.
Day-in-the-life pain
The PM starts with a giant spec PDF and ends up babysitting rows.
A small contractor wins a job. The project team must read hundreds of pages of specifications, identify every required submittal, create a spreadsheet, chase subcontractors for documents, attach files in folders, watch approvals, and remember which RFIs or orders are blocking progress. As project volume grows, the tracker becomes a second job.
Input
Upload the project spec PDF, current Excel tracker, submittal folder export, open RFI list, order log, and the next two-week lookahead.
Checks
SubmittalPulse extracts required submittals, maps them to spec sections, checks missing due dates/owners/status, and links each row to the latest document or folder.
Output
A clean register packet: required submittals, overdue approvals, missing attachments, RFI/order dependencies, owner assignments, and a PDF/Excel export for the weekly PM meeting.
Why the workaround breaks
Excel can list rows. It cannot keep the register honest across specs, folders, RFIs, and orders.
Community complaints point to the same gap: small construction teams are not asking for a prettier spreadsheet. They need a low-friction way to find required items, attach proof, spot missing owners, and know which approvals are putting the job at risk.
Spec-to-register extraction
Turn 300-900 page project specs into a first-pass submittal register instead of copy-pasting sections by hand.
Spreadsheet plus folder reconciliation
Match existing Excel rows to folder files and flag rows with no attachment, duplicate names, stale revisions, or unclear approval status.
RFI and order dependency flags
Show when a submittal is blocked by an RFI, material order, vendor drawing, or missing PM decision so the weekly meeting is not just row chasing.
Two-week risk digest
Send a focused list of overdue, due-soon, and ownerless items before they become schedule or payment application problems.
Concierge-first validation
Early users can submit one active project package and receive a manually reviewed register-health packet before any software rollout.
Community evidence
The signal is narrow and repeated: submittal/RFI tracking lives in spreadsheets because full CM adoption is too heavy or absent.
Reddit r/ArtificialInteligence · GC PM submittal register
A construction PM describes reading 300-900 page specification PDFs, finding every required submittal, copying requirements into a spreadsheet, and distributing the register to the project team.
Open source →
Reddit r/projectmanagement · spreadsheet pain
A construction PM says the least-liked task is tracking submittals, approvals, RFIs, and orders in a spreadsheet plus folders, and asks for a better way to attach documents to each row.
Open source →
Reddit r/ConstructionManagers · no CM software
A project engineer says the company uses Excel spreadsheets to track all submittals with no plan to buy external CM software, creating fear that manual tracking will haunt the role.
Open source →
Reddit r/PMCareers · growing small construction company
A PM at a rapidly growing small construction company reports losing track of updates across estimation, RFIs, change orders, warehouse receiving, payment applications, and submittals.
Open source →
Objections
A register preflight layer, not a giant CM migration.
The first test is intentionally small: prove that PMs will pay for one useful register-health packet before asking the company to change its project management stack.
Why not Procore or Autodesk Build?
Many small contractors either do not have full CM software, cannot force every subcontractor into it, or still keep critical trackers in Excel. SubmittalPulse starts with the messy files they already use.
Is this replacing the PM?
No. It is a register preflight and evidence packet. The PM still decides what matters; the product finds missing rows, stale files, and owner gaps before the meeting.
Can a spreadsheet already do this?
A spreadsheet can hold rows, but it does not read specs, reconcile folder attachments, explain dependencies, or produce a clean weekly risk digest without manual policing.
What about project confidentiality?
The waitlist test starts with redacted or sample project packages and a limited concierge workflow. No private project data is published or used as marketing proof.
Early waitlist
Send one redacted project package. Get a register-health packet.
Demand will be validated by how many PMs share a real or redacted project package, whether the packet catches meaningful gaps, and whether they ask for the same review on the next job.