‘Eight weeks’ is not a date. A usable commitment needs a defined duration, a complete prerequisite set, a recorded last-satisfied event, a calendar and an output milestone.
The deposit was paid on Monday, drawings were approved on Friday, the finish sample changed two weeks later and hardware remained open for one door type. Each party selects a different day as 'week one'. The dispute was designed into the schedule because the quotation carried a duration but no start rule. The remedy is not a universal trigger such as payment or drawing approval. It is a controlled prerequisite matrix by released scope, a last-prerequisite record and a programme that shows what can start, what remains held and what the stated duration actually reaches.
1. Define the promise before choosing its start
Write the output milestone: design issue, material readiness, factory completion, pre-shipment release, carrier handover, arrival or site delivery. These are different events. State whether the duration uses calendar days, working days or weeks; identify calendars, holidays, shutdowns, cut-off time and time zone; and say how partial lots are treated.
Separate planning ranges from commitments. A quotation-stage estimate based on assumed configuration and load is not the same as an accepted baseline for released line items. Preserve the assumptions and validity date so a later start cannot be attached to a stale duration without review.
Incoterms may identify delivery and risk events for a shipment when incorporated, but they do not define factory production lead-time prerequisites. Payment, title, acceptance and delivery should remain separate unless the parties' authorised documents deliberately connect them.
| Element | Controlled answer | Ambiguity prevented |
|---|---|---|
| Scope | Line IDs, quantities and configuration revision | A project-wide date applied to unreleased items |
| Start event | Last required prerequisite and evidence timestamp | Competing deposit/drawing/material dates |
| Duration | Number plus unit and calendar | Calendar weeks confused with working weeks |
| Output | Factory complete / released / carrier handover / named delivery event | Production date mistaken for site arrival |
| Assumptions | Capacity, sequence, material route and buyer inputs | Estimate retained after its basis changes |
| Status | Estimate / proposed / accepted baseline / current forecast | Forecast treated as contractual commitment |
2. Build a finite prerequisite matrix by release package
List only prerequisites that genuinely control the stated work: executed commercial authority where required; agreed payment evidence where required; released opening schedule; approved drawings; glass, finish and hardware decisions; performance/evidence requirements; delivery and packing inputs; and buyer-supplied information. For every item define scope, responsible provider, objective evidence, reviewer and status.
Avoid the phrase 'all information received'. It gives no finite test and can move after the event. Conversely, do not declare a prerequisite satisfied merely because a file arrived. Received, reviewed, approved for stated purpose and released for production are distinct states.
Use configuration-level release where technically and commercially authorised. A complete set for standard windows may allow that package to proceed while a bespoke entrance remains held. Check shared dependencies first: one finish batch, common extrusion order, system test, consolidated shipment or minimum material lot may prevent apparent independence.
| Prerequisite | Objective evidence | Scope/state |
|---|---|---|
| Commercial authority | Executed order/contract or authorised release record | Applicable lines; open / satisfied |
| Payment event if applicable | Bank-confirmed receipt or contractually defined evidence | Do not infer technical approval |
| Configuration | Released drawings and opening schedule at named revisions | Line/type-specific |
| Selections | Approved glass, finish, hardware and accessory records | Decision plus sample/reference identity |
| Evidence requirements | Approved test/submittal/inspection plan | Required before procurement/production where applicable |
| Logistics inputs | Named delivery point, package constraints and shipment sequence | Confirmed / assumption / hold |
3. Timestamp the last prerequisite and control every reset
For each release package, the start record should show when every required item reached its defined satisfied state. The latest valid timestamp is the candidate start event, subject to the signed terms and authorised confirmation. Preserve time zone, evidence links, reviewer and programme revision.
A later change does not simply erase the original start. Log the changed requirement, affected lines, date, current work status and programme assessment. Decide through the authorised route whether unaffected work continues, affected work is held or a revised baseline is approved. Keep original baseline, current forecast and any approved adjustment separate.
ISO 10005 covers establishing, reviewing, accepting, applying and revising quality plans for outputs including projects and contracts. Use its control logic to assign responsibilities and documented information around release. The standard gives guidance rather than a legal start-date rule.
| Field | Entry | Audit test |
|---|---|---|
| Release package | Line/type/lot IDs and quantity | Is scope finite and internally consistent? |
| Prerequisite snapshot | Required items and satisfied evidence | Was any open item silently assumed? |
| Last event | Item, timestamp, time zone and evidence ID | Is this actually the latest valid prerequisite? |
| Calendar/output | Applied calendar, duration and target event | Can another reviewer reproduce the date? |
| Authority | Prepared, reviewed and authorised statuses | Does the issuer have programme authority? |
| Qualifications | Open shared dependency or approved condition | Is the apparent release still constrained? |
4. Update from actual evidence without moving the goalposts
Maintain three dates: accepted baseline, current evidence-based forecast and actual event. Status updates should cite completed activities, remaining logic, constraints and a data date. A forecast shift is not itself proof of contractual delay, and preserving the baseline is essential for honest comparison.
Use an exception report for missing approvals, late or changed inputs, material confirmation, constrained production routes, inspection holds, package redesign and carrier bookings. Assign owner, effect under assessment, action and next update. Avoid retrospective labels that attribute every variance to the last prerequisite.
At handover between sales, engineering and production, reconcile the quoted assumptions, signed scope, release package, prerequisite record and current programme. The useful answer is not 'the clock has started'; it is 'these lines started against this controlled basis, these lines remain held, and this is the evidence-backed milestone forecast.'
FAQ
Does lead time always start when the deposit is paid?
No universal rule exists. Payment may be one prerequisite if the signed terms say so, but technical and logistics releases may also control. Define the complete finite set.
Does drawing approval start all items?
Not if other stated prerequisites or shared dependencies remain open. Release and timestamp by actual package.
Can one product type start before another?
Potentially, if authorised and technically independent. Check shared materials, finishes, tests, capacity, packing and shipment first.
What does eight weeks lead time deliver?
Nothing precise until the output event and calendar are named. Factory completion, shipment and site delivery are different milestones.
Does a design change restart the entire clock?
Not automatically. Preserve the baseline and assess affected scope, status, logic and authorisation instead of applying a blanket reset.
Is a supplier start certificate legally binding?
This guide's record is an evidence/control tool only. Its contractual effect depends on the signed documents, authority and governing law.
Continue the project review
Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.
Official sources used
ISO 10005:2018 — Quality management: guidelines for quality plans ↗ISO 10013:2021 — Guidance for documented information ↗ICC — Incoterms rules: purpose and scope ↗UNCITRAL — CISG official text and explanatory material ↗Related buyer guides
This article is general procurement and programme education, not legal, scheduling, accounting, banking or contract advice. It does not prescribe a deposit, approval mechanism, deemed approval, notice period, production duration, completion date, extension, damages or remedy; interpret delay; or state any Cavorlen lead time, capacity, stock, policy or delivery commitment. The signed contract, approved programme, applicable law and authorised project, commercial and legal professionals govern the transaction.