Returns for this period
| Area | Wanted person return |
Target package return |
Rows | DIUs | Last activity | Reconciliation |
|---|
By Area click any card to open that Area's return
Still to come in
Past the deadline and not yet approved by the AIC. The note underneath is ready to go out; once the office server is connected it can be sent from here instead of copied.
| Area | Station / DIU | Return | Where it is | Overdue by | Reason given |
|---|
Activity most recent first
| When | Area | What | Detail |
|---|
Special wanted person return
Choose the person from the master list. Division, offence and warrant fill themselves in from CIB headquarters' list and cannot be typed over, so the return always reconciles.
| # | Name of wanted person (from master) | DIU / AFAT | Casings sub. | Date submitted | Date operationalized | Division (master) | Offence (master) | Warrant # (master) | Executed | As recommended | Operational outcome | Remarks |
|---|
Target package return to PIU totals and percentages calculate themselves
| DIU | Vol 8 VP workbook |
Vol 9 VP workbook |
Vol 10 VP workbook |
Other violence contributors |
Total submitted this period |
Feedback earlier periods |
Feedback this period |
Total feedback cumulative |
This period % fb this / sub this |
Cumulative % fb all / sub all |
As reported now fb all / sub this |
|---|
Cumulative packages submitted are carried forward automatically from earlier periods in this system. Where there is no earlier period recorded, the cumulative percentage uses this period only.
Three percentages, because the documents contain three different formulas
Reading the submitted returns and the deck together, the words "percentage feedback compliance" currently mean three different things:
| Where | What is actually divided | Example | Problem |
|---|---|---|---|
| Area 4 and 5 returns | Total feedback now ÷ feedback as at last period | 153 ÷ 145 = 106% | This is week-on-week growth in feedback. It sits near 100% by construction and can never show a gap. |
| The CPO deck, slide 12 | Cumulative feedback ÷ packages submitted | 154 ÷ 66 = 233% | Feedback counted since January over packages counted for a shorter window, so it cannot be read as a percentage of anything. |
| Not currently computed | Feedback this period ÷ packages submitted this period | 2 ÷ 20 = 10% | None. This is the one that can be chased week to week. |
There is a deeper issue underneath all three. Across the five Areas this period, 940 feedback items are reported against 346 packages submitted. Feedback and packages are plainly not the same unit: either one package draws several feedback items, or feedback is arriving for packages sent long before the window being counted. Until that is settled, no ratio of the two is a compliance rate. The table above shows all three side by side so the team can decide which they mean; nothing is hidden and nothing is quietly corrected.
Entries that do not agree with the master list
The station knows the person, so the station answers the query. Say what the correct information actually is and send it up: the DIM approves the correction, then the AIC, and only then does it reach headquarters as an agreed correction to put to CIB headquarters. Nothing typed here changes the master list on its own.
| Area / station | What the station returned | What CIBHQ holds | Where they differ | The station’s answer |
|---|
Approval chain for
You are seeing:
Each DIU enters its own part of the week’s return. It goes to that division’s DIM, then to the Area’s AIC, and only when every division has been approved does the Area’s return count as in. The management team sees every division at every stage, so a return is never invisible while it is still travelling. A return that has left the DIU can no longer be edited by the DIU.
| Area | Division / DIU | Wanted person return | Target package return |
|---|
Status of wanted persons the figures behind slide 5
| Area | Wanted | Casings sub. | Casings ops. | Casings pend. | Outcome / success | Impacted | % Imp. | At large |
|---|
Wanted, impacted and at large come straight from the master list. Casings come from the Area returns for this period. Nothing here is typed by hand.
Target package returns the figures behind slide 12
| Area | Vol 8 | Vol 9 | Vol 10 | Other | Total submitted | Feedback earlier | Feedback this period | Total feedback | This period % | Cumulative % | As reported now |
|---|
Returns received
| Area | Wanted return | Target package return | Rows | Last change |
|---|
Week by week
Every period the system holds, oldest first. This is the view that answers whether things are improving, rather than what they are today.
Returns that still arrive by email
While Areas are still sending Word documents, drop them here rather than re-keying them. The page reads the tables, works out which Area and which return it is, matches every name against the master list and shows you what it found. Nothing is saved until you accept it, so an upload can never quietly overwrite a return. Files must be .docx; an older .doc needs Save As in Word first.
Names that do not agree
The Areas submit to CIB headquarters, who compile the island-wide list, so where the two disagree the Area is the closer source. Each row below shows what the Area sent and the nearest person CIBHQ holds. Decide which one this system should carry. Anything you settle in the Area's favour is collected into a correction list you can send back to CIBHQ.
| Area | What the Area submitted | What CIBHQ holds | What the difference is | Likeness | Which should this system carry? |
|---|
Status does not agree
CIBHQ records these people as impacted, yet an Area is still working them as an active target. One of the two is out of date, and until it is settled the impact rate is wrong in one direction or the other. Settling a row here changes the figures on the Consolidated tab straight away.
| Area | Person | CIBHQ records | The Area's return shows | Which is right? |
|---|
Other checks
Dates, duplicates, missing rows and people already recorded as impacted. An empty table is the goal.
| Severity | Area | Where | What |
|---|
Checks the system runs
- Each person on a return exists on the master list, and is in the Area that submitted the return.
- Nobody already recorded as impacted on the master list is still being returned as an active target.
- No person appears twice on the same Area's return for the same period.
- Dates fall inside the reporting period, and no date is in the future.
- Casings operationalized do not exceed casings submitted plus those carried in.
- Every DIU in the Area has a target package row, or an explicit nil.
- Feedback counts do not exceed packages submitted on the cumulative measure.
Master list
Maintained by CIB headquarters. Read-only here. Areas reconcile to it; nobody edits it in this system.
| Reference | Name, alias, age, address | Area | Division | Status | Offence | Warrant # | How impacted |
|---|
Audit trail
Every certification, approval, return and administrative action, in the order it happened. Entries are only ever added: nothing here can be edited or removed from inside the system.
| When | Who | What | Detail | Reference |
|---|
Register a person
Everyone who is to touch the system is registered once, here. Where they sit is recorded separately as a posting with a date it takes effect from, because people move: when an AIC transfers, the old posting closes the day before the new one opens, and the history stays. Nobody is ever deleted — a person who leaves is suspended or marked no longer serving, so everything they signed still points at a real person. A confirmation code is issued on registration; it cannot be emailed until the office server is connected, so the code is shown here in the meantime.
| Person | Contact | Role | Area | Station / DIU | Posted from | Status | Code |
|---|
Transfer or re-post
The posting they hold now closes the day before this one takes effect, and they pick up the new seat from that date. Nothing already signed is touched.
Seats and privileges ISSU is the super administrator
The chain as it is actually shaped: each Area across the top with its AIC at that level, then every station under it with its DIU and its DIM together. Who holds each seat comes from the register above.
| Seat | Role | Held by | Can see | Can do |
|---|
Master list source
The list loaded now is , generated , holding people.
Produced from the CIB workbook with masterlist.py in the build-tools folder. The real list contains personal data on real people: keep it on the machine that needs it and do not email it.
This period's returns
A prototype. Returns are held in this browser only. Once the shape of the return is agreed, this gets the same accounts, authenticator and relay as the consular system, so each Area enters its own and the consolidation happens by itself.
