Loading…
This site does not send reset emails. Ask here and an administrator will set a one-time password and pass it to you; you choose your own the next time you sign in.
Choose a new password of at least 8 characters.
You will see exactly what they see and anything you do is done as them. Running accounts and changing passwords are not offered, and a report you submit while working as somebody receipts you, not them.
New tasks appear at the end of the plan and can be edited like any other.
Names arrive as free text in email, so the same person or client turns up several ways. These are the records they resolve to.
For loading a batch after a workshop. Tasks are added under the parent you choose, continuing its existing numbering.
Recognised columns: name, owner, start, finish, priority, status, sprint, objective, notes, days. Dates as YYYY-MM-DD.
Every edit to every task, newest first — who made it, what it was, and what it became. Tasks added, deleted and moved are here too. Nothing is ever removed from this.
| When | Who | Task | Field | Change |
|---|
Every edit made to a service issue here, newest first — and every time two people or clients were merged into one record. The pipeline’s own updates are not changes made here and do not appear.
| When | Who | Issue | Field | Change |
|---|
The monthly .xlsx. It is read here in your browser — only the figures are sent, not the file. A load replaces that month alone and never touches what anybody has typed.
Every action, owner, status and note recorded against a client, newest first.
| When | Who | Client | Field | Change |
|---|
Every root cause, comment and risk typed into these screens, newest first.
| When | Who | Client | Field | From | To |
|---|
A record of something being quoted. It stays a draft until it has an issue date.
Every price on every proposal comes from here, so a change to this is a change to what the firm charges. Each one is recorded.
| When | Who | Item | What | Change |
|---|
Every price, date and decision on every proposal, newest first. This is a commercial record, so nothing is edited without landing here.
| When | Who | Client | Proposal | What | Change |
|---|
The figures come from the compliance workbook. Root causes, comments, risk and the action plan are kept here and are never replaced by an update.
On a schedule, the site fetches the extract from a link you configure and imports it exactly as the upload does. It skips the import if what it finds is older than what is already loaded, so a stale or half-written file cannot walk the figures backwards, and it records a failure rather than failing quietly.
Set COMPLIANCE_SOURCE_URL in the project's environment variables to a link that returns the extract — a published file, a shared workbook export, or whatever the generating script can write to. Add COMPLIANCE_SOURCE_TOKEN if that link needs a bearer token. Nothing else changes: the schedule is already in place.
Until a link is set, the schedule runs, finds nothing to fetch, and says so. Uploading by hand keeps working either way.
Progress captured through the week, ready to fold into the plan — plus what has already changed.
Loading…
Sign in to see the improvement plan, the service issues and the compliance figures.
| Outline | Task | Workstream | Owner | Start | Finish | Sprint | % | Status | RAG | Pri |
|---|
| Owner | S1 | S2 | Total open |
|---|
| Month | Client Code | Company | MA | FC | Missing | Week | Deadline P&L | Deadline BS | Overdue (wd) | Status | RCA | Comments |
|---|
| Client | Proposal | Owner | Service lines | Annualised | One-off | Status | Days | Issued |
|---|
Trackers and other files that go out with the Friday report. Everyone with reporting access can see them and add to them; a file of the same name replaces the earlier one. Up to 3 MB each.
| Code | Procedure | Outcome | Folder | Owner | State | Review due | Steps | Issues |
|---|
Sign-ins, failed attempts, and every change to who has access.
Norareads this app — she cannot change it