Category: Requests

  • Choosing the right place for a request

    The intake form is the starting point for new work. Give the review team a short subject, the outcome you need, and the deadline that matters. A receipt confirms that the request arrived; the queue owner records the next step after review.

    Use the service desk when an existing request is blocked. Include its receipt reference so the team can find the original context. Project milestones belong in Studio, while document approvals belong in Records. Keeping these conversations with the relevant record makes the eventual handoff easier to follow.

  • Reading an intake receipt

    The intake endpoint returns a reference when a submission has been accepted into the queue. This is useful when someone needs to check on a request or send a corrected attachment. It is not an approval or a delivery commitment.

    Keep the original reference when replying to a request for more information. A second submission is appropriate for a different piece of work, but it creates avoidable review work when it is merely a retry of an accepted submission.

Fieldwork Notes · Requests, records and delivery

Service directory · RSS · Editor sign in