Live planning model
Test whether dependent wedding work fits the calendar
Venue/guest-list work feeds vendor booking while attire progresses in parallel. Finalization waits for the slower chain, then schedule contingency is added. This is a compact dependency model, not a checklist duration sum.
| Workstream or milestone | Duration | Earliest start day | Earliest finish or buffer |
|---|
Current calculation process
Formula, default substitution, intermediate quantities, and check
critical path = max(venue/guest-list + vendor booking, attire) + finalization + contingency
The venue-to-vendor chain and attire chain begin together. Finalization begins only after both finish, so the longer chain controls the gate. Buffer equals available calendar minus critical path.
Five-step schedule model
Map logic before counting days
- Fix the event date and count the actual calendar days available from the proposed planning start.
- Define which venue and guest-list decisions must finish before vendor booking can proceed.
- Estimate vendor-booking duration and the parallel attire procurement/fitting duration separately.
- Add finalization work that cannot complete until both parallel chains clear, plus an explicit reserve.
- Inspect the controlling path and buffer, then preserve duration bases, dependencies, and the exported schedule.
Five scheduling concepts
Why parallel work changes the answer
Dependency
Vendor booking follows venue/guest-list decisions in this model; adding their durations represents a finish-to-start link.
Parallel work
Attire can progress while venue and vendor work proceeds, so its days are compared with the chain rather than added to it.
Controlling gate
Finalization waits for the slower parallel chain, identified by max.
Critical path
The controlling chain plus finalization and reserve determines earliest modeled completion.
Buffer
Positive buffer is calendar flexibility; negative buffer is delay pressure requiring scope, duration, or start-date change.
Symbols and default substitution
Run the compact forward pass
| Symbol | Meaning | Default | Unit |
|---|---|---|---|
| A | Available calendar | 240 | days |
| V | Venue/guest-list duration | 35 | days |
| B | Vendor-booking duration | 70 | days |
| T | Attire duration | 125 | days |
| F | Finalization | 45 | days |
| C | Contingency | 20 | days |
Default substitution: critical path = max(35 + 70, 125) + 45 + 20. Buffer = 240 - critical path. The live ledger shows earliest start and finish at each gate.
Three schedule lenses
Act on the controlling chain
Duration evidence
Use vendor lead times, alteration windows, decision deadlines, and review cycles rather than aspirational guesses.
Fast-tracking risk
Starting dependent work early can shorten time but may create rework if venue, attendance, or requirements change.
Reserve ownership
Keep contingency visible so ordinary work does not silently consume every day before the event.
Two schedule cases
Positive and negative buffer
Attire controls the gate
In the default run, the 125-day attire chain is longer than the 105-day venue-to-vendor chain. Finalization cannot start until attire clears.
Calendar shorter than the path
If available days fall below critical-path duration, buffer is negative and latest safe start remains zero. The model reports delay pressure rather than inventing a past start date.
Terms
Schedule vocabulary
- Activity
- Defined work with a duration and dependency position.
- Dependency
- Logical condition controlling when work may start.
- Parallel path
- Workstream progressing at the same time as another.
- Critical path
- Longest modeled dependency chain to completion.
- Buffer
- Available calendar minus critical-path duration.
- Forward pass
- Calculation of earliest starts and finishes through the network.
Timeline questions
Frequently asked questions
Why are venue and vendor durations added?
The compact model assumes vendor booking begins after venue and guest-list decisions finish, creating a sequential chain.
Why is attire compared with that chain instead of added?
Attire is modeled as a parallel workstream. Finalization waits for whichever parallel chain finishes later.
What does negative buffer mean?
The entered critical path is longer than the available calendar. Scope, durations, logic, or the start date must change.
Why is latest safe start zero when buffer is negative?
A negative value would imply starting before the modeled planning date; the calculator reports zero and exposes delay pressure separately.
Should schedule contingency be a percentage?
This calculator uses explicit days so the reserve is visible. Choose days based on actual uncertainty and vendor evidence.
Can I use business days?
Only if every entered duration and the available calendar use the same business-day basis. The default interpretation is calendar days.
Limits and evidence
This is a compact network, not the full wedding plan
- Invitations, permits, travel, production, tastings, payments, and vendor-specific dependencies are not separate activities here.
- All durations are deterministic whole calendar days.
- Resource conflicts and work calendars are not modeled.
- Contingency is placed at the end rather than distributed across risk-sensitive activities.
Evidence record: retain vendor lead-time statements, contract deadlines, fitting plan, dependency notes, calendar basis, change log, and exported schedule. This is planning support, not a guarantee that vendors or activities will finish on time.
Source and connected planning
Use schedule logic that can be traced
- U.S. GAO Schedule Assessment Guide — critical path, float, duration, and schedule logic.
- CFPB Your Money, Your Goals — planning and record tools for financial commitments.