Log your work location
Pick your name and the week, then set where you worked each day. Takes under a minute.
C · Client Office
J · JLL Office
W · WFH
H · Holiday / Leave
Team dashboard
Compiled weekly submissions across the team, with a live pending count.
Team size
–
Submitted
–
Pending
–
| Name | Account | Mon | Tue | Wed | Thu | Fri | Status |
|---|
Pending this week
Employees who haven't submitted yet — a nudge list.
Monthly report
Aggregated day-count per employee across all weeks in the selected month — ready to export and circulate.
Select a month and click Generate.
| Name | Account | Client Office (C) | JLL Office (J) | WFH (W) | Holiday/Leave (H) | Days logged | Working days in month | Compliance |
|---|
Google Form version (optional fallback)
If you'd rather collect responses over Google Forms instead of this page, set it up exactly like this so a script can compile the responses automatically each week.
Form settings
- Title: Weekly Work Location Update
- Description: "Tell us where you worked each day this week. Takes under a minute — please submit every Friday."
- Settings → General: turn ON "Collect email addresses" (verifies identity, avoids a Name dropdown typo) and "Limit to 1 response" if using a company Google Workspace domain.
- Settings → Responses: turn ON "Response receipts" and link responses to a new Google Sheet named Work_Location_Responses.
Questions (in order)
- 1Name — Dropdown, required. Options: the 17 employee names (Anubhav, Archit, Deepti, Devansh, Gaurav, Girish, Mahesh, Ojas, Rahul, Rakesh, Ruchi, Saurabh, Shakti, Shubham, Swati, Vaibhav, Vijaylakshmi).
- 2Week ending (Friday's date) — Date, required.
- 3Monday — where did you work? — Dropdown, required. Options: Client Office / JLL Office / WFH / Holiday or Leave.
- 4Tuesday — where did you work? — same dropdown options as above.
- 5Wednesday — where did you work? — same dropdown options.
- 6Thursday — where did you work? — same dropdown options.
- 7Friday — where did you work? — same dropdown options.
- 8Comments (optional) — Short answer, not required.
Making it quick to fill
- Use dropdowns (not checkboxes or free text) for every location field — one tap per day, no typing.
- Keep all five day-questions on a single page so it reads as one short grid rather than a multi-page form.
- Turn on "Shuffle question order" = OFF, so the Mon–Fri order stays intuitive.
- Add a pre-filled link per person (Google Forms → "Get pre-filled link") if you want each employee's own recurring email to already have their name selected.
Why this page is a better fit than a Forms + Sheet chain
- Google Forms + Sheets works for collection, but compiling a Mon–Fri grid across 17 people, spotting who hasn't responded, and rolling that up into a monthly file all need extra formulas or Apps Script glue.
- The Fill Weekly Update, Team Dashboard, and Monthly Report tabs on this page do all three automatically: one shared place to submit, a live pending-count dashboard, and a one-click Excel export for the monthly circulation — no Sheet wrangling needed.
- Use the Google Form only if employees need to fill this from a channel where this page isn't reachable — otherwise this page is the simpler single source of truth.
Backend setup — Hostinger (PHP + JSON file)
This page needs its api.php companion file uploaded alongside it so everyone's submissions land in one shared place.
One-time setup (whoever owns the tracker does this once)
- 1Log in to hPanel on Hostinger and open File Manager (or connect via FTP) for the domain/subdomain you want this on.
- 2Navigate to public_html (or a subfolder inside it, e.g. public_html/tracker, if you want it at a sub-path).
- 3Upload both index.html and api.php into that same folder. They must sit side by side — the page calls api.php as a relative path.
- 4In File Manager, right-click the folder → Permissions and make sure it's writable (755 on the folder is usually enough; Hostinger's PHP user needs to be able to create data.json the first time someone submits).
- 5Visit the page at your domain, e.g. https://yourdomain.com/tracker/index.html. Submit a test entry from the Fill tab, then check the Team Dashboard tab shows it.
- 6Share that URL with the team — everyone who opens it now reads and writes the same data file on your server.
How it works
- Submitting the form sends a small JSON payload to api.php, which stores one row per employee per week inside data.json in the same folder.
- The Dashboard and Monthly Report tabs fetch every row from api.php and filter it in the browser — no separate sync step.
- Re-submitting the same person + week overwrites that row, so people can correct a week after submitting it.
- There's no login built in — anyone with the page link can submit or view. If that's a concern, Hostinger lets you password-protect the folder from hPanel (Website → Directory Password Protection), or you can add one from the Advanced tab.
Data location & backups
- The full dataset lives in data.json on your server. Do not delete it — it's the single source of truth.
- Use the Download full backup (Excel) button below any time to pull every stored row into a real .xlsx file for safekeeping or emailing.
- For extra safety, periodically download data.json itself via File Manager/FTP as a raw backup.