Documentation
How SiteSignal works, in detail.
Reference material for the questions that come up during evaluation: what your spreadsheets need to look like, who can see and do what, and how a project earns a red score.
Data import
CSV import schemas.
SiteSignal imports budgets and schedules from CSV. You do not need to rename your columns first — the importer suggests a mapping from your headers, shows a preview of the first rows, and lets you correct any column before committing. Rows that fail validation are reported individually with the source row number, and valid rows still import.
Currency values may include dollar signs, commas, and surrounding whitespace. Blank optional numeric cells are treated as zero.
Budget import
| Column | Requirement | Type | Notes |
|---|---|---|---|
| Category | Required | Text | Cost code or line item name. Also matched from headers named Cost Code, Description, Item, Line Item, or Account. |
| Budgeted amount | Required | Currency | Original or current budget for the line. Matched from Budget, Budgeted, Original Budget, Planned, Estimate. |
| Committed amount | Optional | Currency | Value under subcontract or purchase order. Matched from Committed, Commitment, Contracted, PO Value, Subcontract. Defaults to 0. |
| Actual amount | Optional | Currency | Cost incurred to date. Matched from Actual, Spent, Cost to Date, Expended. Defaults to 0. |
Category,Budgeted Amount,Committed Amount,Actual Amount
03 30 00 Cast-in-Place Concrete,1250000,1180000,905000
05 12 00 Structural Steel,2400000,2400000,1610000
09 91 00 Painting,180000,0,0Schedule import
| Column | Requirement | Type | Notes |
|---|---|---|---|
| Milestone name | Required | Text | Milestone or activity name. Matched from Milestone, Name, Task, Activity, Description. |
| Target date | Optional | Date | Planned finish. Matched from Target Date, Finish, End Date, Due, Date. Accepts ISO (2026-08-15) and common US formats. |
| Material lead (weeks) | Optional | Whole number | Procurement lead time in weeks, used in delay forecasting. Matched from Lead Weeks, Lead Time, Procurement. |
Milestone,Target Date,Lead Weeks
Foundations complete,2026-10-15,
Structural steel topped out,2026-12-04,14
Building dried in,2027-02-20,6Exports mirror these schemas. Admins can download every organization dataset as CSV from Settings at any time, which makes the platform straightforward to exit — a point worth raising with procurement.
Access control
Roles and permissions.
Every user belongs to exactly one organization and holds one of four roles. Permissions are enforced server-side on every request, and organization scoping is additionally enforced by row-level security policies in Postgres, so a bug in application code cannot expose another organization's data.
| Role | Summary | Capabilities |
|---|---|---|
| Admin | Full control | Everything below, plus invite and deactivate users, change roles, edit organization settings and risk weights, manage report recipients, run exports, and configure MFA enforcement. |
| Project Manager | Create and edit project data | Create projects, edit budgets, schedules, RFIs, change orders, and subcontractors, run risk analysis, and generate status reports. Sees only assigned projects once project assignments exist. |
| Executive | Read-only plus audit | Portfolio and project visibility across the organization, plus access to the audit log. Cannot change project data. |
| Viewer | Read-only | Portfolio and project visibility. No write access and no audit log. |
Admins can require multi-factor authentication for the entire organization from Settings → Security. Enterprise organizations can additionally federate sign-in through SAML or OIDC single sign-on where it has been configured for their tenant.
Methodology
How risk scoring works.
Every project carries a Red, Yellow, or Green score. The score is deterministic — it is computed by a rules engine from your own numbers, not by a language model. The same inputs always produce the same score, which means you can explain it in an owner meeting.
Four weighted inputs feed the score:
| Input | What it measures |
|---|---|
| Budget variance | Forecast at completion against budget, using committed and actual costs across all line items. A forecast overrun moves the score toward yellow, then red. |
| Schedule variance | Actual milestone completion against the completion expected by today's date, derived from start date and target end date. |
| Open RFIs | Count and age of unresolved RFIs. A backlog of aging RFIs signals coordination drag before it shows in cost. |
| Change orders | Total approved and pending change order value relative to contract value. |
Business and Enterprise organizations can tune the relative weight of each input under Settings → Notifications, so a firm that lives and dies by schedule can weight it more heavily than change orders.
The AI layer sits on top of the deterministic score. It explains the score in plain language, drafts a recovery plan, and writes weekly status report copy. It never changes the score itself, and every AI output is a draft for human review. Details of what is sent to our AI provider are in the Privacy Policy.
Something not covered here?
Compliance and vendor review material lives in the Trust Center. For anything else, ask us directly.