RMS
 
+
Technical Level
 
Functional Level
   
1.
Data Creation
   
2.
Data management & security.
   
3.
Search candidates for requirements.
   
4.
Streamlining the ‘Requirement Tracking Processing' as per ISO guidelines.
   
More Features...
  + RESUME Hunter

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 
 
4.

Streamlining the Requirement Tracking processing as per ISO guide lines.

   

4.1 Bookmark the candidates against the stages of the requirement.

4.2 Remembers requirement's current status and the History.

4.3 Communicate vitals requirement processing information to both candidates and clients.

4.4 Provide the vital statistics for the requirement tracking.

4.5 Supports decision making at all the stages of requirement.

4.6 Stores user's observations and comments for the stage of the requirement.

4.7 Head Hunting.

   
 

4.1 Bookmark the candidates against the stages of requirement.

  • RMS encapsulates the guidelines of ISO 9000 for ‘Requirement/ mandate management' (with respect to ‘recruitment consultancy' business).
  • RMS implicitly registers actions taken by the RMS users for a requirement under the following pre-defined heads as also suggested by ISO.
    • Draft of Advertisement.
    • Approved Draft.
    • Date and Publication.
    • Scrutiny.
    • Preliminary Interview.
    • Bio-Data Sent.
    • First Interview.
    • Second Interview.
    • Final Interview.
    • Selection Intimation.
    • Receipt of offer letter.
    • Issue of offer letter.
    • Joining Details.
    • Bill.
    • Review.
  • ‘Short listed' candidates out of search result for a requirement, can be bookmarked against the Scrutiny Stage just by a click (Implicitly). RMS would than remember these candidates till the requirement exists.
  • Similarly candidates can be bookmarked/ tagged against the stages for a requirement.
  • The tagged information is further used for maintaining the candidates' history. History is the collection of information like under how many requirements a candidate is being processed and at which stage.
 

4.2 Remembers requirement‘s current status and the history.

  • ‘Status View' / Stages form of RMS, recalls the ‘client requirements' with processed information and allow further processing.
  • By default in ‘ Status View' the last / current status of the selected requirement is highlighted.
  • ‘Status View' a part from remembering the current stage/ status of the requirements also retains all information about the previous stages & the respective bookmarked candidates.
  • E.g. say, 2 candidates are selected for ‘Final Interview' out of 5 short listed candidates in the ‘Preliminary Interview' stage. Now imagine a situation where the Client rejected the first candidate and the second didn't turned up.
  • In above case, since RMS remembers the stage of the requirement & the respective candidates, the user may not be required to go through the process of searching. Instead RMS user can JUST go to the previous stage (Preliminary Interview) and can consider rest of the 3 candidates.
  • Maintaining Requirement's history can also be utilized for Management Information System.
 

4.3 Communicate vitals requirement processing information to both candidates and clients.

  • RMS through ‘View Status form' e-mails vitals like interview details, salary, joining details etc. to both candidates and clients .
  • At every stage of requirement ‘View Status' / Stages form provides it's own communication module.
  • These mails are personalized in nature and by default carries all the vital information required for communication.
  • The pre-defined formats are editable and can be customized as per the need.
 

4.4 Provides the vital statistics for the requirement tracking.

  • ‘View Status' / Stages form holds following vital information desired for requirement tracking.
    • As per the RMS User login, the requirements are shown I.e. The user will see their own requirements only. This would limit traversing through the requirement for a user.
    • Sorting of the requirement as per the client name.
    • Displays the vitals like ‘date of requirement' and ‘Number of person required' for identification of a requirement.
    • Interview details for the requirements.
  • Even the processing of requirement has been made intelligent by controlling duplication of candidates for the stages of the requirement.
 

4.5 Supports ‘decision making' at all the stages of the requirement.

  • RMS supports in taking decision in choosing/ short listing candidates for a requirement across the package. The Decision Making is again available at all the stages in the following manners.
    • Bio-data.
    • Entered Information.
    • User's view on a candidate.
    • Evaluation of Soft Skills of a candidate by any/all the RMS users for a candidate.
    • History of the candidate with reference to RMS & RMS processing by any/ all RMS users on a candidate.
    • The F2 – for further keyword search.
 

4.6 Stores user's observations and comments for the stage of the requirement.

  • ‘View Status'/ Stages form, allows RMS user to record ‘notes' for a candidate being processed for the requirements.
  • The Result, Date and the Remark being stored at each stage of the requirement for a candidate are used in Candidates' History.
 

4.7 Head Hunting.

  • Head Hunting can be used for directly (without being searched) bookmarking any candidate from the RMS candidate database. While processing a requirement, at any stage candidates can be bookmarked using this.