The register starts buried in the specifications.
Before product data can be reviewed, the team has to identify each instruction, category, source page, and governing quote.
Submittal Review
Review what was submitted against what the specification requires.
Mobus builds an editable, cited register from specification sources, checks the current package against each requirement, and keeps the reviewer in control of the final response.
SpecificationRFICurrent submittal
Mobus Submittal ReviewFictional demo
QC passedSummit Medical Pavilion · 26 24 13
Low-Voltage Switchgear
Product data + shop drawings · BrightLine Power · Rev 1
4register items
2open issues
v2review run
RequirementModelEffectiveEvidence
Seismic anchorage certification. Model and effective finding: Not found. No submitted evidence found.
Spec page 24 · Still openNo submitted evidence found
ReconciledRegister CSV + review PDF available after QC
The review problem
A submittal package is not the requirement.
Evidence arrives in a different structure.
The submission, RFIs, and reviewer comments rarely line up row-for-row with the requirements they are meant to answer.
Resubmissions can erase the trail.
Without versioned findings, it is difficult to see what was corrected, what remains open, and which decision belongs to which revision.
Packet roles
Keep the governing source, clarification, and submission distinct.
Required
Specification
The governing source used to build the cited requirement register.
Optional
RFI
A directly relevant clarification can refine the requirement context without replacing the specification.
Required for review
Submittal
The current labeled package or resubmission reviewed against every active requirement.
Register-first workflow
Build the review from cited requirements.
The register is created and checked before the submission is evaluated, so every finding has a named requirement and an openable source.
- 01Create the package
Anchor the review to a project, specification section, package type, owner, and need-by date.
- 02Build the cited register
Extract requirements from the specification, then let a reviewer clean up or add cited rows before review.
- 03Add the current revision
Upload the labeled submittal and any directly relevant RFI response, then validate the packet.
- 04Review requirement by requirement
Place the governing quote beside submitted evidence and preserve supported, partial, non-compliant, and not-found states.
- 05Deliver after quality control
Keep the response draft editable and unlock the register CSV and review PDF only after coverage and citations reconcile.
Requirement-level evidence
Missing evidence stays missing.
Mobus preserves four explicit states—fully compliant, partially compliant, non-compliant, and not found—then lets the reviewer inspect and correct the effective finding without overwriting the initial model result.
Mobus Submittal ReviewFictional demo
QC passedSummit Medical Pavilion · 26 24 13
Low-Voltage Switchgear
Product data + shop drawings · BrightLine Power · Rev 1
4register items
2open issues
v2review run
RequirementModelEffectiveEvidence
Seismic anchorage certification. Model and effective finding: Not found. No submitted evidence found.
Governing requirementSpec page 24
“Submit seismic anchorage certification signed by the manufacturer for installed switchgear assemblies.”Division_26_Specifications.pdf
Submitted evidenceStill open
No submitted evidence found
The gap remains explicit for reviewer disposition.
No anchorage certificate or shake-table reference was found in the current revision.
ReconciledRegister CSV + review PDF available after QC
Reviewer control
Decision support without hiding the decision-maker.
Requirement and submission stay separate
The reviewer sees the cited specification instruction beside the exact submitted quote instead of a blended summary.
Model and effective findings stay separate
Mobus preserves the initial classification while the reviewer controls the final status, rationale, and action needed.
Every reviewed revision keeps its place
New, still-open, partially corrected, and corrected outcomes remain attached to the reviewed package version.
Revision and delivery
Preserve the trail before releasing the output.
Historical review runs remain tied to their uploaded revision. The current register and report become exportable only after finding counts and citation coverage reconcile.
Immutable prior runs
A later upload does not rewrite the review that came before it.
Editable response draft
The reviewer can refine the recommendation, rationale, and transmittal text.
QC + reconciliation
Partial or untraceable analysis does not silently become a deliverable.
Register CSV + review PDF
Both outputs stay keyed to the latest reconciled review run.
Current workflow boundary
Clear inputs. Human approval.
Supports native-text English PDFs for the specification, RFI, and submittal roles. Scanned files that require OCR are outside the current workflow.
Mobus prepares evidence-linked decision support. A qualified project reviewer owns the effective finding and final approval.
Fictional package. Complete source path.