A scope that says 'install the network' leaves room for different ideas about completion. For a public-service office, acceptance criteria should explain what the receiving team will review before it takes responsibility for the finished work.
Describe an observable result
Pair each work item with a result that someone can check. An outlet installation might require matching labels, the agreed test record, and an updated location drawing. A service change might need a user task demonstrated with an authorized staff member present. Keep the criteria tied to the actual scope, rather than adding broad promises that no single project can reasonably prove.
Name the reviewer
Identify who can accept each type of work and when that person needs to participate. Explain how exceptions will be recorded, corrected, and reviewed again. A field representative may confirm an installation detail while a service owner decides whether an operational workflow is ready. Clarifying that distinction prevents a signature collected for one purpose from being treated as approval for everything.
Practical takeaway
Write acceptance criteria while the scope is still being shaped. It is easier to price, schedule, and deliver work when the finish line is visible.