How HoursCast works
Total Estimated Hours
0
Estimated Labor Cost
—
Estimated Travel Cost
—
Enabled Work Packages
0
Unverified Assumptions
0
Unmapped Roles
0
Project Assumptions — technical/planning drivers, disclosed and editable, never a hidden default
Work Packages, Drivers & Activity Norms — every norm's source is shown; an unverified norm is never presented as an organizational standard
A Work Package groups related activities (e.g. all GIS-bay engineering) and holds the quantity drivers — like a bay count — those activities scale from. Each Activity assigns one role's hours via a calculation type; hover a field for what it does.
Role-Hour Results — every row totals what's currently configured in Assumptions
Phase Allocation — each phase bucket's own monthly-loading method
Proposed Monthly Loading — an estimate, not a resourcing commitment
Peak Proposed Demand
—
Travel & Additional Costs
Validation & Reconciliation
Department Review — a decision recorded here is advisory; it travels with the estimate, it doesn't apply anything by itself
For each department with estimated hours, record what it plans to do with them. This is metadata for whoever applies the transfer in ResourceCast — the actual write to ResourceCast is controlled separately, by the import mode chosen there (see "Transfer to ResourceCast" below).
Draft
  • Pending review — no decision made yet (default)
  • Accepted as estimated — the department will use these hours as-is
  • Accepted with adjustment — accepted, but the department intends to change the figure on import (say what, in Comments)
  • Rejected — the department will not use these hours at all
  • Retain existing plan — ResourceCast already has a number here — keep it, ignore the estimate
  • Deferred — a deliberate postponement, distinct from "pending"
Transfer to ResourceCast — prepares a governed exchange payload; nothing is written to ResourceCast from here
Preparing a transfer stages the current estimate for ResourceCast's own Import Resource Estimate inbox, where it must be reviewed, reconciled against the current approved plan, and explicitly applied by a Department Head or functional approver. Review-only is always the default import mode there, and applies nothing on its own. A role or phase ResourceCast doesn't recognize, or a month outside ResourceCast's own project timeline, is blocked from ever being written — no import mode can override that. Requires a Start Date in Project Details (left sidebar) — without one, hours can't be anchored to real calendar months.