Proposal template

In Upwork's proposal flow the cover letter is written for each job. The article describing the form asks you to say what you can do for the client, ask questions about the project and suggest next steps such as a chat or call, and it offers AI tips once you start typing. It does not describe saving or reusing a letter. Templates therefore live outside Upwork, in a document, a text expander or a bidding tool.

What a template should fix. The order of the letter, the voice, the proof you lead with, the call to action and the length. These are decisions you make once and test.

What it must not fix. Anything the client wrote. The opening line, the problem restated, the relevant case and any answer to a screening question come from the job post. A template whose placeholders survive into the sent letter, or which reads the same for every job, is the letter clients flag: Upwork lets a client report a cover letter as spam and decline the proposal, and says spamming is against its Terms of Service.

Testing. A template is a hypothesis about what earns a reply. Running two or three side by side on comparable jobs, and reading reply rate per template, is the only way to know which works; Upwork reports no figure by template.

How Upsight uses it. Cover letter templates are records in the knowledge base. The writer follows a template's structure and voice, must replace every placeholder from the job and the knowledge profile, and applies the workspace's house instructions on top. A campaign can rotate several templates, drawing one at random per proposal so each gets a fair share of jobs.