PROPOSED PROJECT
Project Scope Checker
Show consulting and design teams where a client request may fall outside an agreed scope. Compare the statement of work with change requests, meeting notes, and time entries, then assemble the relevant passages, estimated effort, and a draft change request for the project lead.
“Just a few changes” is now a defined piece of work.
SOW-04 → email E17
Project-lead review
SOW-04 / §2 → E17 / line 1
SOW-04 / §3 → E17 / line 2
SOW-04 / §4 → E17 / line 3
The project in practice.
A fictional website engagement includes six pages, one language, and two review rounds in SOW-04. Email E17 requests nine pages, a Spanish version of all nine, and a third round. The proposed additional effort is 12 hours for three pages, 18 for translation/layout, and 4 for the extra review: 34 hours, pending project-lead approval.
WHAT IS USUALLY DONE
A project lead compares a new email with an old proposal and relies on memory to judge what was included. Extra pages, another language, and an additional review round may be discussed as one small change, with effort hidden across team notes.
WHAT SOVRUN CAN DO FOR YOU
Sovrun would build a scope review that places each requested change beside the relevant passage in the designated statement of work. It separates work already included from possible additions and unresolved wording, links supporting notes, and assembles a draft effort estimate and change request. The project lead decides what to discuss with the client.
Keep the request
beside the agreement.
E17 asks for three additional pages, Spanish versions of all nine pages, and one extra review round. The translation estimate therefore covers nine pages, not just the three new ones.
Six pages in one language, with two consolidated review rounds.
Designated baseline for this example. Later approved changes would need to be included before comparing.
Make it nine pages, add Spanish across the site, and include a third review.
Break the request into separate work items before estimating or discussing a change.
- Three additional pages
- 3 × 4 = 12 hours
- Spanish / all nine pages
- 9 × 2 = 18 hours
- One extra review round
- 1 × 4 = 4 hours
Assumptions for discussion. The project lead confirms the work and estimate.
A clearer scope discussion.
An estimate people can inspect.
The proposed tool assembles the relevant evidence and draft work items. Agreement, pricing, billing, and client communication remain with the project team.
Name what changed.
- Pages
- 6 → 9
- Languages
- 1 → 2
- Review rounds
- 2 → 3
Ready for discussion.
- Baseline
- SOW-04
- Request
- Email E17
- Effort
- Lead review pending
- Client agreement
- Not obtained
How we’d make it happen.
Identify the agreed baseline
Load the designated scope and approved variations. Link each new request to its source and date.
Separate included work from additions
Compare outputs, quantities, languages, and review rounds. Keep ambiguous wording open for the project lead rather than forcing a yes/no answer.
Prepare the discussion
Attach reviewed effort assumptions and draft a clear change request. The project lead approves the proposal before anything is sent or billed.
Where AI helps
Document and language models locate candidate scope passages and break requests into concrete work items. Code totals the supplied effort assumptions and retains source versions. The system flags potential differences; it does not interpret a contract conclusively or decide what a client owes.
What people approve
Project leads confirm the governing scope, interpret ambiguities with the appropriate reviewers, validate effort estimates, and approve any client discussion. Draft change requests remain unsent and do not alter the agreed scope or billing records.
What we’d need to start
- The designated statement of work and approved changes
- Client requests, meeting notes, and relevant time records
- Effort assumptions, review owners, and change-request format
How we’d test it
Test requests already included, partly included, ambiguous, or covered by a later approved change. Check source passages and version precedence with the project lead. Recompute estimates and confirm that suggestions cannot silently change fees, scope, or client messages.
Prepared for Professional services. We would agree on the work after reviewing your brief, materials, and requirements.
This is a proposed project, not completed client work. The visuals and numbers show example outputs, not measured results.
