Management dashboard
One page for the review: where the network stands against target, which sites are slipping, what material is overdue and what is waiting on a decision — then the region matrix, showroom first with the pending locations listed under it, service next.
Target against actual
Every site measured against its own target live date and the plan on its activities. Click a number for the sites behind it.
Sites running late
Past target, or with activities finished after their planned finish. Worst first.
Material overdue
Expected on site before today and still not marked received.
Waiting on a decision
Open messages, DP remarks with no JSW answer, and sites flagged for a site change.
Pending is the live action only — a gate counts as pending once everything before it is cleared. Locations under each matrix are the sites sitting at that gate right now, shortest form first so the list reads in a review.
Where the Phase-1 network stands
Brownfield and greenfield
Each site counted once against its own type, as recorded in the site code.
Facility mix
1S is a showroom, 2S a service workshop, 3S both on one site. Showroom counts below add 1S and 3S; service counts add 2S and 3S.
Document and approval pipeline
Pending means the item is the live action on that site — everything ahead of it in the flow is already cleared. Where an earlier step is still open the item counts as not reached, not pending, so nobody is chased for work that cannot start yet.
Where the network is actually stuck
Each site counted once, against the one gate it must clear to move forward. Paperwork that runs alongside the flow — DD drawings, photos, video, vastu, tile and HVAC orders — is chased in the table above, so a site in construction is not filed under dealer documentation because a vastu box is blank.
Region matrix — done against pending at each gate
The full region matrix, the same as its own tab and driven by the same three buttons: all sites together, then showroom, service, and the sites that carry both. Showroom counts add 1S and 3S; service counts add 2S and 3S; the fourth block is the 3S sites on their own. Bracketed figures are the share of the sites that gate applies to, and every number opens the list behind it.
RAG position
Taken straight from the Status column of the master sheet, not recalculated.
The six regions
South, South East, West, West Central, North and North Central. Region is read from the area code on each row, which resolves the handful of rows where the region column and the area code disagree.
Sites by region
Brownfield and greenfield split, facility mix and RAG position for each region.
Showroom and workshop count by region
A 3S site contributes one showroom and one service workshop, so these totals are larger than the site count.
Region progress against the pipeline
Share of tracked items signed off, from dealer documents through to GFC release.
Areas within each region
States, markets and dealers
State-wise breakup with the market, dealer principal and RDDM behind every site. Click any site code to open its full record.
State summary
Market and dealer listing
One row per site, grouped by state and market.
Site ledger
Every site keyed to its site code, with the one item each site is actually waiting on. Click a code to open the full record — identity, all 26 tracked items, the Bucket-1 checklist, SPOC details and the remark history.
Stage reached is the furthest item on the core chain the master sheet records as cleared. Live action is the first gate on the main flow that is still open — dealer documents, PMC validation, first-cut layout, feasibility, DP feedback, final layout, DP approval, management approval, PCW, GFC Bucket-1, PERT, work start, work complete. A site sitting at first-cut layout is not also counted as pending on DP feedback or management approval, because those cannot start yet. Also open counts paperwork running alongside the flow that does not block it.
Milestone status
For each tracked item, the sites where that item is the live action — everything before it in the flow is already cleared. The small grey figure beside each count is the number of sites not yet at that step; they are waiting on something earlier and are not chased here.
Item by region
Green: completed. Red: this is the live action. Grey: not reached, waiting on an earlier step. Denominator: sites in that region for which the item applies. Every figure opens the list behind it.
Sites pending the critical items
Sites where the final layout release, PCW or GFC Bucket-1 is the live action. Sites still working through the first-cut layout are left out — they are not yet at these gates.
Site reports
The daily progress report from site, written against the site's own PERT and GFC Bucket-1 activities, with photos. Progress entered here moves the PERT schedule and the Bucket-1 checklist too, so the site team only records it once. The weekly report builds itself from the dailies.
PERT control
Site-by-site construction schedule from your PERT templates — 24 activities for a showroom, 28 for service and combined sites, plus govt approval, civil foundation and structure work on greenfield sites. Set a start date, generate the plan, then log actual dates and percentage done as the work moves. Delay, planned-versus-actual progress and forecast finish are worked out for you.
All sites against their plan
Click a site code to open its schedule. Sites without a start date have no plan yet.
Alerts
Anything carrying a date that falls due tomorrow, today, or has already passed — tracked items, activity plans, PERT milestones, material deliveries, remark actions, and the daily report from each site. Every row comes with a message written for the person who owns it, so you can send the reminder a day ahead. W opens WhatsApp, @ opens the mail, and P raises the reminder inside the portal against that site.
A missing daily report is only chased once a site is genuinely under way — PCW or work start recorded, or at least one activity moved. Sites that have not started are left out so the list stays worth reading; the full picture is on Site reports → Who has reported.
Falling due tomorrow
The one-day-before list. Send these today.
Due today
Already overdue
Past their date with nothing recorded as complete.
Coming up in the next seven days
Dates come from four places: the target date on a Bucket-1 activity, the date set against a tracked item, the target date on a remark, and the Target Completion column of the master sheet. Nothing is sent automatically — this file has no server behind it, so the list is worked out when you open the dashboard and the mail opens in your own mail client when you click it.
Region matrix
Four matrices over the same Phase-1 network. Pick one from the list below — each keeps its own settings, so you can set one up and come back to it.
Pending is the live action only: a gate counts as pending once everything before it is cleared. The small grey figure is sites not yet at that gate, so they are not chased here. With Showroom & Service on, a 3S site is counted in both Showroom and Service. All sites still counts each site once. Every figure opens the list behind it.
Pending is the live action only: a gate counts as pending once everything before it is cleared. The small grey figure is sites not yet at that gate, so they are not chased here. With Showroom & Service on, a 3S site is counted in both Showroom and Service. All sites still counts each site once. Every figure opens the list behind it.
Read straight from the PERT sheet, with no sequencing applied: Approved, Yes or a date counts as done; WIP has its own column on the site-work milestones and shows as the small amber figure beside pending on the rest; blank, 0, No or Pending counts as not started. Bracketed percentages run against the sites the milestone applies to, so N/A rows are left out. Every figure opens the list of sites behind it. Slide view strips the percentages and tightens the table for a deck; the print comes out landscape.
A facility counts in a window when its Target Completion – DP date falls on or before that date and after the one before it. Showroom covers 1S and 3S sites, workshop covers 2S and 3S, so a 3S site is counted once on each line. Where a 3S cell holds two dates, the first counts for the showroom line and the second for the workshop line. Cells with no date, or with text instead of a date, sit in Beyond / undated. Every figure opens the list behind it.
GFC Bucket-1 site activities
The 46 work items that make up a Bucket-1 release, across eight trades. Activities only count as pending once Bucket-1 drawings are actually released to that site; until then they sit as not reached, so the numbers here are work the site teams can genuinely be asked about. Open any site to mark items off, then print its pending list.
Trade progress across the sites in view
Percentages run against the full scope — every site in view × its 46 items — not just the released ones, so the figure is real progress against Phase-1 rather than progress against whatever happens to be live. Every count opens the list behind it.
Site-by-site trade completion
Items completed in each trade, against that trade's item count. A dash means the site has no Bucket-1 release yet. Click a site code to open its checklist.
Activity checklist
The full Bucket-1 scope as issued. Pending counts are clickable and cover released sites only.
RDDM load and site contacts
Portfolio held by each RDDM, and the dealer-side single point of contact for every site.
RDDM portfolio
Regional manager and area sales manager
WhatsApp groups and DP numbers
One group per site. Paste the invite link once and everyone on the programme can open that group from here — PMC and JSW accounts may add and change a link, everyone else can open it. Open group opens the invite; Message group opens it and puts the site’s status message on your clipboard to paste, because WhatsApp gives no way to post into a group from a link. Message DP opens a direct chat with the message already written.
Site SPOC directory
Reach out opens WhatsApp, the phone dialler or your mail client with a message already written for that site — its code, market, dealer, current stage and everything pending on it. Rows marked as not captured have no number in the master sheet.
Activity tracking
Every activity on a site, from land document verification through to facility readiness approval — the thirty stages carried in the Base sheet of the master workbook. An activity only counts as pending once the gate in front of it is cleared, so the numbers are work the site can genuinely be asked about. Every count opens the list behind it.
Progress by activity
Percentages run against the whole scope in view — every site × every activity — not done against pending. Click any number for the sites behind it.
Region roll-up
Activities completed in each region against that region's full activity scope.
Site by site
Where each site stands across the six activity stages. Click a site code to open it.
Material order status
What has been ordered for each site, when it was ordered, when it is expected and when it landed. Ordering only becomes due once GFC Bucket-1 is released, so nothing is counted against a site that has no drawings yet. Tile, HVAC and light orders come straight from the master sheet; the rest are maintained here.
Order book by item
Each material against the sites that need it. Percentages run against the full scope in view. Click any count to see the sites.
Arriving next
Orders placed with an expected delivery date, soonest first. Overdue deliveries are flagged in red.
Site by site
Order status per site. Open a site to record order, expected and received dates.
Vendor directory
Contractors and suppliers by region. PMC and JSW accounts see the whole directory; a site team sees the region its own site sits in, and adds only there. PMC and JSW can remove any entry, and a site team can remove what it added itself.
Add a vendor
Directory
The directory lives with your edits in this browser and travels in the backup and the access file. It is a contact list, not a contract record — keep rates and commercial terms out of it.
Minutes of meeting
One record per site — who met, what was agreed, and who owes what by when. A point stays open until somebody closes it, so nothing quietly falls off the list between visits.
Record a meeting
Meetings
Minutes live with your edits in this browser. They travel in the backup and in the site report pack, so a meeting recorded on site reaches the PMC copy with the daily report.
FAQ
The questions site teams keep asking, answered once. Everyone can read it; PMC and JSW accounts can add, edit and remove entries.
Add a question
Questions
All remarks
The management review page. Activity review lists every activity with the DP remark and the JSW remark side by side, so one read down the page tells you what the dealer said and what JSW answered. Everything is the full chronological register — minutes, site issues, daily notes, messages and the master sheet as well.
The register
Approved drawings
The signed-off layout for every site, in one place. It is the same file that sits inside each site record — this page is here so nobody has to open a site to find it. PMC and JSW upload and replace; everyone with access to a site can open and download.
By site
Drawings are held in this browser with your photos and travel in the backup and the site file. Keep the master set on your own drive as well — this is a working copy, not an archive.
Update the dashboard from your master workbook
Everything on every other tab is read from the master Excel. Upload a newer copy here and the whole dashboard re-reads it — site list, regions, milestone dates, remarks, activities and the PERT sheet. Statuses you have changed inside the dashboard are kept and re-applied by site code.
Upload the master Excel
Pick your latest JSW_Master_Sheet_Dashboard_PH_1….xlsx. The dashboard reads three sheets and ignores the rest:
- Main New — the site register: codes, regions, dealers, SPOC, every milestone column and the dated remark columns.
- Base — the thirty activities per site that feed Activity tracking and the material order seed.
- Main Pert — per-site PERT status, applied to the schedules in PERT control.
Check what changed
After the upload the dashboard tells you how many sites were read and how many of your edits were re-applied. Anything the sheet cannot be read for is listed below under Data notes.
Columns are matched on their heading, not their position, so you can add or move columns in the workbook without breaking anything. New dated remark columns are picked up automatically.
Keep everyone in step
This dashboard has no server behind it, so each person holds their own copy of the file. After a master upload, send the refreshed HTML file around, or export your edits and have the team load them.
Update or remove a site
Admin only. This writes the site list in the database, so everyone sees the change. A later master Excel upload replaces these details with the workbook.
Add a site that is not in the master sheet
For a site the workbook has not caught up with. It joins the register straight away and stays through a master upload; when the sheet does carry it, the sheet’s row takes over. PMC and JSW accounts.
Backup, restore and photo storage
This dashboard has no server behind it. Everything you and the site teams record lives in this browser, so a backup is a file you download and keep somewhere else. Nothing leaves this device unless you send it.
Take a backup
The photo backup is the large one — keep it on a shared drive, not in email. The light one carries every status, date, remark, order and report but no images.
Restore
Load a backup file to put this browser back to how it was. Everything currently held here is replaced, so take a backup first if you are unsure.
Photo storage and retention
Counting photos…
Photos are shrunk on upload and held in this browser’s database. Clearing old ones frees space on a device that is running out; back them up first.
Data notes from the current workbook
What the master sheet could not tell the dashboard, or told it twice. Nothing here is corrected silently — it is listed so the sheet can be fixed at source.
What is in the file right now
Users and access
Who can sign in, what they may change, and which regions or sites they see. Changes take effect here immediately; to put them on everyone else's copy, download the access file and have each person load it once.
Who covers each region
Head office accounts by region. Editors can update; view accounts see everything; site accounts are counted separately.
Change log
Every status, date and remark anyone has changed in this copy of the dashboard, newest first, with the user who made it and what it was before.
The log lives in this browser alongside the edits. Save my edits writes it out with everything else, and Load edits merges someone else's log into yours, so a weekly round of exports keeps one consolidated history.