One professional dashboard for submittals, finance, and field coordination

A Deliverable Package number is the unique identifier for each design deliverable on the project. It typically follows a numbering convention like DP.001 or DP.315. Every row in your DP import templates must have a unique DP_Num — this is how the dashboard links plan, forecast, and actual dates together.

Work Breakdown Structure number. This is the accounting or cost code assigned to a deliverable or budget line in your project management system. It is optional in most templates but helps link deliverables to budget categories.

Original (Plan) is your locked baseline schedule. You import this once at the start of the project and never change it. It represents the dates you committed to at contract or kick-off. The S-curve uses this as the baseline reference line.

Forecast is your current expected completion date for each milestone. On a new project, forecast starts equal to plan. As the project progresses, a plan date may not be met — in your weekly coordination meeting the PM asks each lead "what is your new submission date?" The PM opens the Submittals tab, clicks the edit button on that deliverable package, updates the forecast date, and saves. The S-curve and look-ahead update immediately. You can also do a bulk forecast update by re-importing the Forecast template if many dates shift at once.

Actual is the date a milestone was actually submitted to the client. When a package is submitted, the PM edits that DP row and enters the actual date. This is what drives earned value — EV is only earned when an actual date is recorded. Like forecast, actuals can also be bulk-imported via the Actual template.

No. The dashboard auto-detects which data type each file contains by reading the file name. For example, it recognizes dp_original_(plan).xlsx as the baseline DP template and subconsultants.xlsx as the subconsultant data. If you rename a file, the dashboard will not be able to identify it and will skip it during import. Keep the file names exactly as downloaded.

No. The column headers must stay exactly as provided. The dashboard reads data by header name. If you rename a header, that column will not import. You can change column widths, hide columns, or reorder rows — those are formatting changes that do not affect the import.

Owner has full access — add and edit all data, import files, export backups, and manage passwords. Temp can add notes, add deliverable packages, and update forecast and actual dates. Temp access has an expiry you set. Read-Only can view all tabs and print reports but cannot edit anything.

The recovery key is generated during setup and downloads as a text file. It is the only way to reset your owner password if you forget it. Save it in the same folder as your project files and JSON backups. Keep it private — anyone with the recovery key can reset the password.

JSON is a standard file format for storing structured data as plain text. Think of it as a complete snapshot of your entire project — every deliverable package, every date, every budget entry, every note, and your sign-in settings — all in one file at a point in time.

The dashboard uses JSON as its backup and restore format because it is universal, lightweight, and human-readable. If something goes wrong — you clear your browser, switch computers, or share the dashboard with a team member — you restore from that file and every piece of data comes back exactly as it was.

Best practice: export a JSON backup at the end of every weekly meeting and save it to your project folder or cloud drive.

Go to Data & Import → Backup → Export JSON. This downloads a complete snapshot of all your project data. Save it to your project folder or cloud storage. To restore, use Data & Import → Restore from JSON on the same dashboard or a fresh one.

The dashboard app is hosted online — you can open it from any browser on any computer by visiting the same URL. The app never disappears.

What does not follow you is your project data. All your deliverable packages, dates, budget entries, and notes live in the local storage of the specific browser where you completed setup. A different browser or computer starts fresh with no data.

This is why the JSON backup exists. Export after every weekly update and save to your project folder or cloud drive. To pick up on a new machine: open the dashboard URL, complete a new setup, then restore your JSON — every entry comes back exactly as it was.

Clearing your browser's cache or site data removes your project data from that browser permanently. The dashboard app itself is unaffected — it is hosted online and will still open normally. But your deliverable packages, dates, budget, notes, and settings will be gone with no way to recover them unless you have a JSON backup.

If this happens: open the dashboard, complete setup again, then restore from your most recent JSON export. Any work done after your last export will need to be re-entered manually.

Best practice: Export a JSON backup at the end of every weekly meeting. Name it clearly — for example Harbor_Crossing_backup_2025-05-12.json — and save it to your project folder or cloud storage.

Earned Value Management tracks project health in dollar terms. PV (Planned Value) is the budgeted cost of work scheduled to be done by today. EV (Earned Value) is the budgeted cost of work actually completed. AC (Actual Cost) is what you have spent. SPI = EV/PV (schedule efficiency). CPI = EV/AC (cost efficiency). The S-curve plots these over time using your DP dates and budgets.

Your project data — deliverable packages, dates, budgets, specs, meeting notes — never leaves your browser. It is stored locally and is not transmitted to any server.

When you complete the initial setup, your name, email address, and project name are sent to us so we can manage your access, send you template updates, and contact you if there is a critical fix. We do not sell or share this information with third parties. You can request deletion at any time by emailing us directly.

That is the only data we collect.