The general principle for electronic approval is:

Consider these example cases and notes.

Attachments to Email: Microsoft Office or PDF Documents

• A document or form in Word, Excel, or PDF formats can include an indication of employee approval (

  Status
  subtle true colour Green title 2: I Approve

  ) but must be sent from a Reliant account to indicate identity (

  Status
  subtle true colour Blue title 1: Verified ID

  )
• Typing a full name or fund number inside a Word, Excel, or PDF document does not provide sufficient indication of identity.
• The internal process to record the submission should include the attached document and some record of the received email to verify identity.

Google Documents from Reliant Verified Account

A Google Document, Spreadsheet, or Form submitted from a verified @reliant.org Google Account verifies identity (

A comment or interaction in the form or document can verify both identity and indicate approval. See also Supervisor Approval for Google Forms.

Comments, Interactions, or Forms using any Reliant Verified Account

• A comment on a Google spreadsheet or document can verify both identity

  Status
  subtle true colour Blue title 1: Verified ID

   and indicate approval 

  Status
  subtle true colour Green title 2: I Approve

  .  See also Supervisor Approval for Google Forms.

• An electronic record submitted via a Reliant website like Staffnet or Toolbox or Reliant.org  This can be both 

  Status
  subtle true colour Blue title 1: Verified ID

   and indicate approval 

  Status
  subtle true colour Green title 2: I Approve

  • In 2015 right now, the example would be submitting an MTD Support Goal.
  • Future example: a checkbox on StaffnetToolbox
  • Lots of things are available in theory here but have to be programmed.
• For office users, a comment submitted via Solomon can indicate both 

  Status
  subtle true colour Blue title 1: Verified ID

   and indicate approval 

  Status
  subtle true colour Green title 2: I Approve

• Interactions are usually submitted to a data source - so it is stored in CRM, in a Google spreadsheet. It could even be converted to a simple email.

Date and Time

Accepted documents or records should include the date they were submitted (and date approved and date received, if different).

• Date submitted is usually also understood as the date the employee approved the document. For old paper records, these can be thought of as the a) date on the signature line, the b) date postmarked and the c) date received in the mail. For electronic records, these dates are usually all the same.
• For email or electronic documents, dates are nearly always recorded automatically and it is not required to have a "date" field alongside a signature inside a document.
• For manually signed ("pen and ink") documents, a date field is required, and internal processes should take care to note the date received if different.