Reflects the current upload only. All-time job history lives on the Report Data and Job Lookup tabs. Last-import status now lives on the Import tab.
Job status value lookup
Status breakdown
| Status | This upload | Previous upload | Delta |
|---|
Last import status
| Last import: | |
| Previous import: | |
| Last file: | |
| Synth Code Report — last imported: | |
| DFE Report — last imported: | |
| Associated Jobs Report — last imported: | |
| Permit Report — last imported: |
Import Workstack Report
Select the BT Workstack export, one row per Synth Code line (.xlsx / .xls / .csv) — e.g. "Full Workstack By Synthetic". Updates the tracked Jobs list cumulatively (new Order IDs added, existing ones updated in place, anything missing from this file that was in the last upload flagged Dropped — nothing's ever deleted) and replaces the Synth Code Report with a fresh snapshot from the same file, both in one import. A job with no Synth Code lines of its own yet won't appear until this file has at least one line for it.
Import Infill Build Tracker
The Infill Survey & Build Tracker from the Telent SharePoint site. Reads the Northwest sheet, matches Build Job Number to an Order ID in this system, and puts that row's Build Comments into that job's Notes, credited to Eve Wyke.
A job gets one tracker note, refreshed each time you import — the comment cell is a running log that grows, so re-importing updates the note rather than adding a near-identical one beside it. Notes anybody has typed by hand are never touched. A row whose job number this system does not know is skipped and reported.
Import Permit Report
The portal's notice/permit report. This is what puts the colour on a job in
Whereabouts — green, amber, red, or blue for done-and-to-register — and a job
with no notice in it reads as Waiting Permit.
It downloads as .xls and is really an HTML table; that is fine, it
reads either way. Replaced wholesale on each import.
This also runs automatically every hour — importing by hand is
for when it has not.
Import DFE Report
Select the DFE report (.xlsx / .xls). Also replaced wholesale on each import.
Import Associated Jobs Report
The report listing each job with its Exchange and BT PCP Order. Jobs sharing both are pieces of the same build, and Job Lookup and the Job Tracker will show them against each other. Replaced wholesale on each import.
Reset imported data
Clears every tracked job, the Synth Code Report and the DFE Report — everything that comes from a BT export. Notes, Gangs and the Rate Card are kept. Importing the files again puts it all back.
Clear entered data
Clears everything typed into this system by hand: the Whereabouts grid, its replan history and notify list, the FX Job Status log, FX ECD dates, Synth line completions, Engineer Portal updates, Job Notes and their attachments, Gangs and gang member status.
None of this comes back from a re-import — none of it is in a BT export. Kept: everything that came from an import (jobs, Synth Code Report, DFE Report, Associated Jobs Report), plus the Rate Card, Users and the landing tiles.
Wipe everything
Empties every list this system owns — jobs, imports, Rate Card, Gangs, Notes, Whereabouts, Users, tiles. Leaves the system running with nothing in it.
The Workstack, DFE and Rate Card imports can be run again afterwards. Gangs, Notes and the Whereabouts notify list cannot — those are typed in, not imported. Users, the landing tile and the import record rebuild themselves on your next sign-in.
Job Lookup
Looks up the all-time job list — so a job still shows here even after it drops off the current BT export. Notes are kept permanently regardless.
Associated jobs
Other jobs on the same Exchange and BT PCP Order — the same build, split by BT into separate orders.
| Order ID | Type | Status | Contract | Planned Start |
|---|
FX Job Status & ECD
Synth Code lines
Record who completed how much against each line: enter an Amount, pick a Gang, and click Save — each Save adds a new, permanent entry (it can't be deleted afterwards) rather than overwriting the last one, so more than one gang can log a different amount against the same line over time, and it's always clear who recorded what. The total shown is the sum of every entry recorded so far. If the total ever exceeds Planned Quantity, a "DFE REQUIRED" flag appears with a Done checkbox to tick once the DFE paperwork has actually been raised.
| Synth Code | Description | Rate Card | Planned Qty | Rate | Total | Completed / Gang |
|---|
Synth Code total: —
DFE outstanding
| Synth Code | Description | DFE Adjustment | Rate | Total | Status | Variation Name | DFE Item Ref |
|---|
DFE total (accepted only): —
Grand total (Synth Code total + DFE total)
Whereabouts history
| Gang | Day | Day Status | Status | Comments |
|---|
Engineer Portal updates
Daily updates sent in from the Engineer Portal app — kept separate from the Job Notes below.
| Timestamp | Engineer | Works Completed | Work Outstanding | Reinstatement | Attachments |
|---|
Add a note for this job
Note history (newest first)
| Timestamp | Owner | Note | Attachment |
|---|
FX Status Update
| Status | Updated by | Date & time |
|---|
No FX Job Status updates recorded yet.
Job Tracker
Search all-time BT Jobs by Contract, Exchange, MGroup Status, Type and FX Job Status.
No status matches that.
Results
| Order ID | Exchange | Contract | Type | MGroup Status | FX Job Status |
|---|
Which days?
Every card below shows what happened on the days ticked here. A day fills up as the hourly import runs and starts fresh at midnight. The last 14 days are kept; older records are deleted automatically on each import.
New jobs
—
| Day | Time | Order ID | Estimate No | Arrived At | Exchange | Cost Code | Planned Start | Job Value | Lines with no rate |
|---|
No new jobs recorded on the selected day(s).
Moved status
—
| Day | Time | Order ID | Estimate No | Was Status | Now Status | Exchange | Cost Code |
|---|
No status moves recorded on the selected day(s).
Dropped off
—
| Day | Time | Order ID | Estimate No | Last Status | Exchange | Cost Code | Job Value | Lines with no rate |
|---|
No jobs dropped off on the selected day(s).
Add a Rate Card
Set up one Rate Card per contract/lot that needs its own pricing, and list the Cost Codes it applies to (from BT Export/Synth Code Report — one per line; a Cost Code can be a short code or a full descriptive name, and may safely contain a comma of its own, e.g. "M3100 - OSA 2.0 LOT 5 Norfolk, Lincs & East Mid"). Job Lookup then picks the right Rate Card for a job automatically from its Cost Code. A Cost Code can only belong to one Rate Card at a time. Anything not covered by a Rate Card here falls back to the General entries below, exactly as before.
Rate Cards
| Name | Cost Codes | Priced entries |
|---|
Import Rate Card
Select a Rate Card export (.xlsx / .xls / .csv) with columns for Synth Code, Unit of Measure, Description, Activity Rate and H&D Rate. A Synth Code already in the chosen Rate Card is updated in place; a new one is added. Nothing is ever deleted — entries in another Rate Card, or for another lot/contract, that aren't in this file are left untouched.
Add rate card entry
Rate Card
| Synth Code | Rate Card | Unit of Measure | Description | Activity Rate | H&D Rate |
|---|
Add a gang
A simple list of gang names — assign one to a Synth Code line from the Job Lookup tab.
Gangs
Add the people in each gang here — this is a simple reference roster; the Job Lookup dropdown still assigns the gang as a whole, not individual names.
| Name | Contract | Members |
|---|
Weekly Whereabouts
Find an Order ID
| Gang | Date | Status |
|---|
No Whereabouts entries found for that Order ID.
Synth Code Report
0 rows loaded, last imported —.
| Order ID | Status Name | Synth Code | Description | Planned Qty | Rate | Line Value |
|---|
DFE Report
0 rows loaded, last imported —.
| Order ID | Variation Name | DFE Item Ref | Synth Code | Adjustment | Status |
|---|
Pick a Job Category Code, a Status Code and a Contract, and this brings back every Synth Code line on the jobs that match — the Order ID, Estimate No and Exchange, then each line's Synth Code, quantity and value. Tick none in a list to mean all of it. Both lists offer only the values actually present in your data.
Pick an FX Job Status and an FX Invoicing Status, and this brings back every Synth Code line on the jobs that match — Order ID, Estimate No and Exchange, both statuses, then each line's Synth Code, quantity and value, with one merged Job Total per job. Tick none in a list to mean all of it. (not set) is a real choice in both lists, so you can find jobs that are finished but have no invoicing status yet.
Finished work only — JOB COMP and DMY COMP. Pick either or both, optionally narrow to a contract and a Job Complete Date range, and you get what was completed in that period and for whom. Updates live, with its own grand total, and exports to Excel below.
Grand Total
| Order ID | Status Name | Job Complete Date | Synth Code | Description | Planned Qty | Rate | Total |
|---|
Every job on the Whereabouts between the two dates below, priced off its Synth Code lines and the Rate Card — the same way every other report on this tab prices a job. Leave a date blank to leave that end open.
A job is counted once, however many days it is in for: a three-day job is worth what the job is worth, not three times it. Each row says how many of its days fall in the range, so a job that straddles the end is visible as one.
Every job whose Green Sheet Payment Date falls in the range below, with its Exchange, Contract and invoicing status. Leave a date blank to leave that end open.
Every Order ID with a DFE against it — the same lines Job Lookup shows under one job, gathered across every job. Shows the status, the Order ID and when this system first saw it, oldest first, so the ones that have been sitting longest come to the top. Tick none to include every status.
On the date: BT's DFE report contains no date of any kind, so there is no applied-for date to report. First Seen is when this system first saw the line, which starts from the next import onwards.
Pulls every Synth Code line where the total completed exceeds Planned Quantity, whether or not a DFE has been marked Done — with a Done column so you can filter/sort in Excel yourself. Independent of the Job Status/date filter above.
Currently flagged: 0
Weekly Billing
One week of the MGroup Works Programme, valued. A job is billed once, in the week of the first day the programme calls it complete; everything else the gangs touched that week is listed below it as not billed. Nothing here is saved — it is worked out fresh from the programme each time you load it.
Worth a look
Days where somebody wrote that a job was complete and the rules did not count it, plus jobs that could not be priced. Nothing here is wrong on its own — "needs ring beam" really is unfinished — but each one is a decision somebody should make rather than one a spreadsheet makes quietly.
| Order ID | Week | What it says | Why it was not counted |
|---|
Billed this week
—
Billing value: —
| Order ID | Gang | Exchange | Location | Days on site | Completed | Value | Check |
|---|
Nothing was finished in this week.
Worked on, not billed
Still in progress, an abortive visit, or not on the workstack at all. The value column is what the job would be worth if it were finished — it is not in this week's bill.
—
Value of unbilled work: —
| Order ID | Gang | Why not | Exchange | Location | Days on site | Value | What the programme says |
|---|
Nothing else was touched in this week.
Billing Sheet
Every job whose FX Job Status is Completed Job or Completed - Sent to Will. This is the only place the FX Invoicing Status is set. The FX Invoicing Status is changed here and nowhere else — press Save on the row. A new job starts at To Invoice; set it to Invoiced and it leaves this tab for Green Sheet Check. Click an Order ID to open its notes underneath it.
—
Total Grand Total: —
| Order ID | Exchange | Contract | MGroup Status | FX Invoicing Status | Grand Total | Notes |
|---|
No jobs are waiting to be invoiced.
Green Sheet Check
Jobs whose FX Invoicing Status is Invoiced. It is shown read-only here — it is changed on the Billing Sheet. Set the Green Sheet Payment Date and press Save, or let the Payments tab fill it in from the client's own sheet. A green PAID sticker appears once there is a date — hover it to see whether the client's payment sheet confirmed it or somebody typed it here. The date range searches on whichever of the two dates you pick.
—
| Order ID | Exchange | Contract | MGroup Status | FX Invoicing Status | Arrived On | Arrived By | Green Sheet Payment Date |
|---|
No jobs have been marked Invoiced yet.
Upload this week's payment sheet
The account summary workbook MGroup send, for any contract — Partner Infill, OSA or otherwise. Its Summary sheet is read, together with Child Works Data or Works Data, whichever it carries: the two are the same report under different column names and both are understood. Uploading the same assessment twice replaces it rather than counting it twice, so a repeat is safe.
Assessment
No payment sheets have been uploaded yet.
—
—
—
—
Paid this period
Jobs whose payable value moved between this assessment and the one before it. This Period is what MGroup released this week; Paid To Date is everything they have paid on that job, which differs when a job is settled in instalments.
Our Value is the synth-line total from Job Lookup, compared against Paid To Date so the two are like for like. Our DFE is shown separately because MGroup assess variations on their own sheet and it is not in their figure at all. Planned Not Done is quantity the client planned and did not complete, priced at their rates — an estimate where a line has no rate.
On a job they have closed — and every job in this table is one they have just marked complete — that is not money still to come. It means their own planned and completed figures disagree, which is worth asking them about but is not owed to us.
A + green variance means they paid more than we had the job down for. A - red one means they paid less.
—
This period the client released —.
To date on these same jobs they have paid — for synths plus — of H&D, against our — () — a variance of —. — of quantity was planned and never done.
| Order ID | Exchange | Order Type | MGroup Status | Job Comp | This Period | Paid To Date | Their H&D | Our Value | Our DFE | Planned Not Done | Variance | FX Job Status | FX Invoicing Status | Was |
|---|
Nothing moved between these two assessments.
Applying works across the whole account, not just this assessment — every job the client has paid for that is not yet recorded here, each dated by the payment that actually settled it. It fills in the Green Sheet Payment Date where that is still empty; a date somebody has typed by hand is left alone. No FX status is changed.
Variances — every job, paid against what we think
There are exactly two ways a job gets on this list, and nothing else appears:
- Its MGroup status is DMY COMP or JOB COMP. Anything at any other status is work in progress and is left out entirely.
- Or we have marked it Invoiced — then it is here whatever their status is, including when they have no record of it, and whether or not it has been paid.
Within that, Values differ means the synth values are more than £1 apart — a few pence is rounding, not a dispute. Complete for them, not in the Grid means they call it finished and we hold no priced lines for it, which is reported whatever the figures say. Invoiced here rows say where their side has got to.
Most variances have a reason and the reason is given. The ones marked Unexplained are the ones to take up — nothing on either side accounts for the gap. Our figure is the synth-line total; DFE is left out of the comparison because the client assesses variations separately.
A + green variance means they paid more than we had the job down for. A - red one means they paid less — those are the ones costing money.
H&D is never part of the variance. The client's figure is the synth value plus the H&D; our Rate Card prices the synths only. The two are shown in separate columns and only the synth halves are compared, so a job whose H&D is the whole difference does not appear here at all.
—
—
| Order ID | Exchange | MGroup Status | Paid — Synths | Paid — H&D | Our Value | Variance | Planned Not Done | What | Why | FX Invoicing Status |
|---|
Nothing to show.
Done but held
Work that is complete and priced on the client's own sheet, sitting on a status that does not release the money. This is the list to chase.
—
| Order ID | Exchange | Order Type | MGroup Status | Held Value | FX Job Status |
|---|
Invoiced here, never paid
Jobs we have marked Invoiced that have not been paid on any assessment loaded. Neither side's paperwork shows this on its own — a job can sit finished for months before it appears on a payment sheet.
—
| Order ID | Exchange | MGroup Status | Our Grand Total | Invoiced here |
|---|
Ask somebody to do something
This goes straight to their phone as an outstanding task. They mark it done and leave a comment, and the comment comes back here and to your inbox. A job number is optional — plenty of asks are not about one.
Tasks
| Asked | What | Who | Job | Where | Needed by | Status | What came back |
|---|
Add a user
Add the Microsoft 365 email address they sign in with, plus their name for reference. Nothing is ticked by default — until you tick a tab below, it stays hidden for them when they sign in. Anyone who signs in whose email isn't listed here at all can't get into the console.
Users
Tick/untick a tab and it saves immediately — that person sees the change next time they sign in (or straight away, if it's your own access you're changing). You can't remove your own Users access or delete your own account, so you can't lock yourself out. Super user is separate from tab access — it lets someone delete any Synth Code completion entry or Job Lookup note, including ones another person recorded, which is otherwise impossible for everyone (see Job Lookup).
| Name | Tab access | Super user |
|---|
Notify contacts
People who can be ticked in the Whereabouts tab's Replan pop-up to get an emailed notice when a day is cancelled or replanned. The app sends it itself, from your own signed-in Microsoft 365 mailbox — nothing is sent unless you tick someone.
| Name |
|---|
Company tiles
Shown as tiles on the landing page everyone sees right after signing in, before the console itself — useful if you work across more than one company/contract. Every tile currently leads into the exact same console/data; picking one just continues in as normal.
| Name |
|---|