Studio Forecast Architectural team & utilisation planner
No file linked — using sample data

Dashboard

Snapshot of the studio. Forecast window starts .

Live projects — start date needs confirming

This month at a glance

Needs attention

Staff

If an actual cost override is set it is used; otherwise the default, then the median from the Rates table.

Up to three holiday periods per staff member. Start and end dates use the Sunday-first picker.

Designation & rate table. Median costs are used as a fallback when a staff member has no actual or default cost.

Projects

Apply a template

Project number is optional. Status drives the dashboard pipeline figures. The standard and the stage durations are set on the Project staging sub-tab.

Project name and dates are mirrored from the Projects sub-tab — change them there. Set the standard and the duration of each stage here; the stages drive the segments on the Gantt.

Stages exceed dates by > 1 wk Stages under dates by > 1 wk Within a week

Reusable staffing patterns. Apply one to a project to generate provisional allocations.

Plan one project week by week. Week columns run across the project's dates and are shaded by the stage that covers them (set stage weeks on the Project staging sub-tab). Each week cell works like the month cells on Allocations · Project — type a %, or drag across the row. When the detail is ready, press Override Allocations · Project to average each month's weeks back into that grid.

Allocations · by staff

One block per person — the projects they're on, with location, dates and notes. The month-by-month % of involvement is planned on the Allocations · Project tab; edits there flow back here and into the utilisation grid.

Date from

Allocations · by project

The same allocations, grouped by project, with a 12-month planner. Start and End are taken from the project (set them on the Projects tab). Each month cell is the % of that month the person works (100% = a full month, about 208 h). Months within the project's dates are white and editable; months outside are greyed, and a value typed into a greyed month shows red. Projects with no dates set leave all months open. Edits flow to the staff view, utilisation and the summary.

Date from
Pick a person to see only the projects they're on.

Utilisation

Total monthly load per person and per provisional role. Real values shown, including above 100%.

Date from
0%55%100%>100%

Each person's share of a single month across every project (1.00 = a full month, 0.35 = 35%). Values are read from the allocations; Annual leave is derived from Assigned holidays. Use ◀ ▶ to change month.

Project Gantt

A 12-month view of each project's overall duration, from its start date to its end date. Projects without both dates set are listed but not drawn.

Date from

Project summary

Allocated hours and cost are rolled up from the Allocations tab.

Export & backup

Everything stays on this machine. Save often.

Download location

Optional. Choose a folder to save JSON files into (the working file copy and backups). If none is set, JSON downloads go to your browser’s Downloads folder.

No folder set — JSON downloads go to your browser’s Downloads folder.

Working file

Save the full database back to your linked file, or download a copy. The file is named after the department chosen on the Staff page, e.g. ARCH_Data.json.

CSV exports

Open in Excel for reporting or sharing.

Reset

Reload the built-in sample data. Your linked file is not changed until you save.