Civi helps prepare service drafts through proposals. You describe the change, inspect the result, and decide what becomes part of the draft.
Describe the outcome you need (link to section)
Open Civi from the service builder and explain the task in the terms you would use with a colleague.
For example:
Add a question asking whether the Lakeview event uses amplified sound, then route requests that answer yes to a staff review task.
Include the condition, the work to assign, and the intended outcome. Smaller requests are easier to review than a request to redesign the whole service at once.
Review the proposed changes (link to section)
Civi can inspect the current service and rehearse supported edits against a copy of the draft. Proposed edits may appear as a temporary preview while it works.
Read the summary and inspect the differences. Check the questions, conditions, assignments, and connections the proposal affects.
If a proposed change does not apply, use the stated reason to understand what needs to change. Do not assume that a description of a change means it has been saved.
Accept or reject (link to section)
Accept the proposal when it matches the change you want. Where individual changes are offered, select the operations you want to keep. A selection must still form a valid set of edits.
Rejecting a proposal leaves the saved draft unchanged. Only an explicit acceptance writes the proposed changes to the draft.
Keep staff decisions with staff (link to section)
Civi’s proposal workflow does not publish services, grant permissions, or make final case decisions. Those remain authorized staff actions.
After accepting a change, preview the service and follow the normal review and publication process.