LearnGrok
Prompts
PromptIntermediateGetting started

Consent form review for service changes

Compare approved service changes with patient materials and prepare a review-ready change list for healthcare managers and governance staff.

5 min read

Nothing here is clinical advice, and nothing here should touch identifiable patient information.

Use this pack when an approved service change may alter what patients are told before booking, at consent, or in supporting information. It is for service managers and governance staff coordinating the work between clinical, privacy and communications reviewers.

Keep the work to process, documents and decisions. Do not paste names, dates of birth, contact details, record numbers, free-text case notes, or any other identifiable patient information. Nothing in this pack decides clinical appropriateness or gives clinical advice.

Key point

Start with the approved record

The patient materials cannot settle what the service change means. Use the approved change record to identify what they must say, then send unresolved points to the right reviewer.

Prepare a clean review pack

Before using a prompt, make a working pack containing only the documents needed for the change. Label each extract with its document name and version or date. If the booking route has several channels, include each one. A web page, reception script, booking confirmation email and SMS reminder can all create different patient expectations.

  1. Remove all identifiable patient information. Use generic examples only, such as a patient or the booking team.
  2. Add the approved change record. It should show what was approved, who approved it, the affected service, scope and planned implementation.
  3. Add the current consent form, patient information sheet and every active booking wording variant.
  4. Add document-control details where you have them: owner, version, review date, approval route and publication location.
  5. Run Source document register if the pack is incomplete or documents use inconsistent names.

The model you are using can organise supplied text, but it cannot establish that a policy, approval or document version is current. For version-dependent platform details, check the xAI documentation overview.

Watch out

Do not fill gaps with plausible wording

If the approved record does not state who is eligible, what information is shared, or how a patient can cancel, record the gap. Do not turn an assumption into patient-facing content.

Produce the document change list

Run Material-by-material change list with the approved record and the three current materials. This gives you the main working output. It assigns each issue to a document, a field or a recognisable wording location.

Read the Evidence status column closely. A change marked supported by approved record is traceable to the source material. A change marked partly supported needs confirmation before wording is finalised. A change marked not evidenced is a question, not an instruction to edit.

Use confirm no change deliberately. It shows that a document was checked rather than overlooked. This matters when a change affects booking but not consent, or changes a contact route without changing the service explanation.

Then run Cross-channel consistency check. It catches an issue the first prompt may not make obvious: each document can be individually reasonable while the set is contradictory. For example, the information sheet may describe a remote appointment while booking text implies an in-person visit. The correct response is not to choose one. Put the discrepancy in the action list and ask the accountable owner to confirm the approved position.

Check

A usable change list is traceable

Every proposed amendment should name the material, the location, the reason, the owner and whether the approved record supports it. If any of these is absent, the item is not ready to action.

Decide whether the pack is ready for review

Run Review readiness decision after you have the change list and consistency matrix. Its decision is about whether reviewers have enough information to do their jobs. It is not an approval to publish a revised form, sheet or booking message.

Use the reviewer sections to route work:

  • Send clinical review questions where patient-facing text describes the service, preparation, limitations, risks, alternatives, follow-up or suitability.
  • Send privacy review questions where wording covers information sharing, contact preferences, data use, third parties or records.
  • Send communications review questions where language, accessibility, translation, reading level, channel choice, links, contact details or booking instructions need confirmation.

If comments return from several reviewers, use Review meeting action log. It keeps a visible distinction between a reviewer comment, the decision on that comment, the person accountable for the action and the evidence needed to close it.

Check the output before you circulate it

The output is wrong, or at least unsafe to rely on, when it claims more than the supplied records show. Look for these signs:

If you see this Treat it as What to do
A new eligibility rule or patient instruction An unsupported inference Ask the service or clinical owner to confirm it against the approved change.
A statement about data sharing with no source A privacy gap Send it to privacy review. Do not draft a definitive statement.
Different service names treated as identical A terminology assumption Ask the document owner whether they refer to the same service.
A missing version described as current A document-control error Obtain the controlled copy or mark the comparison incomplete.
A readiness result that says publish or approve A scope error Reframe it as readiness for review, then use the local approval process.

Also compare short quotations in the output with the original material. A summary can accidentally drop a qualifier such as may, where appropriate, or subject to assessment. Those words can change what a patient understands.

