Add SOW template to contract template

[fourthletter]

Additional context

#8

Description

Compliance needs to provide contractors and auditors with a contract and the SOW. The SOW contains part of the information in the PAF, and can be generated by the WebApp.

Summary

A bundle of information could be exported as pdf files for external stakeholders as a batch action.

Possible workflows

(Bestest) Option 0. Generated at the same time as the contract:

• Amended to the contract template information
• CA can create a contract with the SOW incorporated into the template (related to Compliance Attorney creates contract #8 )
• CA can export both contract and SOW templates into their document editor
• Contract and SOW will be stored in the system of record/relevant google drive folder

Option 1. The manual process could be something like:

• Finance user goes to Hypha and identifies the projects they need to export as a pdf output
• Finance user asks the Lead Dev for these projects to be exported
• Lead Dev does the export, which creates a number of pdf files
• Finance user downloads/receives pdf files from Lead Dev

Option 2. A more self-service process could be:

• Finance user goes to Hypha and identifies the projects they need to export as a pdf output
• Finance user goes to Hypha to highlight/select the projects
• Finance user then "exports" the information bundle (contract and scope of work) and downloads the pdf files

What is required?

0. Generated at the same time as the contract

• Validation that the contractor and auditors get the same SOW - needs OTF to answer
  -design: include SOW creation into the contract creation process
  -technical: to figure out how to generate the contract template at the same time as the SOW template

2. Minimum process

• design: the Scope of Work output file
• technical: @frjo to figure out how the pdfs get exported

3. Self-service process (images below)

• design: the process so the user can select the projects in Hypha and export the Scopes of Work
• design: the Scope of Work output file
• technical: @frjo and devteam figure out how the pdfs get exported

[Erioldoesdesign]

Design a pdf or 'output' that is easy to read

[frjo]

@fourthletter Is not all this information added in the PAF form? So all that is needed is a SOW view (page) plus PDF export.

[Erioldoesdesign]

@frjo Di's github is @fourthletter we're going to keep pinging this poor person that isn't part of our project

[Erioldoesdesign]

I made this same mistake don't worry!

[ei8fdb]

Is not all this information added in the PAF form? So all that is needed is a SOW view (page) plus PDF export.

@frjo Yes it is - based on what I've understood, the SOW is a subset of the PAF information. I am going to propose a rewrite of this issue description. I'm putting together a first design for the SOW pdf file at the moment. Then we can discuss how the SOW gets exported.

[ei8fdb]

I've put together this initial design for the Scope of Work PDF printout.

I'd like a review from @OpenTechFund/devs @fourthletter @Erioldoesdesign.

[Erioldoesdesign]

Couple of quick review comments:

1. In the issue description it says this is a 'legal document' does that mean there needs to be any legally identifying information on the pdf beyond the 'letter header' type of design you've added Bernard? e.g. An OTF staff members name, legal entity number/reg, legal physical address etc. I'm not super familiar with legally binding documents but if this is one, we should ensure it's air tight so to speak.

2. Similar to the first comment, if this is a legal document in .pdf format do we need to ensure that Hypha 'spits out' a non-editable .pdf? as in when you open it with acrobat it won't let you edit it? I've been on the receiving end of .pdf files like this but never 'set up' one. I think it's a 'read only' .pdf. https://community.adobe.com/t5/acrobat-sdk-discussions/how-to-create-a-read-only-pdf/m-p/3889018