Key takeaway
Total staff hours do not establish a feasible date. Schedule each dependency against a named owner’s available window before promising a release.
Convert hours into a calendar
A proposal that needs seventeen staff hours can still take two working weeks. Different people may be available on different days, and later tasks may require an earlier decision. Before promising a package, identify task owners, predecessor evidence, available windows and what counts as completion. Distinguish internal preparation from the business’s separate decision to share a sample; a finished extract is not permission to transmit it.
NASA’s technical planning guidance describes resource-aware scheduling, task dependencies and critical-path considerations. Read on 8 October 2026, it offers a useful engineering starting point for this business planning exercise. It does not certify a commercial date or prescribe the hours used below. Use actual committed availability from your own team and preserve uncertainty when someone cannot yet confirm their review window.
Complete a named-owner plan
This hypothetical sponsor wants an internal review package by working day D5. Mina can spend two hours per day on the field map on D1 and D2. Nadia’s three-hour review window is D4. Owen has three hours each on D5 and D6 for the six-hour internal extract after that review. Mina’s later three-hour quality check is available only on D8, followed by Elena’s one-hour sponsor decision on D9.
The completed dependency plan totals seventeen hours, but its earliest planned sponsor decision is D9. D5 is infeasible under those stated windows. The sponsor can accept D9, obtain a confirmed earlier window or reduce the scoped work and replan it. The illustration assumes each named window is actually committed and all predecessors pass. It does not assume overtime, instant review, substituted staff or permission to disclose the resulting package.
| Task / fictional owner | Effort and availability | Predecessor and planned completion |
|---|---|---|
| Field map / Mina | 4 h; 2 h on D1 and D2 | No predecessor; complete D2 |
| Scope review / Nadia | 3 h; D4 only | Field map required; complete D4 |
| Internal extract / Owen | 6 h; 3 h on D5 and D6 | Scope review required; complete D6 |
| Quality check / Mina | 3 h; D8 only | Internal extract required; complete D8 |
| Sponsor decision / Elena | 1 h; D9 only | Quality check required; decide D9 |
| Proposed D5 date | 17 total hours across five tasks | Cannot meet D5 under these commitments |
Identify the constrained role before reducing scope
Compare each task with the person’s available window rather than pooling every team member’s hours. Mina’s D2 completion enables Nadia’s D4 review; Owen cannot start the assumed internal extract before that review finishes. Finishing the map a day earlier would not change D9 if Nadia, Mina’s second window and Elena remain unavailable earlier. The bottleneck is the dependency schedule, not simply the sum of task hours.
A narrower description might need less extraction work, but the responsible reviewer must confirm that the reduced scope still answers the intended question. Moving to a metadata-only introduction is a different deliverable from preparing a sample. Record that choice explicitly instead of calling the smaller deliverable a completed version of the original package. The inventory tool can help define the proposed categories before the schedule is recalculated.
Reserve the ability to correct a failed check
The table contains no rework buffer. If the D8 quality check finds a material defect, D9 should become a review of the unresolved problem rather than a release promise. Assign the correction to its actual owner and locate the next available review window. Do not spend someone else’s nominal spare capacity when they lack the required source access or authority. A substitute owner needs a confirmed handoff and availability.
NASA’s scheduling guidance considers dependencies, resource timing and changes affecting a critical path. For this proposed plan, record the assumption that each predecessor passes and the date for reassessing that assumption. When the source system changes or the requested fields expand, update both task completion criteria and downstream windows. A stale seventeen-hour estimate should not continue to support a date after the work definition has changed.
NASA’s technical assessment guidance distinguishes status reporting from assessment and defines reviews using entry and success criteria. In this plan, Owen’s completion note should identify the internal package version and unresolved issues before Mina’s D8 check begins. If the required scope-review evidence is absent, that entry condition has failed even when six hours of work were logged. Record the failed condition, then locate a new feasible review window; a completed timesheet does not resolve the dependency.
Give the sponsor a concrete decision
The immediate decision in the example is to decline the D5 package promise and provisionally plan the internal sponsor review for D9. Elena confirms the scope, named commitments and rework rule before accepting that plan. Separately record who may approve any recipient-facing description or sample, with its purpose and fields. The calendar remains an internal preparation plan until those disclosure decisions are made.
Use readiness to flag unconfirmed owners and unresolved checks, and link the plan to the inventory’s exact category description. Track completed tasks with evidence rather than marking the entire effort done because the extract exists. This article establishes operating feasibility, not a license price, expected earnings or referral payment. If the next stage is a VOID introduction, its named-recipient permission concerns the agreed description; the schedule itself authorizes no communication.