Note

Keep approval separate from review

Clinical, privacy and communications review may all be complete while formal document approval, version control and publication checks are still outstanding.

When the pack does not work

Stop and rebuild the inputs if the approved change record is absent, the service scope is unclear, or you cannot identify which patient materials are live. Ask the change owner for the approved decision and ask the document owner for controlled copies.

If the prompts return broad suggestions instead of a change list, paste less background material and label each document more clearly. If they produce definitive clinical or privacy statements without evidence, remove those statements from the working output and route the underlying question to the appropriate reviewer. Record the unresolved point in the action log rather than trying to solve it in the prompt.

Copy-ready prompts

5 prompts. Open one to read it, or take the whole pack.

1Source document registerUse this first when the change approval and patient materials have arrived from different teams or in different formats.
Create a source document register for a proposed healthcare service change. This is administrative and governance work only. Do not provide clinical advice. Do not include, infer, retain or request identifiable patient information.

Review these documents:
- Approved change record: [paste approved change record]
- Current consent form: [paste current consent form]
- Current patient information sheet: [paste current patient information sheet]
- Current booking wording, including web, telephone script, SMS or email text where applicable: [paste current booking wording]
- Local document-control details, if available: [paste owner, version, approval and review details]

Return one Markdown table with these columns: `Document`, `Purpose`, `Version/date shown`, `Owner shown`, `Applicable service or patient group`, `Key statements relevant to the change`, `Missing or unclear information`.

Then add a section called `Document control gaps` with bullets. Identify only gaps visible in the supplied text, such as no version number, conflicting titles, missing owner, undated wording, or an unclear relationship between documents.

Treat the approved change record as the source of truth only where it is explicitly approved. If approval status, scope, effective date, affected patient group, location, delivery method, eligibility criteria, risks, alternatives, follow-up, costs, data use, or booking route is unclear, write `Not evidenced in supplied material`. Do not guess.
2Material-by-material change listUse this when you need the main operational output: the exact changes each patient-facing document needs.
Compare an approved healthcare service change against three current patient-facing materials. This is administrative and governance work only. Do not provide clinical advice. Do not include, infer, retain or request identifiable patient information.

Approved change record:
[paste approved change record]

Current consent form:
[paste current consent form]

Current patient information sheet:
[paste current patient information sheet]

Current booking wording:
[paste current booking wording]

Produce a document change list in Markdown. Use one table with these columns: `Material`, `Section/field or exact wording location`, `Current position`, `Required change`, `Reason linked to approved change`, `Change type`, `Owner to confirm`, `Priority`, `Evidence status`.

Use only these values for `Change type`: `add`, `amend`, `remove`, `confirm no change`, `cannot assess`.
Use only these values for `Priority`: `before use`, `before publication`, `routine update`, `decision needed`.
Use only these values for `Evidence status`: `supported by approved record`, `partly supported`, `not evidenced`.

Check, where relevant, service name, purpose, who can use the service, what happens, expected appointments or contact, preparation, consent statements, voluntary choice, withdrawal or cancellation route, benefits and limitations described in the approved record, risks or side effects described in the approved record, alternatives or signposting described in the approved record, information sharing, costs or charges, contact details, accessibility, interpreter needs, booking route and effective date.

Quote short current phrases only where needed to identify the location. Do not draft clinical wording, and do not invent explanations, risks, alternatives, legal bases, timeframes or patient entitlements. If the approved record does not support a proposed amendment, mark it `not evidenced` and state the question that the document owner must answer.
3Cross-channel consistency checkUse this after the main change list to find contradictions that may confuse a patient before they book or consent.
Check whether the current consent form, patient information sheet and booking wording give a consistent account of an approved healthcare service change. This is administrative and governance work only. Do not provide clinical advice. Do not include, infer, retain or request identifiable patient information.

Approved change record:
[paste approved change record]

Consent form:
[paste current consent form]

Patient information sheet:
[paste current patient information sheet]

Booking wording:
[paste current booking wording]

Return these sections in Markdown:

## Consistency matrix
Create a table with columns: `Topic`, `Approved position`, `Consent form`, `Patient information sheet`, `Booking wording`, `Status`, `Action needed`.

