Weekly Performance
No data loaded
Designers Tracked
โ€”
this period
Studio Avg Weekly Score
โ€”
Avg Utilization
โ€”
logged vs expected
Weeks of Data
โ€”
๐Ÿ“Š
No weekly data yet
Go to Weekly Data Entry to get started.

Total Projects
โ€”
Avg Client Score
โ€”
external score avg
Avg Budget Adherence
โ€”
Score Mismatches
โ€”
internal vs client gap >1.5
๐Ÿ“
No project data yet
Add projects or upload your project management sheet.

๐Ÿ“ค Step 1 โ€” Upload Timely CSV
โฑ
Drop Timely CSV here
Logged hours auto-populate per designer
๐Ÿ“… Step 2 โ€” Week Details
โ„น๏ธ Date range and week number are auto-detected from your Timely CSV. Click any date to adjust manually.
W1 = first week of January
No range selected
โœ๏ธ Step 3 โ€” Scores Per Designer
โ„น๏ธ Logged hours auto-fill from Timely CSV filtered to selected date range. Enter declared days, leaves, and 3 metric scores. Expected hours = (Declared Days โˆ’ Leaves) ร— 8.6
Studio Declared Days this week: Applies to all designers โ€” override individually per row if needed. Resets each week.
DesignerDeclared DaysLeavesExpected Hrs Logged HrsLearning (1โ€“5)Collab (1โ€“5)Upskilling (1โ€“5)Remarks
๐Ÿ“ค Upload MS Forms (Client Feedback)
๐Ÿ“‹
Drop MS Forms Excel here
Client ratings matched by job number
๐Ÿ“ค Upload Project Management Sheet
๐Ÿ“Š
Drop Project Management Sheet here
Auto-fills project name, client, AM, category by job number
โž• Add / Close a Project
Job Details (AM Entry)
Select designer(s)
Select AM
Manual โ€” not in Timely export
Job Ratings (Raksha / Sheetal)
Timely Data
Client Feedback (MS Forms)
โž• Add Team Member
โ„น๏ธ Data Integrity
โœ… Names capitalised automatically
โœ… Duplicates blocked
โœ… Ex-employees hidden from dropdowns, data preserved
โš ๏ธ Members with data cannot be deleted โ€” use Ex-Employee
โœ๏ธ Rename updates all records automatically
Team Members
NameRoleStatusData RecordsActions
๐ŸŸข RAG Thresholds โ€” Weekly Score

Set the score boundaries that determine whether a designer's weekly score is Green, Amber or Red. Changes apply immediately across all views and historical data.

Score at or above this = ๐ŸŸข Strong
Score below this = ๐Ÿ”ด Needs Support
Preview
๐ŸŸข RAG Thresholds โ€” Project Score

Set the score boundaries for project scores. These are applied independently from weekly score thresholds.

Score at or above this = ๐ŸŸข Strong
Score below this = ๐Ÿ”ด Needs Support
Preview
โš ๏ธ About Changing Thresholds
โ€ข Threshold changes apply immediately to all data โ€” including historical records. A designer who was green last month may become amber after a threshold change.
โ€ข This is intentional โ€” it means you can calibrate thresholds as you collect more data and understand what scores are realistic for your team.
โ€ข Recommended approach: Start with the defaults (Green โ‰ฅ 4.0, Red < 2.5) for the first 6โ€“8 weeks, then review once you have a realistic distribution of scores.
โ€ข Thresholds are saved in the browser and persist between sessions.
โฑ Timely CSV
๐Ÿ“‚
Upload Timely CSV
.csv ยท weekly export
๐Ÿ“‹ MS Forms Excel
๐Ÿ“‹
Upload MS Forms Excel
.xlsx ยท client feedback
๐Ÿ“Š Project Management Sheet
๐Ÿ“Š
Upload Project Management Sheet
.xlsx ยท re-upload weekly
๐Ÿ“ฆ Data Status
Weekly recordsโ€”
Project recordsโ€”
Active team membersโ€”
Client responses loadedโ€”
Project mgmt rowsโ€”