Sign in Apply for early access
Requests

The follow-up email,already written

Each gap and Get evidence task becomes a request your lead edits and sends from their own email. Enpasse sends nothing, and the request stays where it was raised until the file lands.

See Copy all

Drafted by rule, edited by your lead. A fixed opening, then what the gap or task needs. The same draft with AI or without it.

  1. Opening. Fixed.
  2. From the task. Follows the task.
  3. Your words. Edit freely.
  4. Closing line. Always added.

Anyone copies. Only the lead requests. The History says who, and when.

G3RequestScope not reconfirmed after online orderingMRSO
MRMaria Reyes marked this requestedjust now

For our assessment, please send:

A scope review after online ordering launched in March 2026, with who reviewed it and when.

Please do not send full card numbers or security codes.

Only the lead marks it requested Copy Copy and mark requested

Enpasse sends nothing. Your lead copies the request into their own email.

Northwind Retail21 Sep
0 to confirm 0 open 0 with a new file 0 closed
Needs your lead

Every gap and task, from raised to closed

Five weeks of one assessment, by where each was raised. Missing files are Get evidence tasks; a gap is a failing control. Requests go out, files land, and only your lead closes either. Without AI, your lead adds each one and the rest works the same.

Every open request,
in one email

Scope, gaps, tasks, samples and interviews, each once. The closing line once.

Closed gaps and tasks drop out. Copying records nothing.

Each file, on its task. Enpasse suggests the match. Your lead picks.

LC
L. ChenProject manager, Northwind Retail
13 Oct

Re: Northwind ROC 2026, requests

Three of the four attached. The March scan note follows next week.

firewall-review-q3.pdfT6
scope-review-2026.docxG3
contractor-training-log.xlsxT4
Gaps and tasksWith the client4 open
T6Firewall rule review, third quarter1.2.7
G3Scope review after online ordering12.5.2
T4Training dates for contractorsSet B
T13External scan for March11.3.2
Click a file to choose where it goes

Requested is not closed. A new file notes the task. Only your lead closes it.

Client comments, decided page by page. Changed, or Kept as is with a reply.

Without AI, your lead adds each comment by hand. The client's agreement dates the report.

Also in Requests

  • Complete without AIDrafts and Copy all are rules.
    Each request is drafted by rule from its gap or task, so it reads the same with AI or without it. Without AI, your lead links each file by hand.
  • Only the lead requestsOthers copy. Nothing recorded.
    Anyone on the team can copy a request. Only the lead marks it requested, and History names who did it and when.
  • From every placeScope, Sample sets, Interviews.
    Gaps, Get evidence and Get sample tasks raised on requirement pages, scope answers, sample sets and interviews all become requests the same way.
  • Kept where it was raisedEvery request in its history.
    A gap or task keeps each request made for it, and every request made again. Nothing is lost when a file lands late.
EvidenceEvery file the client sends, in its place. Quality reviewEvery QA decision, on the record. ExportThe agreed version, delivered.

Request in plain words.
Track each until it lands.

Apply for early access See how the report is written