—
Construction schedule
Installation or work windows by area (optional crew label). Use the calendar to see overlaps.
Rows are inclusive date ranges (e.g. 1 June through 10 June).
| Area / scope | Start | End | Crew (optional) | |
|---|---|---|---|---|
| Open this tab to load schedule lines. | ||||
Events use the same windows as the list. Month view shows multi-day bars.
Tasks
Each row is an installation window (same records as Schedule and the calendar).
| # | Task name | Duration | Start | End | Progress | Dependencies | Assigned | Status | |
|---|---|---|---|---|---|---|---|---|---|
| Open this tab to load tasks. | |||||||||
Drawings
Current set, revisions, and sheet metadata (project-scoped).
Specifications
Procore-style spec book: CSI sections on the left, PDF on the right. Link a PDF URL per section (stored on the spec section record).
Pricing
LEMOS cost types (Labor, Material, Equipment, Subcontract, Other) on project takeoff lines.
Formal estimate summary for this job is not wired here yet.
RFIs
Procore-style log: # / Subject / Status / Ball-in-Court / Assignees / Due. Same APIs as the full RFI workspace (rfis.html). Use the Submittals tab for shop drawings and submittal workflow.
| # | Subject | Status | Ball in court | Assignees | RFI Manager | Due |
|---|
Submittals
Procore-style register: workflow dates, contractor, responses, and attachments. Open a row for PDF review markup. Pair with the RFIs tab for questions linked to drawings or specs.
| # | Title | Spec | Type | Status | Responsible | Submit by | Received | Sent | Returned | BIC | Due | Rev | Response | File |
|---|
Procurement
Purchase orders, subcontracts (retainage when applicable), and RFPs for this job. POs and subs share the commitments API; RFPs use the same list API as the full RFP workspace.
Committed cost when approved; multiple vendor bills per PO (PO-to-bill).
| Ref | Title | Vendor | Linked RFP | Status | Total |
|---|
Subcontracts; retention % on the commitment when applicable.
| Ref | Title | Vendor | Linked RFP | Status | Total |
|---|
Draft and manage RFP packages scoped to this project.
| Title | Status | Due | Token | Actions |
|---|
Invoicing
Owner payment applications (G702-aligned summary lines) with a schedule of values grid (G703-style columns, Textura-like layout). Field meanings follow common AIA practice; USIS does not reproduce AIA copyrighted forms.
| App # | Period to | Status | Payment due | Certified | Lines |
|---|
Payment application
| Line 1 — Original contract sum | |
|---|---|
| Line 2 — Net change by change orders | |
| Line 3 — Contract sum to date | — |
| Line 4 — Total completed & stored to date | — |
| Line 5 — Retainage (total) | — |
| Line 6 — Total earned less retainage | — |
| Line 7 — Less previous certificates | — |
| Line 8 — Current payment due | — |
| Line 9 — Balance to finish (incl. retainage) | — |
Architect certificate
| Phase | Description | Sched. value | Net C/O | Prev. work | This period | Materials | Retainage | % comp | Bal. to comp. |
|---|
Contract admin
In Sage Construction Management, contract administration centers on the prime contract (financial terms, dates, retention), change orders that adjust that contract, and how approved commitments (subcontracts and POs) roll into committed cost and billing — not on submittal packages. Submittals are a separate document workflow; use the Submittals tab for this project’s register.
| Contract value | — |
|---|---|
| Contract date | — |
| Start date | — |
| Substantial completion | — |
| Closeout | — |
| Retention % (prime) | — |
| Sage project id | — |
Master line items for the owner contract. Use Edit SOV to add or change rows; totals should match Contract value above.
Loading SOV summary…
Owner-facing prime CO log (not SCO). USIS has no prime-CO API yet — track and approve prime COs in Sage CM until a register is added here.
| # | Title | Status | Amount |
|---|---|---|---|
| No prime change orders yet (endpoint TBD). | |||
- Loading snapshot…
Project flags that often drive Sage / contract compliance checks.
| Prevailing wage | — |
|---|---|
| DBE required | — |
Org-level P2P / approval chains live in Sage Intacct configuration. Commitment workflow_rule_active locks edits while a rule is active.
Sage references (external): PO overview · SCO overview
Job costing
Costing views are not configured for this screen yet.