Page Format Sample Clauses

Page Format. To meet the page limits requirement listed above, all text shall be in an Arial font that is a minimum of 11 points in size, single-spaced, and printed single-sided (except financial statements may be printed double-sided, and 10 point Arial font is acceptable for graphics, organization charts, tables and footnotes). Each page shall be numbered consecutively within each volume (i.e., Volume I, Page I of 2…; Volume II, Page 2 of 2… etc.), and the page numbers shall be centered at the bottom of each page. Margins shall be not less than one inch at the top, bottom, and sides of all pages, except for headers and footers.
AutoNDA by SimpleDocs
Page Format a) Unless otherwise specified, all pages shall be printed double-sided on recycled paper as much as practical. For example, original letters are exempted from the double-sided requirement.
Page Format. ‌ Pages shall be formatted in a standard page style as follows.
Page Format. The proposal text shall be printed single-sided. Type size for text shall not be smaller than Microsoft Word Times New Roman 12 point font, single column, normal proportional spacing and one inch (1”) left and right margins. The font size requirements do not apply to charts, e.g. Organizational Charts; however, these charts shall be no smaller than Microsoft Word, Times New Roman or Arial Narrow, 8 point font, and used only when absolutely necessary. Text lines will be single-spaced. The background color of each page of the proposal submission shall be white or ivory stock only. Information submitted shall not exceed the page limits stated in L- 5.3.3 below for each Volume.
Page Format. Citycode will provide a single column layout with headers and footers containing page numbers and descriptive text, where appropriate.
Page Format a) Unless otherwise specified, pages shall be 8.5 x 11 inches, not including foldouts.

Related to Page Format

  • Coverage Form Coverage shall be at least as broad as the unmodified Insurance Services Office (ISO) Commercial General Liability (CGL) “Occurrence” form CG 00 01 04/13 or substitute form providing equivalent coverage and shall cover liability arising from premises, operations, independent contractors, products-completed operations, personal and advertising injury, and liability assumed under an insured contract (including the tort liability of another assumed in a business contract).

  • VERSION Each Quote will be governed under the version of this Agreement that is in place as of the “last updated” date indicated at the bottom of this document. For that reason, you should keep a copy of this document and make a note of the date indicated below when you accept a Quote.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Alternate Schedules Employees working alternate schedules who are normally scheduled to work more than eight (8) hours on a day observed as a holiday may use vacation leave, compensatory time or leave without pay to make up the difference between the employee’s normally scheduled shift and the eight (8) hours of holiday pay.

  • Contract Formation Subject to FAR Sections 1.601(a) and 43.102, the Government Order must be signed by a duly warranted contracting officer, in writing. The same requirement applies to contract modifications affecting the rights of the parties. All terms and conditions intended to bind the Government must be included within the contract signed by the Government.

  • Notice of Enrollment Said meeting and conferring shall not be subject to the impasse procedures in Government Code Section 3557. The Department sponsoring the NEO shall provide the foregoing information no less than five (5) business days prior to the NEO taking place. The Department will make best efforts to notify the Union NEO Coordinator of any last-minute changes. Onboarding of individual employees for administrative purposes is excluded from this notice requirement.

  • Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:

  • Transfer Format Transfers may include, but are not limited to, conversion of all Data into or from an industry standard format or providing application programmable interface. ENCRYPTION Data must be encrypted at all times unless specifically outlined otherwise in the Authorized User Agreement. At a minimum, encryption must be carried out at the most current NYS Encryption Standard (NYS-S14-007), (or successor policy with key access restricted to the Authorized User only, unless with the express written permission of the Authorized User. All Data in transit must be handled in accordance with ITS Policy NYS-S14-007 (or successor) or the National Institute of Standards and Technology (NIST) Federal Institute Processing Standard (FIPS)-140-2 or Transport Layer Security (TLS) 1, or TLS2 (or successor). The Authorized User Agreement shall specify the respective responsibilities of the Authorized User and the Contractor for the encryption of Data.

  • Codebook Format The codebook describes an ASCII data set (although the data are also being provided in a SAS transport file). The following codebook items are provided for each variable: Identifier Description Name Variable name (maximum of 8 characters) Description Variable descriptor (maximum 40 characters) Format Number of bytes Type Type of data: numeric (indicated by NUM) or character (indicated by XXXX) Start Beginning column position of variable in record End Ending column position of variable in record

Time is Money Join Law Insider Premium to draft better contracts faster.