- Published
- 8 October 2026
- Last reviewed
- 8 October 2026
How to use these FAQs
Choose one working location, manage access and resolve conflicting document versions with a clear decision record.
Select a question to expand its answer. The first answer is open initially; each answer can be opened or closed independently. These are original RDE practical explanations. Any example described as fictional is a teaching scenario.
Common questions
How do we avoid several competing final files?
Agree the working location, owner and current version before review starts. Share a link where appropriate instead of repeatedly circulating new attachments. Record which version was approved and how later changes are handled. A file name containing “final” does not establish approval if another copy is still being edited in a different location.
Who should be allowed to edit?
Give editing access to people who need it for the task, following organisational rules. Others may only need viewing or commenting access. Review external sharing and access when responsibilities change. Do not assume that a familiar collaborator should retain access to every document indefinitely, or that a broad public link is the simplest safe review method.
What can version history help with?
Where supported and enabled, it can help inspect earlier versions and recover an appropriate previous state. Microsoft provides version-history features for SharePoint and OneDrive, subject to configuration and permissions. Check the actual service before relying on it. Keep a clear approval record too; version history alone does not explain why a change was accepted.
What if two people edit conflicting copies?
Compare the changes and identify the intended outcome before merging. Ask the appropriate owner to resolve conflicting decisions. Keep useful material from both copies where it is relevant, and record which version becomes the working one. Do not automatically choose the most recently saved file if it omits an earlier approved correction.
Can comments replace a decision log?
Comments can capture discussion, but a reader may struggle to identify the agreed outcome among unresolved suggestions. Summarise important decisions, owners and follow-up actions in the agreed record. Link to the relevant discussion when useful. Closing a comment is not necessarily formal approval, so make the local meaning clear to reviewers.
What should I do before restoring an earlier version?
Check what will change, who is currently working on the file and whether restoration requires approval. Preserve relevant current information through the approved process. After restoring, confirm the result and tell affected collaborators. Practise with a disposable file when learning the feature, rather than discovering its behaviour on the only working copy of a live document.
Put one answer into practice
Choose the question closest to your current task. Write one action in your own notes, identify the information or permission you need and set a review point. Use the related resources below to develop the task further. No response is submitted or stored by this page.
Sources and scope
The sources below provide relevant context and terminology. The examples, practical suggestions and wording are original RDE teaching material. Apply your organisation’s policies and the guidance relevant to your situation. Reviewed 8 October 2026. Author: Jefferson Otonbara Imgbi.
Cover image: AI-generated illustrative scene created specifically for this resource.