Volume 19, Chapter 1
Managing Special Orders and Large Contracts
Definition
A large wedding-party contract at MANIAC MINDZ was scheduled exactly like any standard order: fit into the day's normal workflow, no separate plan of its own. Each individual sub-task got done competently. But with no single timeline connecting them, several small delays quietly piled up, unnoticed, until the overall deadline was suddenly, dangerously close.
is work significant enough, in value, complexity, or how much rides on it, that it needs its own dedicated plan, rather than simply flowing through the ordinary daily workflow alongside everything else.
Why did competent work on every individual task still add up to a near-miss? Because a normal daily schedule only tracks each task on its own, it was never built to notice that five small, separate delays add up to one large deadline problem. A project needs one single timeline watching the whole thing, not just each piece.
Volume 18, Chapter 3 already flagged this: an ordinary day's schedule works for ordinary orders, but a wedding order, a large uniform contract, or any unusually big or complex job needs its own timeline and milestones, treated as a small project, not squeezed into the daily rhythm and hoped for the best.
When Does Something Become a "Project"?
Unusually large value
A single failure point risks a disproportionate loss.
Multiple stages or people involved
More coordination points means more that can silently go wrong.
Customization or unique requirements
Can't be handled by the standard process alone.
A significant deposit or advance payment received
Recall Volume 07, Chapter 1's warning: a deposit is still capital, not yet profit, and now carries a specific obligation to deliver.
If losing track of this one order would genuinely hurt the business, it's a project, not just a bigger version of a normal order.
What Changes Once Something Is Treated as a Project
| Ordinary Order | Special Order / Project |
|---|---|
| Fits into the day's normal schedule | Gets its own timeline (Chapter 2) |
| Standard approval, if any | May need Volume 11's approval ladder before commitment, given the value at stake |
| Tracked like any other order | Tracked with named milestones and checkpoints |
Example Story: The Large Order Handled Like Any Other
Here's the full version of the wedding-contract story from the start of this chapter.
A large wedding-party contract at MANIAC MINDZ was initially scheduled exactly like any standard order: fit into the day's normal workflow, with no separate plan. Individual sub-tasks were each completed competently, but with no single timeline connecting them, several small delays piled up unnoticed until the overall deadline was suddenly, dangerously close.
Nothing had gone wrong task by task. The connecting plan simply hadn't existed. Recognizing it explicitly as a project, with its own dedicated timeline from day one, was the only change needed to prevent the same pile-up of small delays on every large order afterward.
Across Industries
What triggers "project" treatment looks different in every trade, but it's always the same underlying signal: this one is big enough to fail quietly if nobody's watching the whole thing.
| Business | What Triggers "Project" Treatment |
|---|---|
| Golden Crust Bakery | A large catering order for an event with a fixed, unmovable date |
| Rapid Auto Works | A multi-vehicle fleet contract |
| Precision Print & Press | A large-run corporate order with custom branding requirements |
Common Mistakes
This is the exact failure in the example story: competent individual work, but no connecting plan.
Without a clear signal (Section 2), the decision to plan separately becomes inconsistent and easy to skip under pressure.
Directly contradicts Volume 07, Chapter 1, the obligation to deliver is still outstanding.
Quiz Yourself
Practice Exercise
List your criteria for what makes an order a "special order" in your business. Review your current largest active order against those criteria, is it being tracked as a project, or just as a bigger normal order?
Quick Summary
Quick Summary
- A special order or large contract needs its own plan once its value, complexity, or stakes exceed the ordinary daily workflow.
- Set a clear, written rule for what triggers project treatment. Don't decide it fresh, under pressure, each time.
- A deposit is still capital, not profit. The obligation to deliver remains fully outstanding.