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.
Sample 1Sample 2See All (4)
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. b) Unless otherwise specified, pages shall be 8.5 x 11 inches, not including foldouts. c) Text pages shall be portrait oriented. Graphics and tables may be landscape oriented if required to properly present the information. d) Pages shall be typed with single line spacing. e) No condensed fonts allowed. Times New Roman, Arial, or similar font preferred. The font size used shall be no less than 10 point except the IMS, WBS, MPS, tables, captions, graphics and Pricing volume submissions may be 8 point font and 0.5” margins. f) Margins on all four edges of each sheet will be at least one inch. g) Proprietary statements, security markings, and page numbers can fall within the defined margin area. h) The following items MUST have page numbers: Volume II Factors 1-3 consecutively from start to finish with the exception of "other required information" in Factor 3 (excluded from page limit). Start with Factor 1 and go through Factor 3 with a single numbering sequence. i) These page format restrictions shall apply to responses to Evaluation Notices (ENs).
Sample 1Sample 2Sample 3
Page Format. ‌ 1. A page is defined as one side of an 8 1/2" x 11", with at least 1-inch margins on all sides, using no smaller than 12-point Calibri font. Any proprietary markings may be placed in the footer. 2. Smaller font sizes (no less than 8 point) are acceptable for graphics. 3. Foldouts count as an equivalent number of 8 1/2" x 11" pages. A foldout should be 8 ½” x 11” in size. 4. All pages shall be numbered sequentially with Arabic numerals (i.e., 1, 2, 3, etc.). The Table of Contents and Glossary are excluded from the page counts and will not be assessed.
Sample 1Sample 2
Page Format. Pages shall be formatted in a standard page style as follows. 1. A page is defined as one side of an 8 1/2" x 11" piece of paper, with at least 1-inch margins on all sides, using no smaller than 12-point (non-compressed) Arial font type for body text, and single spaced between lines. Any proprietary markings may be placed in the footer. 2. Smaller font sizes (no less than 8-point Arial on graphics and no less than 10-point font on headers/footers and tables) are acceptable for headers/footers, graphics, or tables but must be easily readable. 3. Digital foldouts are discouraged, however, if included, they will be counted as an equivalent number of 8-1/2" x 11" pages. For example, each side of an 11” x 17” digital foldout will be counted as two pages. 4. All pages shall be numbered sequentially with Arabic numerals (i.e., 1, 2, 3, etc.). The Table of Contents and Glossary are excluded from the page counts and will not be assessed.
Sample 1
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.
Sample 1
Page Format a) Unless otherwise specified, pages shall be 8.5 x 11 inches, not including foldouts. b) Text pages shall be portrait oriented. Graphics and tables may be landscape oriented if required to properly present the information. c) Pages shall be typed with single line spacing. d) No condensed fonts allowed. Times New Roman, Arial, or similar font preferred. The font size used shall be no less than 10 point except the IMS, WBS, MPS, table s, captions, graphics and Pricing volume submissions may be 8 point font and 0.5” margins. e) Margins on all four edges of each sheet will be at least one inch. f) Proprietary statements, security markings, and page numbers can fall within the defined margin area. g) The following items MUST have page numbers: Volume II Factors 1-3 consecutively from start to finish with the exception of "other required information" in Factor 3 (excluded from page limit). Start with Factor 1 and go through Factor 3 with a single numbering sequence. h) These page format restrictions shall also apply to responses to Evaluation Notices (ENs).
Sample 1
Page Format. Citycode will provide a single column layout with headers and footers containing page numbers and descriptive text, where appropriate.
Sample 1
AutoNDA by SimpleDocs

Related to Page Format

  • Name; Formation The name of the Company shall be ARAMARK Sports and Entertainment Services, LLC or such other name as the Member may from time to time hereafter designate. The Company constitutes a continuation of the existence of the Converted Corporation in the form of a Delaware limited liability company. In accordance with Section 18-214(b) of the Act, the Certificate of Conversion (converting the Converted Corporation to the Company) and the Certificate of Formation of the Company have been duly executed by a Member or other person designated by a Member or by any officer, agent or employee of the registered agent of the Company in the State of Delaware (any such person being an authorized person to take such action) and filed in the Office of the Secretary of State of the State of Delaware. As provided in Section 18-214(d) of the Act, the existence of the Company is deemed to have commenced on February 28, 1966, the date the Converted Corporation was originally organized under the laws of the State of Delaware.

  • 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.

  • State Specific Contract Form Observe the state of the Seller on the Contract, if the Seller lists an address in Alaska, Arkansas, Delaware, North Carolina, Virginia, Maryland, Montana, Connecticut, Vermont, Louisiana or Mississippi, confirm the form number on the Contract is on the List of Approved Contract Forms, for the corresponding state.

  • Escrow Format Specification 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.

  • 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.

  • Project Manual A bound manual prepared by the Design Professional. It includes the Invitation to Bid, Instructions to Bidders, the Bid Form, the Specifications, the General Conditions and Supplementary General Conditions.

  • Notice of Enrollment Notice shall include a list of new employees represented by the Union scheduled to attend the NEO. If practical, the City agrees to provide additional identifying information including, but not limited to, classification and department. Six months from enactment, in the event the City is unable to provide classification and department information in the Notice of Enrollment, the Union can reopen this Agreement for the sole purpose of meeting and conferring over the identifying information provided in this Section II.C.3

  • 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: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!