Assess these topics where they appear in the supplied material: service name; purpose; eligibility; exclusions; location or delivery method; preparation; appointment type; booking route; cancellation; consent; information sharing; patient contact route; accessibility; charges; effective date.

Use only these values for `Status`: `consistent`, `incomplete`, `conflicting`, `not stated`, `cannot assess`.

## Patient confusion risks
List the five highest-priority inconsistencies or omissions. For each, give: `What a patient may understand`, `Why this differs from the approved position`, `Material to change`, `Question for owner`.

## Safe wording boundary
Identify statements that need clinical, privacy, legal or communications confirmation before any patient-facing wording is drafted. Do not write replacement clinical content. Where documents use different terms that might mean the same thing, do not assume they are equivalent. Mark them `terminology decision needed`.
4Review readiness decisionUse this last when you need to decide whether the pack is complete enough to send to clinical, privacy and communications reviewers.
Make a review-readiness decision for patient-facing materials affected by an approved healthcare service change. This is administrative and governance work only. Do not provide clinical advice. Do not include, infer, retain or request identifiable patient information.

Approved change record:
[paste approved change record]

Document change list:
[paste completed change list]

Consistency matrix and patient confusion risks:
[paste completed consistency check]

Document-control details, if available:
[paste document owners, versions, approval route and planned publication date]

Return a Markdown report with exactly these sections:

## Decision
Choose one: `ready for clinical, privacy and communications review`; `ready with named gaps`; `not ready for review`.
Write two to four sentences explaining the decision. This is a readiness decision, not approval to publish or use the materials.

## Review pack checklist
Create a table with columns: `Required item`, `Status`, `Evidence`, `Action before review`. Assess: approved change scope; named document versions; consent-form changes; patient-information changes; booking-wording changes; unresolved clinical statements; unresolved privacy or information-sharing statements; unresolved communications or accessibility issues; document owners; proposed effective date; publication or deployment route.
Use only: `present`, `partial`, `missing`, `not applicable`, `cannot assess`.

## Questions by reviewer
Create three bullet lists titled `Clinical review`, `Privacy review`, and `Communications review`. Put only decisions that require that review function in the relevant list. Each bullet must name the material, the exact decision needed, and why the supplied record does not settle it.

## Release blockers
List only items that prevent safe completion of review or publication. If none are evidenced, write `No blockers evidenced from supplied material`. Do not treat an assumption as evidence.

## Handover note
Write a short note for the service manager stating what to send, who should respond, and what must be recorded after review.
5Review meeting action logUse this when reviewers have returned comments and you need a controlled record of decisions before revised materials are issued.
Convert healthcare service-change review comments into a controlled action log for the consent form, patient information sheet and booking wording. This is administrative and governance work only. Do not provide clinical advice. Do not include, infer, retain or request identifiable patient information.

Approved change record:
[paste approved change record]

Current document change list:
[paste document change list]

Comments from clinical, privacy and communications reviewers:
[paste reviewer comments]

Return one Markdown table with these columns: `Comment ID`, `Reviewer function`, `Material`, `Section/field`, `Decision or question`, `Required action`, `Accountable owner`, `Dependency`, `Status`, `Evidence to record before closure`.

Use only these values for `Status`: `open`, `awaiting decision`, `accepted change`, `rejected with rationale`, `closed`.

After the table, add:

## Decisions requiring formal record
List decisions that alter the approved service scope, patient information, consent process, information-sharing statement, booking eligibility, accessibility route, or publication timing.

## Closure check
State whether the supplied comments support moving to revised-document approval. Choose one: `yes`, `no`, `cannot assess`. Give reasons based only on the comments and records supplied.

Do not resolve conflicting reviewer comments yourself. Record the conflict, name the decision owner needed, and state what evidence is missing.

Last checked against xAI’s own pages on 2026-08-21. Grok changes quickly; anything version-specific should be confirmed upstream before you rely on it.

More in Getting started

Found something out of date?

Grok changes quickly and this page is a snapshot. If something here is wrong, or you know a better resource, send it over.

Suggest a link →

Advertise on LearnGrok

$420.69one-time, for a 30-day run

Square works best. PNG, JPEG or WebP, up to 2 MB.

Stripe on the next step. Live once approved.