Common use of FREQUENCY AND COVERAGE Clause in Contracts

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements Contracts have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (Month; referred to as a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements Contracts have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (Month; referred to as a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return provide the Authority with an MI Report for each Month even where there are no transactions to report in the relevant Month (Month; referred to as a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements Contracts have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return provide the Authority with an MI Report for each Month even where there are no orders (including Orders) or transactions to report in the relevant Month (Month; referred to as a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Panel Period and thereafter, until all transactions relating to Call Off Agreements Legal Services Contracts have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements Contracts have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements Contracts have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 3.4.1. in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 3.4.2. as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority Fund on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority Fund of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority Fund querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Call-Off Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Dynamic Purchasing System Period and thereafter, until all transactions relating to Call Off Agreements Contracts have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 2.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements have permanently ceased. 3.2 2.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 2.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 2.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 2.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 2.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's's MI. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return provide the Authority with an MI Report for each Month even where there are no orders (including Orders) or transactions to report in the relevant Month (Month; referred to as a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements and/or Lease Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's ’s MI Report and not September's’s. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (( a "“Nil Return"”). 3.4 . The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 3.1. All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period Term and thereafter, until all transactions relating to Call Call-Off Agreements Contracts have permanently ceased. 3.2 3.2. The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's ’s MI Report and not September's’s. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 3.3. The Supplier must return the MI Report for each Month even where there are no transactions Transactions to report in the relevant Month (Month; referred to as a "“Nil Return")”. 3.4 3.4. The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 3.4.1. in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 3.4.2. as a result of the Authority querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority CCS on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Call-Off Agreements Contracts have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority CCS of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority CCS querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority CCS on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements Contracts have permanently ceased. 3.2 . The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 . The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 . The Supplier must inform the Authority CCS of any errors or corrections to the Management Information: 3.4.1 : in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 or as a result of the Authority CCS querying any data contained in an MI Report.

FREQUENCY AND COVERAGE. 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority CCS on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements Contracts have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority CCS of any errors or corrections to the Management Information: 3.4.1 3.4.1. in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 3.4.2. as a result of the Authority CCS querying any data contained in an MI Report.