Skip to content
CREEP//LOCK

Tool

Project Scope Readiness Check

Use this before work begins. It checks whether the operational boundaries of an agreed-in-principle project are clear enough to confirm—not whether a contract is legally sufficient. Choose only Clear, Unclear, or Not applicable; your answers stay in this browser and are not transmitted.

Principle

Four boundaries are critical: what you will deliver, how its extent or completion is defined, the commercial boundary, and what happens when a later request changes the baseline. Supporting details cannot compensate for one of those being missing.

1. Are the deliverables named specifically? Critical

For example: five page designs, not simply “website work.”

2. Is the extent or completion point clear? Critical

Use quantity, format, acceptance point, or another observable limit.

3. Is the commercial boundary recorded? Critical

The fee, included hours, rate, or another agreed limit.

4. Is there a rule for additional requests? Critical

Changes are assessed and any price or timing impact is approved before work starts.

5. Are likely exclusions stated?

Name adjacent work the client could reasonably assume is included.

6. If revisions apply, is their boundary clear?

A number of rounds or a clear definition of included refinement.

7. If client inputs are required, are they clear?

Content, access, feedback, decisions, and when each is needed.

8. If the work relies on assumptions, are they recorded?

Conditions that would change effort, price, or delivery if they prove false.

Turn the result into one pre-kickoff confirmation

Resolve the gaps, then summarize the agreed baseline in a short client message. This check doesn't create anything in CREEPLOCK on its own; after confirmation, the product can keep the deliverables, revision limit, exclusions, assumptions, hours, value, and rate available for later scope decisions.