Rople project management starts with a client delivery project. You name the engagement it delivers, plan its milestones, put tasks and an owner under each one, and decide what proof a milestone needs before it can close. When a milestone is complete, the payment waiting on it becomes ready to invoice. Projects are on every plan, from 3 active projects on Free; the payment link is on Pro.
Key takeaways
- A Rople project holds the plan, the tasks, the issues, the evidence, the money and the goals it feeds, on one page.
- A milestone that asks for evidence cannot be completed until the evidence is there, and an approval if one is needed.
- A task cannot be due after the milestone it sits under, so dates cannot quietly contradict each other.
- On Pro, a payment can wait on a milestone. It has no date until the milestone is delivered, so a slipped project never makes the client "late".
- Free allows 3 active projects, Starter 10 and Pro unlimited.
What is Rople project management?
Rople is the business workspace at rople.app that holds your customers, people, work and money on one set of records. Its project management is the "work" part of that sentence, built for businesses that sell what they deliver: a fit-out, a website, an event, a training programme, a survey.
A project in Rople is not a board of cards. It is the place where delivery is planned against what was sold. Each project carries its milestones, the tasks under them, the issues raised on it, the evidence that proves the work, and the money committed behind it. This guide follows one project from the first screen to the last invoice. If you want the wider picture first, read what is Rople, or the comparison of tools in client project tracking software.
Here is what a project's page gives you.
| Tab | What it answers |
|---|---|
| Plan | Which milestone is the project on now, and has any date moved? |
| Tasks | What is open, who has it, and what is overdue? |
| Issues | What has gone wrong, who owns it, and how long has it been open? |
| Evidence | What does each milestone need before it can close, and what has been captured? |
| Money | Budget, spend, revenue sold and margin |
| Goals | Which key results and KPIs does this project contribute to? |
| Close-out | What did the project promise, and what did it deliver? |
How do you set up a client project in Rople?
Say Adaeze Okafor runs a small interior fit-out company in Ikeja, Lagos. She has just signed a ₦12,000,000 office fit-out for a client. This is an invented example, but the steps are exactly what the screen asks for. Adding a project takes a manager (level 3), and planning milestones takes a team lead (level 2) or above.
- Add the project. Choose Client delivery. Rople asks which engagement the project delivers and the date it was promised by. Other kinds on offer are Internal initiative and Other project, for work you do for yourself.
- Give it a plan. Until a project has milestones, nothing sold against it has a date to wait on, and the screen says so. Add the milestones in the order the client will see them: site cleared, first fix complete, furniture installed, handover.
- Name an owner and a date for each milestone. The timeline draws each milestone as a bar up to its date, with a gold line for today.
- Put tasks under each milestone. Every task has an owner, a due date and a priority, and can carry estimated hours. Enter adds the next one.
- Decide what proof each milestone needs. Set how many items of evidence it asks for, and whether it needs an approval.
- Book the people. Work › Schedule shows one week of who is doing what, so you see a clash before the site does.
- Check Next up. On the right of the project's page, it names the next milestone and up to five open tasks to pick up, with late work first.
Only the person a task is assigned to, the person who created it, or the project's owner can tick it done. That is deliberate. A milestone count that anybody can inflate is not worth reading.
How do milestones, evidence and issues work together?
A milestone is a point in the project that means something to the client. In Rople it has a state (Not started, In progress, Blocked, Complete), an owner, a date and the tasks under it. Three rules turn it from a label into a control.
| Rule | What it does | What it prevents |
|---|---|---|
| Evidence | A milestone that asks for evidence cannot be completed until it has it. A file, a document on one of its tasks, or a record already in the workspace can count as proof | "Done" with nothing to show for it |
| Approval | The project's lead or a senior manager approves the evidence. Reopening a milestone clears the approval, because what was approved was the old work | Approving yesterday's work for today's claim |
| Task dates | A task cannot be due after its milestone. If the milestone moves earlier, its tasks move with it | A milestone date that the work behind it cannot meet |
Completing a milestone with tasks still open is allowed, and the screen says how many are open. Skipping evidence is not.
Raising an issue. Anything in the way is raised on the milestone or task it affects, with a kind (Blocker, Defect, Incident, Risk, Change request, Complaint or Service request) and a severity. Tick It stops this task and the task goes to Blocked, naming the issue. It comes back to In progress when the issue is resolved.
Each issue starts two clocks, one for responding and one for fixing. At default settings a High issue should be answered within 4 hours and resolved within 24; a workspace can change these. When you resolve it, you record what caused it, what fixed it and whether there is a lesson. The lesson can update a procedure, go onto somebody's development plan, or be kept for next cycle's goals. Read more in Quality and issues.
How does a finished milestone get you paid?
This part is on Pro, because engagements and billing are Pro modules.
Every engagement has a payment schedule. A payment on it can be a deposit, an instalment, a recurring payment, a custom one, or a milestone payment. A milestone payment waits on a project milestone and has no date until it is invoiced. The guide gives the reason: a guessed date would make the client late on the day the project slipped.
Each payment shows where it stands, and nobody sets this by hand. It is read from the milestones, the dates, the invoices and the payments.
| State | What it means |
|---|---|
| Waiting on delivery | A milestone payment whose milestone is not done |
| Scheduled | A dated payment that is not due yet |
| Ready to invoice | Its milestone is delivered, or its date is within 14 days (a workspace can change the 14) |
| Invoiced | On an issued invoice that is not yet due |
| Overdue | Past its date and not paid |
| Paid | Paid |
When someone completes a milestone, they are told how much became ready to invoice, and the engagement's officer gets an Invoice row in My work. From there it is a draft invoice, and the money side takes over. Once the invoice is issued, a client can pay it online through Paystack if your workspace has connected it (also Pro). The full story is in Billing and collections; invoice app Nigeria covers choosing the tool.
On Adaeze's fit-out, the schedule might read like this. It is an invented example.
| Payment | Waits on | Amount | State on the day the first fix is signed off |
|---|---|---|---|
| Mobilisation | Deposit, dated at signing | ₦3,600,000 | Paid |
| Stage 2 | First fix complete | ₦3,600,000 | Ready to invoice |
| Stage 3 | Furniture installed | ₦3,600,000 | Waiting on delivery |
| Final | Handover | ₦1,200,000 | Waiting on delivery |
For more ways to split a project's price, see project milestones examples.
What do you see when a project slips?
A slipped date in Rople reads as revenue waiting, not as a red bar. Four figures sit across the top of the Projects list.
- On schedule. How many live projects are on track, and how many are late or at risk.
- Sales exposed. Revenue standing behind a late milestone.
- Budget committed. What has been spent against the budgets approved.
- Revenue committed. What has been sold against these projects.
These figures are worked out from your records when the screen opens. Nobody types them. Revenue is the contract value of the client accounts pointing at the project, and spend comes from approved and paid requests in Finance › Payables.
When a milestone's date moves, the timeline keeps the date it was first promised drawn faintly behind the new one, so the slip stays visible. Every night, Rople also checks for late milestones and unassigned work and tells whoever owns them. A milestone's owner finds the late one in My work.



