A number is not enough when the document defines its counting rule elsewhere
The two-day phrase is incomplete without the calendar rule and the event that starts the count. A reviewer needs to know whether a request received outside working hours starts immediately or at the next working period. The document may answer that question in a separate definition, or it may leave a real decision unresolved. The project record should not fill the gap by using the server's calendar. One option is to reference a named calendar revision; another is to capture the exact rule that governed the agreement. Either approach should let the team reproduce a deadline calculation later. The boundary sample should include a request near a holiday and a request with an uncertain receipt time. That exposes both counting behavior and the limit of what the available evidence can establish.
Working through the example
A service agreement promises a response within two days. Its definitions section specifies business days and excludes a regional holiday calendar. Attach the definitions excerpt to the response candidate. Represent the duration, calendar, starting event, and any unresolved timezone explicitly.
A discriminating check
Test an incoming request immediately before a weekend and a listed holiday. A calendar reference can itself change; the approved requirement should identify the relevant revision or governing rule. The project’s requirement-demarcation and traceability notes support retaining contextual evidence. Their application here is a proposed review workflow; it is not a demonstrated extraction guarantee.