Keep the batch
together.

Request contract

A nonempty need is required. Use action: "quote". Put email only in contact.email. Incomplete specifications can be recorded; missing_specifications identifies required fields still open. The schema requires film and area, not a full production specification.

Specification fields: film, area, future, use, scans, prints, deadline, flexibility, handoff, other, proposed_scope, open_questions, next_work, source_note, revision_history and supersedes_reference. All are strings. Current batch and future cadence must stay separate; preserve calendar-month wording and ranges. Keep other film outside the C-41 scope.

Deadline and handoff are natural-language strings, not confirmed dates. Include the date, time, timezone and timing basis where known. Do not manufacture an exact date from a vague preference. For any field declared format date, send YYYY-MM-DD: an unreadable date is kept as sent and also listed in missing_specifications; it is not treated as dated. The service refuses supplied values only for type, maxLength or minimum/maximum constraints. Enum, pattern and format are not rejection rules.

One complete example

{
  "action": "quote",
  "need": "Develop and scan 2 exposed 35mm C-41 rolls, with local handoff near Lititz. Recommend scans for web sharing and occasional 8 x 10 prints with cropping.",
  "specifications": {
    "film": "2 exposed 35mm C-41 rolls ready",
    "area": "Lititz 17543",
    "future": "Around 4 to 6 rolls per calendar month, usually 2 batches",
    "use": "Web sharing, occasional 8 x 10 prints, some cropping",
    "deadline": "About a week after drop-off",
    "flexibility": "No hard deadline",
    "prints": "No prints ordered"
  },
  "geography": {
    "text": "Lititz 17543",
    "country": "US"
  },
  "contact": {
    "email": "photographer@example.com"
  }
}

Continue the same engagement

Inspect the successful response and its returned reference, errors, missing_specifications and what_happens. Receipt is not provider acceptance, a quote or an agreed date. Latent Mile will check local handoff options and deadline feasibility, clarify file dimensions, format and colour/exposure correction, and email proposed price, service terms, handling and negative-return arrangements for your agreement. Carry explicit corrections in revision_history and link updates with supersedes_reference. No request-status retrieval route is provided by this page. A saved client copy is unverified information only.

Contact retention: Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time.