Know what the office
can carry.
An agreed source list. Separate client matters. A record the next person can use. This is a representative installation, not a customer result.
Start with the question
and its sources.
We name the three matters, five authorised people, up to twelve digital assets and twelve official source pages. The written scope records access, check dates, attachments, reviewer and delivery channel.
The installed desk can work with selected files, exact public HTML or text pages and authorised read-only mail headers. Linked PDFs and recordings need their own agreed handling. A page check does not automatically read everything it links to.
What goes in the source register?
The exact page address, included attachments, capture method, check schedule, responsible reviewer and action when a check fails. Access and any system changes require written approval.
See the change.
Keep the judgment.
A selected page is captured while the local desk is running. Its earlier version stays beside it. The operator checks what changed against the client question, retains unresolved points and reviews the resulting brief.
| Source | Selected Council agenda and its retained version. |
|---|---|
| Review | Item changed. Linked decision still needs checking. |
| Action | Named reviewer to check the minutes before the client update. |
Local drafts need review. Mail access covers headers, not message bodies. The desk records a failed or missed check instead of treating it as confirmation that nothing changed.
Leave an office
someone can continue.
The asset register names ownership, administration and recovery responsibility. Up to three approved configuration corrections address the agreed gaps. Passwords and recovery codes do not belong in this register.
One approved export or recovery exercise checks the handover route. You receive the operating instructions, matter exports, reviewed briefs and any unresolved access or recovery question. The exercise records what was tested.
Is an installation needed?
A suitable existing workflow can support an operated month. Local installation is a separate decision. Hardware, large migrations and additional integrations need their own scope.
Stages and dates are recorded on the individual invoice before payment. This walkthrough shows the documented workflow; it does not establish a completed client installation.