Read the sync-mode rules
Open the related page.
Resources
What counts as one request
One request is one clear outcome. If the work hides multiple goals, multiple templates, or a broader redesign, WPFlow splits it before build starts.
Short explanation
A request counts as one request when it points at one clear outcome that can be scoped, approved, and reviewed safely.
- A homepage hero refresh can be one request if it is one scoped outcome.
- A homepage refresh, pricing rewrite, and navigation restructure may become multiple scoped items.
- Splitting work is not bureaucracy. It is how the commercial truth stays clear.
Example
A simple example or comparison usually makes the rule easier to understand.
| Likely one request | Usually needs splitting |
|---|---|
| Update one hero section and CTA hierarchy | Redesign the homepage, pricing page, and footer in one approval |
| Fix one mobile breakpoint issue across one template | Overhaul multiple templates and the checkout path together |
| Refine one landing page section for conversion clarity | Bundle several unrelated marketing jobs into one vague brief |
Related links
Useful next reading if you want the full delivery context.
Next step
Want to see how this applies to your site?
Use the signup flow and describe the kind of changes you need.