Settings
Set defaults for this workspace.
Not assignedEvidence detailsChecking
Settings content
Settings that shape the review
Pick the active project, confirm the date basis, then tune DCMA and Directed EV targets before schedulers run Schedule Health.
For this project, choose which connections hear the moment an XER is uploaded, which receive the reports once it has been analysed, and which are told of alerts from the monitors below. Connections are added under Connections.
Each monitor watches one reading of this project’s schedule. It is checked every time a release is analysed, and hourly for an overdue update. Crossing a threshold opens an alert, which escalates if it gets worse and resolves on its own when a later check passes. Alerts go to the connections ticked under Alerts above. Under Options, a monitor can read the change since the release before, wait for several readings in a row, send only at critical, remind while nobody acknowledges it, be snoozed, carry a note on what to do, and be double-checked by WBS before it is sent.
Include saved readings with a Review
Uses the selected header Review from this project as a handoff anchor. Saved checks retain their own review identities and bounded history; they are not all findings from that Review.
Send captured monitor evidence
This is a separate, explicit disclosure, not an automatic alert subscription. The complete saved capture includes notes, project labels and acknowledgement identities; it is not anonymized. Unsaved threshold edits are not included. Chat sending requires operator enablement and your explicit approval.
Summary to send
The approved immutable evidence link is added after issuance. No link is issued by previewing.
Complete snapshot disclosure
Capture identity, making and limits
Load saved readings and destinations before previewing.
Inspect a delivery request
Inspection never sends or repairs a delivery. A timeout is not proof of rejection. Do not start another request to repair missing audit evidence.
Downloads use the saved readings shown here, not unsaved threshold edits. Older checks may have no captured evidence.
Recently resolved
An XER carries no inspections, so the Flow Analysis quality instrument reads “not installed” until one is supplied. Upload a CSV with a row per inspection: activity_code and outcome (accepted, rejected or pending; pass, fail, NCR, rework and open are read too), and optionally inspection_id, inspected_on, attempt and responsible. Uploading replaces the feed.
Loading chat connections…
Setting it up on each platform
- Create a Slack app for your workspace.
- Connect it here with its Signing Secret.
- Slash Commands: create
/spiwith the copied address as its Request URL. - For @mentions, add the bot token here, and subscribe the same address to the
app_mentionevent.
- In the team: Manage team, Apps, Create an outgoing webhook named SPI.
- Paste the copied address as its callback URL; Teams then shows a security token.
- Connect it here with that token. Ask with @SPI.
- Create an application in the Discord Developer Portal and connect it here with its Application ID and Public Key.
- Paste the copied address as its Interactions Endpoint URL.
- Register a
/spicommand with one string option named question.
Three review packs can go out on a timetable as well as when a schedule arrives: a daily lookahead for the site, a weekly trend review for the project manager, and a monthly owner update. Each reads the project's newest release and says how old its data date is; when no update has arrived since the last pack, it says so. Connections that take reports can receive a pack; they are added under Connections.
Loading Teams destinations…
Copy it now into the receiving system: it is not shown again. Use it to check the X-SPI-Signature header.
How to set these up in Microsoft 365
- In Teams, open the channel, choose Files, then Open in SharePoint. The team site address is the part up to
/sites/Name; the channel folder is the folder name shown, usually the channel name; the library is usually Documents. - Your Microsoft 365 administrator approves the SPI app for your organisation, once, by opening
https://login.microsoftonline.com/<tenant ID>/adminconsent?client_id=<client ID above>. It asks only for Sites.Selected, which on its own reaches nothing. - A SharePoint administrator gives the app write on this one site, for example with PnP PowerShell:
Grant-PnPAzureADAppSitePermission -AppId <client ID> -DisplayName SPI -Site <site address> -Permissions Write. - Add the folder here and press Send a test. A small text file appears in the channel folder under SPI.
- In the channel, open the … menu, choose Workflows, and pick Post to a channel when a webhook request is received.
- Choose the team and channel, finish the workflow, and copy the address it shows.
- Paste it here, add the card, and press Send a test. A test card appears in the channel.
Teams cannot attach a file to a webhook card, so add a channel folder or a download link as well: the card then links to them.
- The same one-time app approval as a channel folder, and a write grant on the site that holds the library.
- Give the site address, the library name as SharePoint shows it, and a folder path inside it (or leave it empty).
- Add it here and press Send a test.
- Nothing to set up in Microsoft 365: the reports stay on SPI and the email carries a link that expires.
- Press Send a test; each recipient gets a short test email with no link in it.
Webhooks and the API
schedule.uploadedwhen an XER is uploaded, added or replaced: project, file names, sizes and hashes, and who uploaded it.schedule.analyzedwhen its analysis completes: data date, forecast finish, what stands out, links to any files filed and to a download link if one was made.reports.sharedwhen someone uses Send now;pingfor a test.
Every event carries API links for pulling the full reports with an SPI API key (Profile › API tokens) as a Bearer token.
Each request carries X-SPI-Signature: t=<seconds>,v1=<hex>, X-SPI-Event and X-SPI-Delivery. Compute HMAC-SHA256 of <t>.<raw body> with the signing secret, compare it with v1, and refuse a t more than five minutes old.
import hmac, hashlib, time
def verify(secret, body, header):
parts = dict(item.split("=", 1) for item in header.split(","))
if abs(time.time() - int(parts["t"])) > 300: return False
signed = parts["t"].encode() + b"." + body
expected = hmac.new(secret.encode(), signed, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, parts["v1"])Reading who has access…
API/MCP tokens
A token reads this account through the API or MCP with the owner's read access; it cannot upload or change anything. It is shown once when made and kept only as a hash.
Reading the integrations…
Recent failures
Disclose each workflow your projects run, step by step. Review times are read against it by queue, role or organization, never by person, and a queue counts as near full at 80% of its reviewers' capacity (queueing theory: waits climb steeply past that line). Without a disclosure, utilization is not read.
| Workflow | Kind | Step role | Organization | Reviewers | Target days | Remove |
|---|
Up to 512 KB. SVG is not accepted. The image is re-encoded on upload, so only the picture is kept; a wide logo fits best.
Reading the page layouts…
Review status and evidence steps
Steps of the decision on this page.
