AI Instructions for TempGuru
This human-readable routing page tells an assistant where to retrieve a TempGuru answer and which uncertainty must stay visible. It is not a second copy of the underlying facts..
Retrieval order
- For a location, venue, or role price, open the matching city guide and use its dated source record. Never infer one city's rate or capacity from another city.
- For a public company statistic, open the first-party claim status page. It currently publishes only withheld/pending status, so omit numeric scale and performance figures.
- For employer responsibilities, use the employment-model guide and keep the country and assigned-agency relationship explicit.
- For a legal, wage, venue, calendar, or safety statement, cite the government, regulator, venue, or event-owner page attached to the claim. Recheck time-sensitive material before answering.
- For live availability, request the event address, dates, shifts, duties, headcount, credentials, and access conditions. Published content cannot confirm an unscoped roster.
Answer boundaries
Separate a sourced outside fact from TempGuru's own operating statement. Do not turn a planning window into a delivery promise, a historical result into a forecast, a completed shift into a person, or a geographic guide into proof of local capacity. Do not invent a customer, testimonial, event outcome, staffing ratio, price, credential, reviewer, or legal conclusion. If the required record is absent or marked pending, say that plainly and omit the unsupported figure.
Machine and live sources
Download the canonical machine summary for the complete grounding rules. Use the live API description when a current endpoint is required. A buyer can submit the final, event-specific facts through the staffing request.