Obscyra Digital · Reference Desk
Frequently asked questions
These are the questions readers ask most often about scope, applicability, exceptions, and how to request a clarification or a correction. Each answer points to the document that carries the full detail.
Scope
Named who and what a document covers
Exceptions
Condition, approver, expiry date
Corrections
Logged against the document named
Reading the scope field
Questions about scope and applicability
Check the scope field before you check anything else. It is the one sentence a document uses to say who it binds and which work it covers.
Where the answer lives
Every document opens with a scope statement naming the roles it applies to, the activities it covers, and the systems it reaches.
If your case is not named
Follow the linked document the scope points to rather than reading the silence as permission. A gap in one scope usually means the rule sits next door, in the companion document that governs that case.
Two documents, two scopes
When two policies overlap on the same task, the narrower scope controls the detail and the broader scope controls the principle. Read both before you decide which one you are answering to.
Contractors and vendors
Where a document names outside contributors, the scope field says so explicitly and points to the clause that carries the obligation. Assume nothing from the title alone.
Open the Documentation Library to read the scope statement of the policy you are asking about.
Questions about exceptions
What an exception carries
Condition
The circumstance the deviation is limited to
Approver
The role accountable for granting it
Expiry
The date the deviation stops applying
Record
Where the decision is written down
If a deviation is not recorded with those four parts, it is read as an error rather than an exception.
Readers often ask whether they can deviate from a rule. Yes — through the documented route, and only while the recorded conditions hold.
An exception is not a verbal agreement or a preference someone carried over from a prior team. It is a written record with a named approver and an end date, so a later reader can see why the deviation existed and whether it still does.
The point of the expiry date is that exceptions do not quietly become the new rule. When the date passes, the original policy governs again and a fresh request is needed to extend the deviation.
The Governance and Review Process page explains how exceptions are recorded, who reviews them, and what happens when an exception is allowed to lapse without renewal.
Governance and Review ProcessQuestions about versions and currency
The most common question we receive is whether a reader is looking at the current text. Two fields answer it, and checking them takes a moment.
[ok]
Version number
Every published document shows a version number at the head of the page. If the document you are reading has no version number, you are looking at a working note, not at policy.
[warn]
Review date
A review date shows when the text was last examined, which is not the same as when it changed. An unexpired review date means the wording still reflects the owner's intent.
[fail]
Later version exists
A change log entry above your version means the text you are holding has been replaced. Work from the newer text, and treat the older one as background reading only.
[ok]▌
Change log
The change log lists later versions of the same document in order. Reading the newest entry first tells you whether anything you rely on was rewritten.
Cited rule
“Where a revision changes an obligation, the change log entry names the obligation and the date the new text took effect.”
Versioning and Change Log carries the current entries and the date each revision took effect.
Versioning and Change LogQuestions about corrections and clarifications
If a sentence is ambiguous or a link is wrong, we want to know. A report names the document and the section, and it is logged against that document.
Correction requests are the most reliable signal that the published text and real practice have diverged, which is why a well-aimed report can start a revision rather than sit in a queue.
What a useful report includes
- The document title and version number, so the report lands against the right text.
- The section heading or the sentence itself, quoted closely enough to find it again.
- What looks wrong — a broken link, a clause that contradicts another document, or wording that could be read two ways.
- The reading you expected, when the meaning depends on context we may not have seen.
Reports are reviewed by the owner of the document you name. If a revision follows, the change appears in the change log with the date it took effect.
Contact the documentation teamWhat we do not publish on these pages
This library documents policy and process. It does not carry marketing content, pricing, testimonials, ratings, or outcome promises.
We do not publish before-and-after material. If a claim is not traceable to a written policy or standard, it does not appear here.
The same rule applies to reader questions: an answer on this page states what a document says, or it points you to the document that does.
Two questions we answer every week
How do I report an error in a policy?
Use the Contact page and name the document, the section, and what looks wrong. Reports are logged against the document and reviewed by the owner, who decides whether the text needs a correction, a clarification, or no change at all.
Can I get an exception to a rule?
Exceptions are handled through the documented process, with a condition, an approver, and an expiry date. The Governance and Review Process page sets out the steps and the record that has to exist before the deviation takes effect.
Does a policy apply to an outside contractor?
It depends on the scope field, and the scope field says so in plain words when outside contributors are covered. Where they are, the document points to the clause that carries the obligation and to the role that enforces it.
Which document do I cite when two rules conflict?
Cite the narrower document — the one whose scope names your specific activity — and note the broader policy it sits under. If the two genuinely disagree, that is a correction worth reporting so the owners can settle it in writing.
How often are documents reviewed?
Each document carries its own review date, set by the owner rather than by a single library-wide schedule. The date is visible at the head of the document, and it is the field to check before you rely on wording for a decision.
Still have a question
If your question is not answered on this page, use the Contact page and name the document you were reading. A specific question gets a specific answer faster than a general one, and it helps us see which documents need clearer wording.
Documentation team
Phone
+1-202-478-1904
Office hours
Monday to Friday, 9:00 AM – 6:00 PM Eastern Time
Address
1201 Market Street, Suite 1400, Philadelphia, PA 19107, United States