Deliverables are how you hand finished work to a client inside ReqMe, and how they accept it. A deliverable is a file: you upload it against the request, the client reviews it, and they either approve it or ask for changes.

Uploading work #

Open the request and use Upload Deliverables. Pick the files you want to hand over — you can add several at once.

Uploading does not notify anyone. The files sit against the request until you press Submit Deliverable, which is what puts them in front of the client. Submitting needs a signed contract on the deal — until the contract is signed, the option is not available. That gap is deliberate: it lets you upload three files over an afternoon and hand them over as one piece of work.

Deliverables have no title, description or due date. They are the files themselves. If the work needs explaining, say it in Messages on the same request, where the client will read it alongside the files.

Any file type is accepted, up to 100 MB per file. Uploads count against your plan’s document storage. See Plan and billing.

What the client does #

Your client is notified when you submit, and opens the request to download the files. They then have two choices:

• Approve — they accept the work.
• Request changes — they must give a reason, which is recorded against the deliverable.

Keeping the reason on the deliverable rather than in an email means that six months later you can still see what was asked for and what you sent back.

When changes are requested, upload the corrected files and submit again. There is no limit on rounds.

Closing the deal #

Set the request’s status to Completed from the status control on the request.

ReqMe will only allow it when both are true:

• The client has approved at least one deliverable.
• Nothing is still sitting with them awaiting review.

In other words, your own submission is not enough — the client has to have accepted something. That is the point: completion means they agreed, not that you finished.

Payment is not checked. You can complete a request with an invoice still unpaid, and ReqMe will not stop you. Chase the invoice separately — see When a client goes quiet.

Closing deletes nothing. Documents, signatures and the whole history stay on the request. Completed requests also stay in your requests list rather than moving to an archive — there is no separate archive today.

Close deals anyway. It is the step people skip, and skipping it is why a request list stops being trustworthy: after a few months of finished-but-open deals, nobody believes the numbers.

If the deal ends without finishing #

Set it to Cancelled. A project that died is not a project in progress, and pretending otherwise costs you an accurate view of your own pipeline.

Frequently asked questions #

Can I break a project into several tracked deliverables? #

Not as separate named items with their own dates — deliverables are files, not tasks. What you can do is submit in stages: hand over the first phase, let the client approve it, then submit the next.

Can the client comment on one specific file? #

They give a reason when requesting changes, which attaches to that deliverable. General discussion belongs in Messages, which is per request rather than per file.

What if the client never responds? #

The request stays where it is, and you cannot complete it until they approve something. Nudge them in Messages — they are emailed when you write.

Can I remove a file after submitting it? #

Submit a corrected version rather than trying to erase the old one. The history of what was sent is part of the record of the deal.

After completion #

A closed deal is the best moment to ask for a review or raise the next piece of work — the client has just accepted something and is happy with you. It is a better moment than any follow-up you send three weeks later.

Need help? #

If this page did not answer your question, send it to us. Tell us what you were trying to do and what happened instead — that is usually enough for us to spot the problem straight away.

Prefer email? hi@reqme.co