Ask your built-in RenX agent or connected external agent to prepare a task. Review the saved task before sharing or publishing it. Creating it does not publish a listing, create an accepted contract, or authorise payment.
For example:
Prepare a task for a three-page portfolio website: home, portfolio, and contact. My budget is GBP 600. I will supply the logo, images, and copy. Ask me about the delivery date, file handover, and acceptance criteria before saving it.
If a requirement is missing, discuss it with your agent rather than leaving the freelancer to guess.
Use a title that identifies the work, such as “Design a three-page portfolio website”, rather than “Help needed”. Choose the category that describes the actual service being purchased.
See supported service categories for descriptions and restricted categories. A category being available does not mean every seller is eligible to provide it.
Explain the purpose of the work, who it is for, and any constraints the freelancer must follow. State what is outside the scope as well as what is included.
For example: “Create a portfolio website using the supplied copy and images. Include home, portfolio, and contact pages. Logo design, copywriting, hosting, and ongoing maintenance are not included.”
Do not put confidential information in a description you intend to publish.
List the outputs you expect to receive. Include quantities, formats, and handover requirements so applicants can price the same work.
For a website, specify the pages, source files, and setup instructions. For research, specify the report format, topics, sources, and whether the underlying dataset must be supplied. Say whether deployment or installation is part of delivery.
Explain how the buyer will check each deliverable. Use observable checks rather than descriptions such as “professional” or “high quality” on their own.
For example: “All three agreed pages are present; layouts work at the agreed mobile and desktop widths; a contact-form test reaches the agreed inbox; source files and setup instructions are included.”
Agree any subjective requirements through examples or references before confirming the contract. Acceptance criteria describe the agreed result; they do not guarantee outcomes beyond the agreed scope.
State both the amount and currency, such as GBP 600, rather than an ambiguous currency symbol. Explain what the proposed service price includes, including any agreed revisions or third-party costs.
Applicants can propose a different price. Confirm the final amount in the contract and review applicable tax and the payment total before authorising payment. A task budget is not a payment authorisation.
See Tax & Payments for payment and tax details.
Specify a calendar date for delivery. If a particular time matters, state the time and time zone in the description as well.
Explain when you will provide required materials or access and any dependencies that affect delivery. For example, if you need delivery ten days after funding, agree the corresponding delivery date before confirming the contract.
If timing changes, update the task before agreement. Once a contract is in place, editing the task does not amend it; use the contract revision process.
Describe what you will supply, such as approved copy, a logo, reference material, or access to a test environment. Include when it will be available. Do not put passwords, API keys, or private account details in a public brief or attachment.
Attach files that help explain the work. Creating a task with attachments does not make those files public. App publishing keeps attachments private; ask your agent to publish selected files explicitly if applicants need them.
Once the task is published, its listing details and any files selected for publication are available to signed-in RenX users. Check both the description and selected files before publishing. Newly added attachments are not automatically made public when you edit the task.
Check the saved task with your agent. Ask it to correct missing or inaccurate details; you can also edit an existing task in the app. Updates create a new version, keeping the earlier version as a record.
You can then share the saved task with a provider or publish it to the marketplace. Both parties should review the same version before moving to a contract.
For the tool fields and commands, see the RenXTask reference.
Ask your agent to send the saved task to up to ten known provider contacts you choose. Recipients are told the task is shared with multiple providers, without seeing how many or who else was invited. The first eligible provider to accept is selected; the others are told they were not selected.
Invite these three providers to this task. Select the first eligible provider who accepts, then bring the terms back to me for review.
Selection is not a signed contract or permission to start work. Your agent then sends the formal task to the selected provider, followed by agreement, review and funding. Work starts only once RenX confirms funding.
Before anyone is selected, you can ask your agent to add more providers to the same round, up to ten in total. Existing invitations remain valid; only the new providers receive an invitation. You can still see everyone you invited and the round’s status.
If you need to change the task or choose someone else before a deal is created, ask your agent to cancel the invitation round and invite again. One cancellation closes all invitations in that round. RenX does not automatically replace the selected provider.
Creating an invitation round removes any public listing for that task. You must cancel the whole round before publishing it again. Cancelling the round does not republish it automatically.
See inviting providers through AgentMessaging for tool usage.