 |  |
QUICK-START GUIDE
Welcome to RPilot
Tips and example conversations to get the best from RPilot in RDrive
RPilot is the AI assistant built into RDrive. Ask it questions in plain language and it will search your project data, summarise what it finds, link you straight to the right records, and explain how any part of RDrive works.
This short guide covers a few tips to get the best results, followed by example conversations you can copy and adapt. Your feedback directly shapes how RPilot develops, so please tell us what works and what doesn’t.
Tips for getting great results
- Write the way you’d talk. No special commands or syntax. Type your question as you’d ask a colleague.
- Use the microphone. Speaking your question can be quicker than typing, especially on site.
- Be as specific as you can. The more detail you give, the more accurate the answer. Name the area or drawing (“Level 3”, “Block B”), the type of record (snag, RFI, permit, inspection), the status, the team or person, and the date range.
- Build on the answer. RPilot remembers the conversation, so follow up with “now just the overdue ones” or “group those by team” rather than starting again.
- Ask for the format you want. A count, a short list, a table, a summary paragraph, or an Excel / CSV file to download.
- Use the links. Results come with links that open the exact records or a pre-filtered view in RDrive, so you can check the detail yourself.
- Ask “how do I…?” RPilot can look up the RDrive help documentation and show you the relevant guide, step by step.
- You stay in control. RPilot asks for your approval before it creates or changes anything, and it only sees the projects and data your RDrive permissions allow.
- If it misses the mark, say so. Tell it what’s wrong (“that’s the wrong building”, “only include closed items”) and it will adjust.
VAGUE VS SPECIFIC
| VAGUE | SPECIFIC |
|---|---|
| Show me snags. | Show me open snags on Level 3 assigned to the electrical subcontractor, oldest first. |
| How are inspections going? | How many permit-to-work forms were submitted last week, and how many are still awaiting approval? |
| Anything overdue? | List issues past their due date in Block B, grouped by assigned team. |
| Give me a report. | Summarise this month’s safety incidents by type and site, as a table I can export to Excel. |
Example conversations
Each example shows an opening question and some natural follow-ups. Swap in your own areas, templates, teams and dates.
FINDING THINGS
Finding open items
| YOU ASK | “Show me all open snags on Level 3 of Tower A.” |
| THEN | “Which of those are assigned to the MEP contractor?” |
| THEN | “Sort them oldest first and give me a link to open them in the Finder.” |
Finding a specific record
| YOU ASK | “Find the RFI about the façade bracket clash that was raised last month.” |
| THEN | “What’s its current status and who is it with?” |
| THEN | “Show me the comments on it.” |
Finding by location or drawing
| YOU ASK | “What issues have been raised against the ground floor car park drawing?” |
| THEN | “Just the ones raised in the last two weeks.” |
| THEN | “How many of those are fire-stopping related?” |
SUMMARISING AND REPORTING
Weekly status summary
| YOU ASK | “Summarise this week’s activity: issues raised, issues closed and forms submitted, by team.” |
| THEN | “Which team has the most overdue items?” |
| THEN | “Write that up as a short paragraph I can paste into the weekly progress report.” |
Comparing across areas
| YOU ASK | “Compare open defects across Blocks A, B and C.” |
| THEN | “Break Block B down by trade.” |
| THEN | “Export that as an Excel file.” |
Summarising multiple records
| YOU ASK | “Summarise all safety incidents reported this month: what happened, where, and any common themes.” |
| THEN | “Are any locations coming up repeatedly?” |
| THEN | “How does that compare with last month?” |
Trends over time
| YOU ASK | “How long is it taking, on average, to close snags since handover started?” |
| THEN | “Show that week by week.” |
| THEN | “Which subcontractors are slowest to close them?” |
GETTING THINGS DONE
Reassigning issues in bulk
| YOU ASK | “Reassign all open snags on Level 2 from Apex Drylining to Northside Interiors.” |
| WHAT YOU GET | RPilot lists the issues it found and the steps for each: set the status to Not Me, update the responsible subcontractor, then move it back to Open. Nothing changes until you approve. |
| THEN | “Just the ones raised this month.” |
Linking inspections to your programme
| YOU ASK | “Find inspection checklists that aren’t linked to a task in our progress monitoring schedule.” |
| THEN | “Suggest the matching task for each one.” |
| WHAT YOU GET | RPilot proposes the links and makes them once you approve. |
Note Multi-step updates like these may need a skill set up for your project’s workflow. We’ll be happy to help you with that.
LEARNING HOW TO USE RDRIVE
Step-by-step help
| YOU ASK | “How do I reassign an issue to a different team?” |
| THEN | “Can I do that for several issues at once?” |
| THEN | “Show me the help page for that.” |
Understanding a feature
| YOU ASK | “What’s the difference between an issue and a form in RDrive?” |
| THEN | “How do I add a drawing and pin locations to it?” |
| THEN | “How do I filter the Finder to only show items assigned to my team?” |
HELP AND FEEDBACK
Tell us what works, and what doesn’t
If something isn’t working as expected, or you have an idea for what RPilot should do next, please let your RDrive contact know. Examples of questions that didn’t work well are especially useful, as they help us improve RPilot for everyone.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article