Consulting
Consulting: project/timesheet, contract, customer.
Challenges
- Without man-day records the true project cost is unknown.
- Retainer and project-based work get mixed in the same report.
- The deliverable list stays in the contract, so scope creep cannot be measured.
- Consultant utilisation is not tracked, so idle capacity stays invisible.
Workflows
From contract to delivery
- The project is opened with scope, deliverables and billing model.
- Consultant working days are posted to the project.
- Deliverables close as they are approved.
Billing and utilisation
- Retainers are billed monthly and project work by milestone.
- An out-of-scope request goes for approval as an additional quote.
- Consultant utilisation is reported from the calendar.
Documents
- Consulting contract
- Deliverable list
- Man-day timesheet
- Milestone invoice
Reports
- Project profitability
- Consultant utilisation
- Scope creep
- Billing model breakdown
Metrics
- Revenue per man-day
- Consultant utilisation rate
- Project profit margin
- Out-of-scope work rate
Compliance
- Professional service receipt or invoice
- Confidentiality agreement records
- Customer personal data retention
Glossary
- Person-day
- Work unit posted to the project
- Retainer
- Contract model with a fixed monthly amount
- Deliverable
- Project output subject to approval
- Milestone
- Project step that triggers an invoice
Frequently Asked Questions
Can I derive project cost from man-days?
Yes — working days are posted to the project and turn into cost.
Can I separate retainer and project work?
Yes — the billing model is chosen in the contract and reports arrive with that split.
Can I measure scope creep?
Yes — out-of-scope requests are recorded as additional quotes and their share is reported.
Can I see consultant utilisation?
Yes — assigned days on the calendar are compared with capacity.
Can I bill by milestone?
Yes — once a deliverable is approved, the related invoice is triggered.
