Manage employee files, departments, attendance and leave records. The steps for joining and leaving follow the way your company already does things.
You deal with AppsCraft. A development company, team or freelancer from our platform builds the system.
Once someone joins, their department, role, attendance and leave details keep changing. If different people keep their own records, HR or admin staff end up checking several places to find out what’s current.
We review the employee information you need to keep and your current procedures for joining, transfers, leave and departure. We then arrange the development work.
How detailed each part gets depends on how you keep records now. Once the features are agreed, we bring in a developer or team.
Basic details, department and role for each employee. What staff and managers can see is set separately.
Attendance records, leave requests and look-ups, set up to follow your current rules.
A checklist showing each step, who’s responsible and whether it’s done.
These are common examples. The actual features are agreed project by project.
Prepare your briefEvery company does this a little differently. This is the usual order.
There are usually three kinds of user. Your company decides what each of them can see and change.
Keep staff records up to date and handle day-to-day HR paperwork.
See the staff records that fall under their responsibilities, and approve leave and other requests.
See the information the company makes available to them, and apply for leave.
Before development starts, we settle these four points one by one.
List the fields you need to keep and the HR steps you deal with regularly.
Staff and managers see different things, based on their responsibilities.
For example, whether a change of position needs approval before the record is updated.
We look at how your records are kept now and in what format, then decide whether to move them into the new system.
An HR system holds staff data, so access rights and scope are settled before work starts. A development company or freelancer from our platform builds it, and we handle the communication in between.
We look at the spreadsheets you use and how leave and new joiners are handled, and talk about budget and timing. Anything still undecided goes on a separate list to confirm later.
Based on the scope and skills needed, we find a development company or freelancer on the platform, and agree the approach, timing and deliverables before anything starts.
The partner develops the system. Send your questions and requested changes to AppsCraft; we discuss them with the developers and track progress. If requirements change, we explain the impact on scope, cost and timing first.
What you’ll receive is listed in the scope before work starts. At delivery we check each item on that list and note anything that still needs follow-up.
Explain the problem and share current spreadsheets and references. You confirm the scope, fees, timing and what’s delivered at each stage.
We write a brief the developers can work from and arrange who builds it. After that, questions, revisions and delivery go through us.
The development company or freelancer builds the system, answers technical questions and hands over the work when it’s done.
You don’t need answers to everything below. If you have HR spreadsheets or leave records, bring them along and we’ll use them to decide which features come first.
Yes. Tell us which part takes the most time and how you handle it now, and bring any reference screens. We’ll list what to do first and what still needs deciding.
Tell us where the records are kept and in what format. Whether to bring them across, and which ones, is written into the scope when it’s agreed.
Usually, yes. Who can see what, and which changes need approval, is agreed point by point at the requirements stage, based on how your company is run.
A development company, team or freelancer from the platform. You don’t have to deal with them directly: questions about records, access or changes come to AppsCraft and we pass them on.
AppsCraft. We agree the stages and the price of each before any development starts, and you pay for each stage before it begins. The quote includes our service fee.
Say you need a new leave type or an extra approval step. We ask the developers how it affects scope, timing and cost, and go ahead once you’ve agreed.
A spreadsheet, or just one problem you want fixed, is enough to start.