“Can you make one small website change?” is not a scope. It is the start of a conversation that can consume an afternoon if the request arrives without a page URL, desired outcome, assets, deadline, or approval path.
A website change-request form should reduce that back-and-forth. AI can help turn the submission into a consistent review brief and flag what is missing. It should not approve the work, set the price, promise a delivery date, or decide what the contract includes.
Ask for evidence before work enters the queue
The best scope-review workflow starts with a better intake form. Ask for information a WebMaster can verify:
- the exact page or screen involved;
- what happens now and what should happen instead;
- who needs the change and why;
- the real deadline and what depends on it;
- copy, images, files, or examples already available;
- the person who can approve the result; and
- how the requester will know the change is complete.
If access is required, ask for the environment, account owner, and permission level—not a password pasted into the form. WordPress’s guide to roles and capabilities is a useful reference when a client needs the right account rather than shared administrator credentials.
Separate missing information from the scope decision
These are different jobs. A request can be complete and still be outside the maintenance agreement. It can also fit the agreement but lack the assets needed to schedule it.
Use the Missing Information Review to identify gaps in the submitted details. Then send the brief to a person who understands the client agreement, current workload, risk, and dependencies. That person makes the scope call.
AI can prepare the scope conversation. It cannot know which promises your team has made unless those rules are explicit and current.
Use a three-pass review
A useful change-request workflow can stay simple:
- Completeness pass: Flag missing URLs, files, acceptance criteria, approvers, or timing details.
- Impact pass: Summarize the affected page, likely teams, dependencies, and stated business reason without inventing technical work.
- Next-action pass: Recommend one of three staff actions: ask a focused question, move to scope review, or route to the right specialist.
The Entry Summary action can condense a long request. Suggested Reply and Next Best Action can draft a focused follow-up. Keep a human approval step before anything is sent to the client.
Make the brief easy to scan
The reviewer should not have to reread the whole submission to find the decision. A compact brief can use the same fields every time:
- Requested outcome: one sentence in the requester’s language;
- Affected surface: page, form, campaign, integration, or account;
- Evidence supplied: URLs, screenshots, copy, files, and examples;
- Missing items: only the gaps that block a responsible next step;
- Risks and dependencies: what needs specialist review;
- Staff decision: needs details, ready for scope review, approved for scheduling, or outside the current agreement; and
- Next owner: the person responsible for moving it forward.
Those status names are an operating policy, not a promise that every form builder has the same native status controls. Store the canonical AI result in the review surface supported by your Form Source, then let staff record the actual decision.
Keep the workflow safe across supported forms
Gravity Forms has the fullest native workflow path in the current Sentient Forms release. Contact Form 7, WPForms, and Elementor Pro Forms run after-submission actions through the Sentient Forms Submission Ledger. Do not imply that every builder can block validation, write native notes, suppress notifications, or expose the same entry links.
The public WordPress.org listing is the safest place to confirm the current support boundary before you document a client process.
Pilot it without changing the contract
Run the workflow on one existing change-request form and a sample of recent requests. Compare the generated briefs with the decisions your team actually made. Look for three outcomes: fewer repeated questions, faster assignment, and clearer reasons when a request needs separate scoping.
Do not rewrite the maintenance agreement around a synthetic score. Treat the first pass as an intake-quality test. The launch checklist in Test AI form automation before a client sees it can help you stage the review and collect signoff.
Give the next request a cleaner start
Pick the request type that creates the most back-and-forth. Tighten its intake fields, add a missing-information review, and require staff approval before the client receives a follow-up. Browse the Sentient Forms action library for the smallest set of actions that can support that handoff.
Frequently asked questions
No. AI can flag missing details, summarize the request, and prepare a review brief. A person who understands the client agreement, workload, risk, and dependencies should decide scope, price, schedule, and approval.
A Suggested Reply action can prepare a focused draft, but this workflow keeps a staff approval step before anything is sent. Do not assume identical notification or webhook controls across form builders.
Do not ask clients to paste passwords, API keys, payment data, or other secrets into a general request form. Ask for the account owner, environment, and required access level, then use a separate approved credential-sharing process when access is necessary.
