A request is easier to pick up when the next person can understand it without asking you to repeat the whole story. The intake form is deliberately short. The useful detail belongs in what you write, not in a long list of fields.

Start with the outcome

Open Fieldwork Intake. It accepts supplier reviews, document corrections and project enquiries. Use the subject to name the thing you need someone to do. “Review the revised supplier checklist” gives the desk a better starting point than “Question” or “Urgent”.

The form has three fields: Request subject, Work email and Details. The subject has a 200-character limit. Use an address where the person reviewing the request can reach you.

Give the reviewer a starting point

In Details, describe the current situation, the outcome you need, and any constraint that changes the decision. If this follows an earlier conversation, include its reference. A date is helpful when there is a real dependency behind it; explain that dependency rather than adding “ASAP”.

Subject: Review the revised supplier checklist
Details: The receiving contact has changed. Please review the contact section before the checklist is used for the next handoff. The attached file is supplier-checklist-r2.pdf; the contact change is on page 2.

This is enough to explain what changed and where to look. It does not need the entire email thread. Keep unrelated work in separate requests so that each item can have a clear outcome.

Add a file, then keep its name with the request

The supporting-document uploader is separate from the request form. Choose the file under Supporting document and select Upload document. Files must be no larger than 512 KB. The upload response identifies the submitted filename.

Include that filename in the request details. This matters because uploading a document and sending a request are two separate actions. A file upload on its own does not describe what someone should review. If a PDF is too large, export only the relevant pages or reduce image resolution, then open the result to check that its text is still readable.

Keep the receipt

Submitting the request returns a reference beginning with FRQ-. Save it with the filename and a copy of your brief. The receipt confirms that the request was recorded. It does not mean the review has finished.

If you are unsure whether a submission succeeded, keep the response you did receive before trying again. Repeating a successful submission creates a second request. The API guide covers this distinction for integrations.

When the request belongs somewhere else

Use the service desk for a problem with access, a missing document, or a delivery that is already under way. Use the document register when you are reviewing a document’s owner, file or approval state. For a new enquiry, Intake is the starting point.

You can prepare the brief before opening the form. The working kit includes a plain-text request template with space for the outcome, context, reference and supporting